E1: 30: Outside Operation PO When Parent Has Lead Time Results in PO Not Having Correct Date

(Doc ID 1621944.1)

Last updated on FEBRUARY 01, 2016

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.


JD Edwards EnterpriseOne : 9.1 version, Discrete Mfg, toole release 9.1
P3003 Routing

Operation sequences display incorrect backscheduling when an outside operation is included in the routing.
The routing application should correctly calculate operation dates to properly reflect start and end operations date.

The issue can be reproduced at will with the following steps:

1. Add a parent with 4 days of level lead time.
2. Set up a routing with an outside operation. Operation sequence 20 (not the first or last operation) has a pay point of zero and purchase order = Y and has a supplier defined. The next operation has a pay point of B. Both have zero hours for run/setup, and zero for queue and move.  (In further testing queue hours were added to show the incorrect backscheduling even more easily)
3. Create a work order in P48013 with a requested date in the future.
4. Run R31410 to attach parts list and routing.
5. Review the routing when the job completes.
6. Note that the outside operation sequence has a start date of 4 days prior, and an end date of 5 days later.
7. The next operation has a start date that is the same end date of the previous operation, and has an end date equal to the requested date on the work order.
8. Review the purchase order and note that the request date is also the end date on the outside operation step.

The issue has the following business impact:
Backscheduling is incorrect, and start dates of routing operations are misleading.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms