SAP PI to Third Party system through RFC Connectivity ??

[Former Member]

Hello All,

We have the following PI Scenario....

SAP HR (IDoc) --> SAP PI -->(RFC Connectivity) Third Party system. (Asynch)

Response

Third Party system.(RFC Connectivity)  ---> SAP PI -->(IDoc) SAP HR (Asynch)

kindly suggest me how to configure the RFC Adapter in SAP PI to connect Third Party system.

Best Regards,

Suresh S

[Bhargavakrishna · Accepted solution]

Hi Suresh,

You can go for IDOC to RFC synchronous scenario.

Ask your third-party team to give the RFC and ask how frequently they are going to send data through RFC and How will they send the data to PI through RFC?

In pi we will just import the RFC structure, there should be some pgm to trigger the RFC from third party system to PI.

Ask your ABAP team (if possible) to develop a program, to trigger that RFC to PI with the data.

Create RFC destination by using the T code sm 59 and Program ID and use the same program id in RFC communication channel.

refer below links for your reference.

http://www.saptechnical.com/Tutorials/XI/RFCtoSOAP/page1.htm

http://www.saptechnical.com/Tutorials/XI/RFC2WebService/Page1.htm

Regards

Bhargava krishna

[deepak_shah]

Hi Suresh,

Please check below link.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/09/19/exchanging-idocs-with-non-sap-sys...

Regards,

Deepak

[MichalKrawczyk]

Hi,

with non SAP RFC it's a bit different then described by Bhargava krishna

for RFC sender (so way back)

1) set up the standard RFC channel where program ID is the same as in saprfc.ini file

2) make sure the RFC metdata repository points to the SAP system where medatada for this FM exists

3) you need to switch off sender system verification in advanced settings

Regards,

Michal Krawczyk 

[Former Member]

Hi Michael,

We are planning for this approach,,

Non-SAP (RFC)--> SAP PI --> SAP HR

1)  Sender RFC Adapter configuration (Non

  Application Server (Gateway) -->  From third party system

·         Application Server Service (Gateway) --> From third party system

·         Program ID-->  Use same name both in third party and RFC Sender channel.

2.)    RFC Metadata Repository Parameter {mandatory}  (Hope it is SAP HR system which has the BAPI’s defined there)

           The RFC metadata repository parameters identify the SAP system containing the repository for the RFC metadata.

           This does not necessarily have to be the sender system. The function to be called has to be defined in that system.

Do you see any difficulties in this approach here?

One more query here.,

Our requirement may ends up with this way for the response...

SAP HR --> SAP PI --> Non-SAP

·         To use the IDOC Adapter the external system has to completely and correctly implement the tRFC Communication protocol including TID handling.

·         For Idoc Metadata in IDX2 RFC-Destination (connection type 3) behind the corresponding port definition(transaction IDX1)

points to the SAP reference-system (SAP HR) and not to the external RFC-client.

Best Regards,

Suresh S

[markangelo_dihiansan]

Hello Suresh,

Although I have not tried it, there is an option in the RFC Receiver Adapter to use an External RFC Server instead of an SAP system.

Hope this helps,

Mark