E1: 31: The Start and Request Dates are Calculated Incorrectly on an Outside Operation Routing Step (P3112) and the Corresponding Purchase Order (P4310) (Doc ID 3011567.1)

Last updated on MAY 01, 2024

Applies to:

Symptoms

According to KM Note 870315.1, when using a manufactured item with a variable leadtime, it is possible to use the Queue Hours on the outside operation routing step to account for the amount of time it takes for the supplier to complete the operation. However, when the Work Order Routing is created (R31410 or P3112), the Request Date on the Routing and corresponding Purchase Order (P4310) is incorrect.

The Status Changed Date (Alias: DCG) field in WO Header Master Ledger File - F48019 is not updated when a manual change is made to the work order status in Manufacturing Work Order Processing - P48013.

Steps:

1. Create a Manufactured item and Outside Operation (*OP) in the Item Master/Item Branch (P4101, P41026).
2. Create three Item Routing operations where the second is the Outside Operation.
3. In the Routing Operation for the Outside Operation, enter Queue Hours (e.g., 48) that will account for the time the operation requires to complete.
4. Create a Work Order (P48013).
5. Run Order Processing (R31410) over the Work Order. Notice that the system creates a Purchase Order for the *OP item.
6. Review the Work Order Routing (P3112). Notice that the Request Date for the Outside Operation is incorrect and may even be later than the Start Date of the subsequent operation.

Changes

Cause

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