E1: 42: 47: Error "F47132_PK" Occurs And R42500 Does Not Ship Confirm If a Line With An Already Existing Unprocessed Record is Present
(Doc ID 3043977.1)
Last updated on DECEMBER 10, 2024
Applies to:
JD Edwards EnterpriseOne Sales Order Processing - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
R42500 (Ship Confirm Batch Application) report does not ship confirm the Sales Order line for which an already unprocessed record exist in F47132 table. Below are the few few scenarios:
Scenario 1 (Lot location change): R42500 report does not ship confirm the Sales Order line which was added and later LOT/Location column was updated by R47131 (EDI Inbound Purchase Order Change) report.
Scenario 2 (Quantity change): R42500 report does not ship confirm the Sales Order line on which the ordered quantity is updated for which an already unprocessed record exist in F47132 table.
Scenario 3 (Branch Plant change): R42500 report does not ship confirm the Sales Order line on which the detail Branch Plant is updated for which an already unprocessed record exist in F47132 table.
Below error can be seen in the log of report R42500:
Steps for Scenario 1 (Lot location change):
- 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 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.
Steps for Scenario 2 (Quantity change):
- Prerequisites:
- Customer Master’s Billing Information: Partial Shipment and Partial Order Shipment is not allowed. Backordered is allowed.
- P4205 processing option:
Tab Edits, #1, #2 and #3 is set to “1”.
Tab Process, #3 Backorder or Cancel Unshipped Quantity is set to “1”.
- Create Sales Order with one line. Make sure quantity is not available. This sends the Sales Order to Backorder.
- Run R42500 report. This creates an unprocessed record in P47130 application for Document number = Sales Order Number.
- Change the quantity ordered to 1 on the Sales Order.
- Re-run the R42500 report.
- 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.
Steps for Scenario 3 (Branch Plant change):
- Same Prerequisites as Scenario 2.
- Create Sales Order with one line. Make sure quantity is not available. This sends the Sales Order to Backorder.
- Run R42500 report. This creates an unprocessed record in P47130 application for Document number = Sales Order Number.
- Change the detail Branch Plant on the Sales Order to a Branch Plant where quantity exists. Changing it from ANKM001 to ANKM002.
- Re-run the R42500 report.
- 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 |