RFC destination & Port Configuration in XI

Hi All,
  I have sap system with 2 client 230 and 231.  The RFCdestination,IDX1 and IDX2 are configured in XI and I am able to send the IDoc successfully.  But in case of client 231 I got a doubt that we can use the same RFCdestination, port if I am going to send the same IDoc.
  As per my undestanding we need to create RFCdestination , port for each and every client separately please tell me whether it is right and sorry for asking silly doubt but got confused to proceed futher.
Regards,
Dhill.

Hi wojciech,
  Thank you one moer clarification required that in case of my sap system I think we can use the same RFC destination,Partner Profile and port because I am going to connect to the same XI server.
And also with regards to IDX2 I think we don't need o add the same IDoc in both the client. Since it is only the metadata please confirm on this.
Regards,
Dhill

Similar Messages

  • 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

  • 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

  • Production Copy Back - RFC's/Ports/EDI

    Before copying back from production to pre-production we want to export the RFC destinations/Ports/EDI partners from the pre-production environment. When the production copy back has been completed we want to import the RFC destinations/Ports/EDI partners copied previously back into pre-production environment. Does anyone have a definitive list of tables that should be copied to perform this task.
    I know SAP identify OSS note 182172 for the EDI partners but what about the RFC's and ports. We know we have to do some manipulation of the ALE/EDI partner/RFC's after but it does reduce the workload greatly rather than having to recreate everything again. We have performed an SQL trace on each area to identify the tables.
    Colin

    It looks infotype for the Unit relationship is missing. How did you copy back or replicate it ?
    Regards,
    Masa

  • RFC Destinations for different clients on same host

    Hi
    I have an SRM and SUS on the same server and the clients are different. I have a flow from SRM to SUS and also back from SUS from SRM.
    Do I have to create seperate RFC Destinations for different clients?
    What about the other details likePort, Partner Profile, Logical system etc, do we have to maintain all for both of them seperately ?
    Regards
    Ajith

    Hi Ajith,
    Do I have to create seperate RFC Destinations for different clients?
    >>> A set of RFC Destination, Port & Parnter Profile is used to connect two systems between one client of source system to one client of Target system. Eg. from clinet 100 of XXX system to clinet 100 of YYY system. So, you need to take this into account and create seperate RFC destination for each different pair of connections.
    What about the other details likePort, Partner Profile, Logical system etc, do we have to maintain all for both of them seperately ?
    >>>In PI, you need to create BS for each different client of SRM & SUS system.
    I hope this helps.
    Regards, Gaurav.

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

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

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

  • Defining a port /RFC Destination on XI for IDOC to File scenario

    When defining a port on XI, what is the client number I am supposed to use to receive the IDOC from R3 to XI. I am assuming that I am supposed to use R3 client number to define the port in XI. Is this correct ?
    Please explain this !!!
    Also I am assuming the same procedure to define a RFC destination in XI. I am using the IP address of R3 client to define the RFC destination in XI to point to R3. Is this correct ?

    hi satya
    u may refer to the doc attached for more insight on the ports
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>

  • Idoc configuration,rfc and port

    whenwe are sending data  from file to idoc then in the receiver communication channel do we have to write the rfc destinations and ports of r/3(Receiver systems)  i.e created in the r/3 systems or that created ion the sender system

    Hi,
    On XI create an RFC destination in Sm59 pointing to the R3 system
    On XI create a port in IDX1 pointing to the R3 system
    and then use these in the Idoc comm channel.
    Also, on the R3 system you would just need the partner profile with an Inbound Idoc in we20.
    Regards,
    Bhavesh

  • No RFC destination is maintained for the port 'SAPERP'

    Hi!
    I am facing with a very strange thing.
    I am implementing a File_to_IDOC scenario.
    Therefore I created in XI system the appropriate Ports in tcode IDX1.
    I use one business system with two clients (SAPERB100 and SAPERB200).
    I defined there of course the appropriate RFC connections (RFC_IDOCERB100 and RFC_IDOCERB200).
    Unfortunately when I go into tcode IDX2 and try to load metadata I get the following error:
    No RFC destination is maintained for the port 'SAPERP'
    Message no. IDOC_METADATA455
    Diagnosis
    No RFC destination has been maintained for logging on to this system for the port SAPERP.
    This means that no structure information can be provided for this port.
    Procedure
    Maintain the required RFC destination for this port.
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    HI Holger
    You need to have a RFC destination created for XI server type 3 (ABAP) to push IDOC from ECC. Similarly you need RFC destination in XI towards ECC to load IDOC / RFC metadata.
    Thanks
    Gaurav

  • 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

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

  • 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

Maybe you are looking for

  • Error message when we do search for claim in Isupplier

    Help Me. GET ERROR PAGE WHEN DO SEARCH FOR CLAIM IN PERSONNALIZATION OF Isupplier Error Page Exception Details. oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT x

  • Can I set the Datasource/Conn-pool credential programmatically ?

    Hi all, Within our ADF BC + Faces application, we use Crystal Report for our reporting solution. Crystal use different db connection from one used by the ADF BC. so I create a Datasource in OAS, to be used only by Crystal Report. Here is my problem :

  • Changes in qs21, qs31, qs41, qdv1

    Hi, pls inform what t-codes should be used to see the changes in qm master data like qs21, qs31, qdv1, qs41 etc?

  • Export to Pages

    I have a Pages document which is a list of items.  I need to alphabetize the list, and am thinking the easiest way to do that is to copy and paste the list into Numbers and sort the list there. However, when I try to copy and paste the now alphabetiz

  • Business Objects Future Carrier

    Hi, I am working in a CORE JAVA Based product as a Core JAVA Developer for nearly 4 years. In Parallel, i have a chance to look into BUSINESS OBJECTS XI as well for last 2 years. Our clients are using BO XI R2 and i have upgraded [newly installed and