Idoc to multiple output files - configuration

[Former Member]

I have got a single idoc type being output from my R/3 system.

Within the idoc is a marker that determines the mapping that the idoc should undergo in XI.

I have set up all the individual mappings, and have tested the flow from R/3 to flat file one message at a time.

However I am uncertain as to how best to configure this in the Integration Directory.

I understand that I will need to set conditions within the configured receivers in the Receiver Determination for the idoc, but after that I am uncertain as to both best practice and most efficient method.

Do I need a separate service for each output?

Do I need to set up Intergration Processes?

How should I set up the Receiver Determination?

Regards

C

[Former Member]

I think I need to give you a little more information here, as I am still not sure what to do.

I have an idoc, roughly like this

ZT1

--IDOC

--EDI_DC40

--ZT1_VERS

-

---

FILE_TYPE

-

---

TYPE1

-

---

details

-

---

TYPE2

-

---

details

-

---

TYPE3

-

---

etc

The FILE_TYPE element determins which of the TYPE segments I am interested in and what the output file is going to be called.

I have created the relevant Message Maps and Interface Mappings for each type.

I have tested all of these by creating configuration scenarios one at a time to ensure that they are correct.

I have a Business Service with a communication channel for each of the types.

Where do I go from here?

I am assuming that for each FILE_TYPE, I will have a row in the configured receivers section of the Receiver Determination.

But that is where I get stuck.

How should I set up the remaining configuration?

Regards

C

[Former Member]

Hi Chris,

I am not really sure about your question but:

Yes you will need one service per output if the output goes to a different system (service defines a system to receive a message).

Now it depends on your process what you want to get as a result.

If there are only some conditions which determine if one receiver should get a message or not you can put them together in one condition as a chain with OR .

If the condition defines the receiver system and per condition there is another system, you need a receiver determination per receiver (with its own condition for the message!).

Integration processes: I think you are talking about BusinessProcessManagement?

No, you don´t need them as long as you don´t work with complex business process e.g. to modify messages or append them within XI area (or other funny things you can do here.) BPM is a kind of workflow and enables you to do MORE than only send message from a to b refering to a condition.

Receiver determination:

Add a new one after adding a new sender agreement (don´t add any receivers i this agreement!) by starting in the middle of the rec.agr. screen. Per condition line you can add one or more receivers. (First you need to complete your interface mapping(s) in Int. Repository!)

After completing this screen save and continue in the screen area at the end of the screen. Here refresh and add now per receiver (with NEW SPECIFIC) the implementation from the int.repository.

(Always use NEW SPECIFIC for the different columns here).

As I wrote your threat is not really clear and sounds like you need complex help. Hope this helps a little bit.

For more questions to this issue add them here...

regards

Dirk