What's New

Update 24B

Revision History

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

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 Redesigned Pages to View Supply Requests

Use redesigned pages to view supply requests and their details on your desktop, tablet, or mobile device. You can now use the supply request reference, supply order, supply document, or item to search for your supply requests. Create and save your own default searches. Filter search results according to the supply's requested date, requested delivery date, request status, and so on. View recommended actions that you need to take to remove exceptions. View the supply documents that Oracle Supply Chain Orchestration created for each request. View details about request lines and take actions.

To use this feature, go to the Supply Orchestration work area, click Tasks > Supply Requests, then search for your supply request.

Improve your efficiency when you search for and view supply requests.

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

Tips And Considerations

Use these attributes to search for your supply requests:

• Supply Request Reference
• Supply Order
• Supply Document
• Item

Use these attributes to filter your search results:

• Supply Requested Date
• Requested Delivery Date
• Supply Status
• Supply Type
• Business Flow

Do more:

• View details about the supply documents for each supply request.
• Create and save your own search. Make that search your default search.
• Drill into into the supply request to get details about the supply request and any exception messages that might exist.
• If a supply request is in exception, then you can view a recommended action to fix it.
• Do various actions on each supply request.

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.

Demand Management

Demand Management

Copy a Measure Between Plans with Aggregated Customer Levels

In a previous update, you could create forecasts at aggregated levels of customer hierarchies, such as a geographical entity that aggregated all customer sites in a region. In this update, the functionality has been extended so that you can take advantage of existing functionality to move measure data between plans or from one measure to another within a plan. Using the Load Measures from Other Plans task, you can move measure data between plans that have aggregated customer levels or from a plan that isn’t aggregated to a plan that’s aggregated on a customer dimension.

Load Measures from Other Plans Page

The Load Measures from Other Plans task and Orchestrate Load Measures Processes scheduled process have been enhanced to support copying measure data between the following:

• From a demand plan without a planning level profile to a demand plan with a planning level profile.

• Within a demand plan with a planning level profile.

• From one demand plan with a planning level profile to another demand plan with the same planning level profile.

• From a sales and operations plan with the Use global demand option selected and Planning Customer Level set to Customer Site to a demand plan with a planning level profile.

• From a sales and operations plan with the Use global demand option not selected to a demand plan with a planning level profile.

Steps to Enable

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

Tips And Considerations

Any existing demand plan with a planning level profile must be run after updating to 24B to utilize the plan with the enhanced Load Measures from Other Plans functionality.

You can’t use the Load Measures from Other Plans to copy measure data between the following:

• From a demand plan with a planning level profile to a demand plan without a planning level profile.

• From a demand plan with a planning level profile to a sales and operations plan.

• From a sales and operations plan with the Use global demand option selected and Planning Customer Level set to Zone to a demand plan with a planning level profile.

• From one demand plan with a planning level profile to another demand plan with a different planning level profile.

Key Resources

• Oracle Cloud Readiness > Sales and Operations Planning
  • Load Data from One Measure to Another Measure Across Plans (update 20A)
  • Schedule Batch Processes to Load Measures (update 20B)

• Oracle Cloud Readiness > Demand Management
  • Copy Measure Data Within a Plan (update 21A)
  • Plan at Flexible Levels for the Customer Dimension (update 24A)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to the Load Measures from Other Plans task or the Orchestrate Load Measures Processes scheduled process will automatically be able to use this feature.

Users who are assigned a configured job role that contains this privilege can access this feature:

• Load Measure Data from Other Plans (MSC_LOAD_MEASURES_FROM_OTHER_PLANS_PRIV)

This privilege was available prior to this update.

Use Automated Hyperparameter Tuning to Improve Forecast Accuracy

Improve the forecast accuracy of Oracle Demand Management machine learning models by using your enterprise's historical demand data to tune engine parameters to their best values. By using this approach, you’ll reduce the need to engage with forecasting model experts to tune the models. The feature introduced in this update runs in the background at individual forecasting levels, for example, an item and organization combination. The process then determines the best settings for the forecasting parameters appropriate for that combination. You can review the forecast and predicted accuracy of the suggested settings and compare the predicted results to the existing values. You can then use the suggested settings the next time you run the plan. The background process can be run for the entire forecasting data set or a subset of the data. The subset is determined by specifying the percentage of data to sample in every run.

This new feature enables you to use automated hyperparameter tuning to produce optimal settings for selected forecasting parameters to improve forecast accuracy.

A new Hyperparameter Tuning Values column has been introduced on the Forecasting Parameters tab on the Manage Forecasting Profiles page.

New Hyperparameter Tuning Values Column

• The Hyperparameter Tuning Values column provides a list of the values to be tested for the specific forecasting parameter. The hyperparameter tuning logic will test each possible combination of values for the forecasting parameters being tuned and select the ones that provide the best forecast accuracy for each forecasting node (such as item and organization combination.)

• Hyperparameter Tuning Values is a text field where you enter the list of values separated by commas.

• Even if you aren’t sure which list of values to add to which parameter, you can still use the hyperparameter tuning capabilities because this tuning process can be done automatically. The new HypertuneParamSet forecasting parameter contains a default set of parameter values that are used when no values exist for the Hyperparameter Tuning Values field for any of the forecasting parameters.

Additionally, 8 new forecasting parameters have been introduced to configure hyperparameter tuning. These forecasting parameters all appear in the Hyperparameter Tuning category.

New Hyperparameter Tuning Category and Parameters

To enable hyperparameter tuning, you must add the HypertuneSamplePercent parameter to your forecasting profile and change it to a value between 1 and 100.

Details regarding the parameters for hyperparameter tuning

• HypertuneSamplePercent forecasting parameter:
  • Specifies the percentage of the forecast population for which hyperparameter tuning is done during each forecast run. Valid values are integers from 0 to 100.
    • A value of 0 indicates that hyperparameter tuning is disabled.
    • A value of 100 indicates that hyperparameter tuning will be performed for the entire forecast population each time the forecast process is run.
    • Values greater than 0 and less than 100 represent the percentage of the forecast population for which hyperparameter tuning will be performed. In this case, the engine will track forecast nodes that have been tuned and select a different set of nodes each time. For example, if HypertuneSamplePercent=20, then each time the engine is run it will select a different 20% of the forecast population. After 5 runs, 100% of the forecast population will have been covered.
    • The default value is 0.  

NOTE: To enable hyperparameter tuning, you must add the HypertuneSamplePercent forecasting parameter to your forecasting profile and set it to a value greater than 0. This is the only hyperparameter tuning parameters that you must add to your forecasting profile. You can add the other 7 if you want to change the default values.

• HypertuneOutputMode forecasting parameter:
  • Specifies whether to save the results of hyperparameter tuning in the output measures. Valid values are 0, 1, and 2.
    • 0 for no output. Saving only the base, untuned forecast in the forecasting profile's output measure.
    • 1 for tune and use. If the forecast resulting from hyperparameter tuning meets the threshold for forecast accuracy improvement then it will be written to the forecasting profile's output measure along with the tuning settings in the settings measure for hyperparameters otherwise the base, untuned forecast will be output.
    • 2 for writing the base, untuned forecast to the forecasting profile's output measure and the forecast resulting from hyperparameter tuning (if it meets the threshold for forecast accuracy improvement) to the tuned forecast measure for hyperparameters along with the tuning settings in the settings measure for hyperparameters.
    • The default is 2.

• HypertuneHalflife forecasting parameter:
  • Specifies the number of days that the output of hyperparameter tuning is considered fresh. After this period, retuning is done for combinations for which the output of hyperparameter tuning is older than this parameter.
    • Default value is 182 days.

• HypertuneHoldback forecasting parameter:
  • Specifies the number of days before the plan start date to use for holdback validation, that is, out-of-sample testing, of the results of hyperparameter tuning.
    • The value for HypertuneHoldback isn't used if it's greater than the value for HypertuneHoldbackPercent.
    • Default value is 182 days.

• HypertuneHoldbackPercent forecasting parameter:
  • Specifies the maximum percentage of history to use for holdback validation, that is, out-of-sample testing, for each combination during hyperparameter tuning.
    • The value for HypertuneHoldback isn't used if it's greater than the value for HypertuneHoldbackPercent.
    • Default value is 30 percent.

• HypertuneMAPEThreshold forecasting parameter:
  • Specifies the minimum percentage of change required between the base, untuned mean absolute percentage error (MAPE) and the MAPE after hyperparameter tuning for a combination for the optimization to be successful. If the percentage of change is below the threshold, the optimization is ignored.
    • Default value is 1 percent.

• HypertuneParamSet forecasting parameter:
  • Specifies a default set of parameter values to be used for hyperparameter tuning if its enabled, but no values have been entered in the Hyperparameter Tuning Values column on the Forecasting Parameters tab.
  • Default value is: IntermitCriterion[10,90],ForecastValidationSensitivity[0.2,5,10],OutlierSensitivity[2,3,4],CollinearityUseRidge[0,1]

NOTE: This default set of parameter values shouldn’t be edited.

• HypertuneAdvisor forecasting parameter:
  • Currently not used. For future use. Leave the default value of 0.

Hyperparameter tuning output measures

When enabling hyperparameter tuning for a specific forecasting profile, the demand forecast writes the tuning outcome to new output measures.

• If a predefined output measure is selected in the forecasting profile (Bookings Forecast or Shipments Forecast), then the 5 new predefined output measures will be added to the selected measure catalogs in the forecasting profile.

• If a user-defined output measure is selected in the forecasting profile, then the 5 new output measures will be created after you save the profile.

NOTE: For a plan that includes a forecasting profile with a user-defined output measure, you must run the plan with the Refresh with current data option enabled before hyperparameter tuning can be performed on the plan.

Output Measure

New hyperparameter tuning output measures

The names of the hyperparameter tuning output measures vary based on the name of the output measure selected in the forecasting profile. For example, if the output measure is Bookings Forecast, then the hyperparameter tuning output measures will be Bookings Forecast: Tuned, Bookings Forecast: Tuned Settings, Bookings Forecast: Tuned Base MAPE, Bookings Forecast: Tuned Best MAPE, and Bookings Forecast: Last Attempt at Tuning.

• <Forecasting Profile Output Measure name>: Tuned
  • A numeric measure which captures the hyperparameter tuning forecast results.

• <Forecasting Profile Output Measure name>: Tuned Settings
  • A text measure which includes the forecasting parameter Name and the optimized value for each selected parameter for tuning. The measure output will be added for each combination/node based on the related forecast tree (forecasting table).

• <Forecasting Profile Output Measure name>: Tuned Base MAPE
  • The base, untuned out-of-sample MAPE calculated on the plan’s population based on the percent specified in the HypertuneSamplePercent parameter.

NOTE: This is the MAPE calculation on the population before the tuning calculation.

• <Forecasting Profile Output Measure name>: Tuned Best MAPE
  • The best out-of-sample MAPE on the same part of the plan’s population based on the percent specified in the HypertuneSamplePercent parameter.

NOTE: This is the MAPE calculation on the population after the tuning calculation.

• Tuning will occur on nodes where the Tuned Best MAPE < Tuned Base MAPE, which indicates a better forecast accuracy, and when the difference between the 2 MAPES is above the minimum threshold required for tuning. Threshold settings is done on HypertuneMAPEThreshold forecasting parameter. If the percentage of the change is below the threshold, then the optimization is ignored.

• <Forecasting Profile Output Measure name>: Last Attempt at Tuning
  • A date measure to capture the tuning timestamp, so the next time hyperparameter tuning runs, it can decide if it should tune this node or not.

NOTE:

• Hyperparameter tuning populates the attempt date measure for every node it runs on whether or not it actually tuned the node.  There are cases that tuning ran but wasn’t able to improve the forecast. In those cases, the forecast profile populates only the Last Attempt at Tuning with the plan’s run date, without populating the other tuned measures.

• In cases where the Sample Percent is < 100, the combinations that don’t participate in the hyperparameter tuning process will get a Last Attempt at Tuning value of: 01/01/2000.

Example of hyperparameter Tuning Output Measures in a Table After Demand Forecast Run

MAPE process: (using the Bookings Forecast output measure as an example)

• When the demand forecast runs in the Hyperparameter Tuning mode, it includes 3 stages with regards to MAPE:
  • Stage 1: The forecast runs on the full population, and this is the base forecast. MAPE output will be to the Bookings Forecast MAPE measure as always. This MAPE is an in-sample MAPE.
  • Stage 2: The forecast runs on part of the population based on the percent specified in the HypertuneSamplePercent parameter. This is an out-of-sample run and it is before the hyperparameter tuning calculations. Output is to the Bookings Forecast Tuned Base MAPE measure.
  • Stage 3: The forecast calculates the tuning based on the hyperparameter tuning parameters on the same population as in Stage 2 and writes the resulting MAPE to the Bookings Forecast Tuned Best MAPE measure. This is also an out-of-sample MAPE.

• After the 3 stages, the demand forecast compares between the 2 out-of-sample MAPE measures based on the HypertuneMAPEThreshold parameter. This means that if the parameter has 1% as the MAPE threshold, and the Best MAPE is different than the Base MAPE in less than 1%, then the demand forecast won’t write to the to the tuned MAPE measures, because it wasn’t good enough and didn't produce a more accurate forecast.

Example for several forecast demand runs on the same forecasting profile with hyperparameter tuning enabled

Forecasting Profile: HyperTuneSamplePercent=5

• 1st run:
  • Hyperparameter tuning is calculated on a random 5% of the plan’s population, and the tuned output measures will include the output data only on that 5%.
  • On the other 95% of the population, the Bookings Forecast Tuned measure and other tuned measures are all Null, except for the Last Attempt at Tuning which displays the 01/01/2000 date.

• 2nd run:
  • Hyperparameter tuning is calculated on another 5% of the population.

• 3rd run and continue:
  • Same as second run until the HypertuneHalflife number of days is reached. When that stage is reached, then the tuning will retune the existing values from the 1st

Nodal tuning:

The Use Automated Hyperparameter Tuning to Improve Forecast Accuracy feature includes the ability for the demand forecast to use the optimal value per parameter from the Tuned Settings output measure, and to use that measure as the input for the next demand forecast run per node.

2 new forecasting parameters are now available to be used for this purpose.

Nodal Tuning Parameters

• EnableNodalTuning parameter:
  • Specifies whether to use a measure with optimized parameter values as the input for the next time the forecast is generated. If hyperparameter tuning is turned on and HypertuneOutputMode=1, then EnableNodalTuning should be set to 2. Parameter values may be 0, 1, 2.
    • 0 for not using nodal tuning.
    • 1 for always using nodal tuning.
    • 2 for using nodal tuning when hyperparameter tuning is enabled and HypertuneOutputMode=1
    • Default value is 2.

• SetNodalTuningSource Parameter:
  • Currently not used. For future use.

Steps to Enable

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

Tips And Considerations

• Hyperparameter related forecasting parameters will be used only in cases where the HyperTuneSamplePercent is > 0.

• The HypertuneHoldbackPercent parameter is an optional parameter, and it’s a secondary limit to the HypertuneHoldback parameter as the max % of history to use as holdback for each node. When using this parameter as well, the holdback used for each combination eventually will be smaller from the values of the HypertuneHoldback and the HypertuneHoldbackPercent.

• 10 predefined measures were added in in this update:
  • Bookings Forecast: Tuned Settings
  • Shipments Forecast: Tuned Settings
  • Bookings Forecast: Tuned
  • Shipments Forecast: Tuned
  • Bookings Forecast: Tuned Base MAPE
  • Shipments Forecast: Tuned Base MAPE
  • Bookings Forecast: Tuned Best MAPE
  • Shipments Forecast: Tuned Best MAPE
  • Bookings Forecast: Last Attempt at Tuning
  • Shipments Forecast: Last Attempt at Tuning

Key Resources

• Watch the Use Automated Hyperparameter Tuning to Improve Forecast Accuracy demo.

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to the Manage Forecasting Profiles task will be able to use this feature.

Users who are assigned a configured job role that contains these privileges can 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)

These privileges were available prior to this update.

Export Data in Planning Tables with Expanded Volume Limits

Export data from tables with as many as 1 million rows and 4,000 columns, subject to a maximum of 2 million cells. The Export Data in Format Specified in a Planning Table feature introduced in the 24A update is now enhanced to support increased volume limits. In addition, you can now export using either Microsoft Excel file format or CSV file format.

Export Data in Table Format Page

Previously, the Export Data in Table Format function supported exporting tables with up to 65,536 rows and 256 columns. These limits have been extended to 1 million rows and 4,000 columns with a maximum of 2 million cells. For example, you can now export a table with any of the following combinations (all of which equate to 2 million cells.)

• 1 million rows and 2 columns
• 500,000 rows and 4 columns
• 100,000 rows and 20 columns

This function has also been enhanced to support exporting in CSV (comma-separate values) format in addition to XLS (Microsoft Excel) format.

Steps to Enable

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

Tips And Considerations

Microsoft XLS format has a limit of 256 columns and 65,536 rows per sheet. When exporting in XLS format:

• The number of columns will be limited to 256.

• If the table selected for export has more than 65,536 rows (but less than 1 million rows), then the output will be split into multiple sheets within the same Excel workbook with each sheet having 65,536 rows or less.

• The resulting XLS file will include a macro that automatically runs the first time the file is opened. This macro will merge the multiple sheets into a single sheet and convert the file from an XLS format to an XLXS format.  Microsoft XLXS format has a limit of 1 million rows.

Key Resources

• Export Data in Format Specified in a Planning Table (update 24A)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to open planning tables will automatically be able to use this feature.

Users who are assigned a configured job role that contains one or both of these privileges can access this feature:

• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

These privileges were available prior to this update.

Enable Receipt-Based Forecasting

A typical healthcare supply chain has several Periodic Automatic Replenishment (PAR) inventory locations where inventory isn’t tracked. However, at these PAR locations, receipt transactions are tracked. To accurately forecast and understand the requirement at these PAR locations, receipts are used as a proxy for usage or consumption information.

With this update, historical receipt transactions are collected from Oracle Fusion Cloud Inventory Management and used to generate a receipt-based forecast. The receipt-based forecast is then used as input to generate the PAR inventory levels. Additionally, a new forecast profile is seeded to smooth the demand when receipts are intermittent and to reflect a more reasonable mean absolute percent error (MAPE) value.

The existing Collect Planning Data process has been enhanced to provide the ability to collect receipts history from Oracle Fusion Cloud Inventory Management for both organizations and subinventories.  Two new check boxes are now available for this process:

• Collect receipts history for organizations
• Collect receipts history for subinventories

Collect Planning Data Page with New Check Boxes

The date range for collection of receipts is determined by your choices in the Collection Time Frame Options section.

Three new measures have been provided related to the collection of receipts:

• Receipts History: This measure is populated by the collection process when receipt history is collected for organizations and/or subinventories. 

• Adjusted Receipts History: This is an editable measure for planners to make manual overrides to the collected receipt history.

• Final Receipts History: This is a calculated measure that returns the Adjusted Receipts History measure value if one exists and otherwise returns the Receipts History measure value.

A new forecasting profile, named Forecast Receipts, has been provided to forecast receipts.

Forecast Receipts Forecasting Profile

This forecasting profile takes the Final Receipts History measure as input and outputs the resulting forecast to a new measure named Receipts Forecast.

This forecasting profile has all intermittent forecast models enabled in order to account for the typically irregular occurrence of receipts.

In addition to the new Receipts Forecast measure, several new measures have been provided related to the forecasting of receipts. These include:

• Adjusted Receipts Forecast:   An editable measure for planners to make manual overrides to the generated receipt forecast using a quantity value.

• Adjusted Receipts Forecast Percentage:   An editable measure for planners to make manual overrides to the generated receipt forecast using a percentage.

• Final Receipts Forecast:  A calculated measure that returns the receipts forecast after applying adjustments made using the Adjusted Receipts Forecast and Adjusted Receipts Forecast Percentage measure values.

• Forecast accuracy metrics: Receipts Forecast MAD, Receipts Forecast MAPE, and Receipts Forecast Bias.

For a complete list of receipts history and forecasting measures, refer to the measure group named Receipts-Based Forecasting.

Steps to Enable

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

Tips And Considerations

Receipts are collected for only items with a planning method of Replenishment Planning.

When collecting receipts for subinventories, receipts are collected for only subinventories that belong to organizations that are enabled for subinventory planning.

The new Receipts History measure is dimensioned by Item, Organization, Customer Site, Demand Class, Sales Representative, and Day. Receipts captured in Oracle Fusion Cloud Inventory Management aren’t associated with a customer site or demand class. As such, when receipt history is collected, the Customer Site and Demand Class levels are populated with a -1 value which appears as Unassigned when viewed in the application.

The following table lists the transactions from Oracle Fusion Cloud Inventory Management that are collected into the Receipts History measure when the Collect receipts history for organizations option is selected.

The following table lists the transactions from Oracle Fusion Cloud Inventory Management that are collected into the Receipts History measure when the Collect receipts history for subinventories option is selected.

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to Collect Planning Data will automatically be able to use this feature.

Users who are assigned a configured job role that contains these privileges can access this feature:

• Collect Planning Hierarchies Data (MSC_COLLECT_PLANNING_HIERARCHIES_DATA_PRIV)
• Collect Planning Reference Data (MSC_COLLECT_PLANNING_REFERENCE_DATA_PRIV)
• Collect Planning Transaction Data (MSC_COLLECT_PLANNING_TRANSACTION_DATA_PRIV)

These privileges were available prior to this update.

Increase Performance of the Aggregate Collected Planning Data Scheduled Process When Run in Net Change Mode

If you're using the Plan at Flexible Levels for the Customer Dimension feature, introduced in the 24A update, data collected at the customer site level is aggregated to the level you want to plan at in the customer dimension. Previously, you could only run the collection process in a targeted mode that reaggregated the entire data set after each collection, which can potentially take a long time. You can now use net change mode. This mode reduces your planning cycle time and runs faster because it reaggregates only the subset of data that changed.

The Aggregate Collected Planning Data scheduled process was introduced in the 24A update as part of the Plan at Flexible Levels for the Customer Dimension feature. This process is run after collections to aggregate and store collected measure data at the levels specified in your planning level profiles. This aggregated data is then used during the Refresh with Current Data step of a plan run for demand plans with planning level profiles selected.

Aggregate Collected Planning Data Page with Choices for the Type Field

Previously the Aggregate Collected Planning Data scheduled process always ran in Targeted mode. This meant than when new measure data was collected, the process reaggregated all existing collected data, not just the newly collected data.

The process has been enhanced to allow the selection of Targeted or Net change mode. The default is Targeted.

Now, when the Aggregate Collected Planning Data process is run in Net change mode, it will reaggregate only measure data that has changed since the last time the process was run.

In the case of incremental collection of measure data, running the Aggregate Collected Planning Data process in Net change mode will result in shorter run times as compared to running in Targeted mode.

Steps to Enable

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

Tips And Considerations

In addition to enhancing the Aggregate Collected Planning Data scheduled process, the existing Orchestrate Refresh Measures Processes scheduled process has also been enhanced. This process is used to perform an incremental refresh of plan data. Previously the process couldn’t be used for Demand Plans with a planning level profile. Now that it’s been enhanced, it can be used for these types of plans.

Key Resources

• Oracle Cloud Readiness > Demand Management
  • Plan At Flexible Levels for the Customer Dimension (update 24A)

• Oracle Cloud Readiness > Sales and Operations Planning
  • Refresh Collected Measure Data (update 22B)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to the Aggregate Collected Planning Data scheduled process will automatically be able to use this feature.

Users who are assigned a configured job role that contains these privileges can access this feature:

• Edit Planning Level Profiles (MSC_EDIT_PLANNING_LEVEL_PROFILES_PRIV)
• View Planning Level Profiles (MSC_VIEW_PLANNING_LEVEL_PROFILES_PRIV)
• Edit Plan Options (MSC_EDIT_PLAN_OPTIONS_PRIV)
• Run Plan with Snapshot (MSC_RUN_PLAN_WITH_SNAPSHOT_PRIV)

These privileges were available prior to this update.

Secure Plan Data Considering Unassigned Entities

Secure plan data providing visibility to unassigned members at the lowest level of the hierarchy for the customers, suppliers, organizations, or products dimension. With this update, you can provide visibility to data that’s currently not applicable to a dimension. For example, by assigning a particular organization to a user, you can now provide visibility to measures that aren’t striped by organization, such as supplier capacity.

You can configure planning data security with an enhanced option to include unassigned members of the Product, Organization, Customer, and Supplier entities. Doing so allows you to access measures that don’t use a dimension’s hierarchy levels. For example, the Supplier Capacity Available measure includes the Product, Organization, Supplier, and Time dimensions. The measure is computed at the Item, Supplier-Supplier site, and Day levels of the Product, Supplier, and Time dimensions. Because the measure value isn’t specific to an Organization, the Organization level isn’t included in the measure’s computation. In such a scenario, you can set up a data access set to get access to specific organizations as well as measures that aren’t specific to an organization (such as Supplier Capacity Available).

The following are examples of Supply Planning measures that can now display values by configuring data security with the Organization entity that has the Include unassigned planning level member check box selected:

• Supplier Capacity Available
• Supplier Capacity Required
• Net Supplier Capacity Available
• Supplier Capacity Utilization Percentage
• Supplier Capacity Required by Supplier Capacity Constraint Date
• Additional Capacity Required by Supplier Capacity Constraint Date

Secure Plans Considering Unassigned Entities applies at the lowest level of the hierarchies for the Product, Organization, Customer, and Supplier dimensions. It is applicable to views displaying measures and planning analytics details for the Product, Organization, Customer, and Supplier dimensions in Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, Replenishment Planning, Global Order Promising, and Backlog Management.

The Administer Data Security view has been enhanced as follows:

• The data access set condition configuration has a new Include unassigned planning level member check box. You can select this check box only when the condition being created includes the Product, Organization, Customer, or Supplier entities at their lowest hierarchy level.

• You can select the Include unassigned planning level member check box along with other lowest-level members of the Product, Organization, Customer, and Supplier hierarchies.

Perform the following steps to secure plan data with unassigned members:

1. Select Product, Organization, Customer, or Supplier as an entity in a data access set.

2. Select the lowest level for Product, Organization, Customer, or Supplier.

Create a Data Access Set on the Administer Planning Security page

3. Select the Create action to create a condition for Condition Name and select the Include unassigned planning level member check box.

Create a Condition for an Organization Entity

4. Create a condition by providing a Condition Name and selecting the Include unassigned planning level member check box. Add other level members if required to configure the data condition.

New Include Unassigned Planning Level Member Check Box

5. Save the condition and assign it to the selected entity.

Assign the Condition to the Organization Entity

Let’s walk through some examples of Supplier Capacity measure details displayed when the Include unassigned planning level member check box is selected in the Supply Planning work area.

We will see how the data access set configured in the preceding screenshot is applied to the measure values in a table. The following pivot table shows Planned Orders measure values for organization-level members M1 and M2 and Supplier Capacity measure values for the unassigned organization-level member. The example shows a data security condition is created with organization-level members M1 and M2, and the Include unassigned planning level member check box is selected.

Pivot Table Created with Organization-Level Members

Let’s see what happens when we configure a data access set with the Include unassigned planning level member check box selected and with other lowest level members. Data security applies an In condition. In the following screenshot, a data security condition was created by selecting Include unassigned planning level member, M1, and M2 for an Organization. The condition applies data security for measures where the organization value can be unassigned, M1, or M2.

The pivot table shows values for Planned Orders and Supplier Capacity Available measures when the data security condition is configured with M1, M2, and unassigned organization-level members.

Data Security Condition for Organization-Level Members and Pivot Table Details

You can enable Include unassigned planning level member across multiple entities within a data access set. When enabled within a data access set, security is applied as an "AND" condition.

When Include unassigned planning level member is selected for an Organization and Customer entity, data security is applied and displayed for the measures when both Organization and Customer combinations are unassigned in a pivot table.

The pivot table shows values for user-defined measures with unassigned-level members for organization and customer entities.

Data Security Condition for Organization- and Customer-Level Members and Pivot Table Details

When you enable Include unassigned planning level member across data access sets, security is applied as a "OR" condition.

In the following example, enabling Include unassigned planning level member for Item in data access set1 and Organization entity in data access set 2, data security is applied and displayed for users for the measures when either Item or Organization have unassigned as lowest-level members in a pivot table.

The pivot table displays values for user-defined measures with unassigned level members for organization or customer entities.

Data Security Conditions for Data Sets and Pivot Table Details

Steps to Enable

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

Tips And Considerations

• Oracle Global Order Promising respects data security for the Organization entity only.

• Customer and Supplier data security configurations are applied for planning analytics user interfaces like pivot tables or graphs in these work areas: Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, and Replenishment Planning.

• You can’t enable Include unassigned planning level member for existing data conditions. You must create a new data condition to enable it.

• You can delete data conditions with Include unassigned planning level member using Manage Conditions only if the condition isn’t assigned to an entity across a data access set.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Administer Planning Security (MSC_ADMINISTER_PLANNING_SECURITY_PRIV)

This privilege was available prior to this update.

Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning

Use deep links to create more connected analytics and a seamless user experience between external applications and Oracle Fusion Cloud Supply Chain Planning. Deep links are a type of hyperlink used to open pages without using menus or navigating through a menu structure. With this update, you can easily navigate from an application, such as Oracle Fusion Analytics Warehouse, to specific pages in Oracle Supply Chain Planning. For example, you could create a deep link to navigate from Oracle Fusion Analytics Warehouse to the plans for an item in Oracle Supply Chain Planning.

This feature is supported for the following work areas: Supply Planning, Demand Management, Demand and Supply Planning, Replenishment Planning, and Sales and Operations Planning. With this feature, you can now navigate to the page layout and table or graph in the respective work areas. Additionally, you can navigate to the Exceptions or Supplies and Demand page.

The sample deep link URL for accessing this feature consists of three parts:

https://<host>/fscmUI/faces/deeplink?objType=<OBJECT_TYPE>&objKey=<Entity;Plan;FilterContext>

Base URL                                            Object Type Path                    Object Key Values

• Base URL: This part must include the host information with “/fscmUI/faces/deeplink?” appended after it; for example, https://<host>/fscmUI/faces/deeplink?

• Object type path: This part should have the work area name under objTypethat that you want to open. For example, if you want to open the Supply Planning work area, pass objType = “MSC_SP_WORKAREA”. This path is appended to the base URL and contains details about the work area you are creating the link to.

• Object key values: 
  • Entity: Pass the table or graph or layout option that you intend to open; for example, objkey=Entity=Material Plan or objkey=Entity=Forecast Graph or objkey=Entity=Plan Summary.
  • Plan name: Pass the plan name or plan ID of the Oracle Supply Chain Planning plan that you intend to open; for example, Plan=RTSP-Supply-Plan.
  • Filter context: The filter context contains details about the hierarchies, levels, and level members of the dimension in the table, graph, or hierarchies and level members details of the dimension in the table or graph. It allows you to filter data records based on the details of the dimension you choose to filter. This information is appended to a combination of a base URL and object type path; for example, hierarchy1=Enterprise;level1=Organization,member1=M1.                       

You can pass the object key values using the following parameters:

• Parameters: Pass the parameters under the object key values; for example, hierarchy1=Product;level1=Item,member1=Laptop_1GB or hierachy1=Product;levelmember1=512342

When using this feature to link an Oracle Analytics report from Oracle Fusion Analytics Warehouse, construct the URL using the reporting platform features that support tokens as follows:

• Token values: Pass the column name under the object key values; for example, hierarchy1=${keyValuesForColumn:Hierarchy};level1=${keyValuesForColumn:level};member1=${keyValuesForColumn:Prd_Member_Id}; or hierachy1=${keyValuesForColumn:Hierarchy;levelmember1=${keyValuesForColumn:Prd_lvl_Member_Id}

The ObjType parameters for the work areas are as follows:

• Demand Management                 MSC_DM_WORKAREA
• Supply Planning                           MSC_SP_WORKAREA
• Demand and Supply Planning     MSC_ISD_WORKAREA
• Replenishment Planning              MSC_REPL_WORKAREA
• Sales and Operations Planning   MSC_SOP_WORKAREA

For example, the following URL takes you to the Material Plan table in the Supply Planning work area from the Oracle Fusion Analytics Warehouse application.

With token values:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=MaterialPlan;plan=${keyValuesForColumn:PLAN_ID};hierarchy1=${keyValuesForColumn:HIERARCHY_ID};levelMember1=${keyValuesForColumn:ORG_LVL_MEMBER_ID};hierarchy2=${keyValuesForColumn:HIERARCHY_ID};levelMember2=${keyValuesForColumn:PRD_LVL_MEMBER_ID};hierarchy3=${keyValuesForColumn:HIERARCHY_ID};levelMember3=${keyValuesForColumn:TIM_LVL_MEMBER_ID}

With parameters:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=Material Plan;plan=RTSP-KB-SP-PL01;hierarchy1=SP_Catalog;level1=Item;member1=KB-CSP-ALLOY;hierarchy2=APS Calendar;level2=Week;member2=1/7/30;hierarchy3=Enterprise;level3=Organization;member3=M1

Additionally, it’s possible to pass the parameters of Member Id, Hierarchy Id, and Level Id details up to 5 parameters with names like member2, level2, hierarchy2, etc. All context details are appended with the AND clause. For example, if multiple Member Id, Level Id, and Hierarchy Id details are passed, then the filter context will be represented as (Member Id1, Level Id1, Hierarchy Id1) AND (Member Id2, Level Id2, Hierarchy Id2).

Steps to Enable

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

Tips And Considerations

The Supplies and Demand page and the Exceptions page in their respective work areas support only the Item and Organization dimensions. However, it's important to note that this feature isn’t supported for Tiles and Tile sets within Graph sections.

If any of the parameters are missing or incorrectly passed, the following error is displayed.

Key Resources

• Watch the Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning demo.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Demand Management Work Area (MSC_MONITOR_DEMAND_MANAGEMENT_WORK_AREA_PRIV)
• Monitor Demand and Supply Planning Work Area (MSC_MONITOR_DEMAND_AND_SUPPLY_PLANNING_WORK_AREA_PRIV)
• Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
• Monitor Sales and Operations Planning Work Area (MSC_MONITOR_SALES_AND_OPERATIONS_PLANNING_WORK_AREA_PRIV)
• Monitor Supply Planning Work Area (MSC_MONITOR_SUPPLY_PLANNING_WORK_AREA_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

Users must have access to the individual pages and tables.

Selected Demand Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Demand Management 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.

Export Data in Format Specified in a Planning Table

In Update 24A, we introduced the Export Data in Format Specified in a Planning Table feature. This feature lets you export tables to Microsoft Excel while retaining the original table layout. With this feature, you can export tables that you weren’t previously able to open because they exceeded the 250,000 cell limitation. You can invoke this feature in the following ways:

• Use the Actions drop-down button in an open plan.
• Use the Actions menu on the Manage Plans page of the selected plan.
• Run the Export Data in Table Format scheduled process with a Plan and Table Name selected.

After this feature was introduced, we discovered that exporting tables with more than 2 million cells could cause an out-of-memory issue and, in some cases cause a server to stop functioning or operating correctly. To protect against this, we are introducing a limitation in Update 24B that will prevent the export of a table that contains more than 2 million cells. It’s possible that you successfully exported a table that exceeded this limitation in Update 24A. If so, this will no longer be possible in Update 24B and later releases.

Oracle reference: 36275383

Steps to Enable

You don't need to do anything to enable 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.

Enable Receipt-Based Forecasting

A typical healthcare supply chain has several Periodic Automatic Replenishment (PAR) inventory locations where inventory isn’t tracked. However, at these PAR locations, receipt transactions are tracked. To accurately forecast and understand the requirement at these PAR locations, receipts are used as a proxy for usage or consumption information.

With this update, historical receipt transactions are collected from Oracle Fusion Cloud Inventory Management and used to generate a receipt-based forecast. The receipt-based forecast is then used as input to generate the PAR inventory levels. Additionally, a new forecast profile is seeded to smooth the demand when receipts are intermittent and to reflect a more reasonable mean absolute percent error (MAPE) value.

The existing Collect Planning Data process has been enhanced to provide the ability to collect receipts history from Oracle Fusion Cloud Inventory Management for both organizations and subinventories.  Two new check boxes are now available for this process:

• Collect receipts history for organizations
• Collect receipts history for subinventories

Collect Planning Data Page with New Check Boxes

The date range for collection of receipts is determined by your choices in the Collection Time Frame Options section.

Three new measures have been provided related to the collection of receipts:

• Receipts History: This measure is populated by the collection process when receipt history is collected for organizations and/or subinventories. 

• Adjusted Receipts History: This is an editable measure for planners to make manual overrides to the collected receipt history.

• Final Receipts History: This is a calculated measure that returns the Adjusted Receipts History measure value if one exists and otherwise returns the Receipts History measure value.

A new forecasting profile, named Forecast Receipts, has been provided to forecast receipts.

Forecast Receipts Forecasting Profile

This forecasting profile takes the Final Receipts History measure as input and outputs the resulting forecast to a new measure named Receipts Forecast.

This forecasting profile has all intermittent forecast models enabled in order to account for the typically irregular occurrence of receipts.

In addition to the new Receipts Forecast measure, several new measures have been provided related to the forecasting of receipts. These include:

• Adjusted Receipts Forecast:   An editable measure for planners to make manual overrides to the generated receipt forecast using a quantity value.

• Adjusted Receipts Forecast Percentage:   An editable measure for planners to make manual overrides to the generated receipt forecast using a percentage.

• Final Receipts Forecast:  A calculated measure that returns the receipts forecast after applying adjustments made using the Adjusted Receipts Forecast and Adjusted Receipts Forecast Percentage measure values.

• Forecast accuracy metrics: Receipts Forecast MAD, Receipts Forecast MAPE, and Receipts Forecast Bias.

For a complete list of receipts history and forecasting measures, refer to the measure group named Receipts-Based Forecasting.

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 Enable Receipt-Based Forecasting 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.

Receipts are collected for only items with a planning method of Replenishment Planning.

When collecting receipts for subinventories, receipts are collected for only subinventories that belong to organizations that are enabled for subinventory planning.

The new Receipts History measure is dimensioned by Item, Organization, Customer Site, Demand Class, Sales Representative, and Day. Receipts captured in Oracle Fusion Cloud Inventory Management aren’t associated with a customer site or demand class. As such, when receipt history is collected, the Customer Site and Demand Class levels are populated with a -1 value which appears as Unassigned when viewed in the application.

The following table lists the transactions from Oracle Fusion Cloud Inventory Management that are collected into the Receipts History measure when the Collect receipts history for organizations option is selected.

The following table lists the transactions from Oracle Fusion Cloud Inventory Management that are collected into the Receipts History measure when the Collect receipts history for subinventories option is selected.

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to Collect Planning Data will automatically be able to use this feature.

Users who are assigned a configured job role that contains these privileges can access this feature:

• Collect Planning Hierarchies Data (MSC_COLLECT_PLANNING_HIERARCHIES_DATA_PRIV)
• Collect Planning Reference Data (MSC_COLLECT_PLANNING_REFERENCE_DATA_PRIV)
• Collect Planning Transaction Data (MSC_COLLECT_PLANNING_TRANSACTION_DATA_PRIV)

These privileges were available prior to this update.

Export Data in Planning Tables with Expanded Volume Limits

Export data from tables with as many as 1 million rows and 4,000 columns, subject to a maximum of 2 million cells. The Export Data in Format Specified in a Planning Table feature introduced in the 24A update is now enhanced to support increased volume limits. In addition, you can now export using either Microsoft Excel file format or CSV file format.

Export Data in Table Format Page

Previously, the Export Data in Table Format function supported exporting tables with up to 65,536 rows and 256 columns. These limits have been extended to 1 million rows and 4,000 columns with a maximum of 2 million cells. For example, you can now export a table with any of the following combinations (all of which equate to 2 million cells.)

• 1 million rows and 2 columns
• 500,000 rows and 4 columns
• 100,000 rows and 20 columns

This function has also been enhanced to support exporting in CSV (comma-separate values) format in addition to XLS (Microsoft Excel) format.

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 Export Data in Planning Tables with Expanded Volume Limits 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.

Microsoft XLS format has a limit of 256 columns and 65,536 rows per sheet. When exporting in XLS format:

• The number of columns will be limited to 256.

• If the table selected for export has more than 65,536 rows (but less than 1 million rows), then the output will be split into multiple sheets within the same Excel workbook with each sheet having 65,536 rows or less.

• The resulting XLS file will include a macro that automatically runs the first time the file is opened. This macro will merge the multiple sheets into a single sheet and convert the file from an XLS format to an XLXS format.  Microsoft XLXS format has a limit of 1 million rows.

Key Resources

• Export Data in Format Specified in a Planning Table (update 24A)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to open planning tables will automatically be able to use this feature.

Users who are assigned a configured job role that contains one or both of these privileges can access this feature:

• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

These privileges were available prior to this update.

Use Independent and Total Demand Forecasts for Enhanced Policy and Replenishment Calculations for Multiechelon Replenishment Plans

In a multiechelon replenishment network, some enterprises prefer to use a single holistic plan to generate both the independent and dependent forecast. Based on the echelon, the independent and dependent forecast will be used to generate inventory policy values and replenishment orders.

Use the new Independent Demand plan option and the existing End Item Demand plan option to model your business use case to generate independent and total forecasts for integrated multiechelon replenishment plans. The total forecast, independent plus dependent demand forecast, at source location is used to calculate policy values, but for replenishment order calculations, the independent demand forecast at source location plus the dependent demand coming from destination organizations is used.

These calculations are supported within a single multiechelon replenishment plan.

Steps to Configure a Single Multiechelon Replenishment Plan

Summary of steps to configure a single multiechelon replenishment plan to generate independent and total forecast, calculate policies, and calculate replenishments.

• Collect transfer orders history along with shipments history.

• Configure a multiechelon plan:
  • Enable these plan options: Calculate Forecast, Calculate Policies, Calculate Replenishments.
  • In the Demand tab, specify these forecasting profiles:
    • Forecast Shipments to generate total forecast.
    • Forecast Independent Shipments (new) to generate independent forecast.
  • In the Supply tab,  Organizations and Schedules subtab, select these values for your demand measures, or you can use user-defined measures.
    • End Item Demand: Final Shipments Forecast
    • Independent Demand: Final Independent Shipments Forecast

Demand Measures

• Also, select these values for the corresponding forecast accuracy measures, or you can use user-defined measures:
  • Measure for MAPE: Shipments Forecast MAPE
  • Measure for Intermittent Demand: Shipments Forecast Is Intermittent
  • Measure for Average Interarrival Time: Shipments Forecast Average Interarrival Time

Forecast Accuracy Measures

• Ensure that all new measures required to generate independent forecast are part of your measure catalog. Details are provided under the Tips and Considerations section.

Summary of How Total Forecast and Independent Forecast Are Generated

The following figure summarizes how total forecast and independent forecast are generated:

Summary of How Total Forecast and Independent Forecast Are Generated

Impact of This Feature on Replenishments and Policy Computation

• Planning will continue to use Gross Forecast measure for policy computation. The Gross Forecast measure represents total forecast and will continue to be driven by the measure selected under the End Item Demand plan option.

• Planning will use a new measure called Independent Gross Forecast for replenishments computation. This measure is driven by the measure selected under the Independent Demand plan option. Forecast processing logic will use this new Independent Gross Forecast measure. Independent Gross Forecast will get consumed by the Sales Orders measure, and then the Net Forecast measure will be populated. The logic for computing replenishment recommendations remains the same.

•  The Independent Demand plan option is enabled for only multiechelon plans with the Calculate Replenishments option enabled.

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 Independent and Total Demand Forecasts for Enhanced Policy and Replenishment Calculations for Multiechelon Replenishment Plans feature, you must opt into 2 features:

• The Replenishment Planning feature. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

• The Use Independent and Total Demand Forecasts for Enhanced Policy and Replenishment Calculations for Multiechelon Replenishment Plans feature.

Other Tips and Considerations:

• Measures and Forecasting Profiles:
  • Ensure that the measure catalog used in your replenishment plan has all the measures that are introduced under the new Independent Shipments Based Forecasting measure group. Otherwise, independent forecast won't be generated.
  • Ensure that you use the new forecast profile Forecast Independent Shipments for generating independent forecast.
  • For replenishments computation, ensure that you add the new measure Independent Gross Forecast to your measure catalog.

• Plan Configuration:
  • This feature is supported for only multiechelon-enabled plans.
  • If your business requires you to configure two separate plans, one for policy computation and another for replenishments computation, then you can continue to do so. It’s not required to have a single plan for policy and replenishments computation to use this feature.

• Validations After Opting in to This New Feature:
  • After you opt in to this feature, check the measures specified under the End Item Demand and Independent Demand plan options. It’s recommended that you validate or change these measures per your business requirement. The End Item Demand plan option should reflect total forecast that you would like to use for policy computation and the Independent Demand plan option should reflect independent forecast that you would like to use for replenishment computation along with the dependent demand propagated by the plan.

• Supersession Chain Items:
  • If you're forecasting for supersession chain items, then it’s recommended to configure a new forecast profile. You can duplicate Forecast Shipments for Supersession Chain profile and change the forecasting table definition/input/output measure definition to use the Independent Shipments History and Independent Shipments Forecast measures.

• External Forecast:
  • To support existing plan configurations, if the plan is driven by external forecast, then both the Gross Forecast and Independent Gross Forecast measures will be updated by the external forecast numbers. It’s recommended that you look into your external forecast numbers. You need to drive policy plan by including total demand in the external forecast and drive replenishment computation plan by including only independent demand in the external forecast.

• Plan Simulation:
  • Note that during multiechelon plan simulation:
    • Change in the Gross Forecast measure won’t change the Net Forecast measure because the Net Forecast measure is driven by the Independent Gross Forecast measure. You can change the Net Forecast measure directly if required.
    • Change in the Adjusted Independent Shipments Forecast measure won’t trigger plan simulation.

Key Resources

• Watch the Use Independent and Total Demand Forecasts for Enhanced Policy and Replenishment Calculations for Multiechelon Replenishment Plans demo.

• Recommended related training:
  • Introduction to Replenishment Planning Cloud (update 19D) Readiness Training
  • On Oracle Cloud Customer Connect: Replenishment Planning Training

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
• Manage Segments (MSC_MANAGE_SEGMENTS_PRIV)

These privileges were available prior to this update.

Filter Planned Buy Recommendations By Order Date, Ship Date, or Dock Date in Buyer Planning

Your business use case determines how the planned buy recommendations need to be displayed in the Buyer Planning work area. Use the new Date Type option in the Change Dates filter to select a date option. The planned buy recommendations will be filtered for display in the Buyer Planning work area by the option you selected. The Date Type options include Dock Date, Ship Date, and Order Date. Previously, planned buy recommendations were filtered only by dock date.

The updated selector to change dates is available on the Overview, Buyer Planning Search, and Buyer Planning Details pages. You select Dock Date, Ship Date, or Order Date as needed for your use case.

Change Dates Panel with the New Date Types Field

The Change dates panel with the Date Type field is where you select the date type of Dock Date, Ship Date, or Order Date to view your orders.

Date Type Selector on the Change Dates Panel Displaying the New Date Types: Dock Date, Ship Date, or Order Date

Due to the types of calculation performed on the Inventory Analysis page, you’ll be able to view orders only by dock date.

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 Filter Planned Buy Recommendations By Order Date, Ship Date, or Dock Date in Buyer Planning 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

Users who are assigned a configured job role that contains this privilege can access this feature:

• Edit Supplies in Buyer Planning (MSC_EDIT_SUPPLIES_BUYER_PLANNING_PRIV)

This privilege was available prior to this update.

Display Stockout Metric in Buyer Planning

For any enterprise, it’s critical to understand when you may run out of material and be unable to fulfill your demand. Having advance visibility to such an exception is critical to your business operations.

With this update, a new Item Locations with Stockout metric is part of the Buyer Planning dashboard. This metric displays:

• Top 10 item stockouts by revenue at risk: A table that displays the top 10 item locations by stockout days. It also displays the revenue that is at risk due to the stockout.

• Stockouts by location: A sunburst chart that displays the top 10 items for each location by stockout days. When you select a specific location the sunburst chart is refreshed to display the top 25 items by stockout days, and the table mentioned in the prior bullet is refreshed to show stockouts for that location only.

In addition, you can access the Inventory Analysis page for the specific item location by clicking on the stockout days to get additional details, such as projected available balance, average daily demand, and updated days of cover. Use this information to analyze your overall plan results and take proactive steps to prevent a stockout.

Details regarding the metric

• The new Item Locations with Stockouts metric:
  • Displays a list of the top 10 items locations by the highest estimated revenue at risk.
  • Each item location shows the number of stockout days for the given date period, the number of days with a safety stock violation, and the revenue at risk.
  • You can click on the stockout days number to view the detailed Inventory Analysis page for the given item, which will show you the dates of the stockouts and safety stock violations, along with additional information.

• The Stockouts by location chart:
  •  Displays the top 10 items stockouts in each location by the number of stockout days.
  • The size of the segment varies by the number of stockouts, and the color of each segment varies by the revenue at risk.

Details for viewing the metric

To refine the stockouts data, click the Change Dates action button and modify the date range.

Item Locations with Stockouts Metric

Hover over the location in the chart to display the total number of stockout days and the revenue at risk for the items at that location. Hover over an item to display that item’s stockout days and revenue at risk.

Details Displayed Upon Hovering

You can get details for a specific location.

• Click on a location in the chart to draw the chart again to show the details for just that location with the top 25 item stockouts for that location displayed.

• At the same time, the Top 10 Item Stockouts by Revenue at Risk table on the left will be refreshed to show entries for only that location.

To reset the chart to the default view of all locations, click the All link.

The Stockout Metrics Refreshed to Show Data for One Location

Steps to Enable

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

Offering: Supply Chain Planning

Tips And Considerations

If you want to use the Display Stockout Metric in Buyer Planning 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.

When there are no item stockouts, the metric card won’t be displayed.

Key Resources

• Watch the Display Stockout Metric in Buyer Planning demo.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Buyer Planning Work Area (MSC_MONITOR_BUYER_PLANNING_WORK_AREA_PRIV)

These privileges were available prior to this update.

Display Price Break Information in Primary Unit of Measure in Buyer Planning

The unit of measure (UOM) used in planning applications may differ from the UOM used to purchase goods. To ensure price is displayed consistently in the Buyer Planning work area, the price break information is displayed in the primary unit of measure. In the Price Break tab of the Item panel, the Purchasing to Primary UOM Conversion field displays the conversion from purchasing to primary UOM.

For example:

• The planned order for an item is in the primary unit of measure of Each, and the price break unit of measure defined on the purchasing agreement for this supplier-item is defined in Box of 5 (BX5).

• The planned order quantity for this purchasing recommendation is 25 Eaches, which meets the minimum threshold value of 25 Eaches (or 5 BX5) for the 10% price break, therefore the qualifying unit price is resolved to the cost of 18.18 USD for 1 Each for the recommended order of 25 Eaches.

Item Details Panel with Qualifying Unit Price, Quantity, and Adjusted Price Reflected in the Item’s Primary UOM

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 Display Price Break Information in Primary Unit of Measure in Buyer Planning 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

Users who are assigned a configured job role that contains this privilege can access this feature:

• Edit Supplies in Buyer Planning (MSC_EDIT_SUPPLIES_BUYER_PLANNING_PRIV)

This privilege was available prior to this update.

Secure Plan Data Considering Unassigned Entities

Secure plan data providing visibility to unassigned members at the lowest level of the hierarchy for the customers, suppliers, organizations, or products dimension. With this update, you can provide visibility to data that’s currently not applicable to a dimension. For example, by assigning a particular organization to a user, you can now provide visibility to measures that aren’t striped by organization, such as supplier capacity.

You can configure planning data security with an enhanced option to include unassigned members of the Product, Organization, Customer, and Supplier entities. Doing so allows you to access measures that don’t use a dimension’s hierarchy levels. For example, the Supplier Capacity Available measure includes the Product, Organization, Supplier, and Time dimensions. The measure is computed at the Item, Supplier-Supplier site, and Day levels of the Product, Supplier, and Time dimensions. Because the measure value isn’t specific to an Organization, the Organization level isn’t included in the measure’s computation. In such a scenario, you can set up a data access set to get access to specific organizations as well as measures that aren’t specific to an organization (such as Supplier Capacity Available).

The following are examples of Supply Planning measures that can now display values by configuring data security with the Organization entity that has the Include unassigned planning level member check box selected:

• Supplier Capacity Available
• Supplier Capacity Required
• Net Supplier Capacity Available
• Supplier Capacity Utilization Percentage
• Supplier Capacity Required by Supplier Capacity Constraint Date
• Additional Capacity Required by Supplier Capacity Constraint Date

Secure Plans Considering Unassigned Entities applies at the lowest level of the hierarchies for the Product, Organization, Customer, and Supplier dimensions. It is applicable to views displaying measures and planning analytics details for the Product, Organization, Customer, and Supplier dimensions in Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, Replenishment Planning, Global Order Promising, and Backlog Management.

The Administer Data Security view has been enhanced as follows:

• The data access set condition configuration has a new Include unassigned planning level member check box. You can select this check box only when the condition being created includes the Product, Organization, Customer, or Supplier entities at their lowest hierarchy level.

• You can select the Include unassigned planning level member check box along with other lowest-level members of the Product, Organization, Customer, and Supplier hierarchies.

Perform the following steps to secure plan data with unassigned members:

1. Select Product, Organization, Customer, or Supplier as an entity in a data access set.

2. Select the lowest level for Product, Organization, Customer, or Supplier.

Create a Data Access Set on the Administer Planning Security Page

3. Select the Create action to create a condition for Condition Name and select the Include unassigned planning level member check box.

Create a Condition for an Organization Entity

4. Create a condition by providing a Condition Name and selecting the Include unassigned planning level member check box. Add other level members if required to configure the data condition.

New Include Unassigned Planning Level Member Check Box

5. Save the condition and assign it to the selected entity.

Assign the Condition to the Organization Entity

Let’s walk through some examples of Supplier Capacity measure details displayed when the Include unassigned planning level member check box is selected in the Supply Planning work area.

We will see how the data access set configured in the preceding screenshot is applied to the measure values in a table. The following pivot table shows Planned Orders measure values for organization-level members M1 and M2 and Supplier Capacity measure values for the unassigned organization-level member when a data security condition is created with organization-level members M1 and M2 and the Include unassigned planning level member check box is selected.

Pivot Table Created with Organization-Level Members

Let’s see what happens when we configure a data access set with the Include unassigned planning level member check box selected and with other lowest level members. Data security applies an In condition. In the following screenshot, a data security condition was created by selecting Include unassigned planning level member, M1, and M2 for an Organization. The condition applies data security for measures where the organization value can be unassigned, M1, or M2.

The pivot table shows values for Planned Orders and Supplier Capacity Available measures when the data security condition is configured with M1, M2, and unassigned organization-level members.

Data Security Condition for Organization-Level Members and Pivot Table Details

You can enable Include unassigned planning level member across multiple entities within a data access set. When enabled within a data access set, security is applied as an "AND" condition.

When Include unassigned planning level member is selected for an Organization and Customer entity, data security is applied and displayed for the measures when both Organization and Customer combinations are unassigned in a pivot table.

The pivot table shows values for user-defined measures with unassigned-level members for organization and customer entities

Data Security Condition for Organization- and Customer-Level Members and Pivot Table Details

When you enable Include unassigned planning level member across data access sets, security is applied as a "OR" condition.

In the following example, enabling Include unassigned planning level member for Item in data access set1 and Organization entity in data access set 2, data security is applied and displayed for users for the measures when either Item or Organization have unassigned as lowest-level members in a pivot table.

The pivot table displays values for user-defined measures with unassigned level members for organization or customer entities.

Data Security Conditions for Data Sets and Pivot Table Details

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 Secure Plan Data Considering Unassigned Entities 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.

• Oracle Global Order Promising respects data security for the Organization entity only.

• Customer and Supplier data security configurations are applied for planning analytics user interfaces like pivot tables or graphs in these work areas: Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, and Replenishment Planning.

• You can’t enable Include unassigned planning level member for existing data conditions. You must create a new data condition to enable it.

• You can delete data conditions with Include unassigned planning level member using Manage Conditions only if the condition isn’t assigned to an entity across a data access set.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Administer Planning Security (MSC_ADMINISTER_PLANNING_SECURITY_PRIV)

This privilege was available prior to this update.

Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning

Use deep links to create more connected analytics and a seamless user experience between external applications and Oracle Fusion Cloud Supply Chain Planning. Deep links are a type of hyperlink used to open pages without using menus or navigating through a menu structure. With this update, you can easily navigate from an application, such as Oracle Fusion Analytics Warehouse, to specific pages in Oracle Supply Chain Planning. For example, you could create a deep link to navigate from Oracle Fusion Analytics Warehouse to the plans for an item in Oracle Supply Chain Planning.

This feature is supported for the following work areas: Supply Planning, Demand Management, Demand and Supply Planning, Replenishment Planning, and Sales and Operations Planning. With this feature, you can now navigate to the page layout and table or graph in the respective work areas. Additionally, you can navigate to the Exceptions or Supplies and Demand page.

The sample deep link URL for accessing this feature consists of three parts:

https://<host>/fscmUI/faces/deeplink?objType=<OBJECT_TYPE>&objKey=<Entity;Plan;FilterContext>

Base URL                                            Object Type Path                    Object Key Values

• Base URL: This part must include the host information with “/fscmUI/faces/deeplink?” appended after it; for example, https://<host>/fscmUI/faces/deeplink?

• Object type path: This part should have the work area name under objTypethat that you want to open. For example, if you want to open the Supply Planning work area, objType = “MSC_SP_WORKAREA” should be passed. This path is appended to the base URL and contains details about the work area to which you are creating the link.

• Object key values: 
  • Entity: Pass the table or graph or layout option that you intend to open; for example, objkey=Entity=Material Plan or objkey=Entity=Forecast Graph or objkey=Entity=Plan Summary.
  • Plan name: Pass the plan name or plan ID of the Oracle Supply Chain Planning plan that you intend to open; for example, Plan=RTSP-Supply-Plan.
  • Filter context: The filter context contains details about the hierarchies, levels, and level members of the dimension in the table, graph, or hierarchies and level members details of the dimension in the table or graph. It allows you to filter data records based on the details of the dimension you choose to filter. This information is appended to a combination of a base URL and object type path; for example, hierarchy1=Enterprise;level1=Organization,member1=M1.                       

You can pass the object key values using the following parameters:

• Parameters: Pass the parameters under the object key values; for example, hierarchy1=Product;level1=Item,member1=Laptop_1GB or hierachy1=Product;levelmember1=512342.

When using this feature to link an Oracle Analytics report from Oracle Fusion Analytics Warehouse, construct the URL using the reporting platform features that support tokens as follows:

• Token values: Pass the column name under the object key values; for example, hierarchy1=${keyValuesForColumn:Hierarchy};level1=${keyValuesForColumn:level};member1=${keyValuesForColumn:Prd_Member_Id}; or hierachy1=${keyValuesForColumn:Hierarchy;levelmember1=${keyValuesForColumn:Prd_lvl_Member_Id}.

The ObjType parameters for the work areas are as follows:

• Demand Management                 MSC_DM_WORKAREA
• Supply Planning                           MSC_SP_WORKAREA
• Demand and Supply Planning     MSC_ISD_WORKAREA
• Replenishment Planning              MSC_REPL_WORKAREA
• Sales and Operations Planning   MSC_SOP_WORKAREA

For example, the following URL takes you to the Material Plan table in the Supply Planning work area from the Oracle Fusion Analytics Warehouse application.

With token values:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=MaterialPlan;plan=${keyValuesForColumn:PLAN_ID};hierarchy1=${keyValuesForColumn:HIERARCHY_ID};levelMember1=${keyValuesForColumn:ORG_LVL_MEMBER_ID};hierarchy2=${keyValuesForColumn:HIERARCHY_ID};levelMember2=${keyValuesForColumn:PRD_LVL_MEMBER_ID};hierarchy3=${keyValuesForColumn:HIERARCHY_ID};levelMember3=${keyValuesForColumn:TIM_LVL_MEMBER_ID}

With parameters:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=Material Plan;plan=RTSP-KB-SP-PL01;hierarchy1=SP_Catalog;level1=Item;member1=KB-CSP-ALLOY;hierarchy2=APS Calendar;level2=Week;member2=1/7/30;hierarchy3=Enterprise;level3=Organization;member3=M1

Additionally, it’s possible to pass the parameters of Member Id, Hierarchy Id, and Level Id details up to 5 parameters with names like member2, level2, hierarchy2, etc. All context details are appended with the AND clause. For example, if multiple Member Id, Level Id, and Hierarchy Id details are passed, then the filter context will be represented as (Member Id1, Level Id1, Hierarchy Id1) AND (Member Id2, Level Id2, Hierarchy Id2).

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 a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning 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.

The Supplies and Demand page and the Exceptions page in their respective work areas support only the Item and Organization dimensions. However, it's important to note that this feature isn’t supported for Tiles and Tile sets within Graph sections.

If any of the parameters are missing or incorrectly passed, the following error is displayed.

Key Resources

• Watch the  Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning demo.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Demand Management Work Area (MSC_MONITOR_DEMAND_MANAGEMENT_WORK_AREA_PRIV)
• Monitor Demand and Supply Planning Work Area (MSC_MONITOR_DEMAND_AND_SUPPLY_PLANNING_WORK_AREA_PRIV)
• Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
• Monitor Sales and Operations Planning Work Area (MSC_MONITOR_SALES_AND_OPERATIONS_PLANNING_WORK_AREA_PRIV)
• Monitor Supply Planning Work Area (MSC_MONITOR_SUPPLY_PLANNING_WORK_AREA_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

Users must have access to the individual pages and tables.

Increase the Upper Limit on the Number of Items, Locations, and Time Buckets in Replenishment Planning

Configure and run a replenishment plan with a maximum of up to 50 million items, locations, and time buckets. The Run Plans Within an Upper Limit on the Number of Items, Locations, and Time Buckets feature introduced in the 22B update is now enhanced to support increased volume limits from 31 million to 50 million.

On the Create Plan Options page, you can configure replenishment plans so that the maximum combination of items, locations, and time buckets is within the 50 million limit. With this update, you can configure and run larger replenishment plans.

Create Plan 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 Increase the Upper Limit on the Number of Items, Locations, and Time Buckets in Replenishment Planning 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

• Recommended related training:
  • Introduction to Replenishment Planning Cloud (update 19D) Readiness Training
  • On Oracle Cloud Customer Connect: Replenishment Planning Training

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
• Manage Segments (MSC_MANAGE_SEGMENTS_PRIV)

These privileges were available prior to this update.

Selected Replenishment Planning Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Replenishment Planning 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.

Export Data in Format Specified in a Planning Table

In Update 24A, we introduced the Export Data in Format Specified in a Planning Table feature. This feature lets you export tables to Microsoft Excel while retaining the original table layout. With this feature, you can export tables that you weren’t previously able to open because they exceeded the 250,000 cell limitation. You can invoke this feature in the following ways:

• Use the Actions drop-down button in an open plan.
• Use the Actions menu on the Manage Plans page of the selected plan.
• Run the Export Data in Table Format scheduled process with a Plan and Table Name selected.

After this feature was introduced, we discovered that exporting tables with more than 2 million cells could cause an out-of-memory issue and, in some cases cause a server to stop functioning or operating correctly. To protect against this, we are introducing a limitation in Update 24B that will prevent the export of a table that contains more than 2 million cells. It’s possible that you successfully exported a table that exceeded this limitation in Update 24A. If so, this will no longer be possible in Update 24B and later releases.

Oracle reference: 36275383

Steps to Enable

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

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:

• Purchase Order Shipments Receipt History (ScpPurchaseOrderRcvHistoryImportTemplate)

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.