Inbound proxies rfc destination issue

Hi Gurus,
Im currently using sending xml message to Integration server using runtime workbench to inbound proxy of SAP ECC system
I used XI adapter on the receiver side ..the HTTP destination configured in PI server connecting to sap ecc system is having the following details.
host name ---sap ecc hostname
service no --abap http port 8080 which is available in smicm.
logon client is 110(testing client not dev client)
i dont know why even after making all the settings in SM59 ,the message is not going to SAP ECC system.
am i missing anything.
Any help appreciated.
Thanks,
Jay

Jay ,
try giving your IP address insted of your host name.
Regards,
naveen

Similar Messages

  • RFC Destination issue

    Hi
    I am facing an issue  while providing destination for RFC function module.I dont know  how to get the destination.
    Many of friends suggested me that we can get it through SM59. As I dont have authorisations for SM59,I could'not do.
    Is there any table or other alternate??
    I have one more doubt,
    Say suppose my RFC function module exist in R/3  development system and I am calling it from SCM  development system. assume  that destination for R/3 development system is DA4200.When  we move our calling program and R/3 RFC function module  to Quality system, destination will be changed.For quality system destiantion would be QA4200. How can we achieve it  programatically?/
    do we need to pass RFC destiantion dynamically?/ if  yes? how ?
    Please reply me. It is an urgent
    thanks
    Rama

    Hi Rama,
    We have to define the RFC Destination at the time of Function Module Call.
    Check this link for more:
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
    and this is step by step for SM59
    http://help.sap.com/saphelp_nw04/helpdata/en/26/64f62cfa8911d386e70000e82011b8/frameset.htm
    Sachin

  • Issue with RFC destination during HCM - VDS - IDM configuration

    Hi,
    I am trying to configure HCM and IDM (v7.1) using VDS. I am following the Configuration Guide. While creating the RFC Destination, I specified program ID as LDAP_VD and in Gatewayhost I have entered the host of IDM Server (where VDS is also installed). In Gateway service I have put sapgw00. But when I do connection test, I get u201CERROR: SAP gateway connection failed. Is SAP gateway started?u201D. Looks like it is trying to connect to IDM server and is looking for sapgw00 (on port 3300) and is not able to find it.
    What could be the reason for error? Am I doing RFC destination configuration correct? Do I need to put HCM system host in the Gatewayhost field?
    Regards,
    Anurag

    Hi Anurag
    You have to enter the hostname of the SAP server, not the LDAP server.
    The LDAP connection is configured later.

  • 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

  • Transaction IDX1: Port SAPPRD, client , RFC destination contain errors

    Hi all,
    when I send an IDOC from Xi to R/3 I get the following message in XI monitoring:
    Transaction IDX1: Port SAPPRD, client , RFC destination contain errors
    ERROR= 2:IDOC_ADAPTER(151)
    However everything is maintained correctly (i think) in IDX1. I can upload the IDOC metadata with IDX2 from the R/3 system.
    I seems that Xi doesn't have the clientnumber available. (should be 600) but is not mentioned in the error.
    Did I miss something?
    Thanx Ron
    Message was edited by: Ron van der Sterren

    Hi Ron,
      Settings in XI side.
      1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is R/3 server name and logon tab enter the R/3 logon details.
      Test the connection is success and check the Remote login button it's connecting the R/3 system or not.
      2. Create the Port IDX1 and pass the client number is (R/3 client) and pass the RFC destination which you created above.
    R/3 side
       1. Create the RFC Destination(SM59) with connection type 3, pass the target host pass is XI server name and logon tab enter the XI logon details.
      Test the connection is success and check the Remote login button it's connecting the XI system or not.
      2. Create the TRFC port to transfer the IDOC'S and pass the RFC destination which you created above.
      3. create the logical system in BD54 this name should be same as XI logical system name.
      4. Create the partner profile (WE20) and partner type is 'LS' with inbound parameters and pas the appropriate values.
      Let me know if you have any issues.
    Regards,
    venu.

  • 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

  • Error in Local Message System: RFC destination MB3AP1039 does not exist.

    Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
    Message no. BCOS088
    Hi,
         When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
    Can anyone help me in resolving the above issue.
    Thanks & Regards,
    Mirza Kaleemulla Baig.

    Dear friend
    You have to of following option
    1.Define Service Desk destination in the R/3 systems:
    Note: for this you need to log in the R/3 system.
    Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
    2.a. Go to transaction SM30.
    b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
    c. Press the Continue button in the following screen:
    d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
    e. In the next screen, enter the following information:
    In the RFC Destination you should point to your Solution Manager destination RFC.
    0ss_msg   w   sm_bsmclnt_back    cust620     1.0
    shailesh

  • 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

  • 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

  • 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

  • RFC Destination was incorrect,send complete BP Data again from CRM to R3

    Hello All
    Iam facing in issue in CRM - BP Application due to incorrect RFC Destination maintained for SAP R3.
    Our CRM Testing system (CRO - Client 300) is connected to R3 Testing System (NCQ - Client 300), but when CRM system went for refresh, RFC Destination was overwritten, and due to that CRM system started pointing to wrong R3 server (NCD - Client 002).
    Till we got to know the problem, User had created a BP in CRM and it had flown to incorrect server. later we corrected the RFC Destination , but now the issue is that If I make any small change in CRM BP data, Bdoc  is going in error state and message says:
    Messages for business partner 0090001677:
    No customer is assigned to business partner 4A13ACE0AB356006E10000000A212
    Entry 0500   does not exist in  - check your entry
    I tried to send BP data through middleware tCode /CRMM_Bupa_Send as well, but Bdoc gain got in error state saying :
    Entry 0500   does not exist in  - check your entry
    I think, these errors are coming because system is assuming that it has already sent the data to R3, and it expects certain data to be present in R3 system, which it is unable to find since data for corresponding BP is not present in SAP R3.
    I there any way, transaction through which I can send complete BP data from CRM to R3??? Please help.
    Edited by: Surbhi Goel on Jun 2, 2009 3:25 PM

    Hi Surbhi,
    Could you try transaction CRMM_BUPA_MAP in order to see what mapping the system thinks there is (if any). It then allows you to send (same as BUPA_SEND) or retrieve data. I guess this will run into the same error, but it might be worth a try.
    Hope this helps.
    Sincerely,
    KZ

  • Doubt about RFC Destination in FILE to IDOC Async scenario

    hi
    In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
    For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
    Any specific reason.
    Thanks in advance.

    First you need to have a clear understading of how the idoc adapters works.
    In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
    In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that  u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
    In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
    Hope this answers your ques.
    cheers
    *Raj*
    *POINTS IF SATISFIED WITH ANSWER.

  • Best practice for creating RFC destination entries for 3rd parties(Biztalk)

    Hi,
    We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
    The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP. 
    We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
    We also wanted to know if there are any best practices to optimise on number of RFC destinations.
    Here were a few suggestions we had in mind to tackle the same.
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
    I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
    I would appreciate if you can suggest the best architecture or practice to achieve  RFC destinations in an optimized manner.
    Thanks in advance
    Sam

    Not easy to give a perfect answer
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    -> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    -> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    -> consider this option 2.
    We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

  • Error in Local Message System: RFC destination 10.189.98.10 does not exist.

    Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
    Message no. BCOS088
    Hi,
          When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
    Can anyone please help me in the above issue.
    Regards,
    Mirza Kaleemulla Baig.

    Hi Mirza,
    For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
    Revert for any clarifications.
    Thanks and Regards,
    Avinash.

Maybe you are looking for