Single file to multiple IDOC's (on Multiple R3 Clients):

[Former Member]

Hi,

We have a complex Landscape with multiple (4) businesses (multiple R3) instances and most common R3 --> DEV 4 instances with 5 clients each, QAS 4 instances with 2 clients each with some additional clients, PRD 4 instances with a client each and Training 4 instances with 2 clients each in the Landscape along with BW systems.

We are trying to implement standard MDM - XI - R3 distribution scenario. Only difference being MDM Production will be the Master distribution client and have to be distributing to all the R3 clients. For those who doesn't know SAP MDM - is Master Data Management Engine and within this scenario the output from MDM is standard XML IDOC file.

To achieve this syndication is being planned as MDM production to distribute files to 4 businesses to 4 file share folders. These files will be picked up by XI production and will be distributing(Creating IDOCs) on multiple receivers (R3 --> DEV, QAS and PRD) clients of the respective instances.

The one to one scenario is very simple to build MDM XML file from file adapter to R3 IDOC of IDOC adapter, but for our business it becomes one file to multiple R3 clients (IDOCs) on multiple R3 instances;

My question is: Is there an easy way to configure single file to mutiple R3 client IDOC receivers scenario? Also there might be additions and deletions of the R3 clients based on business requirements. Is there any proposed or already implemented procedure to achieve this complex distribution?

We have planned on trying to define a business system for each R3 client (DEV/QAS/PRD) and to have the integration directories configuration built for all the 47 clients that the data needs to be distributed. With IDOC Adapter is this the only way to go? Also, in future if there are additions or deletions of clients it becomes maintenance intensive and there won't be a quick way to stop the distribution?

Your time and input is appreciated.

Thanks and Regards,

-Raj.

[MichalKrawczyk · Accepted solution]

Hi,

1. first of all : why do you use only one XI (for DEV and PRD) <- this should never be the case

each landscape (DEV, test, PRD) should have one XI

2. Also, in future if there are additions or deletions of clients it becomes maintenance intensive and there won't be a quick way to stop the distribution?

this is not true:

a) if you want to remove one business system

you just need to delete the business system from the receiver deretmination

(one minute)

b) if you want to add - it's the same thing - one minute

if the mappings are the same

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member]

Michal,

Thanks for your answer and FAQ.

I think I am confusing everyone with my long messages!

We already have XI DEV, XI QAS, XI PRD.

But business requirement for the global harmonization MDM scenario is that MDM PRD should be able to distribute the XML files (IDOC fields in GLMAST01 - IDOC format) to all the DEV, QAS and PRD (R3) systems in the landscape. For this distribution XI is used as the integration partner (File adapter picks up the XML file from MDM file share location and IDOC adapter creates an IDOC on the respective R3).

For this specific scenario though XI-DEV and XI-QAS systems are present they are available only for testing phase. After the scenario is moved into production, XI-PRD should be able to pick up the XML file from MDM and distribute it to all the DEV, QAS, PRD R3 systems.

Same file needs to be distributed to 20 DEV clients across 4 DEV instances, 27 QAS clients across 4 QAS instances and 12 PRD/TRN(training clients).

Yes, as you said in your answer earlier deleting a client from the distribution is removing the client from the receiver determination (and removal of corresponding Interface determination, sender agreement and receiver agreement).

Addition of a client for distribution is adding the client (business system) in receiver determination (and addition of of corresponding Interface determination, sender agreement and receiver agreement).

Do I have to maintain all the 59 (Clients from different systems) sets of config within the ID and all the systems in SLD of XI - DEV/QAS/PRD? Even if I do so, Is this the right way to go, defining all the DEV/QAS/PRD clients within all the SLD's of XI - DEV/QAS/PRD?

I am not finding an easy way to architect this.

I appreciate your time and patience.

Thanks and regards,

Rajani Kanth Yalamanchili.

[Former Member]

Samson,

Do, I still have to maintain all the individual clients of the R3 systems as individual business systems or is it fine if they are multiple communication channels within the same business system?

Thanks for your input, will check the references mentioned.

-Raj.

[Former Member]

Hey

AFAIK,yes u have to maintain individual business system for all the clients,if ur using the same business system,then it will go to same system and i guess u dont want that.

thanx

ahmad

Message was edited by:

Ahmad

[bhavesh_kantilal]

> Do, I still have to maintain all the individual

> clients of the R3 systems as individual business

> systems or is it fine if they are multiple

> communication channels within the same business

> system?

If you are dealing with Idoc's / Proxies you need to create one Buss System each for each client.

If you are using RFC"s would not be an issue, but for Idoc's and proxies it is mandatory.

Regards

Bhavesh

[Former Member]

Hi Raj,

Looking at the description that you have posted, i think you will need to look around in the Receiver Determination Page in Configuration.

Check the Section "Configured Receivers", you can add as many receivers as you wish, based on the condition you specify, your message will be routed to the appropriate receiver(s).

check the weblogs, for more information on how to use the above mentioned.

Regards.

[Former Member]

Ahmad,

Problem is, in the scenario there are not only 4 R3 client systems; there are 47 client systems. Basically MDM will take care of splitting into 4 different files for 4 businesses. But, within 4 integration scenarios I have more than 10 clients spanning R3 DEV, QAS and PRD client systems. I was checking to see if all the 47 business systems, CC, Receiver agreement, Receiver determinations, Interface determinations and Sender agreements are necessary or else if there was a way to determine the R3 Client receiver systems dynamically?

Thanks and regards,

-Raj.

[Former Member]

hey

I dont see any reason why u should not be able to send the files to multiple receivers.

u need to create 4 separate receiver communication channels,receiver agreement ofcourse u will have 4 business systems(each with correct logical name of R/3)

thanx

ahmad