Update 23C

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
15 NOV 2023	Supply Chain Orchestration	Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning	Updated document. Revised feature description.
29 SEP 2023	Demand Management	View Quantities for Open Sales Orders	Updated document. Revised Tips and Considerations section.
02 JUN 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

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Process Supply Request Lines that Pass Validation

Use the Create Supply Request REST API to process supply request lines that pass validation. If your supply request includes more than one supply request line, and if you set the AllowPartialRequestFlag attribute to Y in your REST API payload, then REST API will process the lines that pass validation. It won't process the lines that don't pass validation and mark them in error. If you set AllowPartialRequestFlag to N, and if any line in the supply request doesn't pass validation, then REST API will reject all lines in the request, including the ones that do pass validation. The default value for AllowPartialRequestFlag is N.

Use this feature to process the supply request lines that pass validation when your supply request includes more than one supply request line.

Steps to Enable

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

Key Resources

• See Use REST API to Manage Supply Chain Orchestration and Using Supply Chain Orchestration on Oracle Help Center.

Access Requirements

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)

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

Use the Supply Chain Orchestration Work Area to Synchronize Supply Documents

Use the Supply Chain Orchestration work area to synchronize supply documents between Oracle Supply Chain Orchestration and Oracle Procurement. Use this feature in your outside processing flow when Supply Chain Orchestration can't record a purchase requisition or purchase order because of a technical failure.

Keep your data up to date so Supply Chain Orchestration has the latest purchasing details and can accurately orchestrate supply for your sales orders.

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  No Longer Optional From: Update 24A

Tips And Considerations

Synchronize your purchase requisitions and purchase orders:

1. Go to the Supply Orchestration work area, then click Tasks > Manage Supply Lines.
2. On the Manage Supply Lines page, click a link in the Supply Order Number column, such as 300100083428746.
3. On the Supply Order Details page, click Actions > Synchronize Supply Documents.

Supply Chain Orchestration will synchronize data for your purchase requisitions and purchase orders between Supply Chain Orchestration and Procurement.

Key Resources

• See Using Supply Chain Orchestration and Supply Chain Orchestration on Oracle Help Center.

Access Requirements

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)
  • Synchronize Supply Document (DOS_SYNC_SUPPLY_DOCS)

Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning

Use your own group codes to manage purchase requests in the Buyer Planning work area, which is available as part of Oracle Fusion Cloud Supply Chain Planning starting in update 23D. You can already use predefined codes such as Buyer, Category, Item, Location, Supplier, and None. This new feature allows buyer planners to create their own group code, and then use it to organize purchase requests into a group and take advantage of price breaks, order minimums, and so on. Oracle Supply Chain Orchestration will send the group code for each purchase request to Oracle Fusion Cloud Procurement. Oracle Procurement will group these purchase requests into purchase requisitions according to the value in the Group Code attribute.

Use this feature to group purchase requests to take advantage of price breaks, order minimums and other constraints.

Steps to Enable

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

Key Resources

• See Using Supply Chain Orchestration and Supply Chain Orchestration on Oracle Help Center.

Access Requirements

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)

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

Extend Supply Chain Orchestration's Integration with Inventory Management

Oracle Supply Chain Orchestration allows you to create service mappings to integrate with Oracle Inventory Management starting in update 23B. This feature extends that capability. You can include a change entity and other attributes when you map attributes between Supply Chain Orchestration and your inventory management system. Here are the new attributes that you can map:

• SourceOrganizationId 
• SourceSubinventoryCode 
• DestinationLocationId
• ItemRevision 
• FreightCarrierId 
• ModeOfTransportLookup
• ServiceLevelLookup 
• ShipmentPriorityLookup 
• FirmFlag 
• RepriceFlag 
• AllowItemSubstitutionFlag

Use service mappings to tailor how you process the change that happens in your supply chain during order fulfillment. You can now use service mappings to integrate with inventory, procurement, or manufacturing.

Steps to Enable

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

Tips And Considerations

• This is an enhancement to an existing opt-in feature that is always optional.

• Make sure your integration can satisfy the validations that Inventory Management applies. Your request payload might be fine, but Inventory Management might not accept the request. 

• Make sure the objects that you reference in your integration algorithm exist, especially when you query for more than one request line. If you reference an object that doesn't exist at runtime, you might encounter an error.

• If you encounter an error, fix it, then use the Supply Chain Orchestration work area to resubmit your request.

Access Requirements

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

Prevent Duplicate Supply Requests for Back-to-Back Sales Orders

Prevent Oracle Supply Chain Orchestration from creating excess supply when a communication problem happens. Sometimes there's a disruption that prevents Oracle Order Management from sending a supply request to Supply Chain Orchestration. The disruption might never get resolved and orchestration never receives the request, or receive it only after a long delay. If Order Management doesn't receive a reply from Supply Chain Orchestration after a specific amount time, then Order Management might resend a create, update, or cancel request, and this makes it difficult for Supply Chain Orchestration to interpret how to handle the resent request.

Use this feature to prevent Supply Chain Orchestration from creating duplicate supply requests for the same demand when there's a communication problem between Order Management and Supply Chain Orchestration.

Steps to Enable

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

Access Requirements

The feature is available to any privilege that can create and submit a sales order.

View Manual Reservations for Your Back-to-Back Sales Orders

You might need to manually create a reservation when Oracle Supply Chain Orchestration can't create enough supply to meet Oracle Order Management's demand. You can view these reservations in the Supply Orchestration work area:

• View details about each reservation that you create manually in a back-to-back flow for your sales order.
• View the work orders, purchase requests, and transfer orders that create supply for these reservations.
• Click a link that takes you to the work order, purchase request, or transfer order.
• View the current state of the supply lines and tracking lines for each manual reservation.
• View an icon on each supply line and tracking line to quickly determine whether you're using it for a manual reservation.
• The Supply Orchestration work area displays a manual reservation only when supply doesn't meet the requested quantity.

Get a picture of the supply that's allocated to the sales order outside of automated processing.

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  No Longer Optional From: Update 24A

Tips And Considerations

• Supply Chain Orchestration doesn't modify a manual reservation for a demand change that it receives from Order Management.  Any necessary changes must be done manually.

• The quantity for the work order, purchase request, or transfer order might be different from the reservation's quantity or the quantity on the supply or tracking line because other requests might also use the work order, purchase request, or transfer order.

Access Requirements

The feature is available to any privilege that can create and submit a sales order.

Use High-Volume Order Processing with Supply Chain Orchestration for Configured Items

Use High-Volume Order Processing with Supply Chain Orchestration to orchestrate the supply that you need to fulfill configured items when you have a high volume of sales orders to process.

Improve performance when you need to orchestrate fulfillment for sales orders that have a lot of configured items, or your configured items are large and complex and have many child components.

Steps to Enable

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

Access Requirements

The feature is available to any privilege that can create and submit a sales order with configured items.

Demand Management

Demand Management

View Quantities for Open Sales Orders

As a demand planner, it’s important to monitor the performance of the forecast to actuals. With this update, you can now analyze open sales orders, in addition to the history of shipped orders, so that you have a complete view of the realized demand including the backlog. Use this ability to have a full demand picture including both shipped and open sales orders to improve the overall forecast accuracy.

In the Demand Management work area, you can now use the predefined Sales Orders measure to monitor performance of the forecast to actuals. You can use the item, organization, customer, demand class, and time dimensions to view aggregated information for this measure.

To view quantities for open sales orders, you must include the predefined Sales Orders measure in the measure catalog used in your demand plan.

• If you're using the predefined Default Demand Management Catalog measure catalog, then the predefined Sales Orders measure is already included in the measure catalog.

• If you're using a user-defined measure catalog that you created by duplicating the Default Demand Management Catalog measure catalog, then the predefined Sales Orders measure is already included in the measure catalog, unless you removed it.

• If you're using a user-defined measure catalog that doesn't already include the predefined Sales Orders measure, then you must add the measure to the measure catalog.

Details about the predefined Sales Orders measure:

• Reflects the required quantity for the booked item on the scheduled ship date.

• Is populated in a demand plan if it's included in the measure catalog selected for the demand plan.

• Is populated during a demand plan run when the Refresh with current data option is selected.

• Can't be populated via the Refresh Collected Measure Data process (scheduled process named Orchestrate Refresh Measures Processes).

• Is populated from collected data from either of the following:
  • From Fusion Source using the Collect Planning Data task and selecting the Supply Entity Sales orders on the Supply Planning Data tab.
  • From an external source using the Load Planning Data from Files task via the Supply Chain Planning Sales Orders File-Based Data Import file (ScpSalesOrderImportTemplate.xlsm).

Steps to Enable

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

Tips And Considerations

By default, the plan will include data from all open sales orders with a scheduled ship date greater than or equal to 90 days prior to the start date of the plan.

• You can change the number of days using the MSC_SALES_ORDERS_SNAPSHOT profile option.
  • For example, if you set MSC_SALES_ORDERS_SNAPSHOT=30 then the plan will include data from all open sales orders with a scheduled ship date greater than or equal to 30 days prior to the start date of the plan.
  • You can also set MSC_SALES_ORDERS_SNAPSHOT=-1 if you don’t want to populate the Sales Orders measure, even if it's included in the demand plan’s measure catalog.

• To override the default of 90 days, follow these steps, and you may need to work with someone who has administration privileges to make these profile-related changes:
  • In the Setup and Maintenance work area, search for and select the Manage Profile Options task.
  • Create a profile option as follows:
    • Profile Option Code: MSC_SALES_ORDERS_SNAPSHOT
    • Profile Display Name: MSC_SALES_ORDERS_SNAPSHOT
    • Application: Planning Common
    • Module: Planning Common
    • Start Date: current date
    • Leave the remaining fields blank.
  • Save the profile option.
  • For the profile option levels, select the check boxes under the Enabled and Updatable columns for the Site level.
  • Save the profile option.
  • In the Demand Management, Demand and Supply Planning, or Plan Inputs work area, go to the Manage Planning Profile Options task.
  • On the Manage Planning Profile Options page, search for the MSC_SALES_ORDERS_SNAPSHOT profile option code.
  • Set the profile value as follows:
    • Profile Level: Select Site.
    • Profile Value: Enter the number of days to use for selecting the sales order data to include in demand plans. Demand plans will include data from all open sales orders with a scheduled ship date greater than or equal to the specified number of days prior to the start date of the plan.
  • Save the profile option value.

• For more information regarding profile options, see the topics titled Set Profile Option Values and Create and Edit Profile Options.

Additional Combinations in Demand Plans

• New combinations will get created in the demand plans if you're collecting demand history (any of the shipments history or bookings history variants or user-defined demand history measure) for different customer sites, demand classes, or both, than you're collecting sales orders for.
  • For example:
    • If you're populating Demand Class when loading shipments or bookings history, but not populating Demand Class when collecting sales orders, then new combinations for existing Items, Organizations, and Customer Sites with an unassigned Demand Class will be created. The Sales Orders measure will be stored and displayed against  the Unassigned demand class.
    • If you're preaggregating shipments or bookings history on the customer dimension and loading these against dummy Customer Sites, but collecting sales orders for actual Customer Sites, then new combinations for existing Items, Organizations, and Demand Classes with the actual Customer Sites from the sales orders will be created. The Sales Orders measure will be stored and displayed against these actual Customer Sites.
      • New combinations don't get created in the demand plans enabled with the Aggregate non-key customer data to an All Other level member option, if the level members populated for the demand class level are same between the demand history and sales order measure data.

• If you're manually entering measure values or loading measure values via REST services or import from Excel at an aggregate level, then these values might be disaggregated to the new combinations depending on the disaggregation settings of the measure. This would happen when the Disaggregation Type of the measure is Same value or Equal. It could also happen when the Disaggregation Type of the measure is By measure or By self, but there are no existing values for the disaggregation basis or secondary basis (in which case the disaggregation reverts to Equal.)

• If you're collecting both demand history and sales orders from the Fusion source, then you won't have additional combinations created.

• If you're loading demand history, sales orders, or both, via file-based data import (FBDI), and are using the same customer sites and demand classes for both, then you won't have additional combinations created.

• The feature can be disabled using either of the solutions described in the following text. Note that if the feature is disabled, then you won't be able to view open sales orders in your Demand Plans.

• If the plan includes user-adjusted values then users need to first remove them, then disable the feature using either of the solutions described in the following text, and then do the Refresh the Plan action. You have to use solution #2, if the demand plan was defined with the predefined Default Demand Management Catalog measure catalog.
  • Alternate Solution #1
    • Remove the Sales Order measure from the user-defined Measures Catalog attached to the plan.
    • Run the plan with the Refresh with current data option selected.
  • Alternate Solution #2
    • Create the MSC_SALES_ORDERS_SNAPSHOT profile option. Set the profile to -1 at site level.
    • Run the demand plan again with the Refresh with current data option selected.

Access Requirements

There are no new security privileges needed to access this feature. Users who currently have access to run plans will automatically be able to use this feature.

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Edit Planning Analytics Configuration (MSC_EDIT_PLANNING_ANALYTICS_CONFIGURATION_PRIV)
• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• Maintain Planning Graphs (MSC_MAINTAIN_PLANNING_GRAPHS_PRIV)

Forecast Using Supersession Relationships

In the service parts and aftermarket parts industries, a supersession relationship is defined to recognize that an item can be superseded by a chain of items. This relationship ensures you can keep track of older revisions by cross-referencing item numbers. Typically, an item is superseded when its effective date become obsolete.

Oracle Demand Management evaluates item supersession relationships and generates a statistical forecast for current or future revision items. The forecast is generated using aggregated demand history of relevant older revision items within a supersession chain or across applicable multiple supersession chains.

Note that the supersession relationship must be bilateral, and the start date for a future revision item must be within the forecast horizon.

Steps to Enable

Step 1: Item supersession relationships measures

• Add these predefined measures to the user-defined measure catalog that is used in the plan for which you want to perform supersession forecasting.
  • Name of Latest Item Revision
  • Inventory ID of Latest Item Revision
  • Item Revision Start Date
  • Item Revision End Date
  • Current Revision
  • Latest Revision

• As an alternative to the user-defined measure catalog, you can also use the predefined measure catalog Supersession Forecasting Catalog in the plan. This catalog includes the preceding list of measures.

Step 2: Forecasting profile

• Add these forecasting parameters to the forecasting profile, and set it to the required measure to enable forecast using supersession relationships.
  • SupersessionForecastLevelMeasure - select measure Inventory ID of Latest Item Revision from the list of values.
  • LaunchDateMeasure  - select measure Item Revision Start Date from the list of values.
  • DiscontinueDateMeasure - select measure Item Revision End Date from the list of values.

• As an alternative to the user-defined forecasting profile, you can also use the predefined forecasting profiles Forecast Shipments for Supersession Chain, Forecast Bookings for Supersession Chain in the plan, which were defined with the preceding parameters as stated. Note that you can't change the definition of the predefined forecasting profile, such as forecast methods and forecasting parameters.

Step 3: Plan definition

• Add the forecasting profile enabled with the preceding parameters to the plan for which you want to perform supersession forecasting.

Tips And Considerations

• You can add parameter SmoothIntermittent to the forecasting profile and set it to 0 to generate a sparse and spiky demand forecast.

• You can define an edit lock expression using the Item Revision Start Date and Item Revision End Date measure to prevent users from adjusting demand forecast for current and latest revision items outside of its effectivity dates.

• A forecasting profile enabled with the SupersessionForecastLevelMeasure parameter is designed to generate a forecast for items with and without a supersession relationship. But you can define one forecasting profile with parameters SupersessionForecastLevelMeasure, LaunchDateMeasure, DiscontinueDateMeasure and add it to the plan with an analysis set to generate a forecast for items with supersession relationship and define other forecasting profiles without the SupersessionForecastLevelMeasure parameter and add it to the plan with an analysis set to generate a forecast for items without a supersession relationship. Make sure the definition of the analysis sets selected for the forecasting profiles don't overlap. In this way, you can generate an optimal forecast for items with and without a supersession relationship in the same plan using multiple forecasting profiles defined with different forecasting tables, forecast methods, decomposition groups, and forecast parameters that are tailored to the demand pattern of the items.

Key Resources

• See the Forecast Using Supersession Relationships (Update 23C) readiness training available on Oracle Cloud Application Update Readiness

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Edit Planning Analytics Configuration (MSC_EDIT_PLANNING_ANALYTICS_CONFIGURATION_PRIV)
• Edit Forecasting Profiles (MSC_EDIT_FORECASTING_PROFILES_PRIV)
• Edit Plans (MSC_EDIT_PLANS_PRIV)
• Edit Plan Options (MSC_EDIT_PLAN_OPTIONS_PRIV)
• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• Maintain Planning Graphs (MSC_MAINTAIN_PLANNING_GRAPHS_PRIV)

Apply Cross-Validation Learning to Additional Forecast Models

Oracle Demand Management generates a forecast using a combination of machine learning algorithms. The cross-validation learning capability, previously available for a subset of forecasting models, offers a robust alternative for evaluating and scoring forecast models.

Cross-validation learning tests out-of-sample subsets of the historical demand to generate a forecast and then compares each resulting forecast to the remaining portions of historical demand. With this update, you can apply this capability for these additional forecast models:

• Auto Regressive External Inputs
• Auto Regressive Integrated External
• Causal Winters
• Dual Group Multiplicative
• Holt Exponential Smoothing

Now you can apply cross-validation learning for all forecast models suitable for forecasting nonintermittent demands.

Additional Forecast Models That Are Supported for Cross-validation Learning

Steps to Enable

1. Go to Supply Chain Planning > Demand Management > Tasks: Manage Forecasting Profiles

2. Select the relevant forecasting profile (must be a user-defined profile. Predefined profiles can't be edited.)

3. Select Actions > Edit

4. Go to the Forecasting Parameters tab
   1. Select Actions > Add
   2. Search for the OutOfSampleTestSets parameter, and add it to the forecasting profile
   3. Change the OutOfSampleTestSets parameter’s value to 10

5. Go to the Forecasting Methods tab:
   1. Select the additional suitable forecast models to be used in the cross-validation learning.

6. Save your changes

7. Run the plan with the forecasting profile.

Tips And Considerations

• When you enable the OutOfSampleTestSets parameter, it's recommended to use the value 10. This value means that the entire historical demand data will be divided into 10 test sets.

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

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

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

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

Key Resources

• See the Improve Model Selection using Cross-Validation Learning (Update 20A) readiness training available on Oracle Cloud Application Update Readiness

Access Requirements

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)
• Edit Plans (MSC_EDIT_PLANS_PRIV)
• Edit Plan Options (MSC_EDIT_PLAN_OPTIONS_PRIV)

Restrict Access to Specific Plans

In enterprises with a large number of planners, it’s beneficial to restrict some actions, such as running a plan, to a subset of users. With this update, in the plan options for a plan, you can create a private plan, assign planners to the plan, and specify the type of access for each planner you assign to the plan. The Full Access and Limited Access access types are now available.

Planners assigned the Limited Access type won’t be able to:

• Run a plan
• Edit plan options
• Save a plan to database
• Delete a plan

Planners assigned the Limited Access type will be able to:

• Make changes to plan data
• Save changes to plan data 
• Release planned orders
• Copy the plan for purposes such as simulating plan changes

Users Access Menu Dialog

On the Plan Options page, you can use enhanced selections for private users to configure full or limited access to a plan. For example, In the preceding image, the APS_ALL user was granted limited access to the plan in the users access menu.

Actions Menu Options for Limited Access Users

As you can see in the preceding image, the options in the Actions menu for a limited access user are restricted. The Run, Save Plan to Database, and Delete actions are disabled. Also, changes to the Plan Options page aren't allowed. For example, a limited-access user can't assign user access, make any changes to scope, planning attributes, or advanced options. However a limited access user can review the setting for all plan options. The Save buttons on the Plan Options UI will be disabled for limited-access users.

Steps to Enable

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

Access Requirements

No new privileges are required to access this feature.

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.

Forecast Using Supersession Relationships

In the service parts and aftermarket parts industries, a supersession relationship is defined to recognize that an item can be superseded by a chain of items. This relationship ensures you can keep track of older revisions by cross-referencing item numbers. Typically, an item is superseded when its effective date become obsolete.

Oracle Demand Management evaluates item supersession relationships and generates a statistical forecast for current or future revision items. The forecast is generated using aggregated demand history of relevant older revision items within a supersession chain or across applicable multiple supersession chains.

Note that the supersession relationship must be bilateral, and the start date for a future revision item must be within the forecast horizon.

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

If you want to use the Forecast Using Supersession Relationships 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.

Step 1: Item supersession relationships measures

• Add these predefined measures to the user-defined measure catalog that is used in the plan for which you want to perform supersession forecasting.
  • Name of Latest Item Revision
  • Inventory ID of Latest Item Revision
  • Item Revision Start Date
  • Item Revision End Date
  • Current Revision
  • Latest Revision

Step 2: Forecasting profile

• Add these forecasting parameters to the forecasting profile, and set it to the required measure to enable forecast using supersession relationships.
  • SupersessionForecastLevelMeasure - select measure Inventory ID of Latest Item Revision from the list of values.
  • LaunchDateMeasure - select measure Item Revision Start Date from the list of values.
  • DiscontinueDateMeasure - select measure Item Revision End Date from the list of values.

• As an alternative to the user-defined forecasting profile, you can also use the predefined forecasting profiles Forecast Shipments for Supersession Chain in the plan, which were defined with the preceding parameters as stated. Note that you can't change the definition of the predefined forecasting profile, such as forecast methods and forecasting parameters.

Step 3: Plan definition

• Add the forecasting profile enabled with the preceding parameters to the plan for which you want to perform supersession forecasting.

Tips And Considerations

• You can add parameter SmoothIntermittent to the forecasting profile and set it to 0 to generate a sparse and spiky demand forecast.

• You can define an edit lock expression using the Item Revision Start Date and Item Revision End Date measure to prevent users from adjusting demand forecast for current and latest revision items outside of its effectivity dates.

• A forecasting profile enabled with the SupersessionForecastLevelMeasure parameter is designed to generate a forecast for items with and without a supersession relationship. But you can define one forecasting profile with parameters SupersessionForecastLevelMeasure, LaunchDateMeasure, DiscontinueDateMeasure and add it to the plan with an analysis set to generate a forecast for items with supersession relationship and define other forecasting profiles without the SupersessionForecastLevelMeasure parameter and add it to the plan with an analysis set to generate a forecast for items without a supersession relationship. Make sure the definition of the analysis sets selected for the forecasting profiles don't overlap. In this way, you can generate an optimal forecast for items with and without a supersession relationship in the same plan using multiple forecasting profiles defined with different forecasting tables, forecast methods, decomposition groups, and forecast parameters that are tailored to the demand pattern of the items.

Key Resources

• See the Forecast Using Supersession Relationships (Update 23C) readiness training available on Oracle Cloud Application Update Readiness

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Edit Planning Analytics Configuration (MSC_EDIT_PLANNING_ANALYTICS_CONFIGURATION_PRIV)
• Edit Forecasting Profiles (MSC_EDIT_FORECASTING_PROFILES_PRIV)
• Edit Plans (MSC_EDIT_PLANS_PRIV)
• Edit Plan Options (MSC_EDIT_PLAN_OPTIONS_PRIV)
• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• Maintain Planning Graphs (MSC_MAINTAIN_PLANNING_GRAPHS_PRIV)

Restrict Access to Specific Plans

In enterprises with a large number of planners, it’s beneficial to restrict some actions, such as running a plan, to a subset of users. With this update, in the plan options for a plan, you can create a private plan, assign planners to the plan, and specify the type of access for each planner you assign to the plan. The Full Access and Limited Access access types are now available.

Planners assigned the Limited Access type won’t be able to:

• Run a plan
• Edit plan options
• Save a plan to database
• Delete a plan

Planners assigned the Limited Access type will be able to:

• Make changes to plan data
• Save changes to plan data 
• Release planned orders
• Copy the plan for purposes such as simulating plan changes

Users Access Menu Dialog

On the Plan Options page, you can use enhanced selections for private users to configure full or limited access to a plan. For example, In the preceding image, the APS_ALL user was granted limited access to the plan in the users access menu.

Actions Menu Options for Limited Access Users

As you can see in the preceding image, the options in the Actions menu for a limited access user are restricted. The Run, Save Plan to Database, and Delete actions are disabled. Also, changes to the Plan Options page aren't allowed. For example, a limited-access user can't assign user access, make any changes to scope, planning attributes, or advanced options. However a limited access user can review the setting for all plan options. The Save buttons on the Plan Options UI will be disabled for limited-access users.

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 Restrict Access to Specific 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.

Access Requirements

No new privileges are required to access this feature.

Honor Decimal Precision for Unit of Measure Conversions

In some industries, it’s necessary to maintain various unit of measure (UOM) conversion rates at a very high level of precision. The profile option MSC_QUANTITY_DECIMAL_PRECISION is currently used to specify the level of precision required for various planning processes and is honored for planning calculations. With this update, the precision specified will be honored on various display pages as well.

Example: The preceding image shows the MSC_QUANTITY_DECIMAL_PRECISION profile parameter with a value of 5 decimal points. The following image shows the UOM measure on the Plan Inputs page displayed in the decimal precision specified in the profile value.

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 Horizon Decimal Prevision for Unit of Measure Conversion 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

IMPORTANT Actions and Considerations

Changes to File-Based Data Import (FBDI) Templates

A Supply Chain Planning FBDI template has changed in this update. For details of the specific changes, refer to the Instructions tab of this FBDI template:

• ERP Integration Service Parameters (ScpErpIntegrationServiceParamsImportTemplate.xlsm)

You can find the latest template in the Supply Chain Planning section of Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM, available on the Oracle Help Center.