Transaction IDX1: Port SAPCP0 client , RFC destination contain errors

Hi Experts,
I am getting following error in SXMB_MONI in IDOC to JDBC scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Adapter
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIAdapter</SAP:Category>
  <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
  <SAP:P1>Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:P1>
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Error: Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
i have created port in idx1 and i imported the idoc in idx2 and i have created rfc destination to R3 in XI, RFC destination is working fine.
Can anyone help me out of this.
Kind Regards,
Praveen.

hi,
>>><SAP:Stack>Error: Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
>>>i have created port in idx1 and i imported the idoc in idx2 and i have created rfc destination to R3 in XI, RFC destination is working fine.
this means that you're checking an incorrect RFC dest
- open IDX1
- click on port SAPCP0
- double click on RFC dest which is over there to open it
- ctrl+F4
does it work?
Regards,
Michal Krawczyk

Similar Messages

  • 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.

  • Error: Transaction IDX1: Port SAPRP1, client ,RFC destination contain error

    Hi All,
      I am faceing the problem while executing the XI ,
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    ============
    It is showing this error and the idoc is not posting to the SAP. When i checked out the IDX2 i am not getting any such structure of our IDOC type, So do i need to create the structure manually, or will it create automaticallywhen the idocs willposted .
    Is there any import and export option for this.
    Please treat this as urgent , thanks in advance...

    Hi Jay,
    how did you create port using IDX1 ,I think you must have to follow the naming convention there.Any user given name might not work.
    I think in your case , create port as SAPRP1 using IDX1.
    can you you give a try  with that.port name exactly same as SAPRP1.
    you may also refer this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

  • Error: Transaction IDX1: Port SAPZ52_002, client , RFC destination contain

    Hi,
    I have a Scenario WebSphere MQ to IDoc. I get the following message in SXMB_MONI when trying to send data.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPZ52_002, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPZ52_002, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have testet my RFC connection in SM59 and it seems to work fine.
    Hope anyone can lead me in the right direction.
    Regards,
    Morten

    I have the following setup:
    IDX1:
    -Port: SAPZ52
    -Client: 002
    -RFC Destination: Z52CLNT002
    SM59:
    -RFC Destination: Z52CLNT002
    -Connection type: 3 ABAP Connection
    e.g.
    Successfully when testing in SM59
    Receiver Communication Channel:
    -Adapter type: IDoc
    -Transport Protocol: IDoc
    -Message Protocol: IDoc
    -Adapter Engine: Integration Server
    -RFC Destination: Z52CLNT002
    -Port: SAPZ52_002

  • Transaction IDX1: Port SAPQA1, client 500, RFC destination  contain error

    Hi experts
    I am configuring XI for MM-SUS scenario, when I try to send Idocs from R/3 to XI I have this message:
    Transaction IDX1: Port SAPQA1, client 500, RFC destination  contain error
    In XI transaction IDX1 I have maintened a port (MM_QA1) and RFC (MM_RFC) that points to R/3
    In XI transaction IDX2 there is no entries
    Some idea how to solve it?
    Thanks
    Nilson

    Hi,
    >>Could you clarify it for me, In XI side Transaction IDX1 I have a PORT and RFC destination to R/3?
    Yes you are correct..
    You should have done this..
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Define Gateway service
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.     
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    Thanks
    SaNv...

  • IDX1: Port SAPIDS, client 800, RFC destination  contain error

    hi
    i changed the client on xi for idoc to file scenario.
    in sm 58 iam getting following error
    Transaction IDX1: Port SAPIDS, client 800, RFC destination  contain error
    regards viju........

    VIJENDER SRIRAMOJU,
    If you change the client on xi for that scenario, make the corresponding changes
    in Idx1.
    Also delete the entries from Idx2. (entries in idx2 are read automatically during runtime)
    There is a howto on idoc scenario in sdn. Just go through that.
    reg,

  • RFC Destination contains errors

    Hello,
    I am doing a IDOC - File scenario.
    for XI :
    RFC  : R3RFC
    Port  : R3PORT
    LS    : XICLNT010
    for  R3 :
    LS   : CLNT090
    RFC : XICLNT100
    Port : XI100
    When the IDOC was sent, its showing up in green color but when I go to SM58, I see the error message, " Transaction IDX1: Port SAPB999, client 800, RFC desestination contains erorrs "
    But when I click on remote logon, the RFC is taking me to XI start sap access screen (same is the case with XI RFC connection, working as expected)
    No messages were shown in SXMB_MONI
    The port specified in the error message and the actual port varies.
    Checked in port... specified a proper RFC destination.
    Where are the things going wrong?
    Checked previous answered posts related to the same and tried few things from them
    dint work out..
    Help !!!
    thanks
    Nikhil.

    Hi,
    Check the User you are providing in RFC Destination is Exist & have the Proper Authorizations
    In XI Side RFC Dest::
    Give the User name & PWD in RFC Destination , Which you are using for R/3.
    In R/3 Side RFC Dest:::
    Similarly Give the User name & PWD in RFC Destination , Which you are using for XI
    Regards
    Bopanna

  • RFC Destination None Error for MIGO

    Hi,
    I am getting RFC Destinatnation NONE error while posting Goods Receipt. GTS service for SD and MM is not active. Error showing for FM GRC01_COST_OBJECT_COST.
    Can any one help in this regard.
    Thanks in advance.
    SP Raj

    Hi,
    Pl find the details below of the error.
    Short text
        RFC destination "NONE" does not exist.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLCK36" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The 'destination' "NONE" for a Remote Function Call
        is unknown.
        You can display the RFC destinations available in the system using
        the transaction SM59.
    Trigger Location of Runtime Error
        Program                                 SAPLCK36
        Include                                 ISAUTO_CK_SAPLCK36============E
        Row                                     812
        Module type                             (FORM)
        Module Name                             PRICE_STRATEGY_NEW
      806 ************************************************************************
      807 *     DOERNER, GRC, 10/11/1999: Add one new strategy:
      808 * 3b. Create costestimate during goods receipt
      809 ************************************************************************
      810     when 4.
      811       if k_debug_loc is initial.
    >>>>>         call function 'GRC01_COST_OBJECT_COST' destination 'NONE'
      813                 exporting
      814                      im_vbeln     = f_mtcom-vbeln
      815                      im_posnr     = f_mtcom-posnr

  • RFC Destination

    I am doing a file--> XI --> IDOC R/3 4.6 scenario.
    R/3 is there in SLD as business system with role as app system and the correspong logical system is maintained in SALE.
    Do we still need to create an RFC destination for R/3 client in XI system. In ta: IDX1 in XI system, there is no port created for R/3.
    When I test this scenario I got the follwing error.
    Transaction IDX1: Port SAP_XIXXX, client , RFC destination contain errors.
    Here port SAP_XIXXX is the tRFC port created in R/3 system by giving the RFC destination created in R/3 for XI system, which we want to use later to send an IDOC to R/3. I am assuming I dont need this port at all to post an IDOC to R/3.
    Please advise.

    Here is my scenario...Sending a file from XI client 105 through XI Server which will be posted as an IDOC in R/3 client (File-XI-IDoc).
    In XI:
    Created RFC Destination for R/3 client (SM59)
    Created Port in IDX1 for R/3 client and loaded metadata in IDX2
    As in my receiver agreement, I already specified sending service as XI105 and receiving service as R/3client....
    Do I need to create partner profile(WE20) for R/3 Client in XI Server?
    Do I need to create partner profile(WE20) in R/3? If, yes, then the partner number in R/3 client should be my business sytem sending the file(XI client 105) or my XI Server client?
    Also, since no Acknowledgement is reqd, I did delete the port I created in R/3 for XI Server. But, I am still getting the following error..
    Transaction IDX1: Port SAP_xxx, client , RFC destination contain errors.
    Here SAP_XXX is the port for RFC destionation pointing to XI, in R/3 client, which I deleted.
    Thanks,
    Steve
    Message was edited by: Steve Hsu

  • Interface RFC destination Error

    Hi, while testing our interfaces we get this error, Stack>Error: Transaction IDX1: Port HED_020, client , RFC destination contain errors
    We have checked IDX1 and SM58/59 and cant find any error.
    Has anybody come across this before?
    Thanks

    Where do you get this error? In MONI or in SM58?
    Make sure that the User Id in the RFC destination has the authoizations to post Idoc's.
    Make sure that the receiver Idoc adapter has a valid Port name and RFC destination values as created in IDX1 and SM59
    Regards
    Bhavesh

  • IDX1 - Port for Subsystem?!

    Hi guys,
    well i gonna receive an IDoc from EDI-Server in native IDoc-Format. This i want to just route through without mapping (IDoc-Tunnel).
    a. In IDX2 i imported the meta-data for the IDocs which will be received.
    b. I made a RFC-Connection Type T pointing to a registerd Server-Program (Connection Test etc. works fine)
    b. in IB Design i imported the IDocs
    c. in IB Directory i configured a Sender-Channel
    When we try to send an IDoc to XI, in my understanding the IDoc-Adapter listens on the RFC and will work with the IDoc. But i guess we forgot sth. because we receiver this error:
    <i>Code 3 (RFC_SYS_EXCEPTION) reported from RFC interface at RfcIndirectCall(IDOC_INBOUND_ASYNCHRONOUS) with TID=0A5E0F0B3E94470D2F67173F
    rfc_error_info.message="Transaction IDX1: Port EDI_Test, client 100, RFC destination  contain errors"</i>
    In the Idoc we posted EDI_Test in the Header-Data for SNDPOR. This error seems to point to IDX1 entry but what should i enter there?! Because the Client is mandatory...
    Could u give me a hand?! What is wrong in my understanding?!
    br

    Hi Sarvesh, well i am nearly desperate on this.
    We have to use tRFC because of a Unix-Program on the EDIServer which connects to the RFC-Destination. As described, the connection seems to work.
    However, because i am not able to test sending an IDoc from the EDI-System on my own i always have to check the EDI-Guy to send data for testing purposes. Well it's not working yet and i am still not getting what might be wrong.
    Even when i give the SNDPOR from WE21 in target R/3 its not working and we get always the same Error message. Again i gonna list what i have done:
    <<[all motivated by the IDoc-Tunneling blog from Michal]>>
    a. Port added in IDX1 , called EDI_Test and Imported IDoc-Metadata from another R/3 System in IDX2
    b. I created a RFC-Connection Type T pointing to a registerd Server-Program (Connection Test etc. works fine)
    b. in IB Design i imported the IDocs
    c. in IB Directory i configured a Sender-Channel
    The EDI-Guy i gave the port-name in XI called EDI_Test but i guess he don't have to use this. Instead he should use Port from target R/3?!
    Target R/3 configuration:
    a. Working RFC-Connection to XI
    b. WE21 'ZXI' for connecting to XI-System
    c. WE20 Partner-Type LS, called EDI with outbound-parameter DESADV
    So do u think port ZXI should be entered by EDI-Guy for sending the IDoc to Target via XI?!
    sorry for my disqualification but its first time i deal with this scenario....
    br

  • XI: idoc 2 file scenario( Contain error in SM58)

    Hi experts,
    Here i am having one issue. i have done Idoc 2 file scenario...i have created material in R/3 successfully. when i have sent the material to legacy system..Idoc was generated Successfully in r/3 but i haven't seen that message in SXMB_MONI..
    i got the error message in SM58 i.e. IDX1 port SAPDE1, Client 220, RFc Destination Contain error.
    plz any one can u help me on this....
    Regards,
    Yadav

    Hi Yadav,
    The RFC port you defined is not correct in IDX1. The Port name must be in the form of u201CSAPxxxu201D, where xxx is the system ID of the backend SAP system.
    Just cross check it.
    Check this for more details:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    Regards,
    Sachin

  • 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

  • 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

Maybe you are looking for