Creating a transport containing RFC destination entries

Hello,
I hope someone can help me.  I'm trying to remember the 3-4 tables which need to be exported to recreate RFC destinations.  We are performing a refresh of our test system.  Rather than re-create all the RFC's I'd like to make a tranport of them now and re-import them after the refresh.  Does anyone know which tables I need?
Thanks,
Ben

Hey Matt,
The link you sent points to the thread I just created. 
Ben

Similar Messages

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

  • RFC destination error in transport

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

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

  • Transporting RFC Destinations

    Hi All,
    We will be doing a client copy of our QA server and before we go ahead with it, we need to transport the
    RFC destinations so that we can import them later after the refresh.I have searched in some forums and
    found the way of exporting from . Can anyone give me a SAP note or procedure of transporting RFC
    destinations.
    Regards,
    Ershad Ahmed

    Hi Subhash , Stefan and Prasanna ,
    Thank you for the replies .
    I tried this on my machine . went to SE01 -
    created a transport request and then added Tables which were mentioned by Stefan and then i gave the target system and released the  transport request.
    After i released it i checked the logs and found this which says t hat 4908 entries had been exported
    Summary:
      1 COMML exported
      1 COMMT exported
    28 DELETE commands exported
    Totally 4908 tabentries exported
    are there any other steps which i need to do or im all set??
    Regards,
    Ershad Ahmed

  • RFC - XI - WEBSERVICES scenario - Where to create RFC Destination

    Hi  Experts
    For my RFC - XI - WEBSERVICES scenario, I have to create one TCP/IP RFC destination on R/3 system with the following details
    RFC Destination Name    : XXXX
    Connection Type            : T (TCP/IP)
    Activation Type              : u201CRegistered Server Programu201D
    Program ID                      : YYYY
    Gateway Host                : R/3 Details ..??
    Gateway Service           : R/3 Details ..??
    My Function Module (Remote-Enabled) - u201CZZZZu201D is defined in R/3 System.
    This Function Module should be communicated with the target system i.e. NW XI system 
    As per the Note from SAP Help: To be able to communicate using RFC, you need to define the target systems as RFC destinations in the sending system(R/3)
    Target system u2013 XI Server
    Sending system u2013 R/3 System
    Are my details provided are good enough as per my explanation? Please guide me in this regard.
    QUESTION : Where exactly do I need to create the RFC Destination(SM59)? on R/3 side or on XI side?

    Refer the following link-
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1636235450DB01012070359836134304End?blog=/pub/wlg/1438
    what are the inputs should be given to Gateway Host and Gateway Service while creating RFC Destination??
    Open transaction SMGW on the R/3 system and choose
    Goto -> Parameters -> Display. Beneath Attributes there will be the
    entries 'gateway hostname' and 'gateway service'.#

  • RFC destination for RFC to File scenario

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

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

  • RFC Destination for RFC adapters?

    What RFC destination is used by RFC receiver adapter?

    Hi SSG,
    You create remote function call (RFC) destinations on the J2EE engine so that SAP BW can make function calls on remote systems.
    Look at these threads.. Shud help u out..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/44/7c95731a9c5918e10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • Checking RFC destination availability

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

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

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

  • RFC Destination could not be created  in TREX administration tool

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

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

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

  • 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