Hello!
We have implemented an IDoc -> XI -> IDoc scenario with complex mappings and enhanced receiver determination using the value mapping API in which about 15 different R/3 platforms send IDocs to XI for internal ordering.
All R/3s are using standard IDoc types like DELFOR.DELFOR02, DESADV.DELVRY03, ORDCHG.ORDERS05, ORDERS.ORDERS05 and ORDRSP.ORDERS05. As XI gets more and more used additional projects are coming up in which we will also use exactly the same IDoc types.
Especially when using enhanced receiver determination it now gets extremely difficult to separate the different business processes once they use the same IDoc types. The projects do not only share the same receiver determination object but what is even worse they also share the same message mapping object to determine the receiver. This makes development, testing and MTP extremely difficult and requires coordination over several project teams.
Within R/3 business scenarios can easily be separated using different message codes and message functions. However, once the R/3 post IDocs to XI there is no clear separation possible any more.
Of course, every project can implement own Java classes for enhanced receiver determination and transport the archives separately but still the problem is that all the projects using the same IDoc message type share the same message mapping object to the determine the receiver. This means that it would be necessary to fill the input parameters for the enhanced receiver determination classes of ALL projects within the same object. Either by putting logic in the graphical mapping or writing another Java function to call the different Java classes for enhanced receiver determination based on the message code and message function.
From a design perspective it is no good approach to mingle logic for different projects and business scenarios in the same development objects. What alternatives do we have? Does SAP plan to support a separation using message code and message function for IDoc scenarios in the Integration Repository?
Regards, Tanja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.