ASCP Plan's Work Order Routings Not Showing In Pegging
(Doc ID 1930041.1)
Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 220.127.116.11 and later
Information in this document applies to any platform.
Ct are in a de-centralized environment with R18.104.22.168.1 version for VCP applications.
Their source is JD Edwards XE. They are conducting legacy collections to load data into ODS.
Ct are noticing that the work order's routing operations are not showing on the pegging screen.
When they look in ODS, they noticed that the routing_sequence_id from msc_routing_operations is same as the work order's msc_resource_requirements' routing_sequence_id.
However, the operation_sequence_id's on the msc_resource_requirements table for all of the work orders are different.
Ct noticed that there is a Note 1537265.1 that stated almost the same problem.
However, Ct disagree with Oracle's recommendation of loading the operation_sequence_id's via legacy collections, since none of the templates for the legacy collections (flat files) require any ID's for any data element.
They believe the pre-process monitor or another seeded concurrent program is responsible for the ID creation and linking.
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