Professional Documents
Culture Documents
Upcoming: Release from Advanced Supply Chain Planning (ASCP) to Oracle Process Manufacturing (OPM)
Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 2
Upcoming Advisor Webcast Schedule
Upcoming: Release from Advanced Supply Chain Planning (ASCP) to Oracle Process Manufacturing (OPM)
Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 3
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
• This Release webcast and Doc ID is the third element of ASCP with OPM as:
– Collections: see How Should I Start my ASCP Integrated with OPM Implementation?
(Doc ID 1146014.1) and Webcast (Doc ID 837233.1), June 2011
– Planning: see Introduction to OPM/ASCP Planning (Doc ID 1518372.1) and Webcast
(Doc ID 837233.1), Jan 2013
– Release: see FAQ – ASCP to OPM Release (Doc ID 2042233.1) and Webcast (Doc ID
837233.1), Aug 2015
– Of these, the most important element of an OPM/ASCP implementation is the
collection of recipe details, including for the subject of Release. Please see the Doc ID
1146014.1 where there is a list of notes designed to explain, identify and resolve
issues with the collection of recipe data under the heading List of Recipe Collection
Notes
• For the circumstance where the User Requires a high level of control
• Planner Releases the Recommendation
• Process Execution (Production Supervisor) decides what to
Implement
• Relatively labour intensive
• Profile GMP:Auto Implement APS Suggestions is No
• Mandatory approach if Document Ordering is Manual
• Note that a recipe is assigned as the alternate bom is populated, the action is Release
and the Sugg Start Date and Sugg Dock Date are different
• Check the For Release check box, the Action changes to None, save, the colour changes,
> Plan > Release and a pop up window opens, see the new Work Order is 1 and see the
Work Order/Schedule id is populated
• Concurrent Program Feedback - suggestions from APS to GMP is initiated. Note the
parameter. Note the Request id is the same as above
• OPM Supply Chain Planner (OLTP) > Production Updates > APS New Batches. See the
Group Id is from the feedback CCP parameters, the other details are from the ASCP
Planned Order
• Production Supervisor > Batch Details. Product, quantity, recipe, dates come from
ASCP>APS New Batches. Batch Status is Pending
• For the circumstance where the User Requires a high level of control but uses a
concurrent program to convert the recommendations from ASCP
• Planner Releases the Recommendation
• Production Supervisor reviews the recommendations through the APS New Batches form
or ASCP Planner Workbench
• Production Supervisor uses the parameters in the Auto Release of Planning suggestions
for APS concurrent program to convert to batches
• Profile GMP:Auto Implement APS Suggestions is No
• OPM Supply Chain Planner (OLTP). Organization Code is mandatory, see the Process id is
the value in the parameters from the Feedback
• Below is an edited version of the log file containing the most useful information. The Group Id
is the parameter from the feedback program, the Header Id is the ASCP Order number, Org
Calendar, start and end dates, product and batch number. Calling GMP APS for constrained
Plans
• For the circumstance where there is no need for the Production function
to review and edit the ASCP recommendations before the Batches are
created
• Planner Releases the recommendation and the batch is automatically
created in OPM
• The Auto Release of Planning suggestions for APS concurrent program is
automatically initiated on processing the Release action within ASCP
• Profile GMP:Auto Implement APS Suggestions is Yes
• The approach covers a circumstance where there is a significantly reduced need for
control over the release of ASCP Planned Orders and for the subsequent creation of
batches.
• The Feedback - suggestions from APS to GMP and Auto Release of Planning suggestions
for APS concurrent programs are initiated automatically as part of the Launch Plan
routine
• Control is achieved through the Inventory > Items > Organization Items MPS/MRP
Planning > Release Time Fence and Days fields whereby which items and which planned
orders (by date) can be dictated
• There is no OPM specific set up or process to this approach
• See Understanding and Troubleshooting the Release from Planners Workbench in VCP
Applications (Doc ID 1346745.1)
Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 26
Considerations, Create Batch
– Releasing planned orders does not automatically release planned orders for
intermediates
– Releasing a planned order for a parent product does create a batch for make
phantom items, where set as Automatic in the formula
– If plan is EDD or unconstrained and planned order Sugg Due Date is within the lead
time the batch is created with a Planned Start in the past
– Firmed planned orders creates batches with a firmed header (when GMP:
Implement Production Orders Firmed in APS as Firm is Yes)
– Batch Planned Completion time backed off the nearest earlier organization calendar
shift end time in Unconstrained Plans
• All the above processes can be used to perform these actions. Here
we will use the Automatic process
• The Manual process through the use of the forms is via the OPM
Supply Chain Planner (OLTP) > Production Updates > APS Reschedule
and APS Cancel Batches forms
• The Action has changed from Reschedule Out to None, see the
Reschedule Works Order = 1 in the pop up window
• Below is an edited version of the log file containing the most useful
information. Note ‘Implementing Reschedule Batches’ action
• Note the batch has been rescheduled with the Planned Completion reflecting the Sugg
Dock Date.
• Cancel Action. In this case using an FPO is being used. As above the same concept and
approach applies to both Batches and FPOs
• The Action has changed from Cancel to None, see the Reschedule Works Order = 1 in the pop
up window
• Below is an edited version of the log file containing the most useful information. Note
‘Implementing Cancel Batches’ action
• Batches in WIP status, even if all the steps (operations) are pending, cannot be
cancelled in this way.
• See the entry in the GMPRELAP: Auto Release of Planning suggestions for APS log
file as The batch <Batch No> is not in pending status. Use Production Supervisor
responsibility to Cancel the batch
• These actions also cannot be implemented through the APS Cancel Batches form
• The most common failure in the release process is seen in the log as:
– “Primary product does not match the current validity rule”
– The most common cause of this is there is no recipe assigned to the Planned
Order
– The most common cause of this is the recipe details have not been collected
– See Note 1146014.1, heading List of Recipe Collection Notes
– There are many other notes in MOS that can be found thru a search of the
error
Accreditation Program Pages Fully leverage support capabilities Stay Informed | Analyzer Scripts |
delivered via My Oracle Support | Workflow Analyzer | Period Close|
• Program Index – 1583898.1 high-value best practices | efficiency Patching | Certifications | Upgrade
• E-Business Suite – 1580100.1 with Oracle tools = more time spent Advisor | Comparison Reports.
on primary role.
https://community.oracle.com/thread/
3570481
Q&A panel
3
Send your question
2
Ask: ALL PANELLIST leave default!
1
type your question here