Cloud Readiness / Oracle Fusion Cloud Demand Management
What's New
Expand All


  1. Update 23B
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Supply Chain Orchestration
    1. Supply Chain Orchestration
        1. Use REST API to Get Supply Sources for Internal Material Transfers
        2. Include Reference Details for Supply Requests on REST API Error Messages
        3. Use Service Mappings to Extend Supply Chain Orchestration's Integration with Inventory
        4. Selected Supply Chain Orchestration Bug Fixes in This Update
  7. Demand Management
    1. Demand Management
        1. Filter on Multiple Time-Varying Measures
        2. Use a REST Service to Update Parameters in Forecasting Profiles
        3. Create Your Own Exceptions for Measures of Type Date
        4. Use Additional Methods to Secure Your Supply Chain Plans
    2. Replenishment Planning
        1. Respect End-Item Substitution and Supersession in Inventory Rebalancing
        2. Use a REST Service to Update Parameters in Forecasting Profiles
        3. Filter on Multiple Time-Varying Measures
        4. Use the Method of Safety Stock Calculation as an Attribute in Segmentation
        5. Create Your Own Exceptions for Measures of Type Date
        6. Use Additional Methods to Secure Your Supply Chain Plans
  8. IMPORTANT Actions and Considerations

Update 23B

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 Module Feature Notes
03 MAR 2023     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle Fusion Cloud SCM: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

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 using the following privileges:

  • Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
  • Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

  1. Click Navigator > My Enterprise > New Features.
  2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
  3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
  4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

  1. Click Navigator > My Enterprise > Offerings.
  2. On the Offerings page, select your offering, and then click Opt In Features.
  3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
  4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Configure Offerings.

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.

Feature Summary

Column Definitions:

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
(Feature 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.

Customer Must Take Action before Use by End Users
(Feature 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

UI or
Process-Based:
Larger Scale*

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Get Supply Sources for Internal Material Transfers

Include Reference Details for Supply Requests on REST API Error Messages

Use Service Mappings to Extend Supply Chain Orchestration's Integration with Inventory

Selected Supply Chain Orchestration Bug Fixes in This Update

Demand Management

Demand Management

Filter on Multiple Time-Varying Measures

Use a REST Service to Update Parameters in Forecasting Profiles

Create Your Own Exceptions for Measures of Type Date

Use Additional Methods to Secure Your Supply Chain Plans

Replenishment Planning

Respect End-Item Substitution and Supersession in Inventory Rebalancing

Use a REST Service to Update Parameters in Forecasting Profiles

Filter on Multiple Time-Varying Measures

Use the Method of Safety Stock Calculation as an Attribute in Segmentation

Create Your Own Exceptions for Measures of Type Date

Use Additional Methods to Secure Your Supply Chain Plans

>>Click for IMPORTANT Actions and Considerations

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Get Supply Sources for Internal Material Transfers

Use the availableSupplySources REST resource to get the supply sources that can fulfill a request for an internal material transfer. Get the one source that can most effectively fulfill the request, or get a list of up to six sources, ranked according to how effectively they can fulfill the request. Get the actual quantity that's currently on hand in each source.

Add flexibility to how you select and use the supply source for each of your internal material transfers.

Steps to Enable

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

Tips And Considerations

  • Use the findBestAvailableSupplySource finder to get the most effective source.
  • Use the findAllAvailableSupplySources finder to get the list of all supply sources. This finder gets a maximum of 6 sources, ranked according to how effectively each one fulfills the request.
  • Get the actual quantity that's currently on hand for each supply source.
  • You can only read data, so you can use only the GET operation.

Key Resources

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles can access this feature:
    • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Process Supply Order Interface (DOS_PROCESS_SUPPLY_ORDER_INTERFACE_PRIV)
    • View Supply Orders (DOS_VIEW_SUPPLY_ORDERS_PRIV)
    • Manage Supply Request Exceptions (DOS_MANAGE_SUPPLY_REQUEST_EXCEPTIONS_PRIV)
    • View Supply Order Exceptions and Status (DOS_VIEW_SUPPLY_ORDER_EXCEPTIONS_AND_STATUS_PRIV)
    • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER_PRIV)
    • Get Best Or All Available Supply Sources (DOS_GET_BEST_OR_ALL_AVAILABLE_SOURCES_PRIV)
    • View Total On Hand Quantity in Supply Source (DOS_VIEW_AVAILABLE_ONHAND_QTY_PRIV)

Include Reference Details for Supply Requests on REST API Error Messages

Add the value of the SupplyOrderReferenceNumber attribute and the SupplyOrderReferenceLineNumber attribute as a prefix on each error message that REST API returns when it processes a supply request. Use the prefix to troubleshoot problems with the request.

Reduce the amount of time you need to troubleshoot and fix problems when you import through REST API.

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: Manufacturing and Supply Chain Materials ManagementNo Longer Optional From: Update 23D

Tips And Considerations

Here's an example of an error message that REST API returns.

{

  "title": "Bad Request",

  "status": "400",

  "o:errorDetails": [

  {

    "detail": "SupplyOrderReferenceNumber:A190102, SupplyOrderReferenceLineNumber:100, MessageType:ERROR, MessageText:The supply order wasn't created because the destination subinventory code, source subinventory code, or both aren't correct."

    },

  {

    "detail": "SupplyOrderReferenceNumber:A190102, SupplyOrderReferenceLineNumber:100, MessageType:ERROR, MessageText:The supply order wasn't created because the shipment priority isn't correct. Ensure that a valid shipment priority is specified in the supply request."

  }

  ]

}

Key Resources

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles can access this feature:
    • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Process Supply Order Interface (DOS_PROCESS_SUPPLY_ORDER_INTERFACE_PRIV)
    • View Supply Orders (DOS_VIEW_SUPPLY_ORDERS_PRIV)
    • Manage Supply Request Exceptions (DOS_MANAGE_SUPPLY_REQUEST_EXCEPTIONS_PRIV)
    • View Supply Order Exceptions and Status (DOS_VIEW_SUPPLY_ORDER_EXCEPTIONS_AND_STATUS_PRIV)
    • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER_PRIV)

If you're maintaining your own job roles, no new privileges were introduced to support this feature.

Use Service Mappings to Extend Supply Chain Orchestration's Integration with Inventory

Use a service mapping to help integrate your Oracle applications. Use the service mapping to meet your specific integration requirements in your transfer order flow. Create a sales order in Oracle Order Management, orchestrate supply in Oracle Supply Chain Orchestration, then create a transfer order in Oracle Inventory Management. As an option, use an extensible flexfield to integrate data that's specific to your implementation. You can also use a service mapping to integrate data that travels from planning and purchasing, to supply chain orchestration, and then to inventory.

For example, here's a service mapping that uses the TransferOrderRequest entity in the TransferRequestSource service to send a request to create a transfer order from Supply Chain Orchestration to inventory:

Modify supply orchestration data so it meets your requirements.

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: Manufacturing and Supply Chain Materials Management

  1. Get the privileges that you need to manage service mappings and algorithms.
  1. Go to the Supply Chain Orchestration work area, click Tasks, then click one of:
  • Manage Service Mappings
  • Manage Algorithms

Tips And Considerations

  • Make sure your integration can send the validations that Inventory Management applies. Your request payload might be fine, but Inventory Management might not accept the request. 
  • Check for empty values when you write expressions in your integration algorithm, especially when you for query more than one request line. A empty value at runtime might create errors.
  • If you encounter an error, fix it, then use the Supply Chain Orchestration work area to resubmit your request.

Role And Privileges

  • Use these predefined privileges to set up this feature:
    • Manage DOS Service Mappings
    • Manage DOS Algorithms
    • Administer Sandbox
    • View Modified Data, so you can view the runtime results

Selected Supply Chain Orchestration Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Supply Chain Orchestration works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Create Transfer Orders That Are Valid When You Import Through File-Based Data Import

Before update 23B, if you used the DosSupplyOrderImportTemplate.xlsm file to import a transfer request, and if the project details in your import weren't valid, then the Load Interface File for Import scheduled process finished successfully, reported the error in its error log, and the Process Supply Chain Orchestration Interface scheduled process created the transfer order without project details.  

After you update to 23B, if the project details in your import aren't valid, then the Process Supply Chain Orchestration Interface scheduled process won't create the transfer order but will instead report the error in its error log. 

Oracle reference: 34862468

Map the Project Organization ID from Supply Chain Orchestration to Procurement

Before update 23B, Oracle Supply Chain Orchestration ignored any mapping that you provided for the ProjectOrganizationId attribute to Oracle Fusion Cloud Procurement. After you update to 23B, if you map the ProjectOrganizationId attribute to Oracle Procurement, then Supply Chain Orchestration will include it when it communicates supply details to Procurement.

Oracle reference: 34902854

Steps to Enable

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

Demand Management

Demand Management

Filter on Multiple Time-Varying Measures

When you work with large volumes of multidimensional data, it’s important that you gain visibility to the subset of data that meets conditions you specify using AND conditions. Previously, you could include data conditions that included the time dimension as part of the query criteria, but not AND conditions for multiple time-varying measures.

You can now include multiple time-varying measures using AND conditions, and you can also filter measures that have complex calculations using AND conditions, such as the projected available balance. You can also use these multiple AND conditions to efficiently analyze plan data by looking for exception conditions at the intersection of multiple dimensions.

Example of using measure filters that include time-varying measures and AND conditions:

Measure Filter with AND Condition

Steps to Enable

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

Tips And Considerations

  • You can use a specific measure only one time when you configure a measure filter with multiple time varying measures.
  • You can impact performance of table and graphs when you use multiple time-varying measures.

Key Resources

Role And Privileges

There are no new roles or security privileges needed to access this enhancement. Users who currently have access to planning tables and graphs will automatically be able to use this feature.

You have a couple options for giving additional people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
    • Maintain Planning Graphs (MSC_MAINTAIN_PLANNING_GRAPHS_PRIV)

Use a REST Service to Update Parameters in Forecasting Profiles

You may need your Oracle Demand Management application to coexist with other enterprise applications. With this update, you can use the forecastingProfiles parent REST resource and its forecastingParameters child resource to retrieve and also update forecasting profile parameters. This new capability enables you to use standards-based interoperability to integrate forecasting profile parameters with other applications you may have in your enterprise and update parameter values using REST API as part of forecast tuning activities.

Examples of REST operations:

Example 1. To get all forecasting profiles.

https://<hostname>/fscmRestApi/resources/11.13.18.05/forecastingProfiles, Operation=GET

Response:

{  "items" : [ {    "ForecastingProfileId" : 4731,    "ForecastingProfileName" : "Forecast Bookings",    "ForecastingProfileDescription" : "Generate forecast based on historical bookings",    "ForecastingProfileTable" : "Forecast Bookings Definitions",    "ForecastingProfileInputMeasure" : "Final Bookings History",    "ForecastingProfileOutputMeasure" : "Bookings Forecast",    "ForecastingProfileType" : "Bayesian",    "links" : [...]  }, {    "ForecastingProfileId": 300100572162014,    "ForecastingProfileName": "UDP Forecast Bookings",    "ForecastingProfileDescription": "Generate forecast based on historical bookings",    "ForecastingProfileTable": "Forecast Bookings Definitions",    "ForecastingProfileInputMeasure": "Final Bookings History",    "ForecastingProfileOutputMeasure": "Bookings Forecast",    "ForecastingProfileType": "Bayesian",    "links" : [...]  } ],  "count" : 25,  "hasMore" : true,  "limit" : 25,  "offset" : 0,  "links" : [...]} 

Example 2. To update one parameter in a user-defined forecasting profile.

https://<hostname>/fscmRestApi/resources/11.13.18.05/forecastingProfiles/300100572162014/child/forecastingParameters/300100572162016, Operation=PATCH

Request payload:

Request:{    "ForecastingParameterValue" : "4.5"}

Response:

{    "ForecastingProfileId": 300100572162014,    "ForecastingProfileName": "UDP Forecast Bookings",    "ForecastingParameterId": 300100572162016,    "ForecastingParameterName": "ForecastValidationSensitivity",    "ForecastingParameterValue": "4.5",    "ForecastingParameterDescription": "Specifies the sensitivity of forecast validation. The smaller the value, the stricter the test. For loose forecast validation use values between 5 and 10.",    "ForecastingParameterDefaultValue": "3.5",    "links": [...]}  

Steps to Enable

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

Tips And Considerations

  • The Forecasting Profiles REST API enables you to update values for existing forecasting parameters on user-defined forecasting profiles.
  • Updates to predefined forecasting profiles aren't allowed.
  • The forecasting profile must already exist to update it via REST API. You can’t create or duplicate a user-defined forecasting profile using REST API.
  • Forecasting parameters must already exist on the forecasting profile to update them via REST API. You can't add or delete a forecasting parameter using REST API.
    • If you want to update a forecasting parameter that doesn't already exist on the forecasting profile, you must first add the required forecasting parameter on the Manage Forecasting Profiles UI from the application work area before using the REST API to update it. 

Key Resources

Role And Privileges

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Edit Forecasting Profiles (MSC_EDIT_FORECASTING_PROFILES_PRIV) for GET/PATCH operations.
    • View Forecasting Profiles (MSC_VIEW_FORECASTING_PROFILES_PRIV) for GET operation.

Create Your Own Exceptions for Measures of Type Date

Due to the large volumes of data that are typical in the supply chain planning process, you may want to manage your plans using your own exceptions. This update enables you to add your own exceptions applicable to measures that are of the data type Date. For example, you can now create an exception where you can capture the items with an erroneously defined discontinuation date that is earlier than the launch date. With this feature, you can manage your plans by exceptions with more flexibility because you can define your own date conditions to be evaluated.

Example of an exception you can now create for measures of type date using the Configure Exceptions page:

Steps to Enable

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

Tips And Considerations

These 3 actions can be performed for date type measure-based exceptions:

  • Create
  • Edit
  • Duplicate

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB) role is common for all the above work area
  • There's no change to existing privileges needed to take advantage of this feature.

Use Additional Methods to Secure Your Supply Chain Plans

In some enterprises, it’s desirable to restrict the data access to plan data to a subset that a planner is authorized to handle. This restriction is possible in Oracle Fusion Cloud Supply Chain Planning when a data access set defines the data that's available to a particular role.

With this update, additional flexibility is available for defining data access sets.

  • You can configure data access set conditions by segments with the Segment Group entity selected. This selection enables you to restrict access to plan data in the Plan Inputs, Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, and Replenishment planning work areas based on the segments criteria.
  • You can also configure data access sets by selecting user-defined customer hierarchies for the Customer entity.
  • Additionally, you can now delete data access set conditions that aren't assigned to any data access sets.

Example of how you can select the Segment Group entity and assign segments as condition while configuring data access sets:

Example of how you can restrict data access by segments in the Supply Planning work area:

Example of how you can select a user-defined customer hierarchy for the Customer entity when configuring a data access set:

Example of how you can select and delete a condition defined through the Administer Planning Security task:

Steps to Enable

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

Tips And Considerations

  • Create segment groups and run the segmentation scheduled process before you configure data access sets with the Segment Group entity
  • You can include one or more segments in a condition for a segment group in a data access set
  • You can include the Segment Group entity with other entities in a data access set configuration

Key Resources

Role And Privileges

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
    • Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Monitor Supply Planning Work Area (MSC_MONITOR_SUPPLY_PLANNING_WORK_AREA_PRIV)   
    • Monitor Demand and Supply Planning Work Area (MSC_MONITOR_DEMAND_AND_SUPPLY_PLANNING_WORK_AREA_PRIV)
    • Manage Demand Planning (MSC_MONITOR_DEMAND_PLANNING_WORK_AREA_PRIV)
    • Manage Sales and Operations Planning (MSC_MONITOR_SALES_AND_OPERATIONS_PLANNING_WORK_AREA_PRIV)
    • Manage Replenishment Planning (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)

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.

Respect End-Item Substitution and Supersession in Inventory Rebalancing

With this update, end-item substitution and supersession relationships are respected while rebalancing inventory for an item within a cluster. When suggesting inventory rebalancing recommendations, Oracle Replenishment Planning will:

  1. Utilize the excess from the substitute item available at the primary location before deciding to transfer excess supply of the primary item from other locations within the cluster.
  1. Utilize the excess from the substitute item available at other locations within the cluster if the substitution or supersession relationship is respected at the specific location. Note that the rebalancing process enables you to utilize excess of substitute items that aren’t connected through sourcing rules.

The use of excess from substitute items or other revisions enables you to meet demand of a primary item from within the primary location or cluster before procuring from your upstream network. This feature also helps you minimize your overall transportation costs and obsolescence within your network.

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

If you want to use the Respect End-Item Substitution and Supersession in Inventory Rebalancing feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again

Key Resources

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned to this predefined job role are automatically able to access this feature:
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
    • Manage Segments (MSC_MANAGE_SEGMENTS_PRIV)

Use a REST Service to Update Parameters in Forecasting Profiles

You may need your Oracle Fusion Cloud Demand Management application to coexist with other enterprise applications. With this update, you can use the forecastingProfiles parent REST resource and its forecastingParameters child resource to retrieve and also update forecasting profile parameters. This new capability enables you to use standards-based interoperability to integrate forecasting profile parameters with other applications you may have in your enterprise.

Examples of REST operations:

Example 1. To get all forecasting profiles.

https://<hostname>/fscmRestApi/resources/11.13.18.05/forecastingProfiles, Operation=GET

Response:

{  "items" : [ {    "ForecastingProfileId" : 4731,    "ForecastingProfileName" : "Forecast Bookings",    "ForecastingProfileDescription" : "Generate forecast based on historical bookings",    "ForecastingProfileTable" : "Forecast Bookings Definitions",    "ForecastingProfileInputMeasure" : "Final Bookings History",    "ForecastingProfileOutputMeasure" : "Bookings Forecast",    "ForecastingProfileType" : "Bayesian",    "links" : [...]  }, {    "ForecastingProfileId": 300100572162014,    "ForecastingProfileName": "UDP Forecast Bookings",    "ForecastingProfileDescription": "Generate forecast based on historical bookings",    "ForecastingProfileTable": "Forecast Bookings Definitions",    "ForecastingProfileInputMeasure": "Final Bookings History",    "ForecastingProfileOutputMeasure": "Bookings Forecast",    "ForecastingProfileType": "Bayesian",    "links" : [...]  } ],  "count" : 25,  "hasMore" : true,  "limit" : 25,  "offset" : 0,  "links" : [...]}

Example 2. To update one parameter in a user-defined forecasting profile.

https://<hostname>/fscmRestApi/resources/11.13.18.05/forecastingProfiles/300100572162014/child/forecastingParameters/300100572162016, Operation=PATCH

Request payload:

Request:{    "ForecastingParameterValue" : "4.5"}

Response:

{    "ForecastingProfileId": 300100572162014,    "ForecastingProfileName": "UDP Forecast Bookings",    "ForecastingParameterId": 300100572162016,    "ForecastingParameterName": "ForecastValidationSensitivity",    "ForecastingParameterValue": "4.5",    "ForecastingParameterDescription": "Specifies the sensitivity of forecast validation. The smaller the value, the stricter the test. For loose forecast validation use values between 5 and 10.",    "ForecastingParameterDefaultValue": "3.5",    "links": [...]}

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 PlanningNo Longer Optional From: Update 23B

Tips And Considerations

If you want to use the Use a REST Service to Update Parameters in Forecasting Profiles feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Other Tips and Considerations:

  • The Forecasting Profiles REST API enables you to update values for existing forecasting parameters on user-defined forecasting profiles.
  • Updates to predefined forecasting profiles aren't allowed.
  • The forecasting profile must already exist to update it via REST API. You can’t create or duplicate a user-defined forecasting profile using REST API.
  • Forecasting parameters must already exist on the forecasting profile to update them via REST API. You can't add or delete a forecasting parameter using REST API.
    • If you want to update a forecasting parameter that doesn't already exist on the forecasting profile, you must first add the required forecasting parameter on the Manage Forecasting Profiles UI from the application work area before using the REST API to update it. 

Key Resources

Role And Privileges

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Edit Forecasting Profiles (MSC_EDIT_FORECASTING_PROFILES_PRIV) for GET/PATCH operations.
    • View Forecasting Profiles (MSC_VIEW_FORECASTING_PROFILES_PRIV) for GET operation.

Filter on Multiple Time-Varying Measures

When you work with large volumes of multidimensional data, it’s important that you gain visibility to the subset of data that meets conditions you specify using AND conditions. Previously, you could include data conditions that included the time dimension as part of the query criteria, but not AND conditions for multiple time-varying measures.

You can now include multiple time-varying measures using AND conditions, and you can also filter measures that have complex calculations using AND conditions, such as the projected available balance. You can also use these multiple AND conditions to efficiently analyze plan data by looking for exception conditions at the intersection of multiple dimensions.

Example of using measure filters that include time-varying measures and AND conditions:

Measure Filter with AND

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

If you want to use the Include the Time Dimension in Multidimensional Filters feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additional Tips & Considerations:

  • You can use a specific measure only one time when you configure a measure filter with multiple time varying measures.
  • You can impact performance of table and graphs when you use multiple time-varying measures.

Key Resources

Role And Privileges

There are no new roles or security privileges needed to access this enhancement. Users who currently have access to planning tables and graphs will automatically be able to use this feature.

You have a couple options for giving additional people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
    • Maintain Planning Graphs (MSC_MAINTAIN_PLANNING_GRAPHS_PRIV)

Use the Method of Safety Stock Calculation as an Attribute in Segmentation

You can now use the Safety Stock Calculation Method attribute to enhance the criteria used in your segmentation process. You can select one of these three values for this attribute: Days of Cover, Planned, or Safety Stock Quantity. The segmentation process will respect this new item attribute, along with other criteria, when creating segments. This capability ensures that all item locations in a given segment have similar characteristics and follow a similar planning behavior.

You can now define the segment criteria as shown in this example:

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

If you want to use the Use the Method of Safety Sock Calculation as an Attribute in Segmentation feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again

Key Resources

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned to this predefined job role are automatically able to access this feature:
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
    • Manage Segments (MSC_MANAGE_SEGMENTS_PRIV)

Create Your Own Exceptions for Measures of Type Date

Due to the large volumes of data that are typical in the supply chain planning process, you may want to manage your plans using your own exceptions. This update enables you to add your own exceptions applicable to measures that are of the data type Date. For example, you can now create an exception where you can capture the items with an erroneously defined discontinuation date that is earlier than the launch date. With this feature, you can manage your plans by exceptions with more flexibility because you can define your own date conditions to be evaluated.

Example of an exception you can now create for measures of type date using the Configure Exceptions page:

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

If you want to use the Create Your Own Exceptions for Measures of Type Date feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

These 3 actions can be performed for date type measure-based exceptions:

  • Create
  • Edit
  • Duplicate

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB) role is common for all the above work area
  • There's no change to existing privileges needed to take advantage of this feature.

Use Additional Methods to Secure Your Supply Chain Plans

In some enterprises, it’s desirable to restrict the data access to plan data to a subset that a planner is authorized to handle. This restriction is possible in Oracle Fusion Cloud Supply Chain Planning when a data access set defines the data that's available to a particular role.

With this update, additional flexibility is available for defining data access sets.

  • You can configure data access set conditions by segments with the Segment Group entity selected. This selection enables you to restrict access to plan data in the Plan Inputs, Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, and Replenishment planning work areas based on the segments criteria.
  • You can also configure data access sets by selecting user-defined customer hierarchies for the Customer entity.
  • Additionally, you can now delete data access set conditions that aren't assigned to any data access sets.

Example of how you can select the Segment Group entity and assign segments as condition while configuring data access sets:

Example of how you can restrict data access by segments in the Supply Planning work area:

Example of how you can select a user-defined customer hierarchy for the Customer entity when configuring a data access set:

.

Example of how you can select and delete a condition defined through the Administer Planning Security task:

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

If you want to use the Use Additional Methods to Secure Your Supply Chain Plans feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additional Tips & Considerations:

  • If you want to use the Use Additional Methods to Secure Your Supply Chain Plans feature, then you must opt in to its parent feature: Replenishment Planning. If you’ve already opted in to this parent feature, then you don’t have to opt in again
  • Create segment groups and run the segmentation scheduled process before you configure data access sets with the Segment Group entity
  • You can include one or more segments in a condition for a segment group in a data access set
  • You can include the Segment Group entity with other entities in a data access set configuration

Key Resources

Role And Privileges

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

  • Users who are assigned any of these predefined job roles are automatically able to access this feature:
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
    • Demand and Supply Planner (ORA_MSC_DEMAND_AND_SUPPLY_PLANNER_JOB)
    • Demand Planner (ORA_MSC_DEMAND_PLANNER_JOB)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Replenishment Planner (ORA_MSC_REPLENISHMENT_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Monitor Supply Planning Work Area (MSC_MONITOR_SUPPLY_PLANNING_WORK_AREA_PRIV)   
    • Monitor Demand and Supply Planning Work Area (MSC_MONITOR_DEMAND_AND_SUPPLY_PLANNING_WORK_AREA_PRIV)
    • Manage Demand Planning (MSC_MONITOR_DEMAND_PLANNING_WORK_AREA_PRIV)
    • Manage Sales and Operations Planning (MSC_MONITOR_SALES_AND_OPERATIONS_PLANNING_WORK_AREA_PRIV)
    • Manage Replenishment Planning (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)

IMPORTANT Actions and Considerations

Changes to File-Based Data Import (FBDI) Templates

Some Oracle Demand Management FBDI templates have changed in this update. For details of the specific changes, refer to the Instructions tab of these FBDI templates:

  • Key Customer Options (ScpKeyCustomerOptionsImportTemplate)
  • Organizations (ScpOrganizationImportTemplate)

You can find the latest templates in Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM, available on the Oracle Help Center.