My Oracle Support Banner

E1: 31: Back Schedule Routing Hours Operation By Operation For Fixed Leadtime Items Enhancement Request (P3112) (Doc ID 2759035.1)

Last updated on MARCH 10, 2021

Applies to:

JD Edwards EnterpriseOne Product Data Management - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.

Symptoms

The Routing Operation Start Dates use the average time per operation for Fixed Leadtime (parent) items. For example, where there is 1 day, then 12 days, and then 2 days for a three step routing, the fixed leadtime days should not be distributed (averaged) evenly. Business requirement is for the standard routing hours for each operation be included in the routing start date calculations for fixed leadtime items. The leadtime rollup currently uses the total routing operation hours to calculate the fixed leadtime, so if operations would vary in duration, the total leadtime accounts for the sum of hours or days across all operations, such as 15 days as in the above example.

The leadtime rollup currently uses the total routing operation hours to calculate the fixed leadtime, so if operations would vary in duration, the total leadtime accounts for the sum of hours or days across all operations, such as 15 days as in the above example.

The attached F3112 routing currently averages the operations in an arbitrary fashion, such as 5 days per routing step, not accounting for the variation of hours as setup in the standard routing, such as 1, 12, and 2 days. This makes for inaccurate routing start dates in the assigned routing for fixed leadtime items.

Client requests that the standard routing hours for each operation be included in the routing start date calculations for fixed leadtime items.

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!


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