Job RECV_01: PO_RECVPUSH failed but RECV_INV succeeded
The job RECV_01 was kicked off by a user for one receipt. It failed at PO_RECVPUSH but the subsequent RECV_INV ran to success, as shown in screenshot below. This happened in production and locked up the inventory transaction at receipt. The receipt was copied from a PO line and the PO was sourced from a requisition.
We believe the job failure was caused by troubled data. Unfortunately we and users haven't been able to replicate the data. What we need now is a temporary work around that could make the program run to success first, and verify if the results are okay or need amending. Users are open to suggestions as they have no clue how the bad data come in the system either.