Configuration settings for RFC-FILE interface

[Former Member]

We have a requirement to test the SAP ECC6.0 connectivity with SAP PI7.1 system with a scenario.

We need to use a RFC in ECC6.0, import the function module in PI and build the scenario.

For this we have created a

1. Logical system in ECC6.0

2. Port in ECC6.0

3. RFC destination in ECC6.0 with a registered program id, type T, gateway host of ECC

4. Partner Profile in ECC6.0

5.Technical System using logical system of ECC6.0(as created in 1) in PI7.1

6. Associated Business system

Somehow our scenario is not working, can anyone suggest with the correct settings.

Rgds

Kishore

[Former Member]

Can anyone give a detailed procedure of the creation of the port, logical system, rfc detination and partner profile for connecting ECC6.0 to PI7.1? In our situation we have this set incorrectly, please help.

Rgds

Kishore

[former_member581827]

Hi,

Please check for the reciever bussiness system and for the reciever interface communication channel has been correctly configured or not.

Regards,

Chandra

[Former Member]

check the receiver agreement configuration and complete ID configuration

Kindly check this will guide u [http://www.riyaz.net/blog/understanding-the-rfc-adapter/]

and [http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm]

[former_member183908]

Hi

-->If the error is with your PROGRAM ID,first in the communication channel maintain the PROGRAM ID and then maintain the same PROGRAM ID name in your RFC destination of type H.

--->If your PROGRAM ID is not registered,register it in the visual administrator.for this consult your Basis people.

-->Thanks for correcting me Rajesh

Thanks

[Former Member]

We also have to manage the configuration aspects , thats a tough nut to crack.

In visual administrator, where do we find the registering a unique program id. Can you suggest with some path.

Rgds

Kishore

[Former Member]

Also should the RFC destination be of type T or H.

[former_member183908]

Hi Kishore,

-->Follow the path:

usr /sap /system id of PI system /DVEBMSG+PI instance number /j2ee /admin

after following the path you can see the go.bat file double click on that your visual admin will open.

-->logon to that,Select services,adapter configurations in that you can find the program id's.

-->RFC destination destination of type T not H.

Thanks

[Former Member]

In PI7.1 we dont have admin folder, can u suggest how to register the program id in PI7.1

I appreciate your help.

Rgds

Kishore

[former_member183908]

Hi

-->The above path which mentioned is for PI 7.0.I dont know about PI 7.1.

but For PI 7.1 also admin should be there.Please consult your Basis People.

Even i dont know much about PI 7.1

Thanks

[Former Member]

>

> Also should the RFC destination be of type T or H.

This is like a client- server communication

You need to register RFC destination Type T only

The important thing in RFC destination Type T is that programId going to mention should be same in both client(in your case PI) and also in server(R/3 in your case)

Once this is done test connection

design a scenario where import the RFC signature to ESR and define a mapping and in ID create a some business service and associate RFc interface and then trigger the same from R/3 .

HTH

Rajesh

[Former Member]

Basically we have registered the program id and also given rfc detination as type T in both the ECC and PI systems. While defining technical system for RFC recevier we have used the logical system

Inpite of all this, the message in SXMB_MONI come up with the same error message:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Technical Routing

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>

<SAP:P1>-BS_Bapi_FileServer</SAP:P1>

<SAP:P2>-BS_Bapi_ECC,urn:sap-com:document:sap:rfc:functions.Z_DISPLAY_NAME</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>No standard agreement found for , BS_Bapi_FileServer, , BS_Bapi_ECC, urn:sap-com:document:sap:rfc:functions, Z_DISPLAY_NAME</SAP:AdditionalText>

<SAP:Stack>Problem occurred in receiver agreement for sender -BS_Bapi_FileServer to receiver -BS_Bapi_ECC,urn:sap-com:document:sap:rfc:functions.Z_DISPLAY_NAME: No standard agreement found for , BS_Bapi_FileServer, , BS_Bapi_ECC, urn:sap-com:document:sap:rfc:functions, Z_DISPLAY_NAME</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error

PLease check and advice.

Rgds

Kishore

[former_member581827]

Hi,

Is both BS_Bapi_FileServer & BS_Bapi_ECC are bussiness systems?

If any one of them is Bussiness service please check adapter specific attributes as well as sender and reciever are reflecting correctly for that Bussiness service.

Regards,

Chandra.

[Former Member]

This error is related to configuration part of ID and I hope that you are able to see the RFC request initiated in inbound payload of PI..

For this to get resolve chk the TestConfiguration option in your ID ..

This is related to agreement you have not assocaited (file adpater) CC to Receiver business system need to do so in Receiver agreement ,if configured already check one more time the interfacename ,namespace business system/service configured so are correct..

Rajesh

[former_member189440]

Hi Kishore,

for file rfc file sceanrio create program id in sm59 in r3 side as connection type as 't' and give the PI ip and gateway host there and now use this in rfc adapter.it will work surely i have done this earlier.it is worked.

[former_member183908]

Hi Kishore,

-->For importing the IDOC,RFC or BAPI from ECC system into PI system we need to configure the ALE steetings.

-->You create the Logical system in ECC,Did u assign the created Logical system to the Client using SCC4 or SALE t-code,if not do it.

-->In PI system you created RFC Destination pointing to ECC system and also create the PORT in PI system using the t-code IDX1,the port number should be SAP+System ID of ECC system and client of ECC system and Logical system should be the LS which you created in ECC

-->Create the RFC destination of type 3 or ABAP connectionn and try with that.

-->If the above destination does not work,

-->In your communication channel mantain the PROGRAM ID first and then give the Same PROGRAM ID in your RFC destination of type H.

Thanks

[Former Member]

Hello Pavan,

Those are all required in case of idoc sending by R/3 system for RFC no need ..

only RFC destination of type T..

Rajesh

[Former Member]

what is the error you are getting, when you try importing the RFC in PI (integartion repository)?

[Former Member]

We are not getting any error in the design or in the configuration and we are able to import rfc's successfully.

[Former Member]

Did you created the RFC destination in PI also

if not create the same in PI also and after that test the RFC destination created in both systems

Rajesh

[Former Member]

Yes I forgot to mention that we also have a RFC destination in PI7.1 of type T with same program ID and gateway host that of ECC. Still this does not work.

Rgds

Kishore

[Former Member]

For RFC you dont need Partner ,profile ..

only required RFC destination Type T on both systems ..

what is the error your are getting are you able test the RFC

just go to one of RFC FM and execute it by providing RFC destination created..

if you are getting any error do just post it

Rajesh