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 |
|---|---|---|
| 08 JUN 2020 | IMPORTANT Actions and Considerations | Updated document. Added a section for IMPORTANT Actions and Considerations. |
| 08 JUN 2020 | Define a Time Window for Plan Pegging Calculations | Updated document. Removed duplicate paragraphs in the feature description. |
| 09 APR 2020 | Extract Sourcing Rules and Assignment Sets | Updated document. Changed the feature category to Opt In Only and identified the feature to opt in to. |
| 09 APR 2020 | Query Supplies and Demands Faster by Specifying Required Search Criteria | Updated document. Provided additional opt in information. |
| 09 APR 2020 | Efficiently Configure Columns to be Displayed | Updated document. Changed the feature category to Opt In Only and identified the feature to opt in to. |
| 20 MAR 2020 | Created initial document. |
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 oracle_fusion_applications_help_ww_grp@oracle.com.
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 by stepping through the following instructions:
Access the Opt In page from the New Features Work Area
- Click the Navigator, and then click New Features (under the My Enterprise heading)
- On the New Features page, select the offering that includes new features you’d like to review
- Click Go to Opt In for any feature you want to opt in
- On the Edit Features page, select the Enable option for the feature, and then click 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 click here to see features with Opt In Expirations across all Oracle Cloud Applications.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable 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 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 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 |
UI or |
|
||
Override the Demand History End Date for Out-of-Sample Forecast Tuning |
||||||
Query Supplies and Demands Faster by Specifying Required Search Criteria |
||||||
Query Supplies and Demands Faster by Specifying Required Search Criteria |
||||||
Implement Fixed Days of Supply Order Policy in a Plan with Aggregate Time Buckets |
||||||
Automatically Include Planned Order Supplies from a Supply Plan |
||||||
Override the Demand History End Date for Out-of-Sample Forecast Tuning
A critical question you often ask with a statistical forecast is “How can I know whether the forecast model is good or bad?” With this update, you can use a technique often referred to as back-testing or out-of-sample testing to assess the validity and accuracy of a statistical forecast. To perform this type of testing, you use historical data up to a point in the past, and then compare the statistical forecast generated using this data to the actual sales history from a predefined point in time in the past to the current date. (You may refer to this technique as the holdout period.)
You can use this technique for your model in Oracle Demand Management Cloud by specifying the offset for the end date of historical data from the current date. Using this offset, you can tune the statistical forecast parameters to reduce the forecast error by comparing the forecast to the actuals in the time period between the offset end date and the current date.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The History Offset Time Bucket value is determined based on the selected Forecasting Time Level value in the plan.
- When you change the History Offset value, the History Start Date, History End Date, and Forecast End Date values are updated automatically.
- You should increase the value of the Demand History Days setting to cover the offset history.
- For seasonal monthly data, the last history dates may be very volatile so at least two years of history is recommended in addition to the removed part, but never less than one year of history.
- The History Average value doesn't reflect the History Offset value.
Key Resources
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)
Forecast for Engineer-to-Order Items
In an engineer-to-order environment, manufacturers compete for business for a product where the actual details of the product are finalized after the sales contract is executed. For example, your enterprise may be competing to build infrastructure for a data center, such as cabling where the details such as the length of the cable and type of cable are determined after the contract is executed. The manufacturing and engineering teams determine the bill of material and other manufacturing details after understanding the details of the sales order.
You can now forecast the engineer-to-order model and consume the sales orders for items that are associated with the model. This capability enables you to plan for the supply of critical components and resources with long lead times even as the details are being finalized. Note that the reference information that ties the model to the item is manually entered. This approach is unlike the dynamic referencing that happens in a typical configure-to-order environment where the configured item is generated and tied to the model upon order entry.
Watch a Demo
Steps to Enable
Navigation: Plan Inputs > Collect Planning Data > Parameters > Demand Planning Data > Collection for ETO Items
To enable the Forecast for Engineer-to-Order Items feature, you need to perform 2 steps:
- Step 1: Select one or more shipments history measures, bookings history measures, or both for which you want to collect data from your order management cloud application.
- Step 2: Select the option to collect history from associated base models
Collect Demand Planning Data
Tips And Considerations
Before starting enablement for the Forecast for Engineer-to-Order Items feature, there is an implementation consideration that you need to take into account. This consideration is the restatement of the existing planning data. When you enable the option to collect history from associated base models, existing data posted against the standard item will need to be restated against the base model item. Follow this action plan to restate the planning data against the base model item of an Engineer-to-Order (ETO) item if you have already defined a demand or demand and supply plan using data that was collected or entered against the standard item of an ETO item:
Rerun collections for the entire history horizon to collect the historical demand against the base model for ETO items and to purge any existing historical demand collected against the standard item for ETO items:
- Collect shipments and bookings history for the entire history horizon (depending on number of years of history used in forecasting and planning). Because history data is always collected in the targeted mode, collection will purge the previously collected data against the standard item of an ETO.
- Run the demand history collection with the option to collect history from associated base models selected.
Then, clear any existing manual entries made against the standard item for ETO items and, if required, manually enter these against the base model:
- User measure overrides and adjustments made for the standard item of an ETO item will be preserved during the demand plan run.
- You can evaluate the following options to remove the user overrides or adjustments from the standard item in aggregate demand plans. Aggregate demand plans are plans with a plan type of Demand Plan and a planning time level of anything other than day.
- Option 1: Create a new demand plan and re-apply the overrides or adjustments against the base model item of an ETO item. Note: Do not create the new demand plan by duplicating the existing demand plan with the option to reference to base plan or the existing entries against the standard item will be copied to the duplicated plan.
- Option 2: If you don’t want to create a new demand plan, then users can manually remove their measure overrides made against the standard item and apply the overrides and adjustments against the base model item of an ETO item. Note that you can use the Copy and Paste actions to copy data from the standard item and paste it to the base model item. You can do these actions within the same table or between two tables within the same plan. You can also use the Edit action in a table to clear the values from the standard item.
- You can evaluate the following options to remove the user overrides that were made using shared editable measure, such as Adjusted Shipments History and Adjusted Bookings History, for the standard item of an ETO item in a day-level plan. These would be plans with a plan type of Demand Plan or plans with a plan type of Demand and Supply Plan and a planning time level of Day:
-
Option 1: Use the parameter overrides setting in demand advanced options to delete the existing shared measure data. Enter SDATA_TRUNCATE_### where ### is the granularity ID. For example, SDATA_TRUNCATE_135 will delete the shared measure data in granularity 135, which is measures with stored levels Item, Organization, Customer Site, Demand Class, Day, Sales Representative. You will also lose the overrides made for items that are not ETO Items. This option is applicable for demand or demand and supply plans defined at day planning time level.
Advanced Demand Plan Option Parameter Overrides
-
Option 2: You can manually remove the measure overrides and adjustments made against the standard item and reapply the overrides and adjustments against the base model item of an ETO item.
-
Finally, determine your approach for existing plan archives - old archives will contain data for the standard item:
- Option 1: Leave the old plan archives as is.
- Option 2: Delete the previous archives. This option will purge the archive of the entire plan, and you will also lose the archive of other non ETO items.
Key Resources
Role Information
Users assigned to the following job role will automatically be able to use this feature and no special privileges are required:
- Demand Planner (ORA_MSC_DEMAND PLANNER_JOB)
Schedule Batch Processes to Load Measures
You may want to orchestrate the flow of measures data across planning applications to enable business processes and drive effective decision making. For example, you may send detailed measures for demand and supply plans to Oracle Sales and Operations Planning Cloud for aggregate-level demand and supply reviews. These reviews enable you to identify potential issues quickly at a macro level and plan appropriate remedial actions. Similarly, you may send aggregate-level consensus data derived in Sales and Operations Cloud into Demand Management Cloud to be disaggregated and allocated down for item level operational forecasting.
With this update, you can automate measure data movements between supply chain plans by scheduling batch processes or by invoking REST services This capability simplifies the administration required for data transfer between plans and enhances their interoperability for effective strategic and tactical planning decisions.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You can schedule the process to load measures, the Orchestrate Load Measures Processes process, for one time or on a repetitive schedule at different frequencies, from the Scheduled Processes UI in the Scheduled Processes work area.
- After a you schedule a process, you can view or cancel it in the Scheduled Processes work area using the process ID.
- You can also run the Load Measures from Other Plans process using a REST service.
- You need to enter the required parameters to run the Load Measures process, such as the From Plan, To Plan, and Measure Copy Set parameters.
- A measure copy set contains at least one source measure to target measure relationship that will be referenced to copy the data from the source to target plan.
- The measure copy set is created in the Load Measures from Other Plans task in the Sales and Operations Planning, Demand Management, and Demand and Supply Planning work areas, and is just used in the load measures scheduled process, Orchestrate Load Measures Processes, and the REST service Load Measures Jobs.
Key Resources
Role Information
Users assigned to the following job role will automatically be able to use this feature and no special privileges are required:
- Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
Efficiently Configure Columns to be Displayed
You can efficiently analyze planning data by filtering the table columns to display and putting them in the order that works best for your enterprise. This capability, provided in the Manage Columns dialog box, was previously available in Oracle Supply Chain Planning Cloud. With this update, you can access the Manage Columns dialog box directly from the view menu in the Items tables.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
- Backlog Manager (ORA_MSC_BACKLOG_MANAGER_JOB)
- Sales and Operations Planner (ORA_MSC_SALES_OPERATIONS_PLANNER_JOB)
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.
Replan for Planner-Specific Edits
A typical replenishment plan covers a number of facilities. Your enterprise may have different planners managing different subsets of your facilities. The planners perform simulations on their subset of the replenishment plan’s item-locations to resolve local issues, such as a stock out in a storeroom or a promotional demand increase at a retail store. As they work, planners typically rerun the plan several times to review the impact of their edits.
The replenishment planning process now supports user-specific plan simulations. When a planner initiates the run plan action, only item-location combinations edited by that planner are replanned. This update ensures planners don’t impact edits made by other planners, and reduces the time required to run simulations.
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
Tips And Considerations
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 also enables the feature described here.
Additional Tip and Consideration:
- Each planner must run the Replan action to simulate changes done by that individual planner.
Key Resources
Role Information
Users assigned to following job role will automatically be able to use this feature and no special privileges are required:
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER)
Review Before and After Results of Segmentation
Item-location combinations may fall into different replenishment segments as their demand, consumption, or sales pattern change over time. With this update, you can compare the before-and-after totals and details of item-locations that were added or removed from segments during a segmentation run. You can click on the count of the item-locations added or removed from a segment, and then view the item-locations that moved in the latest segmentation run.
Watch a Demo
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
Tips And Considerations
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 also enables the feature described here.
Additional tips and considerations:
- If you want to compare the latest segmentation results with the previous results, then execute segmentation with this option selected: Save the last segmentation results.
-
If you want to retain manual overrides that were performed prior to running segmentation, then execute segmentation with this option selected: Retain segment overrides.
-
To review the previous segment associated to an item location, use the Previous Segment column on the Manage Segment Members page.
Key Resources
Role Information
Users assigned to following job role will automatically be able to use this feature and no special privileges are required:
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
Efficiently Configure Columns to be Displayed
You can efficiently analyze planning data by filtering the table columns to display and putting them in the order that works best for your enterprise. This capability, provided in the Manage Columns dialog box, was previously available in Oracle Supply Chain Planning Cloud. With this update, you can access the Manage Columns dialog box directly from the view menu in the Supplies and Demands and Items tables.
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
Tips And Considerations
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 also enables the feature described here.
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
- Backlog Manager (ORA_MSC_BACKLOG_MANAGER_JOB)
- Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
Query Supplies and Demands Faster by Specifying Required Search Criteria
The data in the supplies and demands table may take a long time to refresh if you decide to run a search that is unconstrained by any filtering condition. The time can be significant if your implementation has hundreds of thousands of supplies, demands, and pegging records.
With this update, a new saved search named Orders Due Within 60 Days requires you to define at least some parameters to refresh the data for the supplies and demands table. These parameters will then be qualified with an asterisk (*) in the search section. This change ensures that the data becomes available faster for your analysis in addition to a more targeted search result. You can still choose to run unconstrained searches by using the Application Default saved search.
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 No Longer Optional From: Update 20D
Tips And Considerations
To use this feature with Replenishment Planning, you must also opt in to the feature named Replenishment Planning.
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
Schedule Batch Processes to Load Measures
You may want to orchestrate the flow of measures data across planning applications to enable business processes and drive effective decision making. For example, you may send detailed measures for demand and supply plans to Oracle Sales and Operations Planning Cloud for aggregate-level demand and supply reviews. These reviews enable you to identify potential issues quickly at a macro level and plan appropriate remedial actions. Similarly, you may send aggregate-level consensus data derived in Sales and Operations Cloud into Demand Management Cloud to be disaggregated and allocated down for item level operational forecasting.
With this update, you can automate measure data movements between supply chain plans by scheduling batch processes or by invoking REST services. This capability simplifies the administration required for data transfer between plans and enhances their interoperability for effective strategic and tactical planning decisions.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- You can schedule the process to load measures, the Orchestrate Load Measures Processes process, for one time or on a repetitive schedule at different frequencies, from the Scheduled Processes UI in the Scheduled Processes work area.
- After a you schedule a process, you can view or cancel it in the Scheduled Processes work area using the process ID.
- You can also run the Load Measures from Other Plans process using a REST service.
- You need to enter the required parameters to run the Load Measures process, such as the From Plan, To Plan, and Measure Copy Set parameters.
- A measure copy set contains at least one source measure to target measure relationship that will be referenced to copy the data from the source to target plan.
- The measure copy set is created in the Load Measures from Other Plans task in the Sales and Operations Planning, Demand Management, and Demand and Supply Planning work areas, and is just used in the load measures scheduled process, Orchestrate Load Measures Processes, and the REST service Load Measures Jobs.
Key Resources
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_JOB)
Plan Assembly Items Using Processing Lead Times
Your enterprise may need to plan manufacturing assemblies within organizations with processing lead times that span months. Oracle Sales and Operations Planning Cloud factors the processing lead times of assembly and subassembly items for aggregate supply planning to allow production of upstream subassemblies to commence in earlier time periods, offset by the manufacturing start dates and consumption of upstream components and resources.
Manufacturing offsets for assembly items use the Processing Lead Time item attribute. Processing lead times are rounded based on the length of the time bucket. For example, assembly items having a 20-day and 35-day processing lead time in a monthly sales and operations plan will be rounded down to no offset and one period of offset respectively. Rounded numbers produce plan results that are easier to explain than partial bucket offsets. The assembly items offset applies to the immediately upstream subassembly, and processing lead times are also rounded. Sales and Operations Planning Cloud cascades these values for all upstream manufacturing stages to adequately offset the time when they should commence.
With this update, you can achieve better modeling of the offsetting required to orchestrate your multistage manufacturing process.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- Resource requirements for assembly items with processing lead times that exceed a planning time period are offset, but not spread across periods.
- Processing lead time is not accumulated across manufacturing stages. Use a simulation set to override processing lead time in order to further offset between stages.
Key Resources
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_JOB)
Efficiently Configure Columns to be Displayed
You can efficiently analyze planning data by filtering the table columns to display and putting them in the order that works best for your enterprise. This capability, provided in the Manage Columns dialog box, was previously available in Oracle Supply Chain Planning Cloud. With this update, you can access the Manage Columns dialog box directly from the view menu in the Supplies and Demands and Items tables.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
- Backlog Manager (ORA_MSC_BACKLOG_MANAGER_JOB)
- Sales and Operations Planner (ORA_MSC_SALES_OPERATIONS_PLANNER_JOB)
Extract Sourcing Rules and Assignment Sets
You may want to replicate data from your supply chain planning cloud instance to another instance or application without manually reentering data, especially because manual entry is error-prone. For example, you might want to replicate the sourcing rules in your supply chain planning cloud production instance in a reporting system or your test instance.
With this update, you can extract the data for assignment sets and associated sourcing rules into a comma-delimited values (CSV) file format. The generated file is in the standard file-based data import (FBDI) file format that you can then use to upload to other systems.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
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_JOB)
Efficiently Configure Columns to be Displayed
You can efficiently analyze planning data by filtering the table columns to display and putting them in the order that works best for your enterprise. This capability, provided in the Manage Columns dialog box, was previously available in Oracle Supply Chain Planning Cloud. With this update, you can access the Manage Columns dialog box directly from the view menu in the Supplies and Demands and Items tables.
Watch a Demo
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
- Backlog Manager (ORA_MSC_BACKLOG_MANAGER_JOB)
- Sales and Operations Planner (ORA_MSC_SALES_OPERATIONS_PLANNER_JOB)
Define a Time Window for Plan Pegging Calculations
Planning cycle time depends on both the volume of data that you need to evaluate and the complexity of the calculations that you need to perform. One of the most time-consuming aspects of a plan run is the generation of the pegging data for the plan. In a variety of manufacturing and distribution environments, pegging information outside a near term horizon is not used when making business decisions, so it may not be necessary to calculate it.
With this update, you can now define a time window to calculate the supply and demand pegging, which provides you another way to improve planning cycle times. No pegging data will be generated outside the horizon, but supply and demand will be balanced.
Steps to Enable
- In the Supply Planning work area, Plan Options UI, access the Supply tab.
- Click the Advanced Options button to open the Advanced Options dialog box.
- Define the demand window for pegging calculations by specifying a value in the Number of Days to Calculate Pegging field in the Pegging Parameters section.
Tips And Considerations
- You should consider the extent of impact on planning output when you select a value for the Number of Days to Calculate Pegging plan option.
- All existing plans, and any copy of these plans, will continue to calculate the pegging for the full plan unless the Number of Days to Calculate Pegging plan option is updated.
Key Resources
Role Information
Users assigned to the following job roles will automatically be able to use this feature and no special privileges are required:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
Extract Sourcing Rules and Assignment Sets
You may want to replicate data from your supply chain planning cloud instance to another instance or application without manually reentering data, especially because manual entry is error-prone. For example, you might want to replicate the sourcing rules in your supply chain planning cloud production instance in a reporting system or your test instance.
With this update, you can extract the data for assignment sets and associated sourcing rules into a comma-delimited values (CSV) file format. The generated file is in the standard file-based data import (FBDI) file format that you can then use to upload to other systems.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
Users assigned to the following job roles will automatically be able to use this feature and no special privileges are required:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
Query Supplies and Demands Faster by Specifying Required Search Criteria
The data in the supplies and demands table may take a long time to refresh if you decide to run a search that is unconstrained by any filtering condition. The time can be significant if your implementation has hundreds of thousands of supplies, demands, and pegging records.
With this update, a new saved search named Orders Due Within 60 Days requires you to define at least some parameters to refresh the data for the supplies and demands table. These parameters will then be qualified with an asterisk (*) in the search section. This change ensures that the data becomes available faster for your analysis in addition to a more targeted search result. You can still choose to run unconstrained searches by using the Application Default saved search.
Watch a Demo
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 No Longer Optional From: Update 20D
Key Resources
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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
- Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
Implement Fixed Days of Supply Order Policy in a Plan with Aggregate Time Buckets
You can now generate planned orders to fulfill the demand for an item in an aggregate time bucket, such as a week or a period, that honor the fixed days of supply order policy specified for the item. Oracle Supply Chain Planning Cloud supports various order modifier attributes that express your ordering policy preferences. Fixed days of supply is the ordering policy to place a single order for the quantity that covers the demand for the number of days specified. This parameter is now honored in plans where the plan needs to be generated in aggregate time buckets.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- In constrained supply planning:
- The inventory requirement is evaluated and then the expected supply order quantity is created with fixed days of supply per bucket.
- Constrained supply planning uses unconstrained dependent demand dates for dependent demand of components in net demand calculation for fixed days of supply.
Key Resources
- Watch Implement Fixed Days of Supply Order Policy in a Plan with Aggregate Time Buckets 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:
- Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
- Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
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.
Automatically Include Planned Order Supplies from a Supply Plan
You can use the Backlog Management work area to reschedule orders using planned order supply imported from a supply planning solution. With this update, you can also designate a supply plan in Oracle Supply Planning Cloud that will share planned orders directly with Backlog Management, so that rescheduling will automatically include the latest supply plan data. As a result, your order schedule dates can take anticipated increases or reductions of supply into account.
Watch a Demo
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
Tips And Considerations
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 also enables the feature described here.
Additional tips and considerations:
- An additional Supply Plan field was introduced on the Manage Backlog Planning Options UI. One or more supply plans can be specified in this field.
- Backlog Management will read planned orders, of the Make, Transfer, and Buy types, from supply plans. For each planned order, supply for the item on the planned order is increased while availability of components and resources required for the planned order is reduced.
- For a planned order of the Make type, component availability and resource capacity required for the planned order is consumed. For a planned order of Transfer type, supply of the item at the source organization is consumed. And for a planned order of the Buy type, supplier capacity is reduced.
Key Resources
Role Information
Users assigned to the following job role will automatically be able to use this feature and no special privileges are required:
- Backlog Manager (ORA_MSC_BACKLOG_MANAGER_JOB)
Extract Sourcing Rules and Assignment Sets
You may want to replicate data from your supply chain planning cloud instance to another instance or application without manually reentering data, especially because manual entry is error-prone. For example, you might want to replicate the sourcing rules in your supply chain planning cloud production instance in a reporting system or your test instance.
With this update, you can extract the data for assignment sets and associated sourcing rules into a comma-delimited values (CSV) file format. The generated file is in the standard file-based data import (FBDI) file format that you can then use to upload to other systems.
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
Key Resources
IMPORTANT Actions and Considerations
BUGS FIXED
Sales and Operations Planning: Storage Costs of Assembly Items Are Now Based on Component Items
For manufactured assembly items, the costs used to calculate plan results are now rolled up from the component items associated with an assembly item’s bill of resources. Plan output now exhibits just-in-time behavior for assembly items defined with partial data for standard cost and annual carrying cost percentage, instead of prebuild behavior. It’s recommended that you still set up item standard cost and carrying cost percentage to provide better plan reporting.
Bug reference: 30463351