XI, SLD & multiple clients for DEV & QA

[Former Member]

<i>Ref: </i>

I have a question regarding the avoidance of duplicated Configuration (Collaboration Profiles, Logical Routing & Collaboration Agreements) for different clients in the DEV/QA landscape.

As we know: many projects have multiple clients in DEV and QA. Here is an example landscape:

SXD_100 - Dev XI server

SED_100 - config dev

SED_200 - ABAP dev

SED_300 - unit test

SED_400 - sandbox

<b>[ 1 technical system : 3 business systems ! ]</b>

LDEV Legacy system

<b>[ 1 technical system : 1 business system ]</b>

SXQ_100 - QA XI server

SEQ_100 - clean config QA

SEQ_200 - ABAP QA

SEQ_300 - data migration prep

SEQ_nnn - yada, yada...

<b>[ 1 technical system : nnn business systems ! ]</b>

LQA Legacy system

<b>[ 1 technical system : 1 business system ]</b>

<b>The problem:</b>

SED_400->LDEV is used for prototyping integration

SED_100->LDEV is used for config development

SED_200->LDEV is used for ABAP development

SED_300->LDEV is used for unit tests

Receiver Determination is able to look into the message for a <b>dynamic receiver</b>, but we are not able to have a <b>sender</b> like "SED*"

<b>The question:</b>

Do we really need multiple sets of configuration in the Integration Directory? Is there a way to re-use the configuration for SED_100->LDEV for the other development efforts?

Any feedback would be greatly appreciated.

Rgds,

Derek

[Former Member · Accepted solution]

Derek,

In my view I don't think its possible. Each of the clients of SAP system is a different technical system as well as corresponds to a different business system.

You have written that your entire DEV landscape is one technical system, which actually is not as each of these clients is configured indivually in the SLD.

So from an SLD / XI stand point each client is a business application.

I don't think we have work around as we are dealing with different systems.

Regards,

Ravi.

Note : please reward points if you find the answer useful.

[Former Member]

Hi Derek,

Since there can only one business system in SLD per client in SAP R/3.

e.g

SED_100 will have lets say BS_100_Dev

SED_200 and BS_200_Dev

In QA

SEQ_100 -> BS_100_QA

SEQ_200 -> BS_200_QA

It is not possible to configure the single scenario catering the Dynamic (multiple) sender agreement to Reciever.

But for QA you can use set transport target in SLD to reflect the BS_100_Dev -> BS_100_QA, where ever used.

This doesnot solve the problem of having dynamic sender service, it is just for information.

We also faced the same problem of testing a scenario from different clients of SAP :(.

Cheers,

Satish