cancel
Showing results for 
Search instead for 
Did you mean: 

To avoid duplicate inbound IDocs

03-10-2021 2:41 PM
3056 views 3 comments
0 Likes
SAP Managed Tags
Subscribe

Hi Experts,

We are receiving 2 files at a time from Dealer portal and it creates a duplicate inbound IDocs via XI system. Marked in Bold are unique keys.

Files Dealer code Order Type Campaign ID External Ref Date Time Action

File 1 ABC ZORD U-00009999 100000001 10/3/2021 10:00:00 Original

File 2 ABC ZORD U-00009999 100000001 10/3/2021 10:00:01 Duplicate

XI team is saying that, this is a standard queue and not able to restrict and avoid the duplicate file before sending it to ECC.

They are sending it to different sequence id from XI to ECC and it requires ECC change to find the duplicate and reject it.

Please help

1) Is there any way it can be avoided in XI/PI system? if yes, what settings has to be carried out (please explain some inputs which helps to take it forward to PI team)

2) if this can be handled in ECC, using Ztable and control record->serialization field, what is the best way it can be avoided?

Please note, the IDoc have split IDoc when the record/segment >5000

Main Unique fields Check

Idoc 1 A_B_C Allowed

Idoc 2 A_B_C Duplicate

Main Unique fields Split Check

Idoc 1 A_B_C Idoc_1A & Idoc_1B Allowed

Idoc 2 A_B_C Idoc_2A & Idoc_2B Duplicate

Hope the above information helps.

Thanks for letting me know your valuable inputs.

Kind Regards.

0 Likes

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member182609
Active Contributor
0 Likes

Try EDIDS and EDID4

You can get the link from the original and subsequent idoc from EDIDS , the subsequent idoc can be filtered on Idoc status

Also you can get link between subsequent idoc and original idoc from EDID4

former_member182609
Active Contributor
0 Likes

You can control this using some custom code in SAP . During Idoc processing add file entry ABC ZORD U-00009999 in a custom table. When the duplicate message comes put a validation if the same file name entry is available in the custom table set the Idoc status to '68' I.e no further processing. In this way, you can avoid duplicate idocs are processing in SAP.If you are storing the file name in any document then based on document level you can check before processing the idoc.

0 Likes

Hi Sridhar,

Thanks for your answer.

Yes, you are partly right that we can make it using custom table but if you see my request, when it has a Split IDocs and the file from Dealer having seconds of difference between two files, then this custom table validation will also omit the split IDocs (Idoc_1A & Idoc_1B) as well and that is a wrong design.

For ex: Please find the attached image.

IDoc1 generated with Split IDoc_1A and IDoc_1B (both are in processing mode as data is huge)

IDoc2 generated with Split IDoc_2A and IDoc_2B, since IDoc2 was generated before the IDoc1 split IDocs then this will be rejected with the help of our custom table validation including the IDoc1 split IDocs. Even if the IDoc2 gets generated after the IDoc1 split IDocs (this will not happen), then the split IDocs 1A and 1B will be rejected as well.

Request:

if you know the EDI tables, Can you help by sharing the EDI tables which we can find the Parent IDoc (IDoc1) and the child/split IDocs (IDoc1A and IDoc1B)?

Thanks.duplicate-idocs-with-split.jpg