To check RFC destination

hello All,
Is there any function module available to check RFC destination is active or not?
Thanks,
Johnny

Hi Johnny,
You can use this FM <b>RFC_VERIFY_DESTINATION</b> if your release is greater than 4.6C.
Check this sample code from Craig Cmehil's weblog.
CALL FUNCTION 'RFC_VERIFY_DESTINATION'
  EXPORTING
    DESTINATION = TMP
        TIMEOUT = 10
  EXCEPTIONS
    INTERNAL_FAILURE           = 1
    TIMEOUT                    = 2
    DEST_COMMUNICATION_FAILURE = 3
    DEST_SYSTEM_FAILURE        = 4
    UPDATE_FAILURE             = 5
    NO_UPDATE_AUTHORITY        = 6
    OTHERS                     = 7.
  IF SY-SUBRC EQ '0'.
    "* Do code here
  ENDIF.
or you can also use this FM <b>RFCPING</b> and check this sample code from other thread.
DATA : IT_RFCSI LIKE RFCSI OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'RFC_PING' 
  DESTINATION IT_SLS-SYST
  EXCEPTIONS
    SYSTEM_FAILURE = 1
    MESSAGE RFC_MESS1
    COMMUNICATION_FAILURE = 2
    MESSAGE RFC_MESS1.
IF NOT RFC_MESS1 IS INITIAL.
  MESSAGE I000(YHPA0K) WITH RFC_MESS1.
ELSE.
  CALL FUNCTION 'RFC_SYSTEM_INFO'
     DESTINATION IT_SLS-SYST
     IMPORTING
       RFCSI_EXPORT = IT_RFCSI
     EXCEPTIONS
       COMMUNICATION_FAILURE = 1
       MESSAGE MSG_TEXT
       SYSTEM_FAILURE        = 2
       MESSAGE MSG_TEXT.
  MESSAGE I001 WITH 'Connection to '(029)
                    IT_SLS-SYST
                    'Succeeded'(030).
  ENDIF.
ENDIF.
Hope this will help.
Regards,
Ferry Lianto

Similar Messages

  • Third Party (Garnishment) checks - RFC destination error

    We have an issue with our testing of Third Party Garnishment checks.  We have a split system, with our HCM system residing separately from the remaining ECC modules.
    We are getting an error in regards to the printing of the checks in A/P.
    The posting is working fine
    the vendor account is cleared
    However, It’s not creating a check # or check form.
    We can do other check runs in this client fine; it’s just the 3PR runs that cause the error.
    The text of the error message is as follows:  An RFC destination could not be specified for the logical system HPQCLNT210.
       We have exhausted our resources here looking into the RFC connection and the partner profile and we cannot find anything wrong with them.
    Can someone offer suggestions on what else we could check?  Thanks so much.

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • Post Install Activities Problem - Checking RFC Destination

    I "successfully" installed Web AS 6.4 SR1 ABAP Non-Unicode.  I am following the instructions in SAP Web Application Server 6.40 SR1 ABAP on Windows: MS SQL Server guide.  The Post Installation instructions (2.2.6) require that I Check the RFC Destinations if my the database is located on a remote server from the central instance server.
    The instructions tell me to locate the SAPOSCOL_<DB_Hostname> under the TCP/IP connections and if I cannot locate it I must add it.
    In my case I cannot locate it so I want to add it.  However, I do not know what data I must enter in the various fields of the RFC Destination screen.  Example: what is the connection type for SQL Server
    Thank you.

    Hi Doug,
    Is your database installed on a separate host from the SAP software? If not, you can safely ignore this recommendation and move on.
    We have many systems on Win / MSS on 6.40 ABAP / Java with db and SAP on the same systems. None of my systems have this RFC, and I am not aware of any problems due to the lack there of.
    Regards,
    Sanket

  • Check RFC Destination without access to SM59

    Hi,
    Typically SM59 is reserved for BASIS teams in our organization.
    Assuming there is no access( even read only) for SM59, is there a way (another tool) to test a RFC destination and check whether its functioning correctly ?
    Regards,
    Jon

    Or with SE37 test RFC_PING and input the target RFC destination (and of course not NONE as in my screen)
    Regards,
    Raymond

  • Checking RFC destination availability

    Hello,
    In a transaction I'm working on, I loop at a table containing RFC destinations, and I call the same function module on each of these destinations. What I would like to do is, prior to the call, test if the system behind the RFC destination is available (neither completely crashed, nor just blocked by an administrator).
    I tried to do this by simply calling any BAPI on the remote system, and check if there was a connection error. But the problem is, if the system is not down but just blocked by an administrator, the transaction suddenly displays the logon page of the remote system.
    Do you know of a simple way to do this ?
    Thanks in advance.

    Hello Thomas
    You could try with asynchronous RFC calls (for details refer to the ABAP documentation of CALL FUNCTION).
    Asynchroner RFC
    2. CALL FUNCTION func STARTING NEW TASK task
                    [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                    parameter_list
                    [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
    Regards
      Uwe

  • Check RFC destination and Valid User

    HI all!
    I'm trying to verify the RFC destination in SM59 transaction.  I have 2 trusted connection to  other sap system with an associated account. My goal is to verify that there isn't problem regarding the account and the connection,  the best it's something that try to made a remote logon and give an exception in case of:
    - account isn't working
    - account is  working but there's no connection (think about a network problem)
    Which function i could try to use to accomplish this goal  ?? any idea or just made report?
    I have only make a  function using  a BDL_SERVER_PING but isn't enough.
    Help are Very apreciated
    thanks!

    Hi,
    Use fm RFC_GET_SYSTEM_INFO

  • Error when test for checking RFC destination

    hi all,
    I config "Vitual Administrator" successful follow document "Configuring ADS for Guided Procedures.pdf",
    when i create ADS(sm59) with use ADSUser, system raise error "You are not authorized to view the requested resource"
    and when run checking the ADS, using report FP_TEST_00, system raise error
    ADS: com.adobe.ProcessingException Problem accessing d(200201)
    Message : FPRUNX001
    if any one seen this error, pls help me !!!
    Thanks,

    Have you assingned the role to that. it should be like this
    7.You perform post-installation steps for Adobe Document Services.
    a.You assign the required roles to users ADSUSER and ADS_AGENT
    Assigning Role SAP_BC_FP_ICF to ADS_AGENT
         1. Log on to the ABAP system with user DDIC or SAP*.
         2. Call transaction SU01.
         3. Enter ADS_AGENT in the User field.
         4. Choose User Names® Change
    5. Choose the Roles tab and assign the role     SAP_BC_FP_ICF to the user ADS_AGENT.
    b.     You perform quick tests for Adobe Document Services (ADS).
    Creating Role ADSCallers and Assigning it to ADSUSER
         1. Log on to the ABAP system.
         2. Call transaction PFCG.
         3. Enter ADSCallers in the Role field.
         4. Choose Role® Create.
         5. On the Create Roles screen, choose Role® Save
    6. Choose the User tab and assign the user ADSUSER in the User   ID field.
         To Check if Adobe Services are working
    Checking the User and Password
    1. Open a web browser.
    2. Enter the following URL:                      http:///AdobeDocumentServices/Config
    3. Choose Test.
    4. Choose rpdata(test...).
    5. Choose Send without entering any parameters.
    6. Enter ADSUser as user name and the password you   entered for this user previously.
    Regards
    Subhash

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • RFC destination error in posting 3rd party payment in 4.7 FI system

    Hi,
    We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
    The error says "An RFC destination could not be specified for the logical system HD1CLNT014
        Message no. B1550
    Diagnosis
        An RFC destination should be specified for the logical system
        HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
        local logical system and this system is not included in the relevant
        Customizing tables.
    Procedure
        Check:
            -   RFC destination
               -Port definition
             -oubound partner profile of message type SYNCH for this logical system
    We checked our configuration for all Logical system and RFC destination and everything seems fine.
    Any help in this regard is appreciated.
    Thanks
    Kesav

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • Function module for checking existance of rfc destination?

    hi all,
       is their any function module for checking existance of rfc destination?
    regards
    deepak

    Hi,
    check teh table 'RFCDES'.
    reward if helpful.
    Regards,
    nagaraj

  • To check the TCP/IP RFC destination connectivity

    I am working on R3-->XI connectivity and when i check the destination it looks fine but when I check with the function module for Connectivity, It gives me error.Please suggest any function module who ensures the R3->XI connectivity.
    Thanx in advance.

    You should just be able to do a test connection from SM59 instead of using a FM.

  • RFC Destination Connection Pool requirement

    Hi Experts,
    I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
    There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
    I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
    Application & Access Details
    Application Location : Home Screen
    Concurrent Users     : 600 concurrent users maximum possible value
    Connection Usage    : Close connection immediately using disconnectIfAlive() method.
    Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
    I have read a lot of post and documents but could not acheive clarity of thought on this.
    Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
    Regards,
    Porselvan

    Hi Muthavudaiyan,
    Hope you are doing good.
    Basically from the JCo perspective, there are only 5 parameters that are involved here:
    jco.destination.pool_capacity:
    Maximum number of connections that are held open in the pool for reuse (default: 1)
    jco.destination.peak_limit:
    Maximum number of connections that can be obtained from a pool at peak usage times
    jco.destination.max_get_client_time:
    Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
    jco.destination.expiration_time:
    Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
    jco.destination.expiration_check_period:
    Regular time interval for checking if pooled connections have expired and will be closed
    The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth

  • 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

  • RFC destination error while importing a client request

    Dear Experts,
    We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
    We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
    FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
    The data file and co file in the backend of development is the same size as that of the Prd system.
    I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
    Regards,
    Suratharajan .S

    Hi Suratha,
    Goto STMS->system overview and select the Communication tab.
    Maintained the Instance number of the ASD system.
    Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
    Also distribute the configuration after entering the instance number.
    With Regards
    Ashutosh Chaturvedi

  • RFC Destination could not be created  in TREX administration tool

    Hi All,
       Recently i installed the TREX server, I am trying to connect the ABAP system with the RFC connection. I entered all necessary data for the RFC connection it giving error as
    RFC Destination could not be created.
    To solve the above problem i created one RFC connection of type TCP/IP in ABAP server eventhough it is not solved.
    Can i have the solution  for the above problem?
    Regards,
    Vivek.

    Hi Michale,
        Thanks for your quick response; I tried all the mentioned possibilities in that help document, still i am facing the same problem.
    It is giving the below error
    Connect to SAP System failed.Possible reasons:
    -Logon data incorrect
    -Password is not uppercase(must also be uppercase)
    -SAP system user locked
    -SAP user not in specified client
    -SAP User rights are insufficient
    -SAP system not reachable
    -saprfc.ini unavailable or entries incorrect
    -TREXTcpipClient.ini section[communication],parameters rfcdestination, sapsystem not set
    -SAP system Basis component below 6.20 or SP too low
    -->check also latest TREXTcpiplient trace file entries.*
    The above all are check by me everything is fine.
    The below information from the saprfc.ini file
    DEST=NPI
      TYPE=B
      MSHOST=server1
      GROUP=server1_group*.
    Is there any mistake, please let me know.
    Regards,
    Vivek.

Maybe you are looking for