on 05-16-2014 1:58 PM
Hi Experts,
We have one idoc to jdbc interface.
Message spliiting is done at Interface Determination level.Idoc will be splitted to three reciever interfaces. All three flows are connected to same database..
It has to execute the message in EOIO.
The other flow should not get executed until the first is completed.
To achieve EOIO, we have checked "Maintain order at runtime" box in ID.
The issue is: when the idoc gets created with program,it comes to PI and gets splitted to three flows.but it gets failed in PI because sometime the 2nd flow gets executed before the first one.
If we reprocess it manually, it ll be successful.
If we trigger the same idoc using WE19, it gets processed through PI successfully and in CORRECT ORDER.
All three flow are using same channel to connect to database.
Please share your views.
Thanks
Vikram
Hi All,
In JDBC reciever channel, we have Transaction isloation level option under Advanced tab..
We changed it to serializable and it worked.
Thanks for your inputs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vikram,
Thats the normal behavior if its following the same queue. Ideally it should not allow you to restart the 2nd message after split if the first is in error.Is this happening in all environments?
Can u try creating 3 different channels with different collaboration agreements in your Dev?
regards,
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vikram,
Ideally Maintain Order at Runtime should work at am Interface Determination level as it would sequence the 1st executed OM in the interface and then 2nd and then 3rd. Can you also explore the options of having an EOIO QoS determined based in ABAP logic from your ECC system.
Regards,
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.