Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
Symptoms:
A batch of X12-850's was rejected due to it being "Duplicates". Trading partner was asked to resend the transactions with new number.
When the new set of transactions arrived, there were three transactions that went to T/E because of duplicates.
After reprocessing the communication session, it went through and attempted to move; the mailbox went to M/F. The PO numbers were existing in the ERP system but marked as "Deleted" transactions.
Diagnosis:
The error was caused by a validation against duplicates. Reprocessing (*RCV) the mailbox will bypass the duplicate check (Be sure, that it is the intention to overlook the "duplicity" of the value). The software already knows that the value has been checked for this communication session.
However, the ERP system/iSeries might still reject this due to the operating system's "duplicate key error". Duplicate key error is a state where a record is attempted to be added to a file where the value of that key is already existing in a file where "Key Uniqueness" is setup.
Prescription:
Ask your trading partner to resend the remaining 3 transactions with new numbers.
OR
Ask the in-charge of the ERP system, if there is a systematic way of "removing" the physical records in the ERP files for these PO Number - from the PO Master thru all the children records.
Do you have a CHALLENGE? Let us know HERE.