E1: 42: 47: R42500 Does Not Ship Confirm Sales Order Line Which Was Generated and Updated By R47131
(Doc ID 3043977.1)
Last updated on AUGUST 30, 2024
Applies to:
JD Edwards EnterpriseOne Sales Order Processing - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
If a Sales Order line is appended to an existing Sales Order through the R47131 (Ship Confirm Batch Application) report, and subsequently, the lot or location is updated using the same R47131 report, the R42500 process will not perform ship confirmation for that Sales Order line, despite the availability of inventory.
Below error can be seen in the log of report R42500:
Steps:
- Create a Sales Order using P4210 application.
- Create an entry in P47130 for the same sales order so that a new line with BLANK Lot-Location is added in the Sales Order. Ensure there is no inventory available on this lot-location.
- Run report R47131.
- New line (Line number 2) is created on the Sales Order with BLANK Lot-Location.
- Run R42500 report.
- Ship confirm was unsuccessful as there is no item available on the BLANK lot-location.
- Create another entry in P47130. This time update Sales Order (Line number 2) Lot-Location number with a lot number where inventory is available.
- Run R42500 report.
- Ship confirm was unsuccessful.
- In P47130 a new record was inserted by R42500 with BLANK Lot-Location.
- In the logs of Report R42500, Primary Key violation can be seen while trying to insert the record in F47132 (EDI Purchase Order Change Detail - Inbound) table.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |