We are running R/3 4.6C and XI 3.0.
I have the following BPM scenario:
RFC -> BPM -> SOAP -> Non-SAP system (NSS) -> SOAP -> IDoc.
Our R/3 landscape is: 2 Dev clients (030 and 041), 1 QAS client (010) and 1 PRD cleint (010). Our XI landscape is: 1 Dev/QAS (XID) server and 1 PRD server (XIP).
The NSS currently has a UAT environment which I have successfully working against QAS . However, a new requirement has been raised to set up a Training system (TRN) on the NSS and they want to hook this into QAS. This needs to run concurrently with the UAT environment.
I thought this would be simple enough to do - just create a new RFC destination in R/3 and setup a new configuration scenario in XI etc. However, this won't work because I can only create one Receiver Determination for the RFC on QAS (only 1 client so only 1 Business System). This RD can therefore either point to the UAT BPM or the QAS BPM but not both.
I have considered the following solutions - none of which fill me with joy:
- 1. Try to pass a parameter to the RFC from the ABAP that calls it that allows me to use the conditions in the RD i.e. if flag = X then use QAS otherwise use TRN. Not sure that this is even possible though.
2. Create a second copy of the RFC so I can create a second RD. But this would mean creating new design time objects for mapping etc.
3. For the UAT and TRN scenarios, make use of the Receiver Service field in the RD to allow multiple RDs for the RFC in QAS - assuming I've understood correctly how this field works
Hope that all makes sense - any comments on these solutions or suggestions for a fourth way would be gratefully appreciated!