Storage of IDOC definitions in Integration Repository

[Former Member]

Hi there,

I'm trying to define development standards for the use of XI and I can't seem to find any recommendation for the storage of SAP interface definitions (IDOCs, RFCs, etc)within the Integration Directory.

We have an environment with multiple SAP systems including regional R/3 systems which have differing definitions of standard IDOCs - eg different ORDERS05 IDOCs, so do I need to store these definitions in system specfic SWCV?

My thought is to create a Product in the SLD (OUR_BASIS) with multiple SWCV relevant to specific SAP systems (OUR_BASIS_R3_EUROPE, OUR_BASIS_R3_USA etc) each of which could be brought into the Integration Repository to store the system specific objects. The names are non-SID specific to prevent naming issues moving through development, quality and live XI environments. I would then link the product to each of the SAP systems in the SLD, adding new SWCV as more systems are put into the SLD.

Does this seem like a reasonible solution? Does anyone else have or know of other recommendations?

I will be grateful for any assistance and will dish out reward points as appropriate.

Many thanks,

- Ian

[Former Member · Accepted solution]

Hi Ian,

I tried to understand the reason of why would you want to create custom software components in your SLD for multiple SAP systems and import IDocs arising out of these systems into different software component versions? I guess this would defeat the basic purpose of developing objects under software components and the idea of developing integration objects (mapping, data type etc) under software components and not based on phycial system or geographical location.

Let's take an example. If you consider software component X release 1.1 installed on SAP system A. Consider this is a standard software component version delivered by the vendor. And you don't have any authorization to change the objects under this software component. In such scenario, whether you have this software component installed on SAP System A or B or C you just need to import it once under that software component version. Say IDoc ORDERS05. Irrespective of which system you download it from, it's definition is going to remain the same.

Also, system dependencies and actual source and target definitions should not be part of your software component versions. They should be in Integration Directory and should be kept independent of the software components.

Any custom development will be obviously grouped under custom software components.

Message was edited by: Anand Shankar

Message was edited by: Anand Shankar

[Former Member · Accepted solution]

The reason behind wanting to do this is that we have a very large infrastructure with over 100 SAP instances, this includes four regional R/3 systems each with extended ORDERS05 (to take your example) IDOCs which are not compatible with each other - therefore we need to use different definitions depending upon which R/3 system is being integrated.

We're embarking on a period of high growth in SAP XI with a great many custom developments and it does not seem practical to have to import IDOC definitions multiple times into each SWCV - in the same way that it does not seem sensible to have all of our SAP objects under one SWCV (e.g. SAP BASIS) as there would be a great many definitions which will lead to confusion.

I'm simply trying to find a way where multiple SWCV can use the same IDOC definition without importing it to each SWCV or dumping everything under one SWCV.

Does this make my purpose clearer?

[Former Member]

It can be a good idea. I can see you centrally imported IDoc, RFC to a shared "library". But if you keep possible context object you may want to set up by different developer, and future different SWCV release into consideration, I am not sure what is the advantage of doing so.

[Former Member]

Hi,

Though the solution looks reasonable, there might be conflict when integrating with different versions of idoc.

Make sure u take care of these things.

[Former Member]

What do you mean by this? Different versions as provided by SAP (MATMAS02, MATMAS03, MATMAS04 etc)? Different versions as provided by an upgrade to a SAP system? Or diferent versions as extended by the company (Z segments)?