Creating Interface through call transaction to send data to XI

Hi All,
I am the new person working in ABAP interface. actually pls help me how i have to create purchase order through transaction code ME21N through ABAP code and it will be transferred to XI. and it should be through user exit or IDOC. user has to put data in ME21N. and save then a puchase order will be create with Number. How the related table will be updated through Internal table also.
Edited by: sanjay behera on Jan 29, 2008 3:35 PM
Edited by: sanjay behera on Jan 29, 2008 3:39 PM

Hello Sanjay
When you look at the output of your purchase order (ME21N: header -> output) you should see several output options, e.g. printout and EDI (mode = 6).
You need to define a partner profile (transaction WE20) for your supplier. When you output your PO via EDI it automatically triggers the creation of an inbound order IDoc.
When you define your SAP-XI as receiver of these inbound order IDocs they will be transferred to SAP-XI.
Regards
Uwe

Similar Messages

Calling FI Validation Rules in BPM server through call transaction

I m trying to call FI validation rules through call transaction (for FBV0) in BPM server but in the messages table of call transaction it does not gives us the validation rules error messages while when i run manually the transaction in R/3 system i get the validation error messages. So please tell how i can get these validation error messages when called through BPM server.

Hi madhvi,
You are using jtab within the form.. i dont think you can use it directly inside ur FORM sub1 without declaring it or without passing it. and it will give you the syntax error.
and please send me the step by step code you have written in editor so that i can check it and can reply you with proper solution'
Thanks ,
Prasanna

Is it possible to create a virtual TCP port and send data to it?

Is it possible to create a virtual TCP port and send data to it?
My application is this: I am reading a constant stream of waveform data from a device via a LabVIEW VI set and I need to get that streaming data to a .NET application. I can poll a TCP port in .NET easily so is there a way I can create a virtual TCP port in LabVIEW and send the data there?

Have a look at the example called simple data server and simple data client and see what you can get from that. I'm not really familiar with TCP myself.
Joe.
"NOTHING IS EVER EASY"

How to rectify the errors through call transaction metod in bdc

how to rectify the errors through call transaction metod in bdc

Hi ,
View the highlited part of the below code.
REPORT ygfrivat1 NO STANDARD PAGE HEADING
                 LINE-SIZE 165
                 MESSAGE-ID yif_groc.
Program     YGFRIVAT1
Function    Report to Upload the VAT Adjustment File.
Author      ARENAPU
Date        11.05.2007
PMTS        AM12810157
Transport   G6DK937834
Description:
Modification log:
1. Changed by :
   Changed on :
   PMTS        :
   Transport   :
   Tag         :
   Description :
       T A B L E S   D E C L A R A T I O N S
TABLES: edidc, "Control record (IDoc)
        edids, "Status Record (IDoc)
        t001w.
Internal Tables Declaration.
Internal table to hold data from table EDIDS
DATA: BEGIN OF t_edids OCCURS 0,
       docnum LIKE edids-docnum,
       logdat LIKE edids-logdat,
       logtim LIKE edids-logtim,
       countr LIKE edids-countr,
       credat LIKE edids-credat,
       uname LIKE edids-uname,
      END OF t_edids,
Internal table to hold data from table EDIDC
      BEGIN OF t_edidc OCCURS 0,
       docnum LIKE edidc-docnum,
       rcvprt LIKE edidc-rcvprt,
       rcvprn LIKE edidc-rcvprn,
       credat LIKE edidc-credat,
      END OF t_edidc,
Internal table to hold data from upload file
      BEGIN OF t_tab OCCURS 0,
       cust(10),        "site/customer number
       date(10),        "transaction date
       currency(04),    "currency
       extnbr(15),      "external reference number
       pos-cont(05),    "POS controler
       pos-id(25),      "POS id
       cashier(10),     "cashier name
       qualif(04),      "qualifier of the article
       matnr(25),       "article number
       qty(10),         "quantity
       sale(16),        "sale value
       pos-tr(04),      "POS transfert type
       paymeth(04),     "payment method
       final(35),       "final price
       tarcur(04),      "target currency
       assign(35),      "assignment day
       error,
      END OF t_tab,
Internal table for Report display.
      BEGIN OF t_tab1 OCCURS 0,
       cust(10),                    "site/customer number
       date(10),                    "transaction date
       currency(04),                "currency
       extnbr(15),                  "external reference number
       pos-cont(05),                "POS controler
       pos-id(25),                  "POS id
       cashier(10),                 "cashier name
       qualif(04),                  "qualifier of the article
       matnr(25),                   "article number
       qty(16)   TYPE p DECIMALS 2, "quantity
       sale(16) TYPE p DECIMALS 2, "sale value
       pos-tr(04),                  "POS transfert type
       paymeth(04),                 "payment method
       final(16) TYPE p DECIMALS 2, "final price
       tarcur(04),                  "target currency
       assign(35),                  "assignment day
      END OF t_tab1,
      t_tab_temp LIKE t_tab OCCURS 0 WITH HEADER LINE,
Internal table to Validate Customer no.
      BEGIN OF t_check OCCURS 0,
       werks LIKE t001w-werks,
       vkorg LIKE t001w-vkorg,
       value(40),
      END OF t_check,
      t_check_temp LIKE t_check OCCURS 0 WITH HEADER LINE.
Internal table to hold data from table ZCS_PARAM.
DATA: BEGIN OF t_zcs_param OCCURS 0.
        INCLUDE STRUCTURE zcs_param.
DATA: vkorg LIKE t001w-vkorg,
      END OF t_zcs_param.
*Internal table to hold Messages.
DATA: BEGIN OF t_message OCCURS 0,
         msgnum TYPE msgnum,
         msgtyp TYPE msgtyp,
         msgtxt TYPE msgtext,
       END OF t_message.
*Work area for table t_message
DATA : w_message LIKE LINE OF t_message.
Internal table to hold BDC data
DATA: t_bdcdata LIKE bdcdata    OCCURS 0 WITH HEADER LINE,
Internal table to collect error messages
      messtab   LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
*Internal table to hold messages from call transaction
DATA: BEGIN OF t_text OCCURS 0,
       desc(150),
       msgtxt(100),
      END OF t_text.
       D A T A   D E C L A R A T I O N S
DATA: n TYPE i,
      gv_status(11) TYPE c, "Shows status, Production or Test
      gv_exit TYPE c, "Exit Flag
      gv_qty(16)   TYPE p DECIMALS 2, "Variable to sum Quantity
      gv_sale(16) TYPE p DECIMALS 2, "Variable to sum Amount
      gv_final(16) TYPE p DECIMALS 2. "Variable to sum Final Amount
DATA: w_text(100),
      gv_mode TYPE c,
      error TYPE c. "Flag to Indicate error.
CONSTANSTS DECLARATION
CONSTANTS : gc_fieldname LIKE dynpread-fieldname VALUE 'P_FNAME',
            gc_seq_no LIKE zcs_param-seq_no VALUE '00110',
            gc_object LIKE zcs_param-object VALUE 'YGFVAT',
            gc_paraname LIKE zcs_param-paraname VALUE 'VKORG',
            gc_back TYPE c VALUE 'N',
            gc_error TYPE c VALUE 'E',
            gc_all TYPE c VALUE 'A'.
           S E L E C T I O N   S C R E E N
SELECTION-SCREEN BEGIN OF BLOCK a1 WITH FRAME TITLE text-001.
PARAMETERS : p_fname LIKE rlgrap-filename OBLIGATORY.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(31) text-002 FOR FIELD p_test.
PARAMETERS : p_test AS CHECKBOX.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK a1.
SELECTION-SCREEN BEGIN OF BLOCK a2 WITH FRAME TITLE text-006.
PARAMETERS : rb_back RADIOBUTTON GROUP rb1 DEFAULT 'X',
             rb_error RADIOBUTTON GROUP rb1,
             rb_all RADIOBUTTON GROUP rb1.
SELECTION-SCREEN END OF BLOCK a2.
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
*Subroutine to provide F4 help for file name
PERFORM fr_get_filename.
       I N I T I A L I Z A T I O N
INITIALIZATION.
*Subroutine to check authorization.
PERFORM fr_authority_check.
        T O P - O F - P A G E
TOP-OF-PAGE.
*Subroutine to diplay header
PERFORM fr_display_header.
         S T A R T - O F - S E L E C T I O N
START-OF-SELECTION.
*Subroutine to upload data from presentation server.
PERFORM fr_upload_data.
*Subroutine to validate records from uploaded file.
PERFORM fr_validate_data.
*Subroutine to build report internal table.
PERFORM fr_build_rep.
         E N D - O F - S E L E C T I O N
END-OF-SELECTION.
*Subroutine to display report.
PERFORM fr_write_report.
        F O R M   S U B R O U T I N E S
*&      Form fr_get_filename
      text
FORM fr_get_filename.
DATA : lv_repid LIKE sy-repid,         " Report id
         lv_file LIKE ibipparms-path.   " File Path
lv_repid = sy-repid.
F4 help for file path.
CALL FUNCTION 'F4_FILENAME'
       EXPORTING
            program_name = lv_repid
            dynpro_number = syst-dynnr
            field_name    = gc_fieldname                    " p_fname1
       IMPORTING
            file_name     = lv_file.
IF NOT lv_file EQ space.
    p_fname = lv_file.
ELSE.
    MESSAGE e999 WITH 'Invalid Path'(005).
ENDIF.
ENDFORM.                    " fr_get_filename
*&      Form fr_upload_data
      text
FORM fr_upload_data.
DATA: lv_fname TYPE string.
CLEAR lv_fname.
lv_fname = p_fname.
Uploading file from PC or presentation server to internal table.
CALL FUNCTION 'GUI_UPLOAD'
       EXPORTING
            filename            = lv_fname
            filetype            = 'ASC'
            has_field_separator = 'X'
       TABLES
            data_tab            = t_tab
       EXCEPTIONS
            file_open_error     = 1.
IF sy-subrc <> 0.
    DESCRIBE TABLE t_message LINES n.
    w_message-msgnum = n + 1.
    w_message-msgtyp = 'E'.
    MOVE text-m01 TO w_message-msgtxt.
    APPEND w_message TO t_message.
Subroutine for writing log.
    PERFORM fr_write_log.
ENDIF.
ENDFORM.                    " fr_upload_data
*&      Form fr_validate_data
      text
FORM fr_validate_data.
DATA : lv_lines1 TYPE i,
         lv_lines2 TYPE i.
*Obtain Status depending on Check box selected.
IF p_test IS INITIAL.
    gv_status = 'PRODUCTION'.
ELSE.
    gv_status = 'TEST RUN'.
ENDIF.
*Batch Mode
CLEAR gv_mode.
IF rb_back EQ 'X'.          "No Display
    MOVE gc_back TO gv_mode.
ELSEIF rb_error EQ 'X'.     "Error Only
    MOVE gc_error TO gv_mode.
ELSEIF rb_all EQ 'X'.       "All Screens
    MOVE gc_all TO gv_mode.
ENDIF.
IF NOT t_tab[] IS INITIAL.
    SORT t_tab BY cust.
    REFRESH t_tab_temp.
    t_tab_temp[] = t_tab[].
    SORT t_tab_temp BY cust.
    DELETE ADJACENT DUPLICATES FROM t_tab_temp COMPARING cust.
    IF NOT t_tab_temp[] IS INITIAL.
      SELECT werks vkorg FROM t001w
                         INTO TABLE t_check
                         FOR ALL ENTRIES IN t_tab_temp
                         WHERE werks = t_tab_temp-cust+0(4).
      IF sy-subrc = 0.
        SORT t_check BY werks.
      ENDIF.
      LOOP AT t_check.
        IF t_check-vkorg <> ' '.
          MOVE t_check-vkorg TO t_check-value.
          MODIFY t_check TRANSPORTING value.
        ENDIF.
      ENDLOOP.
    ENDIF.
    FREE t_tab_temp.
ENDIF.
IF NOT t_check[] IS INITIAL.
    REFRESH t_check_temp.
    t_check_temp[] = t_check[].
    SORT t_check_temp BY value.
    DELETE ADJACENT DUPLICATES FROM t_check_temp COMPARING value.
    IF NOT t_check_temp[] IS INITIAL.
      SELECT * FROM zcs_param INTO TABLE t_zcs_param
               FOR ALL ENTRIES IN t_check_temp
               WHERE seq_no   EQ gc_seq_no
                 AND object   EQ gc_object
                 AND paraname EQ gc_paraname
                 AND value    EQ t_check_temp-value.
      IF sy-subrc = 0.
        SORT t_zcs_param BY value.
      ENDIF.
    ENDIF.
    FREE t_check_temp.
ENDIF.
IF NOT t_tab[] IS INITIAL.
    LOOP AT t_tab.
      READ TABLE t_check WITH KEY werks = t_tab-cust BINARY SEARCH.
      IF sy-subrc <> 0.
        MOVE 'X' TO t_tab-error.
        MODIFY t_tab TRANSPORTING error.
        DESCRIBE TABLE t_message LINES n.
        w_message-msgnum = n + 1.
        w_message-msgtyp = 'E'.
        CONCATENATE t_tab-cust text-030
        INTO w_message-msgtxt SEPARATED BY space.
        APPEND w_message TO t_message.
Subroutine for writing log.
        PERFORM fr_write_log.
        EXIT.
      ELSE.
        READ TABLE t_zcs_param WITH KEY value = t_check-vkorg
                                                     BINARY SEARCH.
        IF sy-subrc <> 0.
          MOVE 'X' TO t_tab-error.
          MODIFY t_tab TRANSPORTING error.
          DESCRIBE TABLE t_message LINES n.
          w_message-msgnum = n + 1.
          w_message-msgtyp = 'E'.
          CONCATENATE text-003 t_tab-cust text-004 t_check-vkorg
          INTO w_message-msgtxt SEPARATED BY space.
          APPEND w_message TO t_message.
Subroutine for writing log.
          PERFORM fr_write_log.
          EXIT.
        ELSE.
          PERFORM fr_format_tab.
        ENDIF.
      ENDIF.
    ENDLOOP.
ENDIF.
DESCRIBE TABLE t_tab LINES lv_lines1.
IF lv_lines1 <> 0.
    DELETE t_tab WHERE error EQ 'X'.
ENDIF.
DESCRIBE TABLE t_tab LINES lv_lines2.
IF lv_lines2 <> 0.
    IF lv_lines2 <> lv_lines1.
      EXIT.
    ELSE.
      IF p_test IS INITIAL.
        LOOP AT t_tab.
*Subroutine to build BDC table
          PERFORM fr_fill_bdctab.
*Subroutine to Post Data into SAP.
          PERFORM fr_data_posting.
        ENDLOOP.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    " fr_validate_data
*&      Form fr_write_log
      text
FORM fr_write_log.
CLEAR error.
error = 'X'.
WRITE:/1 'Msg No'(027), 10 'Type'(028), 20 'Text'(029).
ULINE:/1(120).
FORMAT RESET.
LOOP AT t_message.
    IF t_message-msgtyp = 'E'.
      FORMAT COLOR 6 INTENSIFIED .
    ELSEIF t_message-msgtyp = 'W'.
      FORMAT COLOR 3 INTENSIFIED .
    ELSEIF t_message-msgtyp = 'I'.
      FORMAT COLOR 5 INTENSIFIED .
    ENDIF.
    WRITE:/1 t_message-msgnum,
          10 t_message-msgtyp,
          20 t_message-msgtxt.
    FORMAT RESET.
ENDLOOP.
ULINE:/1(120).
ENDFORM.                    " fr_write_log
*&      Form fr_write_report
      text
FORM fr_write_report.
CLEAR gv_exit.
LOOP AT t_message.
    IF t_message-msgtyp = 'E'.
      gv_exit = 'X'.
      EXIT.
    ENDIF.
ENDLOOP.
IF NOT gv_exit IS INITIAL.
    EXIT.
ELSE.
    PERFORM fr_display_report.
    IF NOT t_text[] IS INITIAL.
Subroutine for Display Call Transaction messages.
      PERFORM fr_write_msg.
    ENDIF.
ENDIF.
ENDFORM.                    " fr_write_report
*&      Form fr_display_report
      text
FORM fr_display_report.
IF NOT t_tab1[] IS INITIAL.
    CLEAR: gv_qty, gv_sale, gv_final.
    LOOP AT t_tab1.
      WRITE:/1(10) t_tab1-cust,
            13(10) t_tab1-date,
            25(05) t_tab1-currency,
            32(14) t_tab1-extnbr,
            48(09) t_tab1-pos-cont,
            60(18) t_tab1-matnr,
            80(16) t_tab1-qty RIGHT-JUSTIFIED ,
            98(16) t_tab1-sale RIGHT-JUSTIFIED ,
           116(07) t_tab1-paymeth,
           125(16) t_tab1-final RIGHT-JUSTIFIED,
           143(06) t_tab1-tarcur,
           152(12) t_tab1-assign.
      gv_qty   = t_tab1-qty   + gv_qty.
      gv_sale = t_tab1-sale + gv_sale.
      gv_final = t_tab1-final + gv_final.
    ENDLOOP.
    FORMAT COLOR 3.
    ULINE: /(164).
    WRITE:/ 'TOTALS',
      80(16) gv_qty RIGHT-JUSTIFIED,
      98(16) gv_sale RIGHT-JUSTIFIED,
     125(16) gv_final RIGHT-JUSTIFIED,
     182 ''.
    ULINE: /(164).
    FORMAT RESET.
ENDIF.
ENDFORM.                    " fr_display_report
*&      Form FR_DISPLAY_HEADER
      text
FORM fr_display_header.
IF error IS INITIAL.
    FORMAT COLOR 1.
    WRITE:/ 'Date upload           :'(007),   25 sy-datum, 38 ''.
    WRITE:/ 'Production or Test Run:'(008),   25 gv_status, 38 ''.
    WRITE:/ 'Upload User Logon     :'(009),   25 sy-uname, 38 ''.
    ULINE: /(164).
    WRITE:/1(04) 'Site'(010),
          13(10) 'Date'(011),
          25(05) 'Curr.'(012),
          32(14) 'Receipt'(013),
          48(09) 'Cashier'(014),
          60(18) 'Article'(015),
          92     'Qty'(016),
          102    'Item Amount'(017),
          116(7) 'M.o.P.'(018),
          128    'Tender Amount'(019),
          143(6) 'T.Curr'(020),
         152(12) 'Assignment'(021).
    ULINE:/(164).
    FORMAT RESET.
ENDIF.
ENDFORM.                    " FR_DISPLAY_HEADER
*&      Form fr_newdynpro
      text
FORM fr_newdynpro USING program LIKE bdcdata-program
                        dynpro LIKE bdcdata-dynpro.
t_bdcdata-program = program .
t_bdcdata-dynpro = dynpro.
t_bdcdata-dynbegin = 'X'.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " fr_newdynpro
*&      Form fr_loadfield
      text
FORM fr_loadfield USING field LIKE bdcdata-fnam
                        value.
t_bdcdata-fnam = field.
t_bdcdata-fval = value.
APPEND t_bdcdata.
CLEAR t_bdcdata.
ENDFORM.                    " fr_loadfield
*&      Form fr_fill_bdctab
      text
FORM fr_fill_bdctab.
REFRESH t_bdcdata.
PERFORM fr_newdynpro USING 'SAPMWPUK' '100'.
PERFORM fr_loadfield USING 'G_FILIALE' t_tab-cust.
PERFORM fr_loadfield USING 'G_DATUM'   t_tab-date.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'BON'.
PERFORM fr_newdynpro USING 'SAPMWPUK' '500'.
PERFORM fr_loadfield USING 'WPSCB01-POSKREIS'   t_tab-pos-cont.
PERFORM fr_loadfield USING 'WPSCB01-KASSID'     t_tab-pos-id.
PERFORM fr_loadfield USING 'WPSCB01-BELEGWAERS' t_tab-currency.
PERFORM fr_loadfield USING 'WPSCB01-CSHNAME'    t_tab-cashier.
PERFORM fr_loadfield USING 'WPSCB01-BONNUMMER' t_tab-extnbr.
PERFORM fr_loadfield USING 'E1WPB02-QUALARTNR(01)' t_tab-qualif.
PERFORM fr_loadfield USING 'E1WPB02-ARTNR(01)'      t_tab-matnr.
PERFORM fr_loadfield USING 'E1WPB02-MENGE(01)'      t_tab-qty.
PERFORM fr_loadfield USING 'WPSCB03-KONDVALUE(01)' t_tab-sale.
PERFORM fr_loadfield USING 'E1WPB02-VORGANGART(01)' t_tab-pos-tr.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'ZAHL'.
PERFORM fr_newdynpro USING 'SAPMWPUK' '530'.
PERFORM fr_loadfield USING 'WPSCB06-ZAHLART' t_tab-paymeth.
PERFORM fr_loadfield USING 'WPSCB06-SUMME'    t_tab-final.
PERFORM fr_loadfield USING 'WPSCB06-WAEHRUNG' t_tab-tarcur.
PERFORM fr_loadfield USING 'WPSCB06-ZUONR'    t_tab-assign.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'SAVE'.
PERFORM fr_newdynpro USING 'SAPMWPUK' '530'.
PERFORM fr_loadfield USING 'WPSCB06-ZAHLART' t_tab-paymeth.
PERFORM fr_loadfield USING 'WPSCB06-SUMME'    t_tab-final.
PERFORM fr_loadfield USING 'WPSCB06-WAEHRUNG' t_tab-tarcur.
PERFORM fr_loadfield USING 'WPSCB06-ZUONR'    t_tab-assign.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'BACK'.
PERFORM fr_newdynpro USING 'SAPLSPO1' '0200'.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'YES'.
PERFORM fr_newdynpro USING 'SAPMWPUK' '100'.
PERFORM fr_loadfield USING 'G_FILIALE' t_tab-cust.
PERFORM fr_loadfield USING 'G_DATUM'   t_tab-date.
PERFORM fr_loadfield USING 'BDC_OKCODE' 'BACK'.
ENDFORM.                    " fr_fill_bdctab
*&      Form fr_data_posting
      text
FORM fr_data_posting.
IF NOT t_bdcdata[] IS INITIAL.
    REFRESH messtab.
    CALL TRANSACTION 'WPUK' USING t_bdcdata
                            MODE gv_mode
                            UPDATE 'S'
                            MESSAGES INTO messtab.
    IF sy-subrc = 0 .
      CLEAR w_text.
      LOOP AT messtab.
        CALL FUNCTION 'FORMAT_MESSAGE'
             EXPORTING
                  id        = messtab-msgid
                  lang      = sy-langu
                  no        = messtab-msgnr
                  v1        = messtab-msgv1
                  v2        = messtab-msgv2
                  v3        = messtab-msgv3
                  v4        = messtab-msgv4
             IMPORTING
                  msg       = w_text
             EXCEPTIONS
                  not_found = 1
                  OTHERS    = 2.
        MOVE w_text TO t_text-msgtxt.
        CONCATENATE 'Site:'(031)    t_tab-cust
                    'Article:'(024) t_tab-matnr
                    'Posted Sucessfully'(032)
          INTO t_text-desc SEPARATED BY space.
        APPEND t_text.
        CLEAR t_text.
      ENDLOOP.
    ELSE.
      CLEAR w_text.
      LOOP AT messtab.
        CALL FUNCTION 'FORMAT_MESSAGE'
             EXPORTING
                  id        = messtab-msgid
                  lang      = sy-langu
                  no        = messtab-msgnr
                  v1        = messtab-msgv1
                  v2        = messtab-msgv2
                  v3        = messtab-msgv3
                  v4        = messtab-msgv4
             IMPORTING
                  msg       = w_text
             EXCEPTIONS
                  not_found = 1
                  OTHERS    = 2.
        MOVE w_text TO t_text-msgtxt.
        IF messtab-msgnr EQ '213'.
          CONCATENATE 'Site:'(031)    t_tab-cust
                      'Article:'(024) t_tab-matnr
                      'Posted Sucessfully'(032)
           INTO t_text-desc SEPARATED BY space.
          APPEND t_text.
          CLEAR t_text.
          EXIT.        ELSE.
          CONCATENATE 'Site:'(031)    t_tab-cust
                      'Article:'(024) t_tab-matnr
                      'Not Posted'(033)
           INTO t_text-desc SEPARATED BY space.
          APPEND t_text.
          CLEAR t_text.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.                    " fr_data_posting
*&      Form fr_authority_check
      text
FORM fr_authority_check.
AUTHORITY-CHECK OBJECT 'Y_VATADJ'
           ID 'VKORG' FIELD t001w-vkorg
           ID 'TCD'   FIELD 'YGFVAT'.
IF sy-subrc NE 0.
    MESSAGE e999 WITH text-m02.
ENDIF.
ENDFORM.                    " fr_authority_check
*&      Form fr_write_msg
      text
FORM fr_write_msg.
SKIP.
ULINE:/(164).
WRITE:/
'Messages encountered while Calling Transaction WPUK'(025),
      90 'Message Text'(026).
ULINE:/1(164).
LOOP AT t_text.
    WRITE:/1 t_text-desc,
          90 t_text-msgtxt,
          164 ''.
ENDLOOP.
ULINE:/1(164).
ENDFORM.                    " fr_write_msg
*&      Form FR_BUILD_REP
      text
FORM fr_build_rep.
IF error IS INITIAL.
    IF NOT t_tab[] IS INITIAL.
      LOOP AT t_tab.
        MOVE:
          t_tab-cust     TO t_tab1-cust,        "site/customer number
          t_tab-date     TO t_tab1-date,        "transaction date
          t_tab-currency TO t_tab1-currency,    "currency
        t_tab-extnbr   TO t_tab1-extnbr,      "external reference number
          t_tab-pos-cont TO t_tab1-pos-cont,    "POS controler
          t_tab-pos-id   TO t_tab1-pos-id,      "POS id
          t_tab-cashier TO t_tab1-cashier,     "cashier name
         t_tab-qualif   TO t_tab1-qualif,      "qualifier of the article
          t_tab-matnr    TO t_tab1-matnr,       "article number
          t_tab-pos-tr   TO t_tab1-pos-tr,      "POS transfert type
          t_tab-paymeth TO t_tab1-paymeth,     "payment method
          t_tab-tarcur   TO t_tab1-tarcur,      "target currency
          t_tab-assign   TO t_tab1-assign.
        REPLACE ',' WITH '.' INTO t_tab-qty.
        CONDENSE t_tab-qty NO-GAPS.
        MOVE t_tab-qty TO t_tab1-qty.
        REPLACE ',' WITH '.' INTO t_tab-sale.
        CONDENSE t_tab-sale NO-GAPS.
        MOVE t_tab-sale TO t_tab1-sale.
        REPLACE ',' WITH '.' INTO t_tab-final.
        CONDENSE t_tab-final NO-GAPS.
        MOVE t_tab-final TO t_tab1-final.
        APPEND t_tab1.
        CLEAR t_tab1.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.                    " FR_BUILD_REP
*&      Form fr_format_tab
      text
FORM fr_format_tab.
DATA : lv_qty TYPE string.
IF NOT t_tab-qty IS INITIAL.
    IF t_tab-qty+0(1) EQ '-'.
      CLEAR lv_qty.
      MOVE t_tab-qty TO lv_qty.
      CLEAR t_tab-qty.
      SHIFT lv_qty LEFT CIRCULAR.
      CONDENSE lv_qty NO-GAPS.
      MOVE lv_qty TO t_tab-qty.
      MODIFY t_tab TRANSPORTING qty.
    ENDIF.
ENDIF.
ENDFORM.                    " fr_format_tab

How to pass the value to the screen through call transaction

hi
i have got an requirement for which i have to call MIGO tcode through call transaction command. But here one list box GODYNPRO-ACTION (screen field) contains list of values . my requirement is when i will call the tcode MIGO it should take defaultly DISPLAY option from list of values. I have searched for parameter id but i cannot get for that list box. please help me to solve this issue.
points will be surely assigned to helpful answers.
regards
shiba dutta

just try this its working...
tables: godynpro.
GODYNPRO-ACTION = 'Display'.
call transaction 'MIGO'.
Message was edited by:
Chandrasekhar Jagarlamudi

Commit work statement creating problem in CALL TRANSACTION

Hi Friends,
we are facing a problem where we need to call a standard program from a Zprogram.
we have tried the following ways.
1. Using SUBMIT statement , we are sending the parameters to the standard program, but when the standard program gives a
    dump our program cannot process further records. we are calling the submit statment in a loop. As because the standard
    program is giving dump our program is not able to process the next record in the loop and this should not be the case.
    To avoid this we have used the second method.
2. we used a CALL transaction, we have created a Tcode for the standard program and called this transaction in the calling
    program. We are passing the parameters for the standard program via BDC table. this works fine even when the standard
    program gives a dump but when ever the control   comes across a Commit work statement the the control comes back to our
   calling program with out executing the rest of the   statments after the commit.
now our concern is even though there is an commit work statement , statements after the commit work should also get executed in call transaction. Is thee any way?
Regards,
Sravan

Hi All,
I got the solution
DATA: ctu_parameters TYPE ctu_params.
ctu_parameters-dismode = 'E'.
ctu_parameters-updmode = 'A'.
ctu_parameters-racommit = 'X'. "No abortion by COMMIT WORK
CALL TRANSACTION USING itab_bdcdata OPTIONS FROM ctu_parameters.
the above code will work even if there is an commit work . This might help some others.

Posting_interface_reverse_doc call transcation FB08. Is there also a posting interface for call transaction F.80

Hello,
With internal posting interface:
posting_interface_reverse_doc
Reverse posting can be made by call transaction FB08 (also batch input)
My quesition ist:
Do we have a posting interface where I can make reversal postings by call transaction F.80 mass reversal.
Thank you for you valueable help and answer.
all the best Erwin

Hi:
You yourself are telling issue faced , you are saying that you have checked in OBC4 and OB41 the business area is has been set as required entry. When this has been set as required entry the field status group of GL Account 14470000 then it is obvious thing that you will get the error Field Bus. Area is a required field for G/L account 2100 14470000 in VF02. Normally Business area is coped to billing document from material master data , you do not need to enter in manually in GL account line item. If you want avoid this error then set Business area as optional in relevant field status group of GL account and posting key used. This will surely resolved your issue.
Regards

How can I allow a sub-vi to run independent of the main program once it has been called while still sending data to the sub-vi

I have a main program where I call a sub-vi. In this sub-vi, there is a while loop that is used to wait for commands in the sub-vi. While the while loop is running, I cannot continue with normal operation of the main program. I would like get the sub-vi to run independently once it has been called, but not hold up the main program. As well, I need to still be able to send data to the sub-vi

One way is to use VI Server, which has been mentioned by others. This will allow you to start another VI (by name) and run it entirely independently of the calling VI. This is a good way to start various independent VIs from a main menu, for example. None of the VIs thus called need have any connection to the others.
Another way it to have the SubVI in a separate while loop on the calling VI's BD. Then, use a local var to start this sub VI from the main loop. The calling VI sets a local START bit and continues running. The sub VI's while loop watches for this START bit to go true, and then runs the Sub VI. The advantage here is that one can more easily pass arguments to the SubVI when it is started, using local vars, which are preferable to globals. Once the Su
bVI is running, however, you must use a global Stop Bit, set in the calling VI, to stop it when the calling VI exits, or the calling VI will hang up, waiting for the Sub VI to close and exit its while loop.
If you need an example of this, email me. ([email protected]). I can also recommend Gary W. Johnson's excellent book which discusses this. ("LabVIEW Graphical Programming", 2nd Ed).
Note: Where possible, I try to call a subvi from within the main VI, wait till it is done, then continue. It avoids the use of locals & globals, and results in cleaner code, with fewer "race" conditions. However, the main VI stops until the subVI is done, hence one should make the subVI modal.

Layout changes when see preview in SP01 through Call transaction

Hi Gurus,
I have to show Spool preview from my program I am doing this by call transaction SP01 with spool no. and mode E.
But the preview which comes is very simple, It does not have graphics and other formatting.
If i check the spool directly from SP01 , its coming fine.
Please help me on this Issue.
Regrads,
Sowmen Das

I guess you mean CALL TRANSACTION 'SP01' USING lt_bdcdata MODE 'E' (so that to remain on the last screen of the BDC data).
Probably SP01 identifies that it is called using CALL TRANSACTION and reacts differently. One possibility is that it tests SY-BINPT which is 'X' when CALL TRANSACTION is used (opposed to space when SP01 is called directly). You may use CALL TRANSACTION ... OPTIONS FROM xx, where xx-nobinpt should be initialized to 'X' (don't forget to set xx-dismode to 'E' also), so that SY-BINPT won't change.
Note: why don't you use the print preview as we do usually? (TDPREVIEW output option)

Wrong template when I launch an ITS through call transaction

Hi to all,
I created an Internet service for an abap program and published the template:
everything works fine if I run it from SICF.
If I launch the transaction linked to the internet service (SE93) in a CALL TRANSACTION instruction
the browser does not show me the pubblished template.
How can I solve this issue? I want to define a module pool menu : clicking a button
I should to run a ITS transaction.
Thanks for your help

Hello Lorenzo,
Is the template in the node/folder with the same name as your service from SE93? Meaning, if the service you are calling is ztransaction then the template should be published to the ztransaction/theme/templatename location. If it is not then you will need to go to SICF and for the service name add ~sources in the GUI Configuration with the value of the location of the template.
Edgar

'Call Transaction' on same data repeated causes it to lock

Hi,
Has anyone come across a case where you use CALL TRANSACTION repeatedly on a tcode with the same input and sometimes you end up having a locked data?
I am calling CN22 repeated with the request to change the same network and I end up having locked data for no particular reason. Do I need to put a PAUSE between the call transaction?
Thanks,
Guan

Hi Guan,
yes it is possible. In fact if the transaction calls a FM in asyncronous mode (that locks an object), it may happend that when the statement CALL TRANSACTION ends, the async.FM has not release the lock yet.
you can ty to do the following (if you know the name of the locked object).
call transaction ...
* loop until the object is unlocked
do.
call function 'ENQUEUE_<object name>'
exporting
    mode = 'E'
    <object key>.
if sy-subrc = 0.
    exit.
endif.
enddo.
call transaction ...
Regards, Manuel

Changes to an order through Call Transaction not showing up in change log

I m having a problem such that if I update an order programmatically with Call Transaction u2018VA02u2019, the order does get updated updated but I donu2019t see the changes in the change log. I m only updating the order quantities. However if I update the same order quantities manually by going to TCode VA02. The changes do get shown in the change log from the Environment u2013> Changes menu. Can you please help.
Following is the simple recorded code.
PERFORM bdc_dynpro      USING 'SAPMV45A' '0102'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                              'VBAK-VBELN'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                              '/00'.
PERFORM bdc_field       USING 'VBAK-VBELN'
                              '10655'.
PERFORM bdc_dynpro      USING 'SAPMV45A' '4001'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                              '=POPO'.
PERFORM bdc_dynpro USING 'SAPMV45A' '0251'.
PERFORM bdc_field USING 'BDC_CURSOR' 'RV45A-POSNR'.
PERFORM bdc_field USING 'BDC_OKCODE' '=POSI'.
PERFORM bdc_field USING 'RV45A-POSNR' '10'.
     PERFORM bdc_field       USING 'BDC_CURSOR'
                                   v_rowid.
PERFORM bdc_dynpro      USING 'SAPMV45A' '4001'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                              '=SICH'.
PERFORM bdc_field USING 'BDC_CURSOR' 'RV45A-KWMENG(01)'.
PERFORM bdc_field       USING 'RV45A-KWMENG(01)'
                               '7'.
PERFORM bdc_dynpro      USING 'SAPLSPO2' '0101'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                              '=OPT1'.
CALL TRANSACTION 'VA02'
                 USING t_bdcdata
                 MODE   'A'
                 MESSAGES INTO t_messtab.
COMMIT WORK AND WAIT.
IF sy-subrc NE 0.
ENDIF.

Could not find answer

Date format for call transaction

Hi,
What is the best solution for passing a date field to a call transaction in the date format that the user has in his settings?.
Rgds

The best solution is to define a character field of length 10. Then WRITE the date to the BDC_DATE and then use this variable when passing to BDC.
data: bdc_date(10) type c.
write sy-datum to bdc_Date.
Regards,
Rich Heilman

Plz tell me BDC CALL TRANSACTION steps with simple example

hi,
plz tell me the steps
BDC CALL TRANSACTION steps with simple example

Hi,
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
? The first is when application data to be replaced is transferred at once, and only once.
? The second situation is to transfer data periodically from external systems to SAP and vice versa.
? There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called ?batch input? or ?batch data communication?.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a ?data transfer? program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
? To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
? To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
? The transaction code, if you do not already know it.
? Which fields require input i.e., mandatory.
? Which fields can you allow to default to standard values.
? The names, types, and lengths of the fields that are used by a transaction.
? Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
? Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System ? Status.)
? Step through the transaction, entering the data will be required for processing your batch input data.
? On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
? Display these by choosing System ? Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
? For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which you?ll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
? Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
? Create a BDCDATA structure
? Write the structure out to a session or process it with CALL TRANSACTION USING; and then
? Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
? Data that is entered into screen fields.
? Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
? PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
? DYNPRO: Screen Number. Set this field only in the first record for the screen.
? DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ? ? (blank) for all other records.)
? FNAM: Field Name. The FNAM field is not case-sensitive.
? FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
? User Name: User name
? Group: Name of the session
? Lock Date: The date on which you want to process the session.
? Keep: This parameter is passed as ?X? when you want to retain session after
processing it or ? ? to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
? Tcode: Transaction Name
? Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter ? 1 is transaction code.
Parameter ? 2 is name of BDCTAB table.
Parameter ? 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter ? 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter ? 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
Thanks &regards,
Sravani

File attachment not available on CALL TRANSACTION

Hello guys,
I am using Generic Object System (GOS) for file attachment in a custom transaction. If I access the transaction directly, it is working fine. But if I use CALL TRANSACTION 'ZTRAN', the file attachment in the application toolbar is not appearing. I debugged in both way, I don't find any difference. But finally through call transaction, GOS is not appearing. please throw some lights on this.Below is my code.
In transaction:
DATA: gcl_manager TYPE REF TO cl_gos_manager.
IF NOT zmm_spa_header-rmsno IS INITIAL.
*   Set object Key
    gv_object-objtype = gc_spah.
    gv_object-objkey = zmm_spa_header-rmsno.
*   GOS toolbar
    CREATE OBJECT gcl_manager
      EXPORTING
        is_object    = gv_object
        ip_no_commit = 'R'
        ip_mode      = 'E'
      EXCEPTIONS
        OTHERS       = 1.
ENDIF.
In report:
CALL TRANSACTION 'ZMMD_SPA'.

Hi,
1, make SY-BINPT = 'X'. then call transaction. Hope it will display.
if not try BDC as mentioned below record only first screen.
data: ctu_params type ctu_params.
ctu_params-UPDMODE = 'A' . " Asyconrous mode.
ctu_params-DISMODE = 'A' " all screens
ctu_params-NOBINPT = 'X'.
CALL TRANSACTION 'ZMMD_SPA' using bdcdata options ctu_params.
Hope it helps.
Regards,
shanmugavel chandrasekaran

Creating Interface through call transaction to send data to XI

Similar Messages

Maybe you are looking for