1. Using Demand Management
  2. Considerations for Collecting Key Customer Information

Considerations for Collecting Key Customer Information

Use the ScpKeyCustomerOptionsImportTemplate.xlsm file to identify the key customers for which nonaggregated data must be made available.

For non-key customers, the aggregation level that you define in the import template determines whether the data is retained or aggregated. You can differentiate between key customers and non-key customers and use the aggregated key customer data to build a plan specifically for your key customers.

Note: For details regarding the ScpKeyCustomerOptionsImportTemplate.xlsm file, refer to the File-Based Data Import (FBDI) for SCM guide. This guide is one of the guides in the Oracle Help Center for Oracle Fusion Cloud Supply Chain Management. Use the All Books link for a list of the guides by category, and look for the Development category.

In the ScpKeyCustomerOptionsImportTemplate.xlsm file template:

  1. Define your key customers on the KeyCusOptnHeader tab. Enter the name of a valid customer hierarchy in the Hierarchy Name column.

  2. Next, enter the level of that hierarchy in the Level Name column. All customers in this level are identified as key customers.

  3. To have only certain customers identified as key customers, enter the specific customer names on the KeyCusOptnMembers detail tab.

  4. Set the aggregation level values for both key and non-key customers. Use the settings in the template to set the data to different aggregation levels, such as 1, 2, or 3.

  5. Upload the template.

Ignore Aggregate by Zone

There are two Customer hierarchies--Customer and Customer Zone--where the lowest level of each hierarchy is Customer Site. If you don't have any key customers, leave the Hierarchy Name and Hierarchy Level columns blank on the KeyCusOptnHeader tab. All customers not named in the template (non-key customers) are aggregated into an All Other member for the hierarchy.

The upload also creates All Other Zone members for the non-key customers in the Customer Zone hierarchy. If you don't want to aggregate by zone, enter #ignore_zone in the Hierarchy Name column in the KeyCusOptnHeader.csv and leave the Level Name column blank.

Aggregation Levels

The aggregation levels are listed in the following table.

Aggregation Level

Description

1

Retain all customer sites, and aggregate non-key customer sites. In addition to key customer data being available, non-key customer data is retained for plans that require data that's not aggregated. Aggregated customer data is available for plans that require aggregated non-key customer data.

2

Aggregate non-key customer sites. Customers that aren't identified as key customers are aggregated to an All Other site by zone. However, if the Hierarchy Name and Level Name columns are blank, all customers are identified as non-key customers and aggregated to an All Other site by zone. This means that there are no key customers.

3

No aggregation of customer sites. All data is available at customer site level.

To remove the key customer designation for previously-loaded customers, use Aggregation Level 3. This enables data for all customers to be made available at the lowest level. No customers are marked as key customers.

If you select the aggregation level 3, the following happens:

  • No aggregation is done. All data is at the customer site level only.

  • If option 2 or 3 was used in previous collection runs, all non-key customer by zone members and data are deleted.

  • Plans using the Key Customer feature become invalid and you have to run them again.

The KeyCusOptnMembers detail tab is optional. Use this tab to identify specific customers as key customers. The Hierarchy Name and Level Name column entries must be the same as the information entered on the KeyCusOptnHeader tab. Enter valid level member names in the Level Member Name column. These members are the only customers that will be identified as key customers.

  • If the KeyCusOptnMembers detail tab is empty, all child members of the hierarchy level chosen in the Header tab are flagged as key customers.

  • If the KeyCusOptnMembers detail tab isn't empty, only the listed members are identified as key customers.

The members must be children of the hierarchy level named on the Header tab.

When you create a plan, there is an option in the Plan Options dialog box that determines what level of customer aggregation is used for the plan:

  • Key customer data is available and non-key customer data is aggregated to a level member named All Other.

  • No customer data is aggregated for the plan if the option is deselected.

Related Topics