E1: 42: Enhancement Request to Add Ability for R42500 to Update the Unprocessed Records in F47131 And F47132 With Latest Values Present in F4201 And F4211 (Doc ID 3067574.1)

Last updated on JANUARY 20, 2025

Applies to:

Symptoms

In the current design, R42500 (Ship Confirm Batch Application) creates the record in F47131 (EDI Purchase Order Change Header - Inbound) and F47132 (EDI Purchase Order Change Detail - Inbound) tables which is then processed by R47500 (Inbound Transaction Processor)  to ship confirm the Sales Order.

However, if the R47500 report fails to ship confirm the Sales Order for the first time due to incorrect data in the F47131 and F47132 tables (as described in the scenarios below), and the user later corrects the data, then the subsequent executions of R42500 for the same Sales Order will fail with the following error, even though the data issue was resolved:

Business Case:

1. The customer has the R47500 report (with the purge processing option set to OFF) scheduled to run. This setup ensures that if a user creates a sales order with the correct data but the inventory is only made available after a delay (e.g., a week), the R47500 report will automatically proceed with the shipment. Enabling purging in this scenario would require the user to manually resend the data by running the R42500 report for the sales order.
2. After submitting changes to the Sales Order, the R42500 report is triggered automatically, which in turn invokes the R47500 report (with the purge processing option set to OFF).

The following scenarios may lead to this issue:

Scenario 1 (Lot Location Change): The R47500 report does not ship confirm the Sales Order line due to insufficient quantity at the current lot location. Later, the user updates the LOT/Location column. Despite this correction, R42500 cannot insert the record in F47131/F47132 to ship confirm the Sales Order because the record for the same Sales Order line already exists in F47132.

Scenario 2 (Quantity Change): The R47500 report fails to ship confirm the Sales Order line because the ordered quantity exceeds the available quantity. After the correct quantity is updated, R42500 cannot insert the record in F47131/F47132 to ship confirm the Sales Order, as the record for the same Sales Order line already exists in F47132.

Scenario 3 (Branch Plant Change): The R47500 report does not ship confirm the Sales Order line due to insufficient quantity at the current lot location for the given branch plant. Later, the user updates the Branch Plant column. Despite this correction, R42500 cannot insert the record in F47131/F47132 to ship confirm the Sales Order because the record for the same Sales Order line already exists in F47132.

The R42500 report should be enhanced to update the unprocessed records already present in the F47131 and F47132 tables with the latest values from F4201 and F4211, instead of triggering the primary key violation error, before executing the ship confirm process by R47500 report.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.