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


  1. Update 22C
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Demand Management
    1. Demand Management
        1. Reference History End Date and Forecast Start Date in Measure Expressions
        2. Specify a Time Range When Loading Measures from Other Plans
    2. Replenishment Planning
        1. Manage End Item Substitution in Replenishment Planning
        2. Reference History End Date and Forecast Start Date in Measure Expressions

Update 22C

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 Product Feature Notes
17 JUN 2022     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 SCM Cloud: 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 Offering Configuration.

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*

Demand Management

Demand Management

Reference History End Date and Forecast Start Date in Measure Expressions

Specify a Time Range When Loading Measures from Other Plans

Replenishment Planning

Manage End Item Substitution in Replenishment Planning

Reference History End Date and Forecast Start Date in Measure Expressions

Demand Management

Demand Management

Reference History End Date and Forecast Start Date in Measure Expressions

When you configure measures in Oracle Fusion Cloud Supply Chain Planning using measure expressions, sometimes you need to reference a relative point in time, such as the history end date. A relative point in time is one that changes as a plan proceeds forward in time. With this update, you can use new measure functions that enable you to query the forecast start date and history end date and configure the measure expression to your business needs. For example, if you want to lock a measure from edits for a certain number of days using a lock measure expression, then you can reference the demand forecast start date in the measure expression.

Use the Manage Planning Measures task to configure measure expressions with the new date type measure functions DemandHistoryEndDate() and DemandForecastStartDate().

  • For plans defined with forecasting profiles:
    • DemandHistoryEndDate: Provides the demand history end date calculated by the demand forecasting process at the forecasting time level
    • DemandForecastStartDate: Provides the demand forecast start date calculated by the demand forecasting process at the forecasting time level

NOTE: The calculations for the demand history end date and demand forecast start date functions take the setting for the history offset parameter into account

  • DemandHistoryEndDate and DemandForecastStartDate: Provide the maximum of the history end date and maximum of the forecast start date calculated between the forecasting profiles

  • For plans defined without forecasting profiles:
    • DemandHistoryEndDate: Provides the date before the plan horizon start date
    • DemandForecastStartDate: Provides the plan horizon start date

Configure measure expressions that reference relative points in time, such as forecast start date, and create measures that align even better to your business needs.

Steps to Enable

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

Key Resources

Role Information

  • 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)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
    • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
    • Supply Chain Planning Application Administrator (ORA_MSC_SUPPLY_CHAIN_PLANNING_APPLICATION_ADMINISTRATOR_JOB)
    • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
  • Users who are assigned configured job roles that contain either this privilege or duty, or both, are able to access this feature:    
    • Maintain Measure Definition (MSC_MAINTAIN_MEASURE_DEFINITION_PRIV)

Specify a Time Range When Loading Measures from Other Plans

Copy and store measure data from a source plan to a target plan for a specified time range instead of importing the entire time-phased measure data. Creating stored versions of copied measure data, especially for measures with complex underlying calculations, improves the analytical performance of tables, graphs, and metrics in the target plan. By specifying an appropriate time range, you can also address measure data spanning both historical and forecast time ranges.

The new Copy Range Relative to Start Date section on the Load Measures from Other from Other Plans page (Navigation: Tasks > Plans > Load Measures from Other Plans)

Improve planning efficiency through better processing of data from other plans and faster visualization of key metrics that support sales and operations decision making.

Steps to Enable

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

Tips And Considerations

  • Specify the time level range start and end that you want to pertain to the target plan.
  • Specify a time range to copy measure data for both forecast and history. Use negative values for historical time periods.
  • You can still search for and select the Orchestrate Load Measures Processes in the Scheduled Processes work area to schedule this process.

Key Resources

Role Information

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)
    • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Load Measure Data from Other Plans (MSC_LOAD_MEASURES_FROM_OTHER_PLANS_PRIV)
    • Run Plan with Snapshot (MSC_RUN_PLAN_WITH_SNAPSHOT_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.

Manage End Item Substitution in Replenishment Planning

In many industries, when an ordered item is in short supply, it's desirable to use a substitute item. For example, you may want to respect your customer commitments by substituting a higher quality item for a lower quality item. You can now define substitution relationships and use them in replenishment planning. The substitution relationships may be defined globally or applicable to a specific organization.

Oracle Replenishment Planning evaluates the substitution relationships and recommends a substitute end item if it can be used to meet demand instead of raising a new replenishment order to get material from upstream facilities. To model the substitution behavior you want, you select the applicable value for the new Use of Related Items Supplies plan option.

  • Maximize use of related items supplies to minimize new replenishment: Promote substitution and ensure an item location’s inventory level is maintained at or above the Minimum Quantity or Reorder Point level. When calculating excess with this option selected, replenishment planning also protects an item’s supplies to ensure projected available balance is above Minimum Quantity or Reorder Point level.
  • Use related items supplies only when necessary to avoid stockouts: Use a substitute item to prevent the projected available balance from becoming negative. When calculating excess with this option selected, replenishment planning also protects an item’s supplies to ensure projected available balance is above zero.
  • Do not use related items supplies: Don’t use any substitutes. This is the default value.

The following screenshot illustrates how you can enable substitution behavior within a replenishment plan.

Navigation: Supply Chain Planning > Replenishment Planning work area > Manage Plans task > Create action

Increase customer service levels and minimize excess and obsolete inventory by using substitute items to meet demand on time.

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 Replenishment Planning feature. If this feature is already opted in to, then you don’t need to do so again.
  • Also opt in to the Respect Organization-Specific Item Substitution Rules feature.

Tips And Considerations

  • It's recommended that you run collections to collect item relationships after opting in to this feature.
  • All items within an item relationship chain must be part of the same segment for substitution to be considered for that relationship chain.
  • Four new measures are introduced by this feature. These measures must be included in your default measure catalog that is linked to the plan.
    • Substitute Demand
    • Substitute Supply
    • Initial Excess for Substitution
    • Initial Shortage for Substitution

Key Resources

Role Information

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)

Reference History End Date and Forecast Start Date in Measure Expressions

When you configure measures in Oracle Fusion Cloud Supply Chain Planning using measure expressions, sometimes you need to reference a relative point in time, such as the history end date. A relative point in time is one that changes as a plan proceeds forward in time. With this update, you can use new measure functions that enable you to query the forecast start date and history end date and configure the measure expression to your business needs. For example, if you want to lock a measure from edits for a certain number of days using a lock measure expression, then you can reference the demand forecast start date in the measure expression.

Use the Manage Planning Measures task to configure measure expressions with the new date type measure functions DemandHistoryEndDate() and DemandForecastStartDate().

  • For plans defined with forecasting profiles:
    • DemandHistoryEndDate: Provides the demand history end date calculated by the demand forecasting process at the forecasting time level
    • DemandForecastStartDate: Provides the demand forecast start date calculated by the demand forecasting process at the forecasting time level

NOTE: The calculations for the demand history end date and demand forecast start date functions take the setting for the history offset parameter into account

  • DemandHistoryEndDate and DemandForecastStartDate: Provide the maximum of the history end date and maximum of the forecast start date calculated between the forecasting profiles

  • For plans defined without forecasting profiles:
    • DemandHistoryEndDate: Provides the date before the plan horizon start date
    • DemandForecastStartDate: Provides the plan horizon start date

Configure measure expressions that reference relative points in time, such as forecast start date, and create measures that align even better to your business needs.

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. If you previously opted in to the Replenishment Planning feature, then this feature is automatically enabled.

Key Resources

Role Information

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)
  • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
  • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
  • Supply Chain Planning Application Administrator (ORA_MSC_SUPPLY_CHAIN_PLANNING_APPLICATION_ADMINISTRATOR_JOB)
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Users who are assigned configured job roles that contain either this privilege or duty, or both, are able to access this feature:

  • Maintain Measure Definition (MSC_MAINTAIN_MEASURE_DEFINITION_PRIV)