Need For Link/peg All Discrete Jobs Related To Final Assembly Together But See End Item As Common
(Doc ID 2131667.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.3 and later
Information in this document applies to any platform.
Qn1:We are running a resource and material constrained plan.
We have an environment where all the Discrete Jobs down the chain of the BOM for a final Saleable Item must always be linked together
and the ASCP scheduling engine must always both suggest planned orders one of one together down the chain, and any existing Discrete Jobs must be planned together (back to back down the chain).
In production this is currently successfully achieved through lot to lot and Project Level Reservation Plan Options as well as hard pegged items.
The problems comes where some of these End Salable Items are MTS and we want to Forecast them.
We can successfully add the project on forecast entries and this links/pegs down the planned orders chain, and then these released jobs are tied together and this is honored by the ASCP Planning engine.
But then of course because the reservation level is project, other works orders on other projects and on-hand inventory considered in planned order calculation, hence the problem.
We also went down the planning group route (reservation level planning group).
This met the requirement of the common supply but the link was broken by the ASCP Planning Engine for both Planned Order and Reschedules for the Discrete Jobs down the chain on a given project.
1. Is there any functionality in ASCP/Oracle that can link the discrete jobs together outside of projects that the planning engine with adhere to?
2. Is there any way to meet this set of requirements with ASCP?
Qn2:Couple of questions.
A) I am assuming with your answer to #2 that you are saying there is not a way to meet this set of requirements with one plan in 12.1.3?
B) When using the functionality that you mentioned for 12.2.5, I do not know that this helps us meet the requirement.
B1) If we ran one plan with reservation level of 'Project', would this help us consider project inventory and project work orders as common supply with trying to use a forecasting/MTS model for hard pegged Final Assembly Items which is required to get the Planned Orders planned correctly?
B2) If we ran one plan with reservation level of 'None', would this help us have ASCP both: I) peg project #'s down the planned order chain (lower level assemblies) for either forecast or sales order demand that references a project, II) keep these project discrete jobs together when rescheduling (in the case of MTO we could reserve the Sales Order to the work either manually or via ATO, but with MTS there will be no reservation on the work order to the demand).
C) With respect the mentioned 12.2.5 functionality, I assume we are talking Sales Order to work order reservations? Does this mean in 12.2.5 if you reserve a sales order without a project to a work order with a project that then it pegs this supply to this demand? I noticed in 12.1.3 that ASCP does not. What other, if any significance is there with the functionality change?
D) Assuming that it is not possible to upgrade to the mentioned 12.2.5 functionality on the 12.1.3 application platform. Can you please confirm this?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!