We’re importing historical demand data into the Demand Planning module but the import tool keeps failing with “Missing product hierarchy” errors. Our demand history file contains 24 months of data for about 2,500 products. The error messages indicate that products in the demand file don’t have complete hierarchy assignments. We assumed that as long as product IDs existed in the product master, the import would work. Is there a specific hierarchy structure required before demand data can be loaded? Our product master is already in CloudSuite, but maybe we’re missing some configuration step. The validation happens before any data actually loads into the staging table.
I’ll walk you through resolving all three aspects of this issue systematically.
Product Master Must Be Loaded First: This is the foundational requirement. The Demand Planning import tool performs referential integrity checks against the Product Master before accepting any demand history records. Here’s what you need to verify:
- All product IDs in your demand history file exist in Product Master with status = ‘Active’ or ‘Inactive’ (not ‘Pending’ or ‘Deleted’)
- Products have basic attributes populated: description, unit of measure, product type
- Products are assigned to the correct planning organization/site combinations
Run this validation query before importing:
- Compare your demand file product list against Product Master
- Identify any products in demand data that don’t exist in master
- Either add missing products to master first, or exclude them from demand import
Hierarchy Mapping Required for All Products: This is your main blocker. CloudSuite Demand Planning uses hierarchies for forecast aggregation and disaggregation. Every product must have complete hierarchy assignments across all defined hierarchy levels. The standard planning hierarchy typically includes:
- Level 1: Category (e.g., Electronics, Apparel)
- Level 2: Family (e.g., Laptops, Smartphones)
- Level 3: Class (e.g., Business Laptops, Gaming Laptops)
- Level 4: Product (individual SKU)
To fix your missing mappings:
-
Navigate to Product Master > Hierarchy Management
-
Select your Planning Hierarchy definition
-
Run the Hierarchy Completeness Report to identify gaps
-
For each product missing assignments:
- Open product record
- Go to Planning tab
- Assign values for Category, Family, and Class
- Verify parent-child relationships are correct
- Save and validate
-
For bulk updates (recommended for 2,500 products):
- Export product list with current hierarchy assignments
- Create mapping spreadsheet with correct values
- Use Data Import Utility > Product Hierarchy Update template
- Import hierarchy assignments in batch
- Validate all records loaded successfully
Import Tool Validates Hierarchy Before Loading: The validation happens in the pre-staging phase, which is why you’re not even getting to the staging table. The import process has three validation gates:
Gate 1 - File Structure: Checks column headers, data types, required fields
Gate 2 - Referential Integrity: Validates products exist and have complete hierarchies (you’re failing here)
Gate 3 - Business Rules: Checks date ranges, demand values, planning parameters
To pass Gate 2, ensure:
- Every product in your demand file has non-null values for all hierarchy levels
- Hierarchy values exist in the Hierarchy Master tables
- Parent-child relationships form valid chains from Category down to Product
- Hierarchy assignments are effective for the date range of your demand history (your 24-month period)
Best practice for your situation:
Day 1: Run hierarchy completeness report, identify all gaps (expect 300-500 products with issues based on typical patterns)
Day 2: Create bulk hierarchy update file, categorize products into logical families/classes
Day 3: Load hierarchy assignments via Data Import Utility, validate all records
Day 4: Re-run demand history import, monitor for any remaining validation errors
One more critical point: if your product hierarchy structure has changed during the 24-month historical period, you need to decide whether to use current hierarchy assignments for all historical data or maintain historical assignments. Most implementations use current hierarchy for simplicity, but if your planning process requires historical accuracy, you’ll need to handle hierarchy versioning.
After fixing hierarchies, your demand import should process cleanly. The staging table will then perform additional validations on demand values, dates, and planning parameters, but those are typically easier to resolve than hierarchy issues.
Go to Product Master > Data Quality Reports > Hierarchy Completeness. This will show you all products with incomplete hierarchy assignments. You can export the results and use it as your remediation checklist. In our implementation, we found that about 15% of products had missing hierarchy values, usually because they were set up before the planning hierarchy was fully defined.
That makes sense. How do I verify which products are missing hierarchy assignments? Is there a report or query I can run to identify the gaps before attempting another import?