Skip to Content
0

Multiple IDOC's into 1 single file based on IDOC's triggered ID with out BPM concept

Aug 07, 2017 at 01:10 PM

74

avatar image
Former Member

Hi Experts,

My scenario is like ECC– PI — BPM–PI—Third-party System. Where the BPM collects 10 IDOC based on IDOC’s generated on ID & merge as one single file. one confirmation IDOC from R/3 triggered to specify that these 10 IDOC’s are triggered on that particular ID for merge call and then process to target as one single file through PI.

Now system is upgrading to single stack where the client do not want any BPM’s (licensing also taken like that). So please help me on this to achieve with out BPM concept.

Thanks & Regards,

Ham

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

avatar image
Former Member Aug 07, 2017 at 01:53 PM
1

Hi Abdul,
From the explanation it wasn't clear to me what your correlation criterion is. If you could direct all messages that should be correlated to the same partner profile, you could use IDoc packaging to bundle the messages on ECC side and create both the output file and confirmation without BPM. If you cannot bundle the messages in ECC, there is no way to do it without BPM unless you want to use a temporary store like a database or a temporary file.

Regards,
Patrick

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Aug 07, 2017 at 02:51 PM
0

Hi Abdul,

If the requirement is to merge the idocs and send this as a single message to the target system, you can do this easily in single stack PI without BPM.

You need to do 2 things mentioned below -

1) Need to select collect idocs and no of idocs to collect in ECC- we20 under corresponding outbound idoc message type maintainance.

2) Select Collect multiple idocs in single message in sender IDOC_AAE CC.

Regards,

Apu Das

Share
10 |10000 characters needed characters left characters exceeded
Rajesh Ginka Aug 07, 2017 at 03:29 PM
0

Hi Apu and Patrick

In my case bundling of Idoc is done on the basis of RUN ID. Under one Run Id 'n' number of payment idocs can be triggered and all of them should be merged in single file.

If it is not possible without BPM then please suggest the possible ways in R3 side.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Adding to the above, there are multiple RUN ID through which client triggers their payment idoc, for every RUN ID initiated one output file should be triggered.

0