Orchestrate Refresh Measures Processes

Use the Orchestrate Refresh Measures Processes scheduled process to refresh data for collected measures in a plan without actually running the plan.

When to Use

These use cases are applicable to the Orchestrate Refresh Measures Processes process:

• Refreshing a subset of collected measures in your supply chain plans, including shipments and bookings history, sales and marketing forecasts, and financial measures such as such as Budget Value and Financial Forecast Value. This process retains measure data for statistical and simulation demand forecasts that are normally purged when running your plan to refresh with current data.
• As part of a weekly demand planning cycle where you generate a baseline, statistical forecast once a week but need to get daily updates for recent shipments (or bookings) and the latest sales forecast.
• The scheduled process considers measures loaded using file-based data import (FBDI) templates for Oracle Fusion Cloud Supply Chain Planning:
  • Supply Chain Planning Measures
  • Supply Chain Planning Shipments History
  • Supply Chain Planning Bookings History
  • Supply Chain Planning Option Shipments History
  • Supply Chain Planning Option Bookings History

Typically, this job is submitted as part of an integrated job set. For example, collect measure data from files, refresh plan measures, then generate measure-based exceptions in the plan.

Privileges Required

• Run Plan with Snapshot (MSC_RUN_PLAN_WITH_SNAPSHOT_PRIV)

Specifications

Review these specifications before setting up this scheduled process:

Specification	Description
Job Type	Scheduled as part of an integrated job set is recommended, but it can be submitted on a spontaneous basis if required.
Frequency	Frequency depends on the business requirement but typically daily.
Time of Day	After work hours is recommended, but it can be submitted any time based on your requirements. It’s recommended not to use the target plan while this process runs.
Duration	Duration depends on plan size, the number of measures in the measure catalog, and the level at which measure data is collected. For example, if measure data is collected at aggregate levels, then the process could take longer to disaggregate data to lower levels. Expect the process to run for minutes. See the Troubleshooting section for tips on increasing performance.
Compatibility	There should be only one instance of the job running at any time on the plan.

Parameters

Parameter	Optional or Required	Description	Parameter Value	Special Combinations Required	Notes
Plan	Required	Select a plan name.	Valid plan name.	N/A	Plans that haven’t run or with error status are excluded.
Measure Catalog	Optional	Select a measure catalog that contains a subset of collected plan measures.	Valid measure catalog.	N/A	Don’t use a plan’s measure catalog.
Refresh Measure Data Incrementally	Required	Refresh measure data in a plan for either existing members only, or for existing, new, and removed members.	For existing members only For existing, new, or removed members	N/A	Prior to update 24D, measure data was refreshed in a plan for existing members only.

Troubleshooting Information

• You can view the status of the Orchestrate Refresh Measures Processes job in the Scheduled Processes work area.
• When the program is submitted, you can Cancel Process as provided by the Scheduled Processes work area.
• See the log file attached to the Refresh Collected Plan Measures child process for details, including warning and error messages.
• Check plan status in Manage Plans if the plan to refresh doesn’t appear.
• The Measure Catalog parameter is optional, but should reference a catalog with a subset of plan measures. Don’t use the plan’s measure catalog because it contains many measures that aren’t applicable to this process and will decrease process performance.
• Include both the Shipments History (or Bookings History) measure and the default measure used to refresh Shipments History in your measure catalog such as:
  • Shipments History + Shipments History: Requested Item by Shipped Date
  • Bookings History + Bookings History: Booked Item by Booked Date
• Configure the enableParallelDisaggMeasure parameter in either the SCP_PARAMETER_OVERRIDES profile option or in plan options to increase disaggregation performance for this process.
• Use REST services, not the Orchestrate Refresh Measures Processes job, to update editable measures.
• If you select For existing, new, or removed members, the scheduled process performs a full refresh of the plan's master data with the following updates:
  • New members are added to the plan.
  • Existing members that previously weren’t within the plan scope but now are because of hierarchy changes are added to the plan.
  • Any existing members that have been deleted are removed from the plan.
  • Any existing members that previously were within the plan scope but now aren’t because of hierarchy changes are removed from the plan.
  • For members added to the plan, measure data that’s been collected since the last plan run (with the Refresh with current data option selected on the Parameters tab in the Run Plan dialog box) or the last run of the Orchestrate Refresh Measures Processes process will be added to the plan.
  • For members removed from the plan, all measure data is removed from the plan.
• You need to run the plan with data refresh to update the price list data.
• When introducing a new loaded measure to a plan, you must first run the plan to refresh with current data before you can refresh that measure's data using this scheduled process.
• Plans created by referring to and copying a base plan can't be refreshed.
• If the reason for errors isn’t clear from the log or you need help with process performance, contact product support.