Skip to Content
avatar image
Former Member

More technical info on registered program ID and RFC sender

Hi All,

I was configuring the RFC sender adapter performed the following steps and everythings looks fine.

1. Enter information like, gateway host, gateway service which you can find using transaction smgw.

2. Select Registered Program Id option button and enter any string as a program id.

3. Now go for configuring communication channel. Provide same parameters for Gateway, Gateway Service and Program Id.

Provide rest all required info like application server, system number, user name , password etc.

4. Now activate your communication channel.

5. Go back to your RFC Destination and now test your connection. It should be working.

Before testing your RFC destination, don't forget to ACTIVATE your communication channel.

But Iam curious to know some more detail,

The RFC destination of type T , pointing to itself (saphost and gateway pointing to itself) and if it is tested the RFC it gives me an error that the program ID does not exists.

But only after I have configured the RFC sender comm channel, and then test on the above created RFC , it works..!!!!

Could any of the experts help me what actually happens in background.

i have referred to Shabarish Vijayakumar & Michal Krawczyk, blogs but could not find more details on this..!

many thanks!

Regards

Edited by: gururaj ravindra on Oct 9, 2009 12:34 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 09, 2009 at 10:42 AM

    Hi Gururaj,

    >>The RFC destination of type T , pointing to itself (saphost and gateway pointing to itself) and if it is tested the RFC it gives me an error that the program ID does not exists. But only after I have configured the RFC sender comm channel, and then test on the above created RFC , it works..!!!!

    I think I didn't get your question completely. Are you asking that after creating the RFC Destination (pointing to XI) you tried testing it and it got failed (with the program id error) and then when you made the RFC Sender channel it got successful??

    Is this the question? If yes then when you created a RFC destination with a Program ID and tried testing it, it failed because there was no listener configured to listen the requests coming from this Destination

    When you created the RFC Sender channel, that listener came into existence and the test got successful

    Regards

    Suraj

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Prateek Raj Srivastava

      Hi Prateek/ Raj,

      Thanks for the explanation!

      So this means a JCO destination is automatically created in the PI stack , and is visible in NWA ?

      Correct me if wrong!

      regards

      guru

  • avatar image
    Former Member
    Oct 09, 2009 at 10:50 AM

    This question (about the Program Id ) has been discussed in the forum many times

    please refer this Program ID in RFC Adapter

    and this

    Program ID for RFC Adapter

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 09, 2009 at 11:09 AM

    Hi,

    Your analysis clears say that

    1. There should be two progids one is server and other is client

    in your case you have created progids ,but not established the connection between server and client

    i.e R/3 (server)and PI (client/listener)

    as a result you got the error

    2 .once you have established the connection using CC then R/3 server identified the listeners with the help of established connections through gateway monitor..

    As a result green ..success...

    HTH

    Rajesh

    Add comment
    10|10000 characters needed characters exceeded