on 05-01-2013 7:04 PM
Hi,
We have File->PI->IDOC Scenario where we there so many back to back files are being processed with a time difference in milliseconds in ECC pertaining to the same object (for example, Purchase Order) which are creating an IDoc in SAP but until the previous Idoc is saved another payload comes in the system and finds the object is locked by the first one therefore the later payloads are failing.
Please advise how should we resolve this scenario.
Thanks,
Chandravadan
Hi Chandra,
Try to use the Exactly Once in Order in the File Sender channel. If not use the Queue processing in the IDOC receiver Channel. Also don't post the IDOCs immediately in ECC, instead you can collect them and then schedule the IDOC processing program that processes the IDOCs in order.
~Srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srini,
Thanks for the reply. Could you please advise where should I collect the IDOCs in ECC or PI?
Do I need to change anything in the Interface or this can be done independently. Could you please also provide a couple of steps as to what I need to do to schedule then as batch job.
Thanks,
CJ
Hi Chadravadan
See my response to your post.
If the requirement for IDoc processing is not real time, you can change the inbound partner profile to process the IDocs in Trigger by background program option. Subsequently you can schedule a background job to run report RSEOUT00 with the message type every 10-15 mins or as per agreement with the process team.
this offcourse needs to be done in ECC.
batch jobs can be scheduled through SM36 in ECC. You need to enter the report name with variant having your message type.This can be done by Basis team as well.
Hope it helps.
Ambrish
No need to change anything in the interface. You need to collect the IDOCs in ECC by following the below steps.
1) Change the partner profile configuration for your IDOC type of respective partner by making the processing type as Trigger by background program.
2) Then schedule the program RBDAPP01 with the IDOC status 64 & Packet Size as 1 with your Message type & the partner number. This will process the IDOCs one by one and will avoid the locking issue.
Hope this helps!
~Srini
Chandravadan,
This is really strange behavior, we can create multiple purchase orders in one shot in ECC.
check with ABAP Team and ask them to fix this issue.
PI interface point of view you are creating IDoc in ECC but IDoc status failure where other PO creation under process right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Data locking happens when you are accessing Master data objects while PO creation or in any other transaction. If the data locking is for a specific data object, you have workarounds in ECC to apply delay in read when object is locked. This is due to high volumes of transactional data executing concurrently in ECC.
cheers,
Ambrish
Hi Chandravadan,
If the requirement for IDoc processing is not real time, you can change the inbound partner profile to process the IDocs in Trigger by background program option. Subsequently you can schedule a background job to run report RSEOUT00 with the message type every 10-15 mins or as per agreement with the process team.
Hope it helps.
Ambrish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In addition to above reply, you might want to see the idoc batch processing from this thread. please check Michal reply.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.