1. Using Supply Chain Planning Common Features
  2. Overview of Aggregating Data for Non-Key Customers

Overview of Aggregating Data for Non-Key Customers

You can aggregate data for non-key customers in your demand, demand and supply, and sales and operations plans for Oracle Fusion Cloud Supply Chain Planning.

By doing so, you can have Customer Site-level data in your plans for only key customers who are relevant to your analysis.

You must use the file-based data import (FBDI) template named Supply Chain Planning Key Customer Options (ScpKeyCustomerOptionsImportTemplate.xlsm) to do the following:

  • Identify a level of the predefined Customer or Customer Zone hierarchy of the Customer dimension.
  • Identify level members for whom data must be maintained at the Customer Site level, which is the lowest level of the Customer dimension, in the MSC_MEASURE_DATA table.
  • Specify whether data for other level members should be aggregated by zone to placeholder sites named <zone name>:All Other or a placeholder site named Default:All Other.

Benefits of Aggregating Data for Non-Key Customers

By aggregating data for non-key customers, you get these benefits:

  • You can focus your analysis on the data for key customers in your plans.
  • You can reduce the number of customers and customer sites and amount of data in your plans.

    While some customers are key to your analysis, most others aren’t and only add to the volume of data in your plans.

More Points About Aggregating Data for Non-Key Customers

Note these points about aggregating data for non-key customers:

  • When you collect or load data at the Customer Site level, the following are created:
    • Placeholder customer sites called <zone name>:All Other or Default:All Other
    • A placeholder customer called All Other, under which the placeholder customer sites are placed
    • A placeholder customer class called All Other, under which the placeholder customer is placed

    These placeholder members are created in the predefined Customer hierarchy.

  • When you collect or load data at the Customer Site level without using the import template named Supply Chain Planning Key Customer Options, data is stored in MSC_MEASURE_DATA as follows:
    • Data is stored at the Customer Site level for all customers.
    • Data is aggregated for all customers to placeholder sites named <zone name>:All Other, where the zone refers to the underlying zone for a customer site. If a customer site doesn’t have an underlying zone, the data is aggregated to the placeholder Default:All Other site.
  • When you collect or load data at the Customer Site level while using the import template named Supply Chain Planning Key Customer Options, data is stored in MSC_MEASURE_DATA as follows:
    • If you’ve defined key customers, their data is stored at the Customer Site level.
    • Depending on the aggregation level that you’ve chosen, data is stored in one of these ways:
      • For the aggregation level of 1, the data for non-key customers is stored at the Customer Site level, and the data is also aggregated to placeholder sites named <zone name>:All Other, where the zone refers to the underlying zone for a customer site. If a customer site doesn’t have an underlying zone, the data is aggregated to the placeholder Default:All Other site.
      • For the aggregation level of 2, the data for non-key customers isn't stored at the Customer Site level, and the data is aggregated to placeholder sites named <zone name>:All Other, where the zone refers to the underlying zone for a customer site. If a customer site doesn’t have an underlying zone, the data is aggregated to the placeholder Default:All Other site.
      • For the aggregation level of 3, the data for all customers is stored at only the Customer Site level.
  • In your plan, on the Demand tab on the Plan Option page, you can use the Aggregate non-key customer data to an All Other level member checkbox to control your access to customer data in MSC_MEASURE_DATA through the plan tables and graphs.
  • You can view and use the Customer Site-level data for key customers and aggregated data for non-key customers using predefined hierarchies for the Customer dimension in your plans.

    When you're using the functionality for aggregating data for non-key customers, you can't use user-defined hierarchies for the Customer dimension.

  • You can't use the functionality for aggregating data for non-key customers in a demand plan to which you've attached a planning level profile. The Aggregate non-key customer data to an All Other level member checkbox isn’t available if you've attached a planning level profile to the demand plan.
  • When you collect or load data at an aggregated level of the Customer dimension, the functionality for aggregating data for non-key customers isn’t used.

Related Topics