GOP Enhancements

Adobe Captivate Tuesday, November 29, 2022
Slide 3 - Oracle Supply Chain Planning Cloud
Slide notes
Hello, and welcome to training for Global Order Promising (GOP) Cloud in Oracle Supply Chain Planning Cloud.
In this session, we talk about the enhancements in Global Order Promising Cloud.
Notes
Page 1 of 54
Slide 4 - Agenda
Slide notes
For the capabilities covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they
bring. Next, we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.
Notes
Page 2 of 54
Slide 5 - Capabilities Overview
Slide notes
The capabilities covered in this training, will provide you with the ability to enable allocation constraints, with Quick Availability REST service, support
quantity- based multilevel allocations, based on the Attribute framework, consider resource availability of option dependent resources while calculating
promise dates for Assemble to Order or ATO configurations, and enhance the source-based promising solution by considering scheduled supply receipts
for future dates during real-time promising.
Notes
Page 3 of 54
Slide 6 - Slide 6
Slide notes
We begin with the feature Respect Supply Allocation Rules in the Quick Availability REST Service.
Notes
Page 4 of 54
Slide 7 - Respect Supply Allocation Rules in the Quick Availability REST Service
Slide notes
This capability will provide you with the ability to invoke Quick Availability REST service, to ascertain supplies of constrained items under allocations.
Multilevel allocations are considered by GOP, while determining available supplies.
Notes
Page 5 of 54
Slide 8 - Respect Supply Allocation Rules in the Quick Availability REST Service
Slide notes
The benefits of this feature are that it improves the accuracy of item availability information for constrained items, that are under multilevel allocations. It
also enhances the overall visibility into the item’s supply picture, by including supplies obtainable through inheritance, and redeployment of allocated
supplies to other allocation nodes.
Notes
Page 6 of 54
Slide 9 - Key Parameters for Quick Availability REST Service With Allocations
Slide notes
The input parameters for the Quick Availability REST service invocation, with allocations, include existing parameters item, date, and organization. In
addition, the allocation node information is newly introduced, as part of this feature. This involves supporting the input of up to three-level allocation
hierarchy, in order to retrieve the item availability information, corresponding to the allocated supply, for the lowest level allocation node.
The output parameters include the ones already supported currently, like Shelf Quantity, representing the ATP supply available for the item, without
consideration for allocations, as well as newly introduced parameters, Available Quantity, Allocated Weekly Quantity for the lowest level allocation node,
and Total Allocated Weekly Quantity.
Available Quantity returns the quantity of available supply, for the lowest level allocation node, on the requested date, which can fulfil new orders. This
includes the allocated quantity for the lowest level node directly, as well as the supply obtained through inheritance, from parent level nodes, and supply
obtained from lower priority nodes through redeployment.
Allocated Weekly Quantity returns the weekly supply allocated directly to the lowest level allocation node.
Total Allocated Weekly Quantity returns the quantity of allocated supply, for the lowest level allocation node, for the week, inclusive of direct allocation to
the allocation node, as well as through inheritance and redeployment of supplies.
Notes
Page 7 of 54
Slide 10 - Additional Information for Respect Supply Allocation Rules in the Quick Availability REST Service
Slide notes
If no allocation node information is provided, or if allocation node information is provided, in the Quick Availability invocation for an item that is not under
allocations, then GOP reverts to the existing behavior, and returns results by disregarding the allocation nodes, and providing the results as though the item
was not under allocations
The complete allocation node hierarchy information should be provided, in the Quick Availability input payload, in order to fetch allocated item availability
information, for the lowest level allocation node.
Item availability information for one or more allocation nodes can be retrieved, using a single Quick Availability invocation.
Item availability information can be retrieved, for one or more item-organization combinations, that are under allocations, using a single Quick Availability
invocation.
Quick Availability information will be retrieved by GOP, assuming a fully open calendar. This implies that GOP will return item availability information, even
on requested dates that are non-working days, in the organization calendar.
Notes
Page 8 of 54
Slide 11 - Invocation of Quick Availability REST Service With Allocations
Slide notes
A sample Quick Availability REST invocation with Allocations is shown here.
Notes
Page 9 of 54
Slide 12 - Output of Quick Availability REST Service With Allocations
Slide notes
The corresponding response from the Quick Availability REST service with Allocations is shown here.
Notes
Page 10 of 54
Slide 13 - Example 1: Quick Availability With Requested Date Towards End of the Week
Slide notes
This example shows a scenario, where the Quick Availability information is retrieved towards the end of the allocation weekly bucket. Assume the allocation
week starts from Day 9 to Day 15. The allocation for three levels are top level All, with 30%, next level Mid, with 20% and lowest level Low, with 50%.
Assume there is on hand supply of 70 units, and an incoming Purchase Order of 30 units, on Day 13.
If the Quick Availability call is invoked with requested date Day 13, for lowest level allocation node Low, then the results are as shown in the table. The
Shelf Quantity is not subject to allocations, and returns the total available ATP supply, for the item on the requested date.
The Available Quantity on requested date shows 100 units as the supply available to meet new orders, inclusive of inheritance and redeployment.
Notes
Page 11 of 54
Slide 14 - Example 2: Quick Availability at the End of the Week Considering Previously Promised Orders
Slide notes
If there are previously promised orders, for the same allocation node, then this example shows how the Quick Availability results are retrieved. As in the
previous example, allocation for three levels is top level All, with 30%, next level Mid, with 20% and lowest level Low, with 50%. Assume there is on hand
supply of 70 units, and an incoming Purchase Order of 30 units, on Day 13.
The Quick Availability call is invoked with requested date Day 13, for lowest level allocation node Low. There is also a previously scheduled order, for
allocation node Low, of 50 units. The results are as shown in the table, The Shelf Quantity is not impacted by allocations, and represents the total ATP
supply available, for the item on the requested date. The Available Quantity on requested date shows the supply available to meet new orders, inclusive of
inheritance and redeployment, less the quantity consumed by the previous sales order.
Notes
Page 12 of 54
Slide 15 - Example 3: Quick Availability With Requested Date Towards Beginning of the Week
Slide notes
Let’s take the case where the Quick Availability invocation is used to retrieve information, towards the beginning of the week. The initial conditions remain
the same as before - Assume the allocation week starts from Day 9 to Day 15. The allocation for three levels is top level All, with 30%, next level Mid, with
20% and lowest level Low, with 50%. Assume there is on hand supply of 70 units, and an incoming Purchase Order of 30 units, on Day 13.
If the Quick Availability call is invoked with requested date Day 11, for lowest level allocation node Low, then the results are as shown in the table. The
Shelf Quantity is not impacted by allocations and represents the total ATP supply available for the item, on the requested date. The Available Quantity on
requested date shows 70 units as the supply available to meet new orders, inclusive of inheritance, and redeployment. The quantity reflects the fact that, as
on requested date, the available ATP supply for the item, is 70 units (this represents on hand quantity only), and this is allocated based on the percentages
defined.
Notes
Page 13 of 54
Slide 16 - Example 4: Quick Availability at the Beginning of the Week Considering Previously Promised Orders
Slide notes
Consider the scenario, where there are previously scheduled orders, for the lowest level allocation node, and the requested date is towards the beginning of
the week. As in the previous example, allocation for three levels is top level All, with 30%, next level Mid, with 20% and lowest level Low, with 50%. Assume
there is on hand supply of 70 units, and an incoming Purchase Order of 30 units, on Day 13.
The Quick Availability call is invoked with requested date Day 11, for lowest level allocation node Low. There is also a previously scheduled order, for
allocation node Low, of 50 units. The results are as shown in the table. The Shelf Quantity is not impacted by allocations and represents the total ATP
supply available for the item, on the requested date. The Available Quantity on requested date shows the supply available to meet new orders, inclusive of
inheritance and redeployment, less the quantity consumed by the previous sales order.
It is to be noted that, as on requested date, the available ATP supply for the item, is 70 units (representing on hand quantity only), and this is allocated
based on the percentages defined. The resultant Available Quantity on requested date, shows 20 units as the supply available to meet new orders.
Notes
Page 14 of 54
Slide 17 - Slide 17
Slide notes
Next, we discuss the feature, Include Define Hierarchical Quantity-Based Supply Allocations.
Notes
Page 15 of 54
Slide 18 - Define Hierarchical Quantity-Based Supply Allocations
Slide notes
This capability will provide you with the ability to define multilevel supply allocations by quantity, for different business-critical classifications, like sales
channels, promotions, customers, regions, and so on. Supply allocations are aggregated in weekly buckets. This capability will also provide you with the
ability to consume allocated supply, from parent nodes, as well as redeploying allocated supply of lower priority allocation nodes, at the same hierarchical
level to higher priority allocation nodes, in the event of a supply shortfall.
Notes
Page 16 of 54
Slide 19 - Define Hierarchical Quantity-Based Supply Allocations
Slide notes
The benefits of this feature are that it adds flexibility to supply allocation definition, by supporting allocations to be defined based on quantity, in addition to
the existing capability of defining percentage-based allocations. It also increases fill-rates, by augmenting availability of allocated supplies through
inheritance from parent nodes, as well as redeployment from other peer nodes, for quantity-based supply allocations.
Notes
Page 17 of 54
Slide 20 - Defining Quantity Based Supply Allocations
Slide notes
For defining quantity-based sourcing rules, the allocation rules should be defined through the UI, or file-based upload process. The allocated quantity will
then need to be uploaded through the REST service, provided for this purpose.
Information such as allocation node ranks, stealing protection percentage, are derived from Allocation Rules, while the weekly allocated quantities, for each
allocation node, are derived from the REST service, by GOP.
Notes
Page 18 of 54
Slide 21 - Example 1: Quantity Based Allocation With Lower Available Supply
Slide notes
Consider a scenario, where the actual available ATP supply, is less than the sum of quantities allocated through the REST service. In such cases, GOP will
proportionally allocate the available ATP supply, based on the quantities that were originally defined, for each allocation node in the REST service.
In the example, the available supply falls short of the sum of allocated quantities, through REST service, by 500 units. This results in GOP adjusting the
allocated quantities for every node, by reducing the allocated quantities, in proportion to the corresponding quantity defined.
Notes
Page 19 of 54
Slide 22 - Example 2: Quantity Based Allocation With Higher Available Supply
Slide notes
In a scenario, where the ATP supply, exceeds the sum of allocated quantities through the REST service, GOP will allocate the excess supply to the top-
level allocation node, in the allocation hierarchy.
In this example, the available ATP supply exceeds the sum of allocated quantities, by 500 units. The excess quantity is added to the ATP supply of the top-
level node, in the hierarchy.
Notes
Page 20 of 54
Slide 23 - Example 3: Quantity Based Allocation With Multiple Top-Level Nodes and Higher Available Supply
Slide notes
In the event that, the allocation node hierarchy has multiple tree structures, and the available supply is in excess of the sum of supply allocated, through
REST service, the excess supply is proportionally distributed among the top-level nodes, based on their original allocations defined, through the REST
service.
Notes
Page 21 of 54
Slide 24 - REST Service Detail for Upload of Allocated Quantities
Slide notes
The high-level input parameters for creating an allocation record, is as shown here.
Notes
Page 22 of 54
Slide 25 - Additional Information for Define Hierarchical Quantity-Based Supply Allocations
Slide notes
Allocation, based on quantities, can only be carried out through REST service, once the Allocation Rule is defined, either through the UI, or through file-
based upload.
File-based upload, of allocation quantities, or edits to the allocation quantities, through the Allocation Rule UI, are currently not supported.
GOP will consider the lowest level allocation node, stamped on the sales order line, and consume its allocated quantity. In case of any shortfall, it will
proceed up the allocation hierarchy defined. All levels of the allocation hierarchy need to be stamped on the sales order. GOP can support one, two or three
level allocation hierarchies. All necessary setups, including allocation hierarchy definitions, Allocation Rules, allocated quantities, are needed for GOP to
consider allocation information accurately.
Historical information of shipped sales orders can also be taken into consideration, for limited duration campaigns, and promotions, with quantity-based
allocations. The campaign interval can be specified in the “Date Range to Consider Shipment History” tab, in the Allocation Rule. For meaningful results,
there are some guidelines to keep in mind, while setting up, and running this capability.
Allocation targets are expected to remain unchanged for the duration of the campaign, and need to be uploaded, for each week of the campaign. The
allocation targets represent the targets for the entire campaign and should not correspond to weekly targets.
Total supply at the beginning of the campaign is expected to remain unchanged, for the duration of the campaign. For the week that includes the system
date, the shipped sales orders will be netted, from the remaining supply, for each allocation node.
The allocation framework, allocation hierarchy and the allocation nodes are expected to remain unchanged, for the campaign duration.
Page 23 of 54
Slide 26 - Implementation Advice
Slide notes
In this section, we provide implementation considerations and setup instructions for the enhancements covered.
Notes
Page 24 of 54
Slide 27 - Define Hierarchical Quantity-Based Supply Allocations Impact
Slide notes
Define Hierarchical Quantity-Based Supply Allocations has actions that need to be taken before use.
Define Hierarchical Quantity-Based Supply Allocations can be accessed using the role Order Promising Manager.
The business process associated with this feature is Manage Order Promising.
Notes
Page 25 of 54
Slide 28 - Summary of Actions Needed to Use Define Hierarchical Quantity-Based Supply Allocations
Slide notes
Before commencing enablement for Define Hierarchical Quantity-Based Supply Allocations, there are implementation considerations that need to be taken
into account.
This feature is aimed at businesses, that have high-demand items with limited supply quantities, which are typically allocated to various hierarchical
channels, defined based on business criteria.
In case of such definitions, if certain channels need to access supplies, from other lower priority channels, then the extent of protected supply, as well as
priorities, need to be decided.
If the enterprise engages in limited duration promotional campaigns from time-to-time, for items under allocation, then the supplies need to be tracked
against the orders shipped out, during the campaign duration. The supplies, duration, and allocation quantities need to be decided, by the business.
Notes
Page 26 of 54
Slide 29 - Summary of Actions Needed to Use Define Hierarchical Quantity-Based Supply Allocations
Slide notes
The enablement for Define Hierarchical Quantity-Based Supply Allocations is achieved by activating the following Opt-ins:
Attribute-Based Planning Opt-in within Supply Chain Planning offering, or
Project-Driven Supply Chain Opt-in within Supply Chain Planning offering and
Multilevel Allocation in Order Promising Opt-in within the High-Volume Order Promising opt-in.
Enablement is done via Functional Setup Manager. The tasks are within the Supply Chain Planning offering.
Functional area is Plan Inputs. The tasks associated with the enablement are Manage Planning Attributes, Manage Supply Allocation Rules
The administrator to determine whether the Quantity Based Allocation REST service and the Quick Availability with Allocation REST service are to be used
by the business.
Notes
Page 27 of 54
Slide 30 - Enablement Detail for Define Hierarchical Quantity-Based Supply Allocations
Slide notes
The attributes to be mapped to the sales order need to be defined.
Notes
Page 28 of 54
Slide notes
Allocation rules need to be defined and assigned to the items under allocation. This should be followed by invoking the REST service to define allocation
quantities.
Notes
Page 29 of 54
Slide notes
ATP rule needs to have allocations enabled for items under allocation.
Notes
Page 30 of 54
Slide 33 - Slide 33
Slide notes
Now, we’ll discuss the feature Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations.
Notes
Page 31 of 54
Slide 34 - Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations
Slide notes
This capability will provide you with the ability to determine scheduled dates, for different configurations, of an ATO Model, based on the resource
availability, corresponding to the specific options selected on the order. The Bills of Resources information is enhanced, to support option dependent
resource information, to help determine the resource availability information accurately.
Notes
Page 32 of 54
Slide notes
The benefit of this feature is that it leads to better accuracy of promising results, since the resource availability associated with the selected options on the
order alone, are considered. In addition, it enhances efficiency through optimizing resource usage information, by focusing on the relevant option selections.
Notes
Page 33 of 54
Slide 36 - Example – 1: Option Dependent Operation with Single Level Model
Slide notes
In this example, we take the case where, there is a single-level model having an option-dependent operation, that uses resource R 1. The operations are
assigned at Option Class level, and the resulting Bills of Resource represents these, with the option-dependent information displayed specifically for the
resource R 1.
When the order is configured and promised, resource R 1 capacity will be consumed if either of the Option items Option 1, Option 2, figuring below Option
Class 'A' are selected. GOP will always consume capacity for resource R 2 since it is not option dependent.
Notes
Page 34 of 54
Slide 37 - Example – 2: Option Dependent Operations for All Option Items With No Option Class
Slide notes
Next, we consider the case where, we have a single-level model with option-dependent operations, for all resources. The Option items figure directly below
the Model item and are associated with different option dependent resources R 1, R 2, R 3, and R 4, respectively.
The resulting Bills of Resource represents these, with the option-dependent information displayed specifically for all the resources. The detail level table
represents the operation sequence numbers, corresponding to the different resources.
When the order is configured and promised, resource R 1 capacity will be consumed if Option 1 is selected, resource R 2 capacity if Option 2 is selected,
resource R 3 capacity if Option 3 is selected and resource R 4 capacity if Option 4 is selected.
Notes
Page 35 of 54
Slide 38 - Additional Information for Include Resources Needed to Produce Assemble-to-Order Options in Capable-
to-Promise Calculations
Slide notes
Bills of Resources generation steps remain the same, both in terms of the steps, and templates used for GOP Bills of Resources generation.
Enhancements in the generation process automatically detect option dependent resources, on the basis of option dependent operations. As a result, all
option dependent resources marked critical, will figure in the generated Bills of Resources. The main table represents these with a new parameter.
Effective date ranges are not considered by the Bills of Resources generation process.
Currently, this feature only processes those option dependent operations, associated with first level components, figuring directly below the ATO Model.
This will be enhanced to more levels, in a future release.
The Aggregate Bills of Resources table does not provide the ability to adjust option dependent information directly in the UI.
Notes
Page 36 of 54
Slide 39 - Reviewing Option Dependent Resource Data
Slide notes
The Aggregate Bills of Resources table is enhanced, to show additional details for option dependent resources, including an attribute, in the main table, to
indicate that a resource is option dependent, and a details table for option dependent resources, to display additional information, such as operation
sequence number, model as well as option data, and so on.
Notes
Page 37 of 54
Slide notes
Notes
Page 38 of 54

Impact
Slide notes
Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations has actions that need to be taken before use.
Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations can be accessed using role Order Promising
Manager
Notes
Page 39 of 54
Slide 42 - Implementation Considerations for Include Resources Needed to Produce Assemble-to-Order Options in
Capable-to-Promise Calculations
Slide notes
Before commencing enablement for Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations, there are
implementation considerations that need to be taken into account.
The use of this feature should be aligned with the enterprise’s business requirements. This feature is beneficial to those enterprises that deal with ATO
Models, where the configuration selection, at the time of order creation, significantly impacts the resources that are employed to build them. If there are
certain key configurations that are fast-moving, then tracking the resource availability, for the resources required to build them, becomes critical for the
business. This feature will allow users to optimally utilize option dependent resources, by only considering their availability for meeting orders, where their
corresponding configurations are selected.
Another consideration to keep in mind is how the key items and resources, that drive successful promising results, will be identified. This requires review of
the Bills of Resources, and marking the right components and resources, as critical.
Notes
Page 40 of 54
Slide 43 - Summary of Actions Needed to Use Include Resources Needed to Produce Assemble-to-Order Options in
Capable-to-Promise Calculations
Slide notes
The enablement for Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations is achieved by enabling the
High-Volume Global Order Promising Opt-in.
The functional areas are Supply Chain Planning and Order Management in the Supply Chain Management offering.
Associated tasks include Create Bills of Resources, Order Promising Options, Simulation Sets, Manage Sourcing Rules, and Manage Assignment Sets.
Notes
Page 41 of 54
Slide 44 - Enablement Detail for Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-
Promise Calculations
Slide notes
Bills of Resources can be generated, by executing the Create Bills of Resources scheduled process, and providing the necessary input parameters,
relevant for GOP.
Notes
Page 42 of 54
Slide 45 - Slide 45
Slide notes
Finally, we’ll discuss the feature Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations.
Notes
Page 43 of 54
Slide 46 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations
Slide notes
This capability will provide you with the ability to consider future dated supplies, during source based promising. Purchase Orders, Work Orders, and
Transfer Orders will be considered as valid ATP supply, while carrying out real-time promising.
GOP will now aggregate supplies belonging to all these supply types as ATP supply, in addition to previously considered supply types On Hand, and In-
Transit supplies, while promising orders.
Notes
Page 44 of 54
Slide 47 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations
Slide notes
The benefits of this feature are that it further improves source based promising capabilities, by additionally considering scheduled receipts of supplies. It
also presents a robust source based promising solution, that addresses realistic promising scenarios reflected in enterprises.
Notes
Page 45 of 54
Slide 48 - Backlog Netting and Order Promising Example
Slide notes
Let us see the behavior of the solution, through an example. Here, Organization 1 has an on hand supply of 10 units. There are incoming supplies, in the
form of a Transfer Order, for a quantity 50 units on Day 5, and a Purchase Order, of 100 units, on Day 10. This adds up to a total of 160 units of cumulative
supply.
Assume, there is a new demand for the item, at Organization 1, on Day 13, for 50 units. The available supply in the system is calculated first. Assuming that
previous orders for the item were promised, for quantities 20 units, and 40 units, this gives a total demand quantity, of 60 units. This total demand is taken
to be due on system date, for netting calculations. Thus, the net quantity of available supply at Organization 1, is 260 units less 60 units, equals 100 units.
In the order promising phase, the new order can be met by consuming 50 units, from the available quantity of 100 units.
Notes
Page 46 of 54
Slide 49 - Additional Information for Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations
Slide notes
This solution is designed to address promising for non-Back-to-Back items. The source side promising solution already addresses promising of Back-to-
Back items.
This feature considers supply types such as Work Orders, Purchase Orders, or Transfer Orders, in addition to On Hand stock and In-Transit supplies, that
were previously supported.
No item specific features are supported by this solution, including plan integration, option specific sourcing, customer specific substitution, and so on.
This solution does not recommend Make or Buy supplies through CTP. It is designed to traverse the supply chain network and locate fragmented supplies.
Further information on the solution is available in the GOP release readiness content for update 22C, titled “Enhancements for Real-Time Promising and
ATO.”
Notes
Page 47 of 54
Slide notes
Notes
Page 48 of 54
Slide 51 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations Impact
Slide notes
Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations has actions that need to be taken before use.
Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations can be accessed using role Order Promising Manager.
Notes
Page 49 of 54
Slide 52 - Summary of Actions Needed to Include Future-Dated Receipts in Real-Time Available-to-Promise

Calculations
Slide notes
Before commencing enablement for Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations, there are implementation
considerations, that need to be taken into account.
This source side promising solution drives promising in business scenarios that deal with several million item-organization combinations, where it is not
practical to run Collections at frequent intervals. If the item-organization volumes are not very high, or Collections durations are not significant, then the
collection based promising solution can be evaluated.
This source side promising solution is designed to traverse the supply chain network of an item, and utilize the supply, lying fragmented in different
warehouses, and distribution centers. If the business requires the promising solution to make new supply recommendations, then the back-to-back
promising solution can be evaluated.
Notes
Page 50 of 54
Slide 53 - Summary of Actions Needed to Include Future-Dated Receipts in Real-Time Available-to-Promise

Calculations
Slide notes
The enablement for Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations, is achieved by setting the profile. Steps are performed
via Functional Setup Manager.
Items that need to be promised using the source side promising solution can then be enabled in Product Information Management work area.
Notes
Page 51 of 54
Slide 54 - Enablement Detail for Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations
Slide notes
Navigate to Setup and Maintenance, search and select the task titled “Manage Administrator Profile Values.” In the page for this task, select the profile
option MSP_ENABLE_GOP_WITH_NEW_ARCHITECTURE, and set to “Yes, with source-based promising” at the Site level.
Notes
Page 52 of 54
Slide 55 - Enablement Detail for Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations
Slide notes
Set the Check ATP item attribute to ‘Source Based Promising’ for items that need to be promised by this solution.
Notes
Page 53 of 54
Slide 56 - Associated Training
Slide notes
Other training modules that are related to these new capabilities and are recommended viewing are:
 22C Global Order Promising feature “Multilevel Allocation in Order Promising” release readiness,
 21D Backlog Management feature “Backlog Management Allocation Enhancements” release readiness,
 20A Global Order Promising feature “Control the Range of Shipment History to Include in Demand Class Allocations” release readiness,
 22A Global Order Promising feature “Support Capable-to-Promise for Manufactured Items” release readiness, and
 22C Global Order Promising feature “Enhancements for Real-Time Promising and Assemble to Order” release readiness.
This concludes this presentation. Thank you for listening. You can easily pause and rewind if you require additional time to take in the detail.
Notes
Page 54 of 54

GOP Enhancements

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GOP Enhancements

Uploaded by

Copyright:

Available Formats

Adobe Captivate Tuesday, November 29, 2022

Slide 3 - Oracle Supply Chain Planning Cloud

Slide 5 - Capabilities Overview

Slide 11 - Invocation of Quick Availability REST Service With Allocations

Slide 12 - Output of Quick Availability REST Service With Allocations

Slide 18 - Define Hierarchical Quantity-Based Supply Allocations

Slide 19 - Define Hierarchical Quantity-Based Supply Allocations

Slide 20 - Defining Quantity Based Supply Allocations

Slide 21 - Example 1: Quantity Based Allocation With Lower Available Supply

Slide 22 - Example 2: Quantity Based Allocation With Higher Available Supply

Slide 24 - REST Service Detail for Upload of Allocated Quantities

Slide 25 - Additional Information for Define Hierarchical Quantity-Based Supply Allocations

Slide 26 - Implementation Advice

Slide 27 - Define Hierarchical Quantity-Based Supply Allocations Impact

Slide 30 - Enablement Detail for Define Hierarchical Quantity-Based Supply Allocations

Slide 31 - Enablement Detail for Define Hierarchical Quantity-Based Supply Allocations

Slide 32 - Enablement Detail for Define Hierarchical Quantity-Based Supply Allocations

Slide 34 - Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations

Slide 35 - Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations

Slide 36 - Example – 1: Option Dependent Operation with Single Level Model

Slide 39 - Reviewing Option Dependent Resource Data

Slide 40 - Implementation Advice

Slide 41 - Include Resources Needed to Produce Assemble-to-Order Options in Capable-to-Promise Calculations

Slide 46 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations

Slide 47 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations

Slide 48 - Backlog Netting and Order Promising Example

Slide 50 - Implementation Advice

Slide 51 - Include Future-Dated Receipts in Real-Time Available-to-Promise Calculations Impact

Slide 52 - Summary of Actions Needed to Include Future-Dated Receipts in Real-Time Available-to-Promise

Slide 53 - Summary of Actions Needed to Include Future-Dated Receipts in Real-Time Available-to-Promise

Slide 56 - Associated Training

You might also like