on 01-02-2014 11:15 AM
Hi,
I am using idoc packaging in PI. In order to test this, I have changed some idocs from 03 to 30 and tried pushing it using RSEOUT00.
Using this method, the idoc packaging does not work.
But when I use WE19 and trigger the same idoc multiple times using repeat factor and executed the idocs using RSEOUT00. By this, the packaging works without any issues.
After this, If i change the status of the idocs executed using WE19 from 03 to 30, it works again fine.
The only think i did not understand is the first approach. Copies of same idoc using repeat factor works again by changing status. But different idocs does not work changing the status. Am i missing anything here?
Regards
Sam
Hi Sam,
In ECC, go to WE20,select required port and Idoc, provide the package size and output mode to Collect Idocs. Once the Idocs are triggered you need to run RSEOUT00 to trigger them to PI, Idocs will be bundled and sent to PI. PI Idoc channel should be configured to received bundle Idocs.
Check if you are missing any step.
Regards,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkat,
The problem I face is that the entire set of payload gets copied for each receiver. We use set of common generic mapping for each service/Party.
If i have 2 idocs in a single message, I would expect the data of 1st idoc to go for a mapping and 2nd idoc to another mapping. But in this case, for the both the mapping both sets of idoc payload gets copied.
It will be too late to enforce mapping change for each party/service. Any other way.
Regards
Sam
Hi Sam,
with IDOC package you will get multiple idoc as same message (XML) in a package then if it is satisfy the condition for two receiver the same message will route to two receiver. If you want to split the message then you need split in mapping or change the scenario to normal IDOC (without packaging).
regards,
Harish
Hi Sam,
In this situation, you can manage these Idocs from ECC.
Create different partner profile for these two Idocs and trigger them accordingly at different times with different variant, with bundling. Message received at PI will be specific to a receiver. It is a small config change at ECC.
Regards,
Pranav
Hi Sam,
IDOC packaging functianality in PI is not depend on how you are triggering the IDOC from source system (by changing the status or by WE19).
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sam - When you say different IDOC's i hope they are of same message type.
Also check for stefan's reply in the below discussion if it helps..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.