Best practice for creating RFC destination entries for 3rd parties(Biztalk)

[alen_mikulic]

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

[former_member66264 · Accepted solution]

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.