Oracle Supply Chain Planning Cloud 20A What's New

TABLE OF CONTENTS

UPDATE 20A ···························································································································································································································· 2

Revision History ····················································································································································································································· 2

Overview ····································································································································································································································· 2

Optional Uptake of New Features (Opt In) ··························································································································································· 2

Feature Summary ················································································································································································································ 4

Demand Management ································································································································································································ 7

Forecast and Analyze Multidimensional Demand Segments ································································································· 7

Improve Model Selection Using Cross-Validation Learning ··································································································· 8

Tailor Forecast Profiles by Business Process ···································································································································· 9

Load Data from One Measure to Another Measure Across Plans ····················································································· 10

Replenishment Planning ····················································································································································································· 11

Manage Segmentation ···················································································································································································· 11

Specify and Compute Inventory Policy Parameters ···················································································································· 13

Compute Demand-Driven Replenishment Orders ······················································································································ 14

Tailor Plan Scope ································································································································································································ 15

Monitor Plan Performance ·········································································································································································· 16

Simulate Replenishments ············································································································································································· 18

Manage Segments and Replenishment Orders Using a REST Service ··········································································· 19

Collect Consumption Data from Oracle Inventory Cloud ······································································································· 20

Forecast and Replenish Items at Subinventory Levels ·············································································································· 21

Enable Inventory Policy Comparison ···················································································································································· 22

Sales and Operations Planning ············································································································································································ 23

Load Data from One Measure to Another Measure Across Plans ···················································································· 23

Include Archived Measures When Copying Plans ························································································································ 25

Use a Forecast Measure in Oracle Demand Management Cloud as a Baseline for Consensus Forecasting ············································································································································································································ 25

Supply Planning ············································································································································································································ 26

Include Archived Measures When Copying Plans ······················································································································· 26

Constraint-Based Planning ·············································································································································································· 27

Plan Outside Processing Operations ···················································································································································· 27

Order Backlog Management ··········································································································································································· 28

Analyze Order Scheduling Performance ············································································································································ 28

Prioritize Demands Based on Extensible Business Rules ······································································································· 29

Honor Previously Promised Dates During Rescheduling ······································································································· 30

Identify Order Rescheduling Revenue Opportunities and Gaps ························································································· 31

Adjust Fulfillment Strategies ······································································································································································ 32

Schedule Orders Based on Configurable Supply Types ··········································································································· 33

Manually Specify, Override, and Lock Scheduling Results ···································································································· 33

Resolve Item Constraints Within a Shipment Set or Arrival Set ·························································································· 34

Schedule Batches of Unscheduled Orders ······································································································································· 35

Automatically Update and Reschedule the Order Backlog ···································································································· 36

Release Rescheduling Recommendations to Order Management Systems ······························································ 37

Update Orders, Reschedule Backlog, and Review Results Using REST Services ····················································· 38

Assess the Scheduling Impact of Order Inquiries ························································································································ 38

Respect Reservations of Supply Against Sales Orders ············································································································· 40

Update Global Order Promising Scheduled Dates in Real Time When Orders Are Released ·························· 41

2

UPDATE 20A

REVISION HISTORY

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes

20 DEC 2019 Created initial document.

OVERVIEW

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

SECURITY AND NEW FEATURES

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at [email protected]

3

2. 3. 4.

1. 2. 3. 4.

5.

On the New Features page, select the offering that includes new features you’d like to reviewClick for any feature you want to opt inGo to Opt InOn the Edit Features page, select the option for the feature, and then click Enable Done

or... Access the Opt In page from the Setup and Maintenance Work Area

Click the , and then click Navigator Setup and MaintenanceOn the Setup page, select your offering, and then click Change Feature Opt InOn the Opt In page, click the icon for any area that includes features you want to opt inEdit FeaturesOn the Edit Features page, select the option for any feature you want to opt in to. If the Enable Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click . Save and CloseClick .Done

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also to see features with Opt In click hereExpirations across all Oracle Cloud Applications.

1.

OPTIONAL UPTAKE OF NEW FEATURES (OPT IN)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users in a couple of ways:

Access the Opt In page from the New Features Work Area

Click the Navigator, and then click New Features (under the My Enterprise heading)

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/optin.htm

4

FEATURE SUMMARY

Column Definitions:

Features Delivered Enabled

= New or modified, Oracle-delivered, ready to run reports.Report = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential UI or Process-Based: Small Scale

impact to users is minimal. = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.UI or Process-Based: Larger Scale*

= Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to Features Delivered Disabledenable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users (Features Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Action is Needed BEFORE Use by End Users (Features Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature Report

UI or Process-Based:

Small Scale


Larger Scale*

Demand Management

Forecast and Analyze Multidimensional Demand Segments

Improve Model Selection Using Cross-Validation Learning

Tailor Forecast Profiles by Business Process

Load Data from One Measure to Another Measure Across Plans

Replenishment Planning

Manage Segmentation

5





Feature Report


Small Scale


Larger Scale*

Specify and Compute Inventory Policy Parameters

Compute Demand-Driven Replenishment Orders

Tailor Plan Scope

Monitor Plan Performance

Simulate Replenishments

Manage Segments and Replenishment Orders Using a REST Service

Collect Consumption Data from Oracle Inventory Cloud

Forecast and Replenish Items at Subinventory Levels

Enable Inventory Policy Comparison

Sales and Operations Planning

Load Data from One Measure to Another Measure Across Plans

Include Archived Measures When Copying Plans

Use a Forecast Measure in Oracle Demand Management Cloud as a Baseline for Consensus Forecasting

Supply Planning

Include Archived Measures When Copying Plans

Constraint-Based Planning

Plan Outside Processing Operations

Order Backlog Management

Analyze Order Scheduling Performance

6





Feature Report


Small Scale


Larger Scale*

Prioritize Demands Based on Extensible Business Rules

Honor Previously Promised Dates During Rescheduling

Identify Order Rescheduling Revenue Opportunities and Gaps

Adjust Fulfillment Strategies

Schedule Orders Based on Configurable Supply Types

Manually Specify, Override, and Lock Scheduling Results

Resolve Item Constraints Within a Shipment Set or Arrival Set

Schedule Batches of Unscheduled Orders

Automatically Update and Reschedule the Order Backlog

Release Rescheduling Recommendations to Order Management Systems

Update Orders, Reschedule Backlog, and Review Results Using REST Services

Assess the Scheduling Impact of Order Inquiries

Respect Reservations of Supply Against Sales Orders

Update Global Order Promising Scheduled Dates in Real Time When Orders Are Released

7

DEMAND MANAGEMENT

FORECAST AND ANALYZE MULTIDIMENSIONAL DEMAND SEGMENTS

As part of your demand management process, you may need to forecast and analyze data using multiple dimensional segments. Each of these segments can have its own demand characteristics. You can then tailor forecasting profiles to each segment.

You can classify your business into different segments where each segment is comprised of various combinations of items, organizations, customer sites, and demand classes. These segments can be based on attributes, such as product lifecycle or item cost, or on metrics, such as volume, intermittency, or volatility. Here are two examples of how you might define segments:

Segment item organization combinations into high cost and low cost segments, or into high, medium, and low volume segments.

Segment item customer site combinations into intermittent, smooth, and erratic demand segments.

You can use these segments for analysis in tables and graphs. You can also use these segments in analysis sets to have different forecasting profiles specifically tuned to the segment. For example, create a forecasting profile where you enable the models best suited to intermittent demand for use in forecasting the segment for intermittent demand.

With this capability you can improve overall forecast accuracy and adopt a segmented supply chain strategy to provide differentiated service to your customers.

Watch a Demo

STEPS TO ENABLE

You don't need to do anything to enable this feature.

TIPS AND CONSIDERATIONS

Configure segment groups using the Manage Segment Groups and Criteria task. You define the granularity of the segment group. The granularity can be a combination of item, organization, customer site, and demand class. Then you define each of the segments within the segment group and the criteria for each segment. Segment criteria can be based on attributes of products or organizations or based on measure values from a specified plan.

After configuring a segment group, you invoke the Execute Segmentation action to generate the individual segments and identify the combinations within each segment. You can view the results using the View Segmentation Summary option. Additionally, you can manually override the results using the Manage Segment Members action.

After a segment group is created and successfully executed, you can use it for analysis and filtering in tables, graphs, and analysis sets. When configuring a table or graph, segment groups are listed on the Hierarchies tab. Select a segment group to include it as a level in the table or graph. Segment groups behave like any other hierarchy level, such as product family or month, except they are multidimensional. For example, if the granularity of a segment group is item and organization, then the segments within this segment group will be made up of item and organization combinations. Segment groups are also listed on the Members tab enabling you to filter on selected segments within a segment group.

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Forecast_and_Analyze_Multidimensional_Demand_Segments/demo/index.html

8

1. 2. 3. 4.

a. b. c.

5.

6. 7.

KEY RESOURCES

Watch Forecast and Analyze Multidimensional Demand Segments Readiness Training

ROLE INFORMATION

Users need the following security privilege to use this feature:

Manage Segments (MSC_MANAGE_SEGMENTS_PRIV)

Users with the following job role will automatically be able to use this feature because this role includes the Manage Segments privilege:

Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)

IMPROVE MODEL SELECTION USING CROSS-VALIDATION LEARNING

Oracle Demand Management Cloud generates a forecast using a combination of machine learning algorithms. This new cross-validation learning feature offers a robust alternative for evaluating and scoring forecast models.

By default, Demand Management uses in-sample testing to evaluate and weight the forecast models. This method compares the forecast to the full set of historical demand used to generate the forecast model.

With this update, you can set a new parameter to perform cross-validation learning during forecasting. This learning tests out-of-sample subsets of the historical demand to generate a forecast and then compares each resulting forecast to the remaining portions of historical demand. You can control the number of subsets used. The result of this cross-validation learning determines the weights for the forecasting models.

Watch a Demo

STEPS TO ENABLE

Go to Supply Chain Planning > Demand Management > Tasks: Manage Forecasting ProfilesSelect the relevant forecasting profile (must be a tailored profile. Predefined profiles can't be edited)Select Actions > EditGo to tabForecasting Parameters

Select Actions > AddSearch for the parameter and add it to the forecasting profileOutOfSampleTestSetsChange the OutOfSampleTestSets parameter’s value to 10

Go to tab The supported methods for cross-validation learning are: , Forecasting Methods : Regression Transformation Regression, Multiplicative Monte Carlo Regression, Modified Ridge Regression,

(Some or all can be enabled depending Logistic, Auto Regressive Logistic, Combined Transformationon other user requirements)Save your changesRun the plan with the forecasting profile

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Forecast_and_Analyze_Multidimensional_Demand_Segments/index.html

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Improve_Model_Selection_Using_Cross_Validation_Learning/demo/index.html

9

When enabling the parameter, it is recommended to use the value 10. This OutOfSampleTestSetsmeans that the entire historical demand data will be divided into 10 test sets.

Generally, no other changes are required in the engine parameters default values.

When only one forecasting method succeeds, at any forecast level, the final forecast will be exactly that method's forecast and cross-validation will have no effect. If this happens for most items, consider appropriate configuration changes to allow more forecasting methods to succeed in forecast.

Intermittent methods aren't supported for cross-validation, but will be used for intermittent history as usual.

Other forecasting methods not supported for cross-validation will be ignored if enabled.

KEY RESOURCES

Watch Improve Model Selection Using Cross-Validation Learning Readiness Training

ROLE INFORMATION

Users assigned to following job role will automatically be able to use this feature and no special privileges are required:

Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER)Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)

TAILOR FORECAST PROFILES BY BUSINESS PROCESS

When you use the integrated supply chain planning suite, you can use multiple demand streams and forecast settings for forecasting future demand for different business processes. For example, you can generate a consumption-based forecast using retail activity for replenishment planning and a shipment-based forecast using trends and seasonality for demand management.

With this update, you can control the availability of forecasting profiles across the Demand Management, Demand and Supply Planning, and Replenishment Planning work areas. This feature simplifies your selection of forecasting profiles and helps you avoid using irrelevant forecasting profiles.

Watch a Demo

STEPS TO ENABLE



FORECASTING TABLE

The list of values available for the Forecasting Table option displays only the pivot tables that are available in all of the work area selected for the Enable for Work Area option.


https://download.oracle.com/ocomdocs/global/apps_20A/scm/Improve_Model_Selection_Using_Cross_Validation_Learning/index.html

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Tailor_Forecasting_by_Business_Process/demo/index.html

10

User-defined forecasting profiles defined prior to this feature will be enabled automatically in the Demand Management and Demand and Supply Planning work areas.

User-defined forecasting profiles can’t be enabled in the Planning Central and Sales and Operations Planning work areas.

KEY RESOURCES

Watch Tailor Forecast Profiles by Business Process Readiness Training

ROLE INFORMATION

Users assigned to any of the following job roles will automatically be able to use this feature and no special privileges are required:

Demand Planner (ORA_MSC_DEMAND PLANNER)Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER)Replenishment Planner (ORA_ MSC_REPLENISHMENT_PLANNER)

LOAD DATA FROM ONE MEASURE TO ANOTHER MEASURE ACROSS PLANS

You need visibility of data from a measure across planning applications to enable business processes and drive effective decision making. With this update, you can copy the data from a plan in one application to another plan in a different application to provide this visibility. For example, you can make the constrained forecast from Oracle Sales and Operations Planning Cloud visible to demand planners in Oracle Demand Management Cloud for reference.

You can also enable further refinement of the operations forecast. And you can copy a calculated measure into another measure, where it can be aggregated or disaggregated. Additionally, you can save measure mappings for reuse in subsequent plan runs.

This new capability enhances interoperability and collaborative planning across the Oracle Supply Chain Planning Cloud applications.

STEPS TO ENABLE



You can create and save your measure mappings in a measure copy set so that you don't have to create them every time you run the Load Measures from Other Plans process.

To quickly run the Load Measures from Other Plans process, you can apply a previously saved measure copy set and then run the process.

You can map a source measure to same or different target measure.

You can map a calculated source measure to a stored target measure.

A target measure will be automatically populated by default with the same measure name as the source measure if the measure is available in the target measure catalog.

USER-DEFINED FORECASTING PROFILES

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Tailor_Forecasting_by_Business_Process/index.html

11

If the source measure is not available in the target measure catalog, then the target measure will not be automatically populated, and you need to manually select the target measure.

Source and target measures should have the same type (numeric, string, or date.)

If the source measure is stored, then the target measure can't be a calculated measure.

A mapping isn't supported when both the source and target measures are calculated with different dependent measures.

When you're creating a new mapping row, you shouldn't select a measure in the source measure that's already used as a source measure in another mapping row.

When you're creating a new mapping row, you shouldn't select a measure in the target measure that's already used as a target measure in another mapping row.

Archive measures will be filtered out of the source and target measures list of values.

KEY RESOURCES

The Oracle Sales and Operations Planning Cloud readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION

Users assigned to the following job role will automatically be able to use this feature and no special privileges are required:

Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)

REPLENISHMENT PLANNING

Maintain optimum inventory levels at each node of your supply chain to meet customer service targets at the lowest inventory cost. Use automated processes to maintain inventory policy parameters and improve customer service levels. These automated processes dynamically update the inventory to keep on hand and reduce costs by calculating the economic order quantity for replenishment when appropriate.

After you opt in to the feature named Replenishment Planning, you can use the features described in this section.

MANAGE SEGMENTATION

It can be time consuming and tedious for an enterprise to maintain planning parameters and attributes for every item-location. Replenishment planning provides a rules-based segmentation scheme that dynamically classifies item-locations into groups or segments using static, dynamic, or configured attributes. You can use rule-based segmentation to help you manage replenishment of items and locations that share the same replenishment behavior at a segment level.

Here's what you can do when you manage segmentation:

Create, edit and, manage segment groups. Each segment group can support multiple segments. Each segment has rules that govern how item-locations are associated with the segment.

http://cloud.oracle.com/saas/readiness?offering=scp


12

Dynamically assign item-locations to defined segments - on demand or through a scheduled process - based on their attributes:

, such as Commodity Type.Static Attributes, such as Volume, Product Life Cycle Phase, Intermittency, Volatility, MAPE, Dynamic Attributes

and a measure in a named plan, Such as Is Repairable and On VMI. Your enterprise can define attributes at User-Defined Criteria

the time of implementation.

View the segmentation results in both tabular form and as a pie chart. The chart shows you the number of item-locations assigned to a specific segment.

Manually update the segment of a specific item-location.

STEPS TO ENABLE

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning


When you opt in to use this feature, you must opt in to the feature named: Replenishment Planning. Opting in to the Replenishment Planning feature enables all of the Replenishment Planning features described here.

Additional tips and considerations:

Run the Execute Segmentation process to perform the segmentation process.

You can manually override segments in the column of the Segment Override Manage Segment page.Members

If you want to preserve manual overrides in the next segmentation run, select the Retain segment check box while performing the Manage Segment Groups and Criteria task.overrides

You can associate only one item-location to a segment within a segment group. But you can associate the item-location to a different segment under a different segment group.

You can associate segment groups with only the Product and Organization dimensions to a replenishment plan. Therefore, it's recommended that you create segment groups with only these two dimensions for creating replenishments, for defining policy parameters, and for policy calculation purposes.

Decide what you will use for the Segment Granularity (Dimension) before creating segment criteria because you can’t modify the segment granularity once a segment criteria is defined. For example: If you wish to create a segment group by using the Product and Organization dimensions, then select these two dimensions first, before defining the segment criteria.

KEY RESOURCES

The Oracle Replenishment Planning Cloud readiness training available on Oracle Cloud Readiness for Supply Chain Planning



13


Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER)

SPECIFY AND COMPUTE INVENTORY POLICY PARAMETERS

Use inventory policies to drive the inventory levels needed to meet your desired or target service levels for demand fulfillment. The safety stock method and inventory policy thresholds influence these policy-based calculations, which apply to the specific replenishment segments that you define.

Here's what you can do with policy parameters:

Create and manage reusable inventory policy profiles. A profile includes inventory policy and its attributes:

Inventory Policies: Min-Max Policy, Reorder Point - Order Quantity (ROP-OQ), Reorder Point - Economic Order Quantity (ROP-EOQ), Fixed Order CalendarInventory Policy UOM: Days or UnitsSafety Stock Calculation Method: Days of Cover or Target Service LevelSafety Stock Attributes: Target Service Level Percentage, Safety Stock Days of Cover, Days of Cover Basis, Horizon of Average Daily Demand, Extrapolation PercentageMaximum Quantity Calculation Method: Days of Cover, Minimum Plus Order Quantity, Minimum Plus EOQDefault Inventory Policy Values: Default Daily Demand, Default Order Quantity, Default EOQ, Default Standard Cost, Default Ordering Cost, Default Carrying Cost Percentage

Additionally, you may provide values for safety stock override, minimum quantity override, maximum quantity override, ROP override, order quantity override, and economic order quantity in the profile at the segment or item-location level.

Create inventory policy profile assignments. Within each assignment, you can associate inventory policies with a segment. All item-locations within a segment inherit the same policy values. Inventory policy profile assignments help you compare results across different policy types and replenishment strategies.

STEPS TO ENABLE




When you opt in to use this feature, you must opt in to the feature named Replenishment Planning. Opting in to the Replenishment Planning feature enables all of the Replenishment Planning features described here.


If you have defined values for Policy Parameters Overrides at either at the segment level or at item-location level, then policies won't be calculated for them.

ROLE INFORMATION

14

1. 2.

Define a large enough value for the Horizon for Average Daily Demand attribute to capture variations in daily demand.

If you have defined segment level policy overrides, then these overrides will be applicable to all item-locations within that segment.

If the value for the Days of Cover Basis attribute is History, then ensure that valid demand history is included in the plan. If the value for the Days of Cover Basis is Forecast, then ensure that a valid forecast is included in the plan. Otherwise, safety stock won't be calculated.

Define Default Policy Parameters, if you think some of these parameters may not be available at Item-Locations level. Policy calculation will first look at parameters defined at item level, if not found then it will look at default policy parameters.

Ensure that all the cost components, such as Standard Cost, Inventory Carrying Cost, and Ordering Costs, are available if you chose to use the EOQ-based maximum quantity calculation.

Don't use a Policy UOM of Days if you want to have policies that are non-time varying.

KEY RESOURCES

Oracle Replenishment Planning Cloud readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



COMPUTE DEMAND-DRIVEN REPLENISHMENT ORDERS

Replenishment planning automates decision making by answering two fundamental questions:

When should orders be placed to restock inventory?How much should be ordered?

Replenishment planning helps you transform raw demand transaction data and order lead time estimates into rules for managing inventory thresholds. It accounts for uncertainty in demand and lead times, along with current inventory thresholds, when calculating replenishment orders to restock facilities. Replenishment planning offers various inventory policy strategies that generate replenishment orders according to your business objectives. The quantities in these replenishment orders maintain inventory positions at or above your desired inventory policy thresholds.

You can calculate inventory policy parameters and replenishments for specific segments or organizations. Replenishment orders are generated instantaneously when the inventory position falls below the minimum threshold. Based on the specified inventory policy, the replenishment order may be a fixed order quantity or computed quantity, calculated as a difference between the maximum threshold and inventory position. You have the option to compute just inventory policy parameters or replenishment orders.

In addition, compute replenishment orders logic uses the primary sourcing lane only, so that supply isn't a constraint. All replenishment orders will be fulfilled from their respective primary source as defined by sourcing rules.



15

STEPS TO ENABLE






You can generate forecast, compute policy parameters, and generate replenishments within the same plan.

Because the frequency of policy calculations is typically different from replenishment calculations, you can decide to calculate policies in a separate plan and feed that plan to a replenishment plan which computes only replenishments.

You can configure a Replenishment plan to run in lights out mode by selecting the Incremental Plancheck box in the plan options. If you selected the option, then the plan will run in the Incremental Plannet change (incremental) mode only for those item-locations whose supplies or demands have changed since the last plan run. You need to run net change collections for this.

You must assign a sourcing rule to generate replenishments correctly for an item-location.

The Make sourcing type isn't supported.

KEY RESOURCES


ROLE INFORMATION



TAILOR PLAN SCOPE

Tailor the scope of replenishment plans to match your business objectives. Create a named replenishment plan by specifying the segments to be planned, along with the hierarchies that you will use for data analysis. You can use one of two approaches:

Base the replenishment plans on forecasts or demand schedules from Oracle Demand Management Cloud, or from shipment or consumption history collected from Oracle Supply Chain Execution Cloud.

Run replenishment plans as a process in lights-out mode using transactional data, such as sales orders, inventory on-hand, and purchase orders from Oracle SCM Cloud.

https://cloud.oracle.com/saas/readiness?offering=scp


16

In both scenarios, you can automatically release replenishment orders based on predefined rules, or manually release orders to Oracle SCM Cloud or external systems for execution.

STEPS TO ENABLE






Ensure that the segments included in the plan scope have policy parameters defined under the plan's policy assignment set. Otherwise, policies will not get recalculated.

For short term execution plans, use a planning time level of Day. For longer term plans, use a planning time level of Week, Period, or Month.

If you use Week or Period as the planning time level, then specify the week or period start dates in the Planning calendar.

Remember these statements:

Only segment groups with the Product and Organization dimensions will be visible in plan options.Only item-organizations with the Replenishment Planning value for the Planning Method attribute are planned in replenishment plans.

KEY RESOURCES


ROLE INFORMATION



MONITOR PLAN PERFORMANCE

Use embedded analytics to orient yourself to the state of the replenishment plan so that you can prioritize the issues to act upon. You can view the changes or exceptions by segment or item-location at a glance, and drill down to access additional details with a single click. These analytics help you monitor changes in a plan and respond to critical issues more rapidly.

The Replenishment Planning work area includes these embedded analytics:



17

Segment Analysis: Shows how item-locations are classified into segments. You can evaluate the performance of each segment based on the number of stockouts, stockout cost, the number of safety stock and fill rate violations, the fill rate shortfall percentage, and other measures.

Policy Effectiveness: Highlights the system level fill rate. This analytic presents the system wide performance across all item-locations. By viewing the associated graph, you can indicate which segments are under performing.

Policy Execution: Highlights the number of shortages and number of replenishment orders planned and released automatically to execution systems. These shortage analytics help you decide whether your policies are ordering enough material to keep inventory at the right level.

Total Inventory Value: Presents the dollar value of the total projected available balance in the supply chain. By reviewing the associated graph, you can see which segments are under-stocked.

From each of these metrics, you can drill down to access additional details and take actions.

STEPS TO ENABLE






Use the Replenishment Workbench view to work on specific item-locations.

You may want to compare the Projected Fill Rate measure to the Target Fill Rate measure. Target Fill Rate is a predefined measure, but it is empty by default. To enter target fill rates for each segment, define a table containing the Target Fill Rate measure, and with a row or column for each segment. Enter the target fill rates into the table. Each plan run will compute values for Projected Fill Rate. After each plan run, open the predefined graph named Fill Rate Performance by Segment to compare the Projected Fill Rate to the Target Fill Rate for each segment.

Use valid filters for your analytics to work with a reasonable data size and for better performance.

KEY RESOURCES

Oracle Replenishment Planning Cloud readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION





18

SIMULATE REPLENISHMENTS

Use simulation models to try out multiple solutions to find the best way to respond to supply chain issues. Simulation models the effects of plan changes without actually executing them.

You can do the following when performing simulations for replenishment planning:

Simulate changes to inventory policy. Identify the inventory policy or parameter alternatives that maximize the performance based on input targets, such as service levels, fill rates, and inventory cost. You can make changes to the policy or policy parameter and compare metrics, such as projected fill rates, inventory details, inventory carrying cost, and inventory shortages

Simulate changes to supply and demand data. Compare baseline and simulation plans to evaluate the impact of plan changes. You can make changes to supply and demand, dates, and quantities that impact a replenishment plan and monitor their effects.

Apply simulation edits across scenarios. Define simulation sets to manage replenishment plan changes and apply them to one or more plans. You can associate a simulation set with any plan that needs evaluation. Simulation changes include inventory policy, inventory policy parameters, supply and demand dates and quantities.

STEPS TO ENABLE




When you opt in to use this feature, you must opt in to the feature named: Replenishment Planning. Opting in to the Replenishment Planning feature enables all of the Replenishment Planning features described here.


To simulate changes to policy parameters at the segment level, use the Manage Policy Assignments view within the planYou can only change the policy type assigned to a segment through the Manage Policy Assignment Set taskAfter making changes in the policy parameters, run the plan with these options selected:

Do not refresh with current dataCalculate policy parametersCalculate replenishments

You can save the policy parameter changes to a policy assignment set using the Save Changes to Policy Assignment Set plan actionThe simulation plan is run for only those segments or item-location combinations for which any one of the following attributes have been changed since the last plan run:

Policy parametersInventory policies, such as minimum quantity and maximum quantitySupplies

19

DemandsItem attributes

KEY RESOURCES


ROLE INFORMATION



MANAGE SEGMENTS AND REPLENISHMENT ORDERS USING A REST SERVICE

You may need to integrate replenishment planning with other enterprise applications in your enterprise. You can use technologies such as file-based data import (FBDI) or REST services to connect other applications. You can retrieve item-locations assigned to a segment and replenishment orders using a REST API. For example, you can use REST APIs to integrate the planned replenishment orders with a reporting system. This new capability enables standards-based interoperability of replenishment planning with other applications that you may have in your enterprise.

STEPS TO ENABLE

Review the REST service definition in the REST API guides, available from the > Oracle Help Center your apps > REST API. If you're new to Oracle's REST services you may want to begin with the service area of interest

Quick Start section.

These REST services are delivered to support the Replenishment Planning feature, which requires opt in. You must opt in to the Replenishment Planning feature in the Supply Chain Planning offering to successfully perform the REST operations described here.


You can use REST Services to:

Get the plan definition and plan options details using the resource named Replenishment Plans

Run replenishment plans using the resource named Runs, which is a child resource of the Replenishment Plans resource

Get the details of the segment groups using the resource named Planning Segment Groups

Run the parts segmentation process using the resource named Execute Parts Segmentations, which is a child resource of the Planning Segment Groups resource

Get the results of the parts segmentation process using the resource named Segmentation Results, which is a child resource of the Planning Segment Groups resource

Oracle Replenishment Planning Cloud readiness training, available on Oracle Cloud Readiness for Supply Chain Planning

KEY RESOURCES



https://docs.oracle.com/en/



20

ROLE INFORMATION



COLLECT CONSUMPTION DATA FROM ORACLE INVENTORY CLOUD

To forecast, compute inventory policy parameters, and generate replenishments based on demand signals closest to your customers, you need to capture consumption transactions or consumption information. With this update, you can collect consumption history from Oracle Inventory Cloud, where this consumption data is maintained. This consumption history provides a stable and consistent pattern of customer behavior and helps you identify changes in trends over time.

Watch a Setup Demo

STEPS TO ENABLE






Use this feature if you decide to forecast and compute inventory policy parameters at the subinventory level.

In the Collect Planning Data UI task, you can decide to collect only transfer order history or history of all inventory transactions such as inventory issues.

The total count of collected history transactions can increase significantly. Enable consumption history collection only if it's required by the business.

KEY RESOURCES

Watch Replenishment Planning Enhancements Readiness Training

ROLE INFORMATION



http://download.oracle.com/ocomdocs/global/apps_20A/scm/Replenishment_Planning/setup_demo/index.html

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Replenishment_Planning/index.html

21

FORECAST AND REPLENISH ITEMS AT SUBINVENTORY LEVELS

In retail or healthcare industries, stores or departments in a hospital were modeled as inventory organizations prior to this update. With this update, you can model retail stores or departments in a hospital as subinventories. As a result, you have the flexibility to choose between inventory organizations or subinventories based on what is the better decision for your specific business requirements.

You can maintain both demand information and inventory information at the subinventory level to enable better generation of forecasts, calculate inventory policies, and generate replenishment orders. This option can help you improve the overall efficiency of your end-to-end business process.

If you set the attribute Plan Subinventories to YES for an inventory organization in the supply network model, then all of the subinventories for that inventory organization are enabled for planning. The organization will be planned at the subinventory level, and not at the organization level. (The default value for the Plan Subinventories attribute is NO.)

Here's what you can do when replenishing at the subinventory level:

Create segment groups that have segments with item-subinventories as members. When validating criteria for an item-subinventory, item attributes of the associated organization will be used.

Forecast at the item-subinventory level. The forecasting process will provide MAPE, intermittency, and average arrival times at the subinventory level to facilitate the determination of safety stock computation.

Identify the subinventories to be replenished in the Plan Options UI.

Specify sourcing rules between the following:

Subinventories of the same inventory organizationAn inventory organization and a subinventory of another inventory organizationA subinventory and a supplier site

Generate replenishment orders for subinventories that respect lead times, order modifiers, and vendor minimums.

Simulate replenishment at the subinventory level.

Review analytics that account for replenishment plans with subinventory information.

Item-subinventories that are part of a segment will inherit the inventory policy and policy parameters assigned to the segment in computing policy values. You can specify policy override values for an item-subinventory.

Watch a Setup Demo

STEPS TO ENABLE




22




For a particular organization, you can plan it either at the organization level, or you can plan the subinventories within that organization.

You are allowed to configure a replenishment plan which includes those organizations which are being planned at organization level and other organizations which are being planned at the subinventory level.

In the Organization hierarchy, subinventories and organizations are treated as the same level. So, the aggregation of subinventory level plan results to parent organizations is not supported.

To generate forecasts at subinventory level, you will need to have demand history transactions at the subinventory level.

In most of the Replenishment planning specific views, the Location column displays both organizations and subinventories. In the Location column, a subinventory is shown in the format Organization:Subinventory. For example, the Store subinventory within the M1 organization will be shown as M1:Store. For an external source system, the source system is prefixed. For example: EXT1:M1:Store.

KEY RESOURCES


ROLE INFORMATION



ENABLE INVENTORY POLICY COMPARISON

Many companies generate forecasts and compute inventory policy parameters on a weekly or a monthly basis, but plan replenishments on a daily basis. Between two successive computations of inventory policy parameters, the forecast may change, so you may need to edit the inventory policy values. Additionally, new events may cause a spike in your forecasts, so you need to consider changes to your inventory policy parameters.

With this update, you can compare the newly calculated inventory policies with existing, in-force policies at the item-location level. If you have defined specific thresholds, the newly calculated policies are automatically accepted if they are within the thresholds. If the policy values are outside the defined threshold, you can follow a systematic policy review process to accept, retain, or manually override the new policy values. To ensure there is no impact to a replenishment plan run, the existing policies will be used until they are updated by new policy values.

Here are a few things to keep in mind regarding policy comparisons:


23

Minimum Quantity, Maximum Quantity, Minimum Days, Maximum Days, Reorder Point Quantity, and Reorder Point Days are the supported policy values.

You can enable this feature in the Plan Options UI:

Select Calculate Inventory Policies, and don't select the Calculate Replenishments option.Choose the plan option Enable Policy Comparison and define a value for the Threshold Percentage for Policy Comparison attribute.

The new inventory policy values will be automatically accepted if the inventory policy type or inventory policy UOM was changed between successive runs.

If the Retain Policy Overrides plan option is selected, then for policy values with user overrides, the suggested policy values are not automatically accepted even if the suggested policy values are within the threshold percentage and the existing policy values are retained. If the Retained Policy Overrides option is not selected, then all of the existing policy overrides will be deleted.

If there are no existing policy values, then the new policy values are automatically accepted.

Use the Policy Comparison page to accept, retain, or manually override the suggested policies. Once you complete the policy review process, you can decide to approve the policies for execution.

Watch a Demo

STEPS TO ENABLE




Watch a Setup Demo

KEY RESOURCES


SALES AND OPERATIONS PLANNING

LOAD DATA FROM ONE MEASURE TO ANOTHER MEASURE ACROSS PLANS

You need visibility of data from a measure across planning applications to enable business processes and drive effective decision making. With this update, you can copy the data from a plan in one application to another plan in a different application to provide this visibility. For example, you can make the constrained forecast from Oracle Sales and Operations Planning Cloud visible to demand planners in Oracle Demand Management Cloud for reference.

You can also enable further refinement of the operations forecast. And you can copy a calculated measure into another measure, where it can be aggregated or disaggregated. Additionally, you can save measure mappings for reuse in subsequent plan runs.

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Replenishment_Planning/demo/index.html



24

This new capability enhances interoperability and collaborative planning across the Oracle Supply Chain Planning Cloud applications.

Watch a Demo

STEPS TO ENABLE



You can create and save your measure mappings in a measure copy set so that you don't have to create them every time you run the Load Measures from Other Plans process.

To quickly run the Load Measures from Other Plans process, you can apply a previously saved measure copy set and then run the process.

You can map a source measure to same or different target measure.

You can map a calculated source measure to a stored target measure.

A target measure will be automatically populated by default with the same measure name as the source measure if the measure is available in the target measure catalog.

If the source measure is not available in the target measure catalog, then the target measure will not be automatically populated, and you need to manually select the target measure.

Source and target measures should have the same type (numeric, string, or date.)

If the source measure is stored, then the target measure can't be a calculated measure.

A mapping isn't supported when both the source and target measures are calculated with different dependent measures.

When you're creating a new mapping row, you shouldn't select a measure in the source measure that's already used as a source measure in another mapping row.

When you're creating a new mapping row, you shouldn't select a measure in the target measure that's already used as a target measure in another mapping row.

Archive measures will be filtered out of the source and target measures list of values.

KEY RESOURCES

Watch Load Data from One Measure to Another Measure Across Plans Readiness Training

ROLE INFORMATION


Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Load_Data_from_One_Measure_to_Another_Measure_Across_Plans/demo/index.html

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Load_Data_from_One_Measure_to_Another_Measure_Across_Plans/index.html

25

INCLUDE ARCHIVED MEASURES WHEN COPYING PLANS

Previously, Oracle Sales and Operations Planning Cloud enabled you to make a standalone copy of a plan with no reference to the original plan. The copy included all plan reference data, such as items, bills of resources, resources, and suppliers, but not archived measures. With this enhancement, you can include archived measures in the standalone copy to generate a complete replica of your sales and operations plan, with all revisions.

Watch a Demo

STEPS TO ENABLE



Create a backup copy of your approved Sales and Operations plan with all details including archived measures at the end of every S&OP planning cycle.

KEY RESOURCES

Watch Include Archived Measures When Copying Plans Readiness Training

ROLE INFORMATION

Users assigned to the following job roles will automatically be able to use this feature and no special privileges are required:

Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER)

USE A FORECAST MEASURE IN ORACLE DEMAND MANAGEMENT CLOUD AS A BASELINE FOR CONSENSUS FORECASTING

When you use Oracle Demand Management Cloud to manage the operations forecast, you might need to use that forecast measure as the input to consensus planning or aggregate supply planning in Oracle Sales and Operations Planning Cloud. You now have the flexibility to use any demand plan measure as the input into your sales and operations plan to simplify your demand review process.

This feature helps manage the demand and supply balancing process flexibly when you're using both Demand Management and Sales and Operations Planning applications.

Watch a Demo

STEPS TO ENABLE


http://download.oracle.com/ocomdocs/global/apps_20A/scm/Include_Archived_Measures_When_Copying_Plans/demo/index.html

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Include_Archived_Measures_When_Copying_Plans/index.html

http://download.oracle.com/ocomdocs/global/apps_20A/scm/Use_Forecast_in_Demand_Management_as_Baseline_for_Consensus/demo/index.html

26

The predefined Final Shipments Forecast measure is the default demand plan measure. You can choose to use another predefined measure, such as the Approved Final Shipments Forecast or Final Bookings Forecast measures as the demand plan measure. If you are using a user-defined, demand forecast measure as the input to consensus planning then it must be added to the End Item Demand measure group.

The demand plan measure is copied to the predefined Shipments Forecast measure in your sales and operations plan.

You can't generate a statistical forecast in a sales and operations plan that uses a demand plan measure as the input to consensus planning. It's assumed that the demand plan measure incorporates the baseline statistical forecast.

Use the Load Measures from Other Plans process to copy data for additional measures from your demand plan to your sales and operations plan.

KEY RESOURCES

Watch Use a Forecast Measure in Demand_Management as a Baseline for Consensus Forecasting Readiness Training

ROLE INFORMATION


Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)

SUPPLY PLANNING

INCLUDE ARCHIVED MEASURES WHEN COPYING PLANS

Previously, Oracle Supply Planning Cloud enabled you to make a standalone copy of a plan with no reference to the original plan. The copy included all plan reference data, such as items, bills of resources, resources, and suppliers, but not archived measures. With this enhancement, you can include archived measures in the standalone copy to generate a complete replica of your supply plan, with all revisions.

STEPS TO ENABLE



Create a backup copy of your approved Sales and Operations plan with all details including archived measures at the end of every S&OP planning cycle.

KEY RESOURCES

The Include Archived Measures When Copying Plans readiness training available on Oracle Cloud Readiness for Supply Chain Planning


https://download.oracle.com/ocomdocs/global/apps_20A/scm/Use_Forecast_in_Demand_Management_as_Baseline_for_Consensus/index.html

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Use_Forecast_in_Demand_Management_as_Baseline_for_Consensus/index.html



27

ROLE INFORMATION


Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER)Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER)

CONSTRAINT-BASED PLANNING

Create and run supply plans that consider material and capacity constraints. Focus on meeting demand on time by evaluating all possible alternatives, such as using different sources, substitute components, or alternative work definitions.

After you opt in to the feature named Constraint-Based Planning, you can use the feature described in this section.

PLAN OUTSIDE PROCESSING OPERATIONS

Your business might use a variety of fulfillment strategies that include outside processing, contract manufacturing, drop shipment, and back-to-back order flows. You can choose which of these fulfillment strategies to use (including the outside processing strategy) based on customer-specific or order-specific situations. With this update, outside processing operations are also planned in a constrained supply plan in addition to the other fulfillment strategies.

STEPS TO ENABLE




When you opt in to use this feature, you must opt in to the feature named . If Constraint-Based Planningyou've already opted in to this feature, you don't have to opt in again.

Additional tips:

You can plan operations performed by suppliers using this feature. These operations are part of routings of items that are manufactured in house.

The duration of the supplier operation is offset based on the organization manufacturing calendar.

An outside processing operation does not technically have a resource as it is a supplier activity. However the planning process create a dummy resource it populates the resource name as Outside Processing.

28

Watch Plan Outside Processing Operations Readiness Training

ROLE INFORMATION


Materials Planner (ORA_MSC_MATERIALS_PLANNER)Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER)

ORDER BACKLOG MANAGEMENT

Reschedule your order backlog by prioritizing orders based on flexible demand priority rules. In contrast to how Global Order Promising in Oracle Order Management Cloud schedules orders on a first-come, first-served basis, Order Backlog Management uses flexible demand priority rules to assign the latest available supply and resources to orders in whatever sequence you choose. You can simulate the effect of different rules to find the best combination of scheduled dates and sources, and then release the updated orders to order management systems for execution.

After you opt in to the feature named Order Backlog Management, you can use the features described in this section.

ANALYZE ORDER SCHEDULING PERFORMANCE

To manage the order backlog effectively, you can use the metrics provided in the Backlog Management work area to understand your company's overall scheduling performance.

These metrics highlight the number and percentage of lines scheduled by the customer's requested date, including both past and in-process orders. The metrics also monitor average order cycle time and the value of delayed orders. You can review performance by item, organization, and customer to quickly identify areas of concern and improvement. You can then drill down to the related demands to improve results.

STEPS TO ENABLE




When you opt in to use this feature, you must opt in to the feature named: Order Backlog Management. Opting in to the Order Backlog Management feature enables all of the Order Backlog Management features described here.


If the analytics are not visible in the Backlog Management work area, use the action and select Openthe Backlog Analytics graph.

KEY RESOURCES

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Plan_Outside_Processing_Operations/index.html

29

You can use the page-level filter to view analytic data for one or multiple organizations. OrganizationThe analytics will then be calculated only for the orders that are shipped from these organizations.

Use the page-level icon to refresh analytic data. You must do this when there are newly Refreshcollected demands, or when planning results have changed and have been saved.

If you are running simulations and launching plans using the action in the Backlog Analysis Run PlanUI, the analytics are updated only when you save planning results using the Save Planning Resultsaction.

KEY RESOURCES

The Analyze Order Scheduling Performance readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION


Backlog Manager (ORA_MSC_BACKLOG_MANAGER)

PRIORITIZE DEMANDS BASED ON EXTENSIBLE BUSINESS RULES

Your most important orders should get priority when supplies are limited. Backlog Management ranks competing demands based on your selection of criteria, such as requested date, order creation date, item category, and customer. You can add your own extensible attributes to the standard ones by loading them through a file from an external source system. You can also override these rule-based priorities as needed to deal with exceptions or changing conditions.

STEPS TO ENABLE




When you opt in to use this feature, you must opt in to the feature named Order Backlog Management. Opting in to the Order Backlog Management feature enables all of the Order Backlog Management features described here.


You can specify multiple demand priority rules and specify one to be the default demand priority rule. While interactively planning orders in the Backlog Analysis UI, you can choose any demand priority rule to simulate planning results with a different prioritization basis.

Demand Priority Rules enable you to prioritize demands based on multiple ranked criteria called demand priority attributes. You can utilize any available order attribute while defining the priority rule. For example, you can prioritize orders for a specific customer first, and then prioritize remaining orders by order revenue, and then by requested date. Also, you can specify how the values for each attribute



30

must be considered in prioritization sequence. For example, for the Order Revenue attribute you can specify , for Requested Date you can select , and also specify a ranked Larger to Smaller Earlier to Laterlist of customers to prioritize by.

You can make use of user-defined attributes to prioritize orders, but this capability is supported only with external order management systems, and not with Oracle Fusion Order Management. If you have already defined priorities using your own logic, you can load the priority into a user-defined attribute and then use that attribute to prioritize your orders.

You can also rank competing demands based on sets of criteria values. For example, you can specify the Rank 1 prioritization to be based on an attribute called where the order My Order Type Expeditedtype has the highest priority, followed by the order type. You can specify a Rank 2 criteria based Ad Hocon an attribute called and then prioritize orders over Product Launch Status New Product Launch

orders. Doing so will prioritize the and orders over Prototype Expedited New Product Launch Ad Hocand orders.Prototype

KEY RESOURCES

The Prioritize Demands Based on Extensible Business Rules readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



HONOR PREVIOUSLY PROMISED DATES DURING RESCHEDULING

Rescheduling orders unnecessarily can reduce customer satisfaction. By default, Backlog Management preserves existing scheduled dates for orders as it identifies opportunities to improve dates for backlogged demands. This approach minimizes the need for you to communicate and negotiate changes to delivery dates. However, you can also choose to let Backlog Management delay lower priority orders in order to satisfy higher priority ones.

STEPS TO ENABLE






The attribute value specification for a demand indicates whether the backlog Enforce Current Commitplanning process must meet the demand's current promised (scheduled) date. This attribute's value is



31

set to by default. You can change the value to for specific demands that are of lower priority Yes Noand which can be delayed.

You can edit the attribute for one or more demands in the Backlog Analysis UI, Enforce Current Commitor you can update it through a REST service. It's not a collected attribute, so it's not accounted for during the planning data collection process.

KEY RESOURCES

The Backlog Management readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



IDENTIFY ORDER RESCHEDULING REVENUE OPPORTUNITIES AND GAPS

To help you address order scheduling issues and opportunities, Backlog Management highlights the value of orders that meet either of these criteria:

Orders you can reschedule to earlier datesOrders that no longer have supply available to meet their current shipment or delivery plan

You can use these intelligent recommendations to maximize the value of orders that you can ship within a fiscal period, or simply to improve customer service.

STEPS TO ENABLE





You can view orders whose scheduled dates can potentially be improved, and also orders that are at risk of not being fulfilled by their scheduled dates. Do so using the Planned Fulfillment Changes by Demand Valueanalytic. This analytic shows you revenue corresponding to demands that can be improved or that are at risk. You can view this metric across all demands, or by organization, and then drill down to individual order details. Alternatively, you can review the value that's calculated for every demand, which Days of Improvementindicates the demand's potential to improve or worsen.

If the analytics are not visible in the Backlog Management work area, use the action and select Openthe Backlog Analytics graph.



32

You can use the page-level filter to view analytic data for one or multiple organizations. OrganizationThe analytics will then be calculated only for the orders that are shipped from these organizations.

Use the page-level icon to refresh analytic data. You must do this when there are newly Refreshcollected demands, or when planning results have changed and have been saved.

If you're running simulations and launching plans using the action in the Backlog Analysis UI, Run Planthe analytics are updated only when you save planning results using the action.Save Planning Results

KEY RESOURCES


ROLE INFORMATION



ADJUST FULFILLMENT STRATEGIES

You may need to update an order's sourcing, shipment method, or other fulfillment attributes to maximize availability. In the Backlog Management work area, you can edit these attributes for groups of order lines. You can first simulate the changes, to review the results of your changes. You can save the edits that best meet your objectives.

STEPS TO ENABLE





KEY RESOURCES


ROLE INFORMATION







33

SCHEDULE ORDERS BASED ON CONFIGURABLE SUPPLY TYPES

Your longer-term orders should consume future supply, preserving on-hand inventory, scheduled receipts, and other existing supply for more near-term demands. Backlog management can schedule based on planned orders loaded from external systems, as well as executable supply sources, such as on-hand inventory, scheduled receipts, and open purchase requisitions. Your planned orders can augment the executable supply in scheduling calculations to reduce backorders and increase the accuracy of longer-term schedule dates.

STEPS TO ENABLE






You use this capability while defining backlog planning rules in the Backlog Planning Rules UIs. These rules are shared by the ATP Rules UIs in Global Order Promising. Changes made to backlog planning rules or to their item assignments may impact real-time promising in Global Order Promising.

Use backlog planning rules to restrict the number of items whose supplies are considered while planning orders, in both Backlog Management and Global Order Promising. Often only a subset of items are supply-constrained. You can configure the supply you want considered for such items and associate the other items with a promising mode that's infinite-availability based or lead time based.

KEY RESOURCES

The Schedule Orders Based on Configurable Supply Types readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



MANUALLY SPECIFY, OVERRIDE, AND LOCK SCHEDULING RESULTS

Sometimes you must ship or deliver a critical order on a particular date. Backlog management lets you specify and lock dates on individual orders, so they are preserved during rescheduling. You can lock dates so you can process the rest of the backlog using rule-based priorities without affecting critical orders.



34

STEPS TO ENABLE






You can lock planning results for an order only after running the plan on that order. The lock applies to the Planned Date attribute, which is made available only after the order has been planned. The lock on an order's planning results is preserved until you unlock them, either manually from the Backlog Analysis UI or by using a REST service.

While manually overriding planning results, you don't need to specify values for all the Planned attributes. For example, you can specify just the planned ship date, and the backlog planning process will automatically calculate the planned arrival date after considering calendars and lead times.

The backlog planning process allocates supply to orders that have been manually overridden and locked by considering them to be of the highest priority. Also, the planning process never automatically changes the planned dates that have been locked or manually specified.

KEY RESOURCES

The Manually Specify, Override, and Lock Scheduling Results readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



RESOLVE ITEM CONSTRAINTS WITHIN A SHIPMENT SET OR ARRIVAL SET

When a group of items should ship or arrive together, limited availability of a single component can delay the entire order. Backlog management provides guided resolution that pinpoints the components or items that are delaying scheduling of a set. Use these details to decide which action to take:

Remove them from the setFind a different sourceSubstitute another item to meet demand

Breaking up sets and resolving arrival set constraints are supported only with an external order management system.



35

STEPS TO ENABLE






The ability to break a set is not supported for orders from Oracle Fusion Order Management. The actions to remove lines from a set or to add lines back to a set are not enabled for such orders.

If you had removed lines from a set that you want to add back, you can do so by first selecting the View action in the Manage Set UI, and by then selecting the lines you want to add back to the set All Lines

using the action.Add Back to Set

KEY RESOURCES


ROLE INFORMATION



SCHEDULE BATCHES OF UNSCHEDULED ORDERS

Your company may not immediately provide a customer with a promise date when they place an order. Instead, you wait until you receive enough orders to schedule them as a batch. Backlog management can process unscheduled orders along with previously scheduled orders in priority sequence, resulting in more accurate shipment and delivery dates.

NOTE: Order Management Cloud does not support this scenario.

STEPS TO ENABLE





36




You can collect unscheduled orders through the same process that's used to collect scheduled orders. You don't need to specify scheduled dates for unscheduled orders.

You can use the attribute in a demand priority rule to prioritize unscheduled or Scheduling Statusscheduled orders.

The backlog planning process automatically allocates supply to meet existing commitments, which are represented by the attribute. If you want to prioritize unscheduled orders over Scheduled Datescheduled orders, you must set the attribute value for the scheduled orders to Enforce Current Commit

.No

KEY RESOURCES

The Schedule Batches of Unscheduled Orders readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



AUTOMATICALLY UPDATE AND RESCHEDULE THE ORDER BACKLOG

It can be time consuming to reschedule backlogged orders whenever supply or demand availability changes. Backlog management can reassess all or part of the order backlog in automated fashion to improve scheduling results based on the latest information. This periodic, lights-out evaluation of the backlog can enhance customer service with a minimum of effort.

STEPS TO ENABLE







37

The Start Backlog Planning scheduled process has a number of parameters that can be used to limit the orders that you want replanned. For example, you can specify an organization to have only demands in this organization replanned when there is new supply availability at this organization. But if you want to replan only a subset of all your demands, like those belonging to a specific organization, you must ensure that these demands are independent of demands at any other organization. Because if components are shared by orders at multiple organizations, then, while the orders at your selected selected organization may be replanned, the orders at the other organizations may not be replanned. This could lead to inconsistent planning results.

You need not select a demand priority rule while launching the Start Backlog Planning scheduled process that is used to plan the order backlog. If you don't select a demand priority rule, the default demand priority rule that was specified using the task will be used Manage Backlog Planning Optionsautomatically.

KEY RESOURCES


ROLE INFORMATION



RELEASE RESCHEDULING RECOMMENDATIONS TO ORDER MANAGEMENT SYSTEMS

To prevent errors, you need to control the communication of rescheduling recommendations to your order management system. Release new dates, sources, and transit modes for affected orders automatically or manually. Updates either flow to Order Management Cloud or to export files that can be loaded into an on-premise order management system.

STEPS TO ENABLE








38

Release planning results for related orders together. For example, if the planned dates for some orders have improved as a result of other lower priority orders being decommitted, then release planning results for all these orders together in order to provide a correct picture within the order management system.

KEY RESOURCES

The Release Rescheduling Recommendations to Order Management Systems readiness training available on Oracle Cloud Readiness for Supply Chain Planning

ROLE INFORMATION



UPDATE ORDERS, RESCHEDULE BACKLOG, AND REVIEW RESULTS USING REST SERVICES

If you want to manage your backlog from an external program, you can use built-in REST services to perform routine tasks. You can programmatically update orders, run plans, and retrieve rescheduling results as part of a larger fulfillment process.

Use the Runs and Releases resources within the parent Backlog Management Plans resource to launch a plan within Backlog Management and release results using the POST action

Use the Demands resource within the parent Backlog Management Plans resource to extract and update demand information using the GET and PATCH actions

STEPS TO ENABLE

Review the REST service definition in the REST API guides, available from the > Oracle Help Center your apps > REST API. If you're new to Oracle's REST services you may want to begin with the service area of interest

Quick Start section.

These services are delivered to support the Order Backlog Management feature, which requires opt in. You must opt in to the Order Backlog Management feature to successfully perform the REST operations described here.

KEY RESOURCES

The Backlog Management release readiness training, available on Oracle Cloud Readiness for Supply Chain PlanningRefer to the documentation available on the REST APIs for Oracle Supply Chain Management CloudOracle Help Center

ASSESS THE SCHEDULING IMPACT OF ORDER INQUIRIES

You might need to process order inquiries to simulate the impact of accepting the order, but you don't want to affect actual results during rescheduling. You can add order inquiries to your backlog that have all the attributes of a sales order, but represent a potential order or demand projection, rather than an actual,



https://docs.oracle.com/en/



https://docs.oracle.com

39

executable order. When you run a plan that includes inquiry orders, backlog management simulates the impact of accepting a high priority inquiry demand on other existing demands without affecting exported results during rescheduling.

You can load inquiry demands into Backlog Management using the same File-Based Data Import (FBDI) file that you generate to upload sales orders.

Note that in this update, Backlog Management only supports order inquiries when deployed with external order management systems.

Watch a Demo

STEPS TO ENABLE






You can create order inquiries in the same FBDI file that you use for actual sales orders. You must set an additional attribute, the attribute, to Yes to indicate that the order is an inquiry Inquiry Demandorder and not a regular sales order

You can search for order inquiries in the Backlog Analysis UI using the attribute, for Simulation Demandwhich the values are Yes or No

You can't release planning results for order inquiries because they're not actual sales orders

Order inquiries and their planning results do not update Analytic data in Backlog Management

Order inquiries will continue to be planned in Backlog Management until they are deleted. You can delete specific order inquiries using the Sales Order FBDI template (like you would delete regular sales orders), or you can delete all inquiry orders using the scheduled Delete Backlog Planning Session Dataprocess by enabling the attributeDelete Inquiry Demands

KEY RESOURCES

Watch Reservations Support and Other Enhancements Readiness Training

ROLE INFORMATION



http://download.oracle.com/ocomdocs/global/apps_20A/scm/Backlog_Management/demo/index.html

https://download.oracle.com/ocomdocs/global/apps_20A/scm/Backlog_Management/index.html

40

RESPECT RESERVATIONS OF SUPPLY AGAINST SALES ORDERS

If you reserve a sales order against on-hand inventory, back-to-back supply, or drop-ship purchase orders, Backlog Management will respect the reservation and use only the reserved supply to plan for the sales order. If the order you are managing is only partially reserved against the supply, then the backlog management processes search for remaining supply, and then allocate it to the order. In case the reserved supply has changed its supply date, then Backlog Management will revise the planned date so that it aligns with the updated supply date.

Watch a Demo

STEPS TO ENABLE






There are additional fields that have been introduced in the Backlog Analysis table for reservation information: Reservation Status (Yes or No), Reserved Quantity, Reserved Supply Document Number that indicates the specific supply number the sales order is reserved to, and Reserved Supply Document Type. These fields are useful to search for sales orders that are reserved. For example, you can search for all sales orders that are reserved against a specific purchase order or work order whose supply date has changed. These sales orders can then be planned again to ensure that their scheduled dates are aligned with the new supply date.

Backlog Management respects reservation information on sales orders as a hard constraint. For example, you cannot change the organization on a sales order to plan it from another organization as that would break the reservation. Edits of the Organization attribute and other attributes on reserved sales orders have thus been disabled.

KEY RESOURCES


ROLE INFORMATION



http://download.oracle.com/ocomdocs/global/apps_20A/scm/Backlog_Management/demo/index.html


41

UPDATE GLOBAL ORDER PROMISING SCHEDULED DATES IN REAL TIME WHEN ORDERS ARE RELEASED

When Backlog Management releases planning results for sales orders, it updates the scheduled information for each order within the global order promising process as part of the release process, without requiring order promising to be restarted. These updates to scheduled information ensure that the scheduled information on your orders is continually synchronized among Backlog Management, Global Order Promising, and Order Management data.

STEPS TO ENABLE






You don't need to do anything specific to enable Backlog Management to update scheduled dates within Global Order Promising. When demands are released, Global Order Promising is automatically called and its scheduled information is updated to be consistent with the planned information in Backlog Management

In addition to the scheduled dates, Backlog Management also updates the organization or drop-ship supplier and site and the shipping method that has been used to plan the sales order within Backlog Management

KEY RESOURCES


ROLE INFORMATION



---


42

Copyright © 2020, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U. S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Oracle Supply Chain Planning Cloud 20A What's New

Documents