E1: 42: Sales Order Entry (P4210) Places an Order Back on Hold that is Past the Status Limit for Changes (Doc ID 2875817.1)

Last updated on JUNE 09, 2022

Applies to:

Symptoms

Sales Order Entry (P4210) places a sales order on hold even though the sales order has a line has been pack confirmed and at the Status Limit for Changes. They release the orders, pack confirm them, the orders sit for a few days and they go back on hold.

If an order line is past the status limit for changes a change to the order should not place the order back on hold.

Steps to reprioduce:

1. Create a Customer (2259) with an A1 Hold in Customer Billing Instructions.
2. Setup a Sales Order Entry (P4210) version with the Status Limit for Changes set to 560.
3. Create a 3-line sales order. Status is 520/540 on all 3 lines.
4. Order went on A1 Hold.
5. Use Release Held Orders (P43070) to release the A1 Hold.
6. Verify Hold Code was removed from all order lines. Order is no longer on A1 hold.
7. Run Pick Slip Print (R42520) and Ship Confirm (P4205) on second line only.
   1. Line 1 and 3 are below the Next Status Limit of 560
   2. Line 2 is greater than the Next Status limit of 560 and was shipped to the customer
8. Using the same SO Entry Version (P4210), change the Requested Date on Line 1 to a Date in the future and save the order.
   1. The Order (all three lines) are on A1 Hold.
   2. The status limit prevents changes to individual lines but does not prevent the order from going on hold f a change is made to a different line.
   3. Because the hold is setup on the Customer, any change to the order for that customer will trigger the order to go on hold.

Cause

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