Orchestrate Load Measures Processes

Use the Orchestrate Load Measures Processes scheduled process to copy measure data between plans or within a plan.

When to Use

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

  • Copying calculated measures into stored versions within the same plan or across plans for comparative analysis and improve table or graph performance. You can reduce the time taken to display analytics for a stored version of a measure as compared to its calculated version.
  • Copying reference measure data across plans as part of integrated planning process. For example, financial measure data from a monthly demand or sales and operations plan into a weekly (hybrid) demand plan. Or,
  • Copying an operations forecast generated with causal data at a weekly detail level in a hybrid demand plan to a strategic demand or sales and operations plan.
  • As part of an approvals process to snapshot a copy of a calculated demand forecast to an approved version.

Typically, this job is submitted as part of an integrated job set. For example, run a source plan, then run a target plan and copy measure data across plans when the latter run is completed. Or, run a single plan and copy measure data within the same plan when the run is completed.

Privileges Required

  • Load Measure Data from Other Plans (MSC_LOAD_MEASURES_FROM_OTHER_PLANS_PRIV)
  • 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 weekly or monthly. When updating stored versions of calculated measures, this process can be 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 sizes, the copy time range, and the number of measure mappings in a measure copy set. Expect the process to run for minutes, or for hours. 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 target plan to avoid database deadlock.

Parameters

Parameter Optional or Required Description Parameter Value Special Combinations Required Notes
From Plan Required Select a source plan name. Valid plan name. N/A Plans that haven’t run or with error status are excluded.
To Plan Required Select a target plan name. Valid plan name. N/A Plans that haven’t run or with error status are excluded.
Measure Copy Set Required Select a measure copy set that contains one or more measure mappings from a source measure to a target measure. N/A Define measure copy sets using the Load Measures from Other Plans task in the Demand Management and Sales and Operations Planning work areas.
Create new combinations Optional Select this check box to insert dimension level combinations from the source plan into the target plan if they don't already exist. If you don't select this check box, source plan combinations aren't created in the target plan if they don't already exist there, and measure data isn't copied for these combinations.

Check box selected

Check box deselected

N/A
Copy Time Level Optional Time level in the target plan at which measure data is copied from the source plan. N/A N/A Copy Time Level is set by the system and not selectable.
Time Level Range Start Optional Starting bucket of a time range in the target plan at the copy time level. Nonzero integer N/A Use negative values for historical time periods.
Time Level Range End Optional Ending bucket of a time range in the target plan at the copy time level. Nonzero integer N/A Use negative values for historical time periods.

Troubleshooting Information

  • You can view the status of the Orchestrate Load 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 Load Measures from Other Plans child process for details, including warning and error messages.
  • Time Level Range Start and End parameters are optional but should be used to increase performance.
  • Consider setting the USE_SCALED_QUERIES_PARALLEL profile option to increase process performance. This profile option should be set at the user level for the name of the administrator submitting the job rather than site level because this option can reduce performance of other plan processes. Specify a number between 4 and 8 for the profile option value. Increasing the number should improve process performance at the cost of consuming more system resources.
  • Check plan status in Manage Plans if either the source plan or target plan doesn’t appear.
  • If the reason for errors isn’t clear from the log or you need help with process performance, contact product support.