USAGE_RATE Collected Into MSC_ST_RESOURCE_REQUIRMENTS From JD Edwards Incorrect
(Doc ID 2307419.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Value Chain Planning Integration Base Pack - Version 11.4 and laterInformation in this document applies to any platform.
Symptoms
A discrete job is coming over from JDE into VCP. When the resource requirements for the job are collected into MSC_ST_RESOURCE_REQUIREMENTS, the USAGE_RATE is set to: SCHEDULED_QUANTITY / OPERATION_HOURS_REQUIRED
This is incorrect. When looking at the Work Order in JDE, we see a work order quantity of 100 and the following Run Hours for each sequence.
| Op Seq | Machine Run Hours | Labor Run Hours |
| 10 | 3.85 | 3.85 |
| 20 | 3.85 | 3.85 |
| 30 | 5.00 | 5.00 |
| 40 | 10.8 | 10.8 |
If we look at MSC_ST_RESOURCE_REQUIREMENTS, we see that the USAGE_RATE is the SCHEDULED_QUANTITY / OPERATION_HOURS_REQUIRED.
| Op Seq | Machine Run Hours | Labor Run Hours | USAGE_RATE |
| 10 | 3.85 | 3.85 | 25.9740259 |
| 20 | 3.85 | 3.85 | 25.9740259 |
| 30 | 5.00 | 5.00 | 20.0000000 |
| 40 | 10.8 | 10.8 | 9.2592592 |
Ultimately, when the plan is run, the USAGE_RATE is used and multiplied by the Job Quantity and the total Resource Hours become super inflated.
| Op Seq | Job Quantity | USAGE_RATE | Resource Hours |
| 10 | 100 | 25.9740259 | 2597.41667 |
| 20 | 100 | 25.9740259 | 2597.41667 |
| 30 | 100 | 20 | 2000.00000 |
| 40 | 100 | 9.2592592 | 925.933333 |
Changes
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |