1. Using Replenishment Planning
  2. Loading of Measure Data at Aggregate Levels

Loading of Measure Data at Aggregate Levels

Use the file-based data import (FBDI) templates to load measure data at aggregate levels for your module in Oracle Fusion Cloud Applications.

About the Aggregation and Disaggregation of Measure Data

When you load data for a measure at an aggregate level, you're loading data at a level that's higher than the level that the data is stored at.

When measure data is loaded at an aggregate level, it's disaggregated to the stored level during the data refresh. The data refresh occurs when you run your plan by refreshing it with current data using the Run Plan dialog box or Batch Run Plan scheduled process. The data refresh also occurs when you submit the scheduled process named Orchestrate Refresh Measures Processes.

For example, the Sales Forecast measure is stored at the Customer Site, Demand Class, Organization, Item, Sales Rep, and Day levels. If you load the measure at the Customer (parent level for Customer Site), Demand Class, Organization, Category Level 1 (parent level for Item), Sales Rep, and Day levels, when you run your plan while refreshing it with current data, the data will be disaggregated from the Customer level to the Customer Site level and from the Category Level 1 level to the Item level based on the demand history. The data is disaggregated for only those customer sites and items for which demand history was loaded at the stored levels, or the data for another measure with the same stored levels as the Sales Forecast measure was loaded at the stored levels.

More Points About Loading Measure Data at Aggregate Levels

Note these points about loading measure data at aggregate levels:

  • Before loading measure data at an aggregate level, you must first load historical demand data because it's used as the basis for disaggregating measure data loaded or generated at an aggregate level.

    Historical demand data must be loaded at the levels that it's stored at: Item, Organization, Customer Site, Demand Class, Sales Rep, and Day. The Demand Class is required for demand, demand and supply, and sales and operations plans and is optional for replenishment plans. The Sales Rep level is required for only sales and operations plans.

  • You must use the import templates to load measures for historical demand data as follows:
    • Supply Chain Planning Bookings History (ScpBookingHistoryImportTemplate.xlsm)
      • Bookings History: Booked Item by Booked Date
      • Bookings History: Booked Item by Promised Date
      • Bookings History: Booked Item by Requested Date
      • Bookings History: Booked Item by Scheduled Ship Date
      • Bookings History: Requested Item by Booked Date
      • Bookings History Value: Booked Item by Booked Date
      • Bookings History Value: Booked Item by Promised Date
      • Bookings History Value: Booked Item by Requested Date
      • Bookings History Value: Booked Item by Scheduled Ship Date
      • Bookings History Value: Requested Item by Booked Date
    • Supply Chain Planning Option Bookings History (ScpOptionBookingHistoryImportTemplate.xlsm)
      • Option Bookings History
    • Supply Chain Planning Option Shipments History (ScpOptionShipmentHistoryImportTemplate.xlsm)
      • Option Shipments History
    • Supply Chain Planning Shipments History (ScpShipmentHistoryImportTemplate.xlsm)
      • Shipments History: Requested Item by Shipped Date
      • Shipments History: Shipped Item by Promised Date
      • Shipments History: Shipped Item by Requested Date
      • Shipments History: Shipped Item by Scheduled Ship Date
      • Shipments History: Shipped Item by Shipped Date
      • Shipments History Value: Requested Item by Shipped Date
      • Shipments History Value: Shipped Item by Promised Date
      • Shipments History Value: Shipped Item by Requested Date
      • Shipments History Value: Shipped Item by Scheduled Ship Date
      • Shipments History Value: Shipped Item by Shipped Date
  • You can load forecast data at the level that it's stored at or an aggregate level using the import template named Supply Chain Planning Forecast Measures (ScpForecastMeasureImportTemplate.xlsm) for these measures:
    • Imported Forecast
    • Marketing Forecast
    • Marketing Forecast Value
    • Sales Forecast
    • Sales Forecast Value
  • You can use the import template named Supply Chain Planning Measures (ScpMeasuresImportTemplate.xlsm) to load any measure for which a specific import template isn't available.
  • Before you load data at an aggregate level for a measure, you must already have loaded another measure with the same dimensions and stored levels as the first measure. Otherwise, the underlying combinations for the dimension levels won't exist, and the aggregate data can't be disaggregated. The underlying dimensions and levels for both measures need to be the same.

    For example, assume that you've a measure called MyForecast that has the Product, Organization, and Time dimensions and is stored at the Item, Organization, and Day levels. Before you can load MyForecast at an aggregate level such as Category Level 1, Business Unit, and Month, you should have loaded another measure with the same dimensions at the Item, Organization, and Day levels. Otherwise, the underlying item-organization-day combinations won't exist, and aggregate data for MyForecast won't be disaggregated. If the second measure included the Customer dimension, the disaggregation of data for MyForecast won't happen.

  • Don't load the same measure at different levels of aggregation. For example, don’t load a measure at both the Category Level 1 and Category Level 2 levels.
  • When loading measure data at an aggregate level, you must specify the name of the hierarchy and level that you’re using in the import templates. Also, ensure that the hierarchy is included in the dimension catalog selected for your plan.

    For a demand plan that's using a hybrid time hierarchy, you can import data to any aggregate level for the hybrid time hierarchy that you selected as the planning calendar or a corresponding hybrid time hierarchy. If you're not importing data at the time level of the measure, enter the name of the hybrid time hierarchy in the Time Hierarchy Name column of the import template.

  • For your demand, demand and supply, sales and operations, or supply plan, for plan-specific measures that include the Customer dimension, you can load the aggregate data without specifying a customer level by entering the #ignore parameter in the Customer Level Name column of the import templates. In this case, you must not enter any value in the Customer Level Member Name and Customer Site Level Member Name columns. Effectively, you’re aggregating the data by the customer level, and the aggregate data is disaggregated to the existing customer sites based on the disaggregation parameters of the measures.

    If you don’t want to specify the customer level name, then you must use the #ignore parameter while loading data at the stored level and also at the aggregate level.

    Note: For a replenishment plan, for plan-specific measures that include the Customer dimension, you must enter the #ignore parameter in the Customer Level Name column of your import template to ignore the Customer dimension in the imported measure data because this dimension isn’t supported for replenishment plans. Otherwise, the load process will fail. You must enter this parameter while loading data at the stored and aggregate levels.
  • For your demand, demand and supply, sales and operations, or supply plan, for measures that include the Demand Class dimension, you can load the aggregate data without specifying a demand class level by entering the #ignore parameter in the Demand Class Level Name column of the import templates. In this case, you must not enter any value in the Demand Class Level Member Name column. Effectively, you’re aggregating the data by the demand class level, and the aggregate data is disaggregated to the existing demand classes based on the disaggregation parameters of the measures.

    If you don’t want to specify the demand class, then you must use the #ignore parameter while loading data at the stored level and also at the aggregate level.

    Note: For a replenishment plan, for plan-specific measures that include the Demand Class dimension, you must enter the #ignore parameter in the Demand Class Level Name column of your import template to ignore the Demand Class dimension in the imported measure data because this dimension isn’t supported for replenishment plans. Otherwise, the load process will fail. You must enter this parameter while loading data at the stored and aggregate levels.
  • After you load data for a measure, during the subsequent plan run, data can either be aggregated or disaggregated based on the planning time level of the plan. However, both aggregation and disaggregation of measure data can’t happen at the same time. This limitation usually crops up when the measure includes the Time dimension, and the planning time level is higher than a day. Don’t load measure data that needs to be disaggregated on one dimension and aggregated on another dimension.

    Consider an example in which you’ve a measure that’s defined at the levels of Item, Organization, Customer Site, Demand Class, and Day. The following table explains what happens when you load the measure for a day-level plan and a month-level plan:

    Load Level Planning Time Level Scenario Supported? Comment
    Item, Organization, Customer Site, Demand Class, Day Day Yes The load is at the stored level.

    During the plan run, no aggregation or disaggregation of the data is done.

    Item, Organization, Customer Site, Demand Class, Month Day Yes The load is at the aggregate level. Data is aggregated by the Time dimension.

    During the plan run, the data is disaggregated from month to day.

    Item, Organization, Customer Class, Demand Class, Day Day Yes The load is at the aggregate level. Data is aggregated by the Customer dimension.

    During the plan run, the data is disaggregated from customer class to customer site.
    Item, Organization, Customer Class, Demand Class, Month Day Yes The load is at the aggregate level. Data is aggregated by the Customer and Time dimensions.

    During the plan run, the data is disaggregated from month to day and then from customer class to customer site.
    Item, Organization, Customer Site, Demand Class, Day Month Yes The load is at the stored level.

    During the plan run, the data is aggregated from day to month.
    Item, Organization, Customer Site, Demand Class, Month Month Yes The load is at the aggregate level. Data is aggregated by the Time dimension.

    During the plan run, no aggregation or disaggregation of the data is done.
    Category Level 2, Business Unit, Customer Site, Demand Class, Month Month Yes The load is at the aggregate level. Data is aggregated by the Product, Organization, and Time dimensions.

    During the plan run, data is disaggregated from category to item and from business unit to organization.
    Category Level 2, Organization, Customer Site, Demand Class, Day Month No The load is at the aggregate level. Data is aggregated by the Product dimension.

    During the plan run, the data must be aggregated from day to month and then disaggregated from category to item.

    This scenario isn’t supported. In this case, the records are collected but won’t show up in the plan.

Related Topics