Program ID in RFC destination-XI

Hi
can any one tell me
for RFC sender channel purpose i'm creating RFC destination in SM59. through sap help and some other weblogs i'm trying create Program iD,but i'm getting some doubts on this:
1. How do i know corrosponding programID for this register server program?
2.How do i know sender system is Unicode system is or not?
Auctully my scenrio is RC--->JDBC, thats the reason i'm trying to create RFC destination in r/3 side..
regards
rambarki

Hi Rambarki,
Is your scenario sysnchronous or asynchronous ?
if your scenario is asynchronous then from ABAP program you can call your RFC using the following syntax...
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IN BACKGROUND TASK .
for synchronous scenarios use this
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IMPORTING ...
You also try using SE37..
In SE37 enter name of your RFC and press on execute..
then enter your RFC destination name , input parameters..and execute.
Is test connection working fine in SM59 ?
Take look at this thread aswell
Re: How to test the RFC to Flat File scenario
Regards
Anand

Similar Messages

  • Program ID in RFC destination of type T

    can one please explain what exactly is program id in rfc destination of type T

    Hi,
    from
    http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042652488911d189490000e829fbbd/content.htm
    "Type T destinations are connections to external programs that use the RFC library to receive RFCs."
    so program id is the name of such a program
    Regards,
    michal

  • Call several .exe program via one RFC destination

    Hi,
    We use a RFC destination (one for each connected user) to communicate between SAP R/3 (4.6c) and an AS400 application via RFC server in .NET.
    We need to call some .NET functions (for transactionnal purpose) and we wish not to mix functions refering to AS400 and .NET.
    Is it possible to use one RFC destination to call functions in at least 2 .NET program ?
    If not, is there other ways to make those communications work ?

    Hi
    It is not possible. I don't think of any other way to resolve this.
    Thanks & Regards,
    Govind.

  • Help with RFC sender, Program And RFC Destination

    Hi!!
    my scenary is asynchronous
         RFC Sender -> SAP-XI -> Oracle reciever
    I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI  receive the message but the message is empty.
    1. In my program on the line
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
    2. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
    3. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
    What is my Error?
    Where am i making a mistake?
    RFC
    FUNCTION zbapi_sd_ped_ord_servic.
    *"Interfase local
    *"  TABLES
    *"      PED_ORDEN STRUCTURE  ZSD_RFC_T04
    *"      RETURN STRUCTURE  ZSD_RFC_R06
      TABLES: zsd_ped_orden, zsd_rfc_r01.
      DATA: tb_ped_orden LIKE zsd_ped_orden  OCCURS 0 WITH HEADER LINE,
                     tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
    *Get Pedido by Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
              FROM zsd_ped_orden
              WHERE estatus  EQ  space.
      LOOP AT tb_ped_orden.
        MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
        APPEND ped_orden.
        tb_ped_orden-estatus = 'X'.
        tb_ped_orden-fecha_actualiz = sy-datum.
        tb_ped_orden-hora_actualiz = sy-uzeit.
        MODIFY tb_ped_orden.
      ENDLOOP. 
      MODIFY  zsd_ped_orden FROM TABLE tb_ped_orden.
      COMMIT WORK.
    *Errors in Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
              FROM zsd_rfc_r01
              WHERE estatus  EQ  space.
      LOOP AT tb_rfc_orden_error.
        MOVE-CORRESPONDING tb_rfc_orden_error TO return.
        APPEND  return.
        tb_rfc_orden_error-estatus = 'X'.
        tb_rfc_orden_error-fecha_actualiz = sy-datum.
        tb_rfc_orden_error-hora_actualiz = sy-uzeit.
        MODIFY tb_rfc_orden_error.
      ENDLOOP.
      MODIFY  zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
      COMMIT WORK.
    ENDFUNCTION.
    PROGRAM
    REPORT  ZBAPI_SD_PED_ORD_SERVIC.
    DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
          return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
         TABLES
              ped_orden             = ped_orden
              return                = return
      EXCEPTIONS
        communication_failure = 1
        system_failure        = 2
        OTHERS                = 3.
    IF sy-subrc <> 0.
      MESSAGE 'error' type 'I'.
    ENDIF.
    COMMIT WORK.
    RFC DESTINATION
    RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
    Connection TYpe: TCP/IP Connection
    Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
    Gateway host: host00
    Gateway service: sapgw00

    hi
    For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
    a) RFC destination
    b) RFC channel in the XI directory
    This weblog is a response to a few question about the basic configuration of the RFC sender adapter
    that were posted on the XI forum (and also on my e-mail)
    So here we go, basically we have to configure 2 things:
    a) RFC destination
    b) RFC channel in the XI directory
    RFC destination:
    1. To create the RFC go to TCODE: SM59
    2. Create new destination of type T (TCP/IP)
    3. Make sure you select Registered Server Program option before writing your program ID
    4. Write you program ID (remember it's case-sensitive)
    5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
    7. No configuration in the J2EE administrator nessecary
    Now we can proceed to RFC channel configuration:
    1. Enter your Application Server
    2. Your Application Server Service
    3. Enter your Program ID from the RFC destination
    And we're done:)
    Now you can test the RFC destination in SM59 to see if it works.
    Please chk this following link.
    1. RFC Processing with the RFC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
    2. Configuring the Sender RFC Adapter -
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    3.  /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    regards
    Manas

  • Is RFC destination is required for accessing BAPI from java/VB program.

    I am not able to understant that all BAPI are Remote enabled ,but no where I observed that RFC destination is required.
    Can any body tell me exact flow and things step by step.
    Any example/full source code so that I can call from java program.
    I have tried some java code posted here but not able to understand ..
    please provide me setttings also in SAP and java system

    Hi Nagaraju,
    Thank you very much. your post resolve one of my basic need .really appreciate your post.
    I was not able to execute bapi BAPI_MATERIAL_GETLIST but I executed BAPI_PO_GETDETAIL succesfully.
    Still I have 2 doubt.
    [1]. I called BAPI function module(BAPI_PO_GETDETAIL) from simple java program,But I need to call API method ( GETDETAIL) created for this BAPI not direct BAPI function module.
    [2] this is something apart from original topic.
    I have tested your java code in java as well as similar in ECC 6.0
    But I am not getting any output in JAVA program.
    I am getting output in ECC6.0 only when I will take internal table lt_mara[] with header line.
    if I will take separate workarea output is not coming. I think this is the problem in JAVA also.
    Please see the code and tell me where I am wrong.
    REPORT ZTEST1.
    types: begin of ty_mara .
       include STRUCTURE BAPIMATRAM.
    TYPES: END OF ty_mara.
    types: begin of ty_list .
      include STRUCTURE BAPIMATLST.
    TYPES: END OF ty_list.
    data: lt_mara type STANDARD TABLE OF ty_mara with HEADER LINE.
    data: lt_list type STANDARD TABLE OF ty_list,
          ls_list like LINE OF lt_list.
    START-of-SELECTION.
    lt_mara-SIGN = 'I'.
    lt_mara-option = 'EQ'.
    lt_mara-matnr_low = '000000000000000088'. "'P1001087'.
    lt_mara-matnr_high = ''.
    APPEND lt_mara.
    lt_mara-SIGN = 'I'.
    lt_mara-option = 'EQ'.
    lt_mara-matnr_low = '000000000000000089'. "'P1001087'.
    lt_mara-matnr_high = ''.
    APPEND lt_mara.
    CALL FUNCTION 'BAPI_MATERIAL_GETLIST'
    TABLES
      MATNRSELECTION                     = lt_mara
      MATNRLIST                          = lt_list[]   .
    WRITE / 'output:  '.
    LOOP AT lt_list into ls_list .
      write: ls_list .
    ENDLOOP.
    REPORT ZTEST2.
    types: begin of ty_mara .
       include STRUCTURE BAPIMATRAM.
    TYPES: END OF ty_mara.
    types: begin of ty_list .
      include STRUCTURE BAPIMATLST.
    TYPES: END OF ty_list.
    data: lt_mara type STANDARD TABLE OF ty_mara, ">> Without header line
           ls_mara like line of lt_mara.
    data: lt_list type STANDARD TABLE OF ty_list,
          ls_list like LINE OF lt_list.
    START-of-SELECTION.
    ls_mara-SIGN = 'I'.
    ls_mara-option = 'EQ'.
    ls_mara-matnr_low = '000000000000000088'. "'P1001087'.
    ls_mara-matnr_high = ''.
    APPEND ls_list to lt_mara.
    ls_mara-SIGN = 'I'.
    ls_mara-option = 'EQ'.
    ls_mara-matnr_low = '000000000000000089'. "'P1001087'.
    ls_mara-matnr_high = ''.
    APPEND ls_list to lt_mara.
    CALL FUNCTION 'BAPI_MATERIAL_GETLIST'
    TABLES
      MATNRSELECTION                     = lt_mara
      MATNRLIST                          = lt_list[]          .
    WRITE / 'output:  '.
    LOOP AT lt_list into ls_list .
      write: ls_list .
    ENDLOOP.

  • RFC destination definition with non-unicode external program

    Hello All,
    we have one issue with our RFID system connecting to WM system (SWD). 
    For most functions, external RFID server/middleware makes RFC call to SAP system.  Means, from outside system to inside SAP.  This seems to be working fine.
    But in one case, SAP needs to print label to RFID printer.  In this case, SAP is calling external RFID server/middleware using RFC destination.  Means, from inside SAP to outside system.  This is failing.
    We think this has something to do with ECC60 being unicode system, and the RFC destination setup.  We define rfc destination "ZRFID_SSI" in SM59.  We define it same way as in as-is SSI 4.6B production system.  But in SWD ECC60 system, SM59 has more options.  We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server.  RFC destination is actually working ok.
    To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI.   Listener on RFID server/middleware will respond to function call.  This also seems to be working.  But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0".  (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
    Compared with production environment, everything is the same, except that SAP is unicode system.  So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data.  I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange.  Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
    Anyone know how to help ?

    Hi Jeongbae,
    as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
    In earlier releases, this is not possible.
    In general, SAP systems use the logon language (SY-LANGU)  to determine the code page, if this is available.
    Please check SAP note 788239.
    Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
    In addition I would recommend to have a look at SAP note 1021459.
    However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
    For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
    Best regards,
    Nils Buerckel
    SAP AG

  • Program not registered - RFC to J2EE (local machine)

    I have a local install of WAS on my laptop using MSSQL 2000. I am trying to integrate local portal into a BI system.
    1. I completed SLD configuration of local J2EE
    2. As part of local SLD config I specified a BW7 system as data supplier
    - entered  BW7 host & gateway
    - kept default settings for "configure data supplier targets" (i.e: sld/active=TRUE)
    3. In Visual composer I successfully triggered SLD data transfer
    4. In Visual Composer I specified a JCo RFC Provider to the BW7 system I want to access.
    5. If I go to BW7 and goto tcode SMGW -> GOTO -> Logged on client, I see 2 pair of entries for JCo RFC provider
    with the following settings
    - system type: Registered Server (REGISTER_TP)
    - state: connected
    - LU name & Host Name = J2EE Host name w/ last 4 characters truncated. Only first 8 characters appear.
    - TP Name: 2 entries = SLD_UC & 2 entries = SLD_NUC. So a total of 4 connections. My understanding is that TP Name is supposed to = Registered Server Program
    6. In BW7, I have an RFC w/ Registered Server Program setting and program ID = JCo RFC Provider program ID
    7. In BW7 RFC & JCo RFC the host & gateway settings are the same, they both refer to the BW7. THIS IS THE PART WHERE I AM UNSURE. I would have thought that the host & gateway settings of BW7 RFC would refer to Local J2EE engine. AND I DON'T KNOW WHAT THE GATEWAY IS FOR LOCAL J2EE.
    8. In BW7 when I try to test the RFC, I get errors:
    - Logon     Connection Error
    - program <...> not registered / CPIC-CALL: 'ThSAPOCMINIT' Tran
    - ERROR: program <...> not registered
    - DETAIL: TP <...> not registered
    - COMPONENT: SAP-Gateway
    - MODULE: gwr3cpic.c
    - RETURN CODE: 679
    - SUBRC: 0
    - RELEASE: 700
    - VERSION: 2
    9. I completed step 1 & 2 of RSPOR_SETUP
    - Step 1 <Create RFC Destination in J2EE engine> messages:
    No Authorization to SMGW
    Profile parameter login/create_sso2_ticket is not set to 2
    Check of RFC destination <...> with RFC_READ_TCPIP_DESTINATION successful
    - Step 2 <Create RFC destination to Portal> messages:
    No Connection
    Option Send SSO tickets not active (see documentation)
    RFC CALL RFC_PING, destination <...> failed with sy-subrc =2
    There a little something missing. Hope u gurus can help, lost a weekend over this.

    Hello,
    we get the same message (program ... not registered, COMPONENT: SAP-Gateway) in sm59, when checking the TCP/IP connection. We got it, after we changed the user name in the Visual Administrator.
    Does anyone know with which tool and where the program can be registered. (The connection has no user name (connection by SAP ticket)).
    Best regards,
    Thomas

  • No RFC Destination maintained

    Hi Experts,
    I am doing User Exit for MIGO.
    I have done it successfully.but problem comes when the email is sent to the vendor, MIGO is getting DUMP.
    So, to cross check i have remove the User Exit of MIGO. but to my surprise when i press POST button in MIGO the similiar DUMP comes.
    So wht is the solution for this.
    For your Information DUMP message is:
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          06.12.2007 14:57:55
    Short text
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    Short text of error message:
    No RFC destination is defined for SAP Global Trade Services
    Long text of error message:
    Technical information about the message:
    Message class....... "/SAPSLL/PLUGINR3"
    Number.............. 002
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_X" " "
    "SAPLMBWL" or "LMBWLU21"
    "MB_POST_GOODS_MOVEMENT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "vngsap1"
    Network address...... "192.168.0.10"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 801586"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "VNGSAP1"
    Database type..... "MSSQL"
    Database name..... "EC6"
    Database user ID.. "ec6"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 20 2007 00:45:21"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
    Patch level. 102
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8176
    EM...... 21953056
    Heap.... 0
    Page.... 73728
    MM Used. 15443024
    MM Free. 1280936
    User and Transaction
    Client.............. 800
    User................ "VEDHRUV"
    Language key........ "E"
    Transaction......... "MIGO "
    Transactions ID..... " "
    Program............. "SAPLMBWL"
    Screen.............. "SAPLMIGO 0001"
    Screen line......... 18
    Information on where terminated
    Termination occurred in the ABAP program "SAPLMBWL" - in
    "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPLMIGO ".
    In the source code you have the termination point in line 59
    of the (Include) program "LMBWLU21".
    Source Code Extract
    Line
    SourceCde
    29
       when a goods movement for an inbound or outbound delivery is posted
    30
       directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31
       CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32
       BKPF as well. There is no other way to forward XBLNR to FI as not
    33
       every document is posted by MB_CREATE -> a new function module in
    34
       MBWL for transferring the information, called by FI, meant to load
    35
       the complete function group for all MBxx postings when this isn't
    36
       required (Performance). Would be the better way to transport the
    37
       information after switching off MBxx in later release.
    38
       corresponding IMPORT ... FROM MEMORY ... can be found in
    39
       AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40
    l_mem_id = 'MKPF-XBLNR'.                                   " 641365
    41
    EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
    42
    ENDIF.
    43
    IF xmkpf-xabln IS INITIAL.                               "note 434093
    44
    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
    45
    ENDIF.                                                   "note 434093
    46
    47
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51
    EXCEPTIONS
    52
    error_message = 4.
    53
    As soon as we have started to put things into UPDATE TASK, we must
    54
    ensure that errors definitely terminate the transaction.
    55
    MESSAGE A is not sufficient because it can be catched from
    56
    external callers which COMMIT WORK afterwards, resulting in
    57
    incomplete updates. Read note 385830 for the full story.
    58
    IF NOT sy-subrc IS INITIAL.
    >>>>>
    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
    60
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61
        MESSAGE A263.
    62
    ENDIF.
    63
    Optische Archivierung
    64
    Spaete Erfassung mit Barcode
    65
    Redesign of barcode handling -> note 780365
    66
    PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
    67
    xmkpf-mjahr
    68
    barcode.
    69
    70
    MOVE-CORRESPONDING xmkpf TO emkpf.
    71
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    72
    EXCEPTIONS
    73
    error_message = 4.
    74
    MOVE-CORRESPONDING xmkpf TO emkpf.
    75
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    76
    EXCEPTIONS
    77
    error_message = 4.
    78
    IF NOT sy-subrc IS INITIAL.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    4
    SY-INDEX
    1
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    MIGO_STATUS
    SY-UCOMM
    OK_POST1
    SY-TITLE
    Goods Receipt Purchase Order 4500017132 - shah
    SY-MSGTY
    X
    SY-MSGID
    /SAPSLL/PLUGINR3
    SY-MSGNO
    002
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20071206
    SY-UZEIT
    145755
    SY-XPROG
    SAPLBPFC
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    7 FUNCTION     SAPLMBWL                            LMBWLU21                               59
    MB_POST_GOODS_MOVEMENT
    6 METHOD       SAPLMIGO                            LMIGOKG1                              921
    LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
    5 METHOD       SAPLMIGO                            LMIGOKD1                              309
    LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
    4 METHOD       SAPLMIGO                            LMIGOKD1                                9
    LCL_MIGO_KERNEL=>DOCUMENT_POST
    3 METHOD       SAPLMIGO                            LMIGOST2                              124
    LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER
    2 METHOD       SAPLMIGO                            LMIGOFR2                              172
    LCL_MIGO_FRAME=>OKCODE_DISPATCH
    1 MODULE (PAI) SAPLMIGO                            LMIGOPAI                               11
    PAI_OKCODE_DISPATCH
    Chosen variables
    Name
    Val.
    No.       7 Ty.          FUNCTION
    Name  MB_POST_GOODS_MOVEMENT
    XBLNR_SD
    2222
    0000
    0000
    0000
    EMKPF
    000000000000000000          ##
    2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    XMSSA[]
    Table IT_3831[0x196]
    FUNCTION-POOL=MBWLDATA=XMSSA[]
    Table reference: 396
    TABH+  0(20) = 0000000088F26C31000000008C010000F70E0000
    TABH+ 20(20) = 00000000C4000000FFFFFFFF04E90400E01B0000
    TABH+ 40( 8) = 08000000C1108001
    store        = 0x00000000
    ext1         = 0x88F26C31
    shmId        = 0     (0x00000000)
    id           = 396   (0x8C010000)
    label        = 3831  (0xF70E0000)
    fill         = 0     (0x00000000)
    leng         = 196   (0xC4000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000134
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x40F26C31
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xA0F5EA30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    RRESWK
    22222222222
    00000000000
    00000000000
    00000000000
    %_SPACE
    2
    0
    0
    0
    L_MEM_ID
    2222222222
    0000000000
    0000000000
    0000000000
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    XMSPR_KEY
    00000000
    222222222222222222222222222222222222233333333
    000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000
    SCREEN
    GODYNPRO-DETAIL_TAKE
    4445455424454445544422222222222222222222222222222222222222222222222222222222222222222222222222
    7F49E02FD45419CF41B500000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IT_RSTRUCT
    Table[initial]
    XMKPF-XABLN
    2222222222
    0000000000
    0000000000
    0000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLMBWL
    5454445422222222222222222222222222222222
    310CD27C00000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    ODM07M[]
    Table[initial]
    GT_GOCOMP
    000000000000                                             ####              00000000000000
    3333333333332222222222222222222222222222222222222222222220000222222222222223333333333333322222
    000000000000000000000000000000000000000000000000000000000000C000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-SUBRC
    4
    0000
    4000
    L_ATPCB
    22222
    00000
    00000
    00000
    XMKPF-MBLNR
    5000011865
    3333333333
    5000011865
    0000000000
    0000000000
    XMKPF-MJAHR
    2007
    3333
    2007
    0000
    0000
    BARCODE
    2222222222222222222222222222222222222222
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T003
    800WE50AMS         X                XX  XXXXXH
    3335433445222222222522222222222222225522555554222222
    80075501D3000000000800000000000000008800888888000000
    0000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000
    KNVV
    00000000                     000
    2222222222222222222222222222222223333333322222222222222222222233322222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    T064B
    2222222222222222222222
    0000000000000000000000
    0000000000000000000000
    0000000000000000000000
    VGMSEG[]
    Table[initial]
    No.       6 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>GOODS_MOVEMENT_POST
    ES_EMKPF_OLD
    5000011865200700000000000000          ##
    3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLMIGO
    5454444422222222222222222222222222222222
    310CD97F00000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    LS_EMKPF
    000000000000000000          ##
    2222222222333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OREF_TITLEBAR
    |
    | E0001000 |
    | 60009000 |
    | LS_EMKPF-SUBRC |
    | 0 |
    | 0000 |
    | 0000 |
    | C_MOD_ON |
    | 1 |
    | 3 |
    | 1 |
    | 0 |
    | 0 |
    | GOITEM-ERFMG |
    | 0.0.0.0.0.0.1.  |
    | 0001000 |
    | 000000C |
    | LS_EMKPF-MBLNR |
    |  |
    | 2222222222 |
    | 0000000000 |
    | 0000000000 |
    | 0000000000 |
    | SY-XPROG |
    | SAPLBPFC |
    | 5454454422222222222222222222222222222222 |
    | 310C206300000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | SY-REPID |
    | SAPLMIGO |
    | 5454444422222222222222222222222222222222 |
    | 310CD97F00000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000 |
    | SY-MSGID |
    | /SAPSLL/PLUGINR3 |
    | 25455442545444532222 |
    | F3103CCF0C579E230000 |
    | 00000000000000000000 |
    | 00000000000000000000 |
    | TV_GODEFAULT_TRANSFER-CX |
    | <initial> |
    | <initial> |
    | <initial> |
    | SPACE |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | SY-MSGNO |
    | 002 |
    | 333 |
    | 002 |
    | 000 |
    | 000 |
    | SY-MSGV1 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | ES_EMKPF_OLD-MSGV1 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV2 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV3 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | SY-MSGV4 |
    |  |
    | 22222222222222222222222222222222222222222222222222 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | 00000000000000000000000000000000000000000000000000 |
    | GODEFAULT_TV |
    | 101  GR goods receipt |
    | 2222223332245266667276666772222 |
    | 000000101007207FF43025359040000 |
    | 0000000000000000000000000000000 |
    | 0000000000000000000000000000000 |
    | LS_EMKPF-MJAHR |
    | 0000 |
    | 3333 |
    | 0000 |
    | 0000 |
    | 0000 |
    | OREF_TIP |
    |
    D0002000
    90006000
    TV_GOSPLIT-CURRENT_LINE
    <initial>
    <initial>
    <initial>
    No.       5 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>DOCUMENT_OPERATION
    I_SIMULATE
    2
    0
    0
    0
    I_SIM_VALUES
    2
    0
    0
    0
    I_ERROR_ONLY
    2
    0
    0
    0
    E_OK
    2
    0
    0
    0
    ET_XMSEG
    Table[initial]
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LS_EMKPF
    5000011865200700000000000000          ##
    3333333333333333333333333333222222222200222222222222222222222222222222222222222222222222222222
    5000011865200700000000000000000000000010000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LT_EMSEG
    Table IT_4407[2x744]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_EMSEG
    Table reference: 460
    TABH+  0(20) = F06C0731F83FE73000000000CC01000037110000
    TABH+ 20(20) = 02000000E8020000FFFFFFFF0400000040420100
    TABH+ 40( 8) = 10000000C1308001
    store        = 0xF06C0731
    ext1         = 0xF83FE730
    shmId        = 0     (0x00000000)
    id           = 460   (0xCC010000)
    label        = 4407  (0x37110000)
    fill         = 2     (0x02000000)
    leng         = 744   (0xE8020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001704
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xB8902E31
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3425  (0x610D0000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0xE0D66931
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x00F11C31
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_XMSEG
    Table IT_4408[2x2364]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_XMSEG
    Table reference: 464
    TABH+  0(20) = A0BEF93070D7693100000000D001000038110000
    TABH+ 20(20) = 020000003C090000FFFFFFFF0400000030310100
    TABH+ 40( 8) = 04000000C1308401
    store        = 0xA0BEF930
    ext1         = 0x70D76931
    shmId        = 0     (0x00000000)
    id           = 464   (0xD0010000)
    label        = 4408  (0x38110000)
    fill         = 2     (0x02000000)
    leng         = 2364  (0x3C090000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001613
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x28DF3031
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3511  (0xB70D0000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    collHook     = 0x00000000
    ext2         = 0x28D76931
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x90F4EA30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_IMSEG
    Table IT_4396[2x2792]
    FUNCTION-POOL=MIGOCLASS=LCL_MIGO_KERNELMETHOD=DOCUMENT_OPERATIONDATA=LT_IMSEG
    Table reference: 465
    TABH+  0(20) = D0D5693190D7693100000000D10100002C110000
    TABH+ 20(20) = 02000000E80A0000FFFFFFFF04000000E0410100
    TABH+ 40( 8) = 04000000C1308001
    store        = 0xD0D56931
    ext1         = 0x90D76931
    shmId        = 0     (0x00000000)
    id           = 465   (0xD1010000)
    label        = 4396  (0x2C110000)
    fill         = 2     (0x02000000)
    leng         = 2792  (0xE80A0000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001702
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xE01BC930
    pgHook       = 0x00000000
    idxPtr       = 0x00000000
    shmTabhSet   = 0x00000000
    id           = 3413  (0x550D0000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 4     (0x04000000)
    lineAlloc    = 4     (0x04000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xC8626B31
    collHook     = 0x00000000
    ext2         = 0x80626B31
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xD88C0331
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    LT_CANCEL
    Table[initial]
    ABAP_TRUE
    X
    5
    8
    0
    0
    LCL_MIGO_GLOBALS=>IF_BADI
    |
    | F0000000 |
    | 70008000 |
    | SYST |
    | ######################################T#########œ#################################ÿ##### C#### |
    | 0000000000000000000000000000000000000050000000005000000000000000000000000000109000F00050240000 |
    | 100010000000000000001000100010000000004000C0B0403000000000000000000000000000B00000F00080030400 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000 |
    | 00000000000000000000000000000000000000000000000010000000000000000000000000000000000000D000000C |
    | LS_XMKPF |
    | 80050000118652007WEWEPR20071206200712062007120614575300000000VEDHRUV |
    | 3333333333333333354545533333333333333333333333333333333333333544455522222222222222222222222222 |
    | 8005000011865200775750220071206200712062007120614575300000000654825600000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | ME |
    |
    F0000000
    D0002000
    %_SPACE
    2
    0
    0
    0
    L_NO_ITEMS
    2
    0
    0
    0
    TV_GODEFAULT-CX
    <initial>
    <initial>
    <initial>
    LCL_MIGO_GLOBALS=>CALLER_SYTCODE
    MIGO
    44442222222222222222
    D97F0000000000000000
    00000000000000000000
    00000000000000000000
    LCL_MIGO_GLOBALS=>RETAIL_CONSIGNMENT_ACTIVE
    2
    0
    0
    0
    %_FSREG_001
    No.       4 Ty.          METHOD
    Name  LCL_MIGO_KERNEL=>DOCUMENT_POST
    E_OK
    2
    0
    0
    0
    ME
    |
    | F0000000 |
    | D0002000 |
    | ABAP_FALSE |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST |
    |  |
    | 2 |
    | 0 |
    | 0 |
    | 0 |
    | %_ARCHIVE |
    |  |
    | 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
    | No.       3 Ty.          METHOD |
    | Name  LCL_MIGO_STATUS=>LIF_MIGO_FRAME~OKCODE_HANDLER |
    | I_OKCODE |
    | OK_POST1 |
    | 4455455322222222222222222222222222222222222222222222222222222222222222 |
    | FBF0F34100000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000 |
    | 0000000000000000000000000000000000000000000000000000000000000000000000 |
    | OREF_BADI_LOG |
    |
    D0002000
    5000A000
    %_FSREG_001
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LCL_MIGO_GLOBALS=>KERNEL
    |
    | F0000000 |
    | D0002000 |
    | %_VIASELSCR |
    | # |
    | 0 |
    | 4 |
    | OREF_DETAIL_BATCH |
    |
    60009000
    0000F000
    GOSEARCH_PO
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       2 Ty.          METHOD
    Name  LCL_MIGO_FRAME=>OKCODE_DISPATCH
    I_OKCODE
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    L_MSG_STRING
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_OKCODE
    OK_POST1
    4455455322222222222222222222222222222222222222222222222222222222222222
    FBF0F341000000000000000000000000000000000000000000000000000000000

    Hi Dhruv Shah,
           Can you please tell me which user exit you are using for doing that. coz i am in need of that.
    Thanks,
    Ajeeth

  • Creation of RFC Destination problem

    Hi Experts,
    I need to establish an RFC communication between TREX7.0 server running on windows 2003 server and the SAPR/3 4.7 EE server running on windows2000.
    server. Initially i used TREXAdminTool to create RFC Destination, i was unable to create successfully
    Then i used SAPR/3 server from  TCODE: SM59, here also am facing the same problem, what are the values i have to give  for
    1. RFC Destination, 2. Program id 3. Gateway Host and Gateway Service.
    PLZ  guide me step by step procedure with some example values to create RFC Destination to TREX Server successfully using TREXAdminTool or from SAPR/3 server---SM59
    ADV Thanks
    Regds
    phanikumar

    Hi,
    Till now i didn't install explicitly any SAP Gateway on TREX server.
    I installed TREX server along with SAP Netweaver WEB AS java.
    Shall i need to install any SAP Gateway to configure RFC Destination?
    If so can you give me the procedure how to install explicitly SAP gateway?
    Regds
    Phanikumar

  • Creating RFC Destination in SAP R/3

    Trying to create an RFC destination in SAP R/3.  Looked at few articles in creating them, but I am getting error while testing.  It says that the "Program" couldn't not be found.  I tried with all options, "Registered in Server Program", "Start on Application Server" etc.,
    Is there a place to register a "Program"?  Is this program specific to my XI server?  How should this program be created or registered.
    Any help is greatly appreciated!
    Thanks
    Satya

    one more hit:
    http://server:port/rwb/index.jsp
    message monitoring
    BTW
    you have created everything in XI repository & configured everything in xi directory haven't you?
    if not you can try this document:
    "Validating a Connection Between R/3 and SAP XI with RFC"
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/validating a connection between sap r3 and sap xi with rfc.pdf
    by Sridhar Rajan Natarajan
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • RFC destination for Sender System  in R/3 4.6c

    Hi All,
    I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?

    Hi Arul,
           One more important point u have missed.
    Program ID,
    When ur configuring sender service from RFC,The most important point is Program ID.
    Use some name and create it.Use the same name in SM59.
    s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
    Reghards
    chandra shekar

  • RFC destination for RFC to File scenario

    Hi,
    I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
    Step 1:
    For this a Registered server program is created in Jco RFc Destinations with,
    Program Id : pgm1
    Gateway host : PI's host
    Gateway service : PI's service
    application server host: ECC's host
    system numer     : ECC's number
    client  : ECC's client
    logon user : ECC user
    password : pwd
    Step 2:
    In SM59, TCP/IP connection the following parameters are given:
    Program ID : pgm1
    Gateway host : PI's host       -
    > is this correct
    Gateway service : PI's service      -
    > is this correct
    Step 3:
    So i am calling the RFC in ABAP program (R/3 system) like:
    CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
    IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
    Step 4:
    In PI side,
    for RFC sender I am passing :
    Application server : PI server
    Application server service: PI host
    program ID: pgm1 which was created in the previos step
    For RFC Metadata Repository Parameter, i am passing all the values related to R/3
    Please let me know whether the steps and values i given is correct.
    B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
    so i am confused as which is the correct method. pls clarify

    Ok I will try to explain....
    Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
    While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
    So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
    CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
      IN BACKGROUND TASK
      DESTINATION 'R3_TO_XI'
      TABLES
        comp_detail = company_detail.
    COMMIT WORK.
    Regards,
    Sarvesh

  • RFC Destination Seetings Problem between R/3 and XI System

    Hi...
    In my RFC to File Scenario I cant see the messages in MONI......
    When we create RFC destination through SM59.....we will fill gateway host and service
    of R/3......Then we Configure the RFC Sender CC and fill same Program ID, Gateway host & service of R/3.
    My doubt is,after this should I have to configure SM59 at XI side ???.....
    I am getting confused in this RFC Settings between R/3 & XI....Can u explain the flow correctly.....
    Please help me out.....
    Thanks,
    Sudheer.

    Hello Sudheer,
    1.Configure the Sender communication channel by giving the programId there,                    
    2.You need to create RFC Destination at Sender R/3 system pointing to PI, there you need to mention the programId, specified in Sender CC,
    3. In RFC destination you need to specify your XI system details for  Host/ServiceName nameand gateway service .
    Note: programId is case sensitive.
    No need to create any RFC Destination in XI system.
    check the following thread for further clarifications.
    Re: TCP/IP connection for RFC sender adapter
    Regards,
    Prasanna

  • Rfc Destination problem in RFC Sender Adapter

    Hi experts
    I created a Rfc destination type TCP/IP for Rfc Sender adapter.
    while creating i passed following parameter:
    1) I selected Activation Type option-> Registered Server  
    2)Given a Program id , same as i given in Rfc sender Adapter config.   
    3)Gateway option:
       i) Gateway Host:Server IP address where i created  Rfc.
      ii) Gateway Service:sapgw00
    After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

    Hi
    please check for the following things.
    1. check the RFC destination using the connection test tab in the R/3 system.
    2. check whether the program id that u have given is registered or not.
    to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
    check for ur program id name in the table.
    3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
    if u still face the problem please reply me back.
    Thanks
    Rinku

  • RFC destination error in transport

    Hello,
    We are trying to import a transport into our BW QA system and we keep getting return code 8 with the following text:
    BW RFC destination <systemname> is not maintained in the source system
    Message no. R3078
    The transport contains cubes and three ODSs.  After the transport fails and I check the QA system, the cubes are active, but the ODSs are not.
    I searched SDN and found another thread explaining the same problem and I tried everything suggested there.  I looked in RSA1 --> Mapping of the source system names, and the BW DEV and QA systems are listed.  I also looked in SM59 and checked the RFC connection, and that is ok as well. 
    Does anyone have any suggestions?
    Thanks
    Charla

    I have searched OSS further and found that the contents of my RSLOGSYSDEST table are off. 
    The contents are as follows:
    Src System    RFC Destination
    AWQ100          AWP100
    QAT100          QAT
    I believe that in the above table, the AWP100 should be AWQ100.  I looked at this table in our production environments, and in those cases the Src system entry and RFC Destination entry are the exact same, so I think this should be the case in our AWQ100 system as well.
    Just curious if anyone knows if there is a program I can use to modify this table. 
    Thanks
    Charla

Maybe you are looking for

  • [BUG] iCal reverts Google Calender recurring events when changed.

    When in Apple Calendar and drag a recurring event to a new time and the pop-up asks if I want to do this for this event or all future events and choose only this event it changes, then moments later it reverts back to the original time. These events

  • Purpose of Apple TV

    Confused about the purpose of Apple TV. Is it really just essentially a $99.00 box that lets you rent movies from the Apple store? I can already do that with Pay-per-view. There HAS to be a more compelling reason to own it... doesn't there?? Any idea

  • Shared Review Web Server - Acrobat 9.0 Pro

    Hey All I'm trialling Acrobat v9 with a view to improving invoice approvals within the business. Firstly, I thought of using the "workflow approval" process, but this doesn't appear to be available. So, I decided to use the "Share Review" process but

  • Running iPhone SDK & Leopard on G4 1.42 emac?

    Looking for a cheap entry point to get into developing apps for iphone. I can get the 1.42ghz G4 emac for $200 or G5 PPC 2.0ghz for $775. I've read that the G4 will run leopard, but havent found anyone running leopard and iphone sdx on the G4. I'd li

  • Stop DIA work process with PRIV mode in my program

    Hello, I  write Program that display in the end an alv report and when i display it after same time my dia wp get in PRIV mode I search about it and I didn't find the solution but it happend only with my program this reject the memory parameter that