Skip to Content
0
Former Member
Jul 16, 2008 at 08:21 PM

IDoc Order Processing

138 Views

In a current integration project with SAP, we found that SAP processes inbound IDocs not necessarily in the order which they were received and meant to be posted; leading to undesired order of postings and inconsistent data replication across various systems.

As a result, another SAP developer and I designed a solution where my source system delivered the IDoc to the destination SAP system and we referenced a parent IDoc serial number in the IDoc header. The IDoc processing engine examined this field and validated whether the IDoc referred by that serial number was successfully posted or not. If not, the subsequent IDoc was left queued for processing; however, if the parent was posted successfully, it continued to post the subsequent IDoc. This insured that the postings inside the destination SAP system were in the desired order the business required.

As we take a step in the future and look at streamlining our approach, strengthening our code base, and to continue to maintain business requirements between both the source system and SAP; I hope the developers here can help with my questions.

Is there a way to insure ordered processing of inbound IDocs to SAP without any special or heavy customizations?

For example, if I post a 101 (po receipt) followed by a 201 (goods issue) to a remote SAP system and both Idocs are movements for the same item and storage location, I would want the 101 to be processed first and immediately followed by the 201. Likewise if the movement order was a 102, 101, then 201; I'd like to force the Idoc processing engine to process the three movements specifically in this order without any type of "retry"/"reprocess" construct.

Is this possible?

From the SAP side, to give a baseline of which version/platform; I'm speaking specifically toward SAP release v4.6c and v4.7.

Thanks!