Data Structure for Customers, Locations and Products

In general, forecast value comes with a customer number, location number, and product number. A customer number represents a specific Customer entity, and a product number or SKU represents a specific Product type. In practical situations, forecast, and also many cost- or revenue-related numbers are summarized by groups. For example, you can represent market segments in the data as Customer groups, regions as Location groups, product families as Product groups.

The image below shows an example product hierarchy.

../_images/product-hierarchy.png

Take Product grouping as an example. The image below shows part of the Product Relation sheet in the input data, which defines the product structure. (This sheet is not a complete representation of the items named in the hierarchy diagram.)

../_images/product-grouping.png

Note that the Product column contains only group names while the SubProduct column can contain either group names or individual items.

Items in the SubProduct column are group names or individual items nested under the group item in the Product column.

The top part of the sheet is the information defining the actual product hierarchy. In the example sheet, “Cake” appears in both the Product and SubProduct columns. “Cake” is defined as a subset (subproduct) of “All Items” while “Fruit Filling Cake” is a subset of “Cake.”

The products that start with “Level” in their name is used as Reporting Level in Product Definition sheet:

../_images/product-reportinglevel.png

In every phase, you can choose any level to view the data. To help you get started, the suggested levels of product groupings shown in each phase are shown in the table below.

PHASE GROUPING LEVEL
Demand Plan Individual items
Demand Review Product Type
Supply Review Product Family
Management Review All Items