Using RFCs

[Former Member]

Hi Experts,

im currently in a IS-Retail implementation (version 4.7*200) in a convenience client with 230 stores, this ones using SRS (Sap Retail Store) functionality.

Some issues about our scenario you should know:

- We are using ITS for the SRS;

- We don't have any middleware (we work with ftp and file integrations);

- All stores have PDC.

As i found in help.sap.com we have some RFCs allowing the integration with third-party provider for SAP Retail Store. We've agreed with the providers that they will develop the third-party system to invoke the RFCs.

So, my questions are:

1) Is this the best solution for our scenario??

2) What do i have to do in our side (SAP) to allow the third-party system integration??

3) Do i have to create RFCs destinations??

4) What's the difference between RFCs and tRFCs??

5) Do you have any example of this kind of customizations??

6) Do you have examples how to invoke the RFCs (outside SAP)??

Thank you very much,

Paulo

[Former Member]

Hi Poulo,

1)Haven't worked on IS Retail, so can't comment on your solution.

2)The Function Modules and BAPIs which are going to be accessed should be Remote Enabled. This is done by making the "Processing Type" in the "Attributes" tab as Remote-enabled module.

3)You will have to create RFC Destinations.

4)tRFC is a type of RFC in which the Remote calls are processed asynchronously on the SAP system. You can get more details on different type of RFCs from:

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

5)Haven't used tRFCs. But know that they are suitable for applications in which the order in which processes are done are not critical.

6)In my project, we invoke an RFC from .NET environment using an SAP .NET connector to access an IS Oil SAP system. The connector creates classes corresponding to the import and export parameters in the BAPIs and we map all the SAP fields to fields in .NET

Hope these inputs helps you.

regards,

Raj.

[Former Member]

Thank you Raj.,

But i still have some issues.

1) Do i have to create RFCs Destination for each RFCs that will be invoked by third-party system??

2) What kind of fields / information i need to fill, to create RFC Destination ??(tcode SM59, i presume?? - This is not done by me, but by the systema administration team)

3) Is it possible to invoke any FM that i create??

4) Who provides SAP .NET connector?? is it provided by SAP?? Do you have any example of code using this connector??

Thank you very much,

Paulo

[Former Member]

Hi Paulo,

1) No need to create Destination for each and every RFC

you are accessing from third party system.

one RFC destnation you nedd to create for that system

to connet to that system.

2) In SAP SM59 is the tcode to create destinations.

go to SM59 and create new destination , you nedd

to seelct type of connection also.

for R/3 system it will be 3 like that.

and the other details depends on the type of

connection you need to provide if it is R/3 need to

give IP of that system.

Hope this will hlep you.

Thanks&Regards,

Siri.

[Former Member]

Thank you Srilatha,

Related to the issue 2) i need more details. In our implementation i don't have authorization to execute tcode SM59, since the administration is made by other team (other company). I never saw tcode SM59.

So i need to ask administration team to create the RFC Destination. Which data do i have to give to administration team allowing the "RFC Destination" creation!!

Thank you very much,

Paulo

[Former Member]

Hi,

You need to give the details of the system to which you want to connect, the ip address, logon credentials etc.

Regards,

Ravi

Note : Please mark the helpful posts.

[Former Member]

I have you got solution on your question. if yes then update me also.

[Former Member]

Hi Paulo,

I am also currently working on IS-Retail Implementaion.

1) We've also used the same scenario as u r going to use.

2) Yes you need to create RFCs as Remote enabled module to access from the third party which ever you are going to use.

3) For these you need to create only one RFC destination using SM59.

Regards

Rafi