We’re facing an issue where key figure values in our distribution planning area remain unchanged after modifying attribute mappings in the IBP Config UI (SI-2211). I updated the planning level assignment to include a new product hierarchy level and activated the calculation view, but the key figures still show old values.
The attribute mapping was changed from Product/Location to Product/ProductGroup/Location to support aggregated planning. I verified the planning area activation completed successfully, but running the planning operator shows no effect on existing key figure data.
Has anyone encountered this before? Do I need to trigger a specific refresh process or recalculate the key figures after changing planning level assignments?
Thanks for the suggestions. I checked the calculation view and it does have the ProductGroup attribute included. Master data looks correct too - all products are assigned to groups. The strange part is that new planning runs create data at the Product level, not ProductGroup level as expected. Could this be a planning operator configuration issue?
I had this exact issue last quarter. The root cause is usually a mismatch between three components that all need to align:
1. Attribute Mapping Verification:
Your planning level assignment change is correct, but verify the attribute mapping sequence in the AML file matches your intended hierarchy:
ATTRIBUTE MAPPING:
PRODUCT -> PRODUCTGROUP -> LOCATION
LEVEL: PRODUCTGROUP (aggregation=SUM)
2. Planning Level Assignment:
In the planning area configuration, ensure all relevant key figures have their ‘Level for Planning’ property updated. This is separate from the planning level definition. Go to each key figure properties and explicitly set:
- Planning Level: Product/ProductGroup/Location
- Aggregation Method: SUM (or appropriate method)
3. Calculation View Activation:
After updating the planning level, you need to do more than just activate the calculation view. The complete process is:
- Save planning area configuration changes
- Activate the calculation view (this creates the database objects)
- Critical step: Run the ‘Initialize Planning Area’ job from the Jobs and Scheduling app. This rebuilds the key figure storage structure to match the new planning level
- Delete existing key figure data at the old planning level (optional but recommended for clean state)
- Re-run your planning operators to generate data at the new level
The initialization job is what most people miss. Without it, the key figure storage remains at the old planning level structure even though the view is activated. You can verify this by checking the planning area status - it should show ‘Initialized’ after the job completes.
4. Data Volume Management:
When changing from Product to ProductGroup level, consider the data volume impact. If you have 10,000 products in 100 groups, you’re reducing granularity by 100x. Make sure your disaggregation logic (if needed later) is properly configured in the planning operators.
5. Operator Configuration Update:
Update all planning operators that interact with these key figures:
- Input key figures: Change source planning level
- Output key figures: Change target planning level
- Aggregation/disaggregation logic: Add ProductGroup handling
After following these steps, your key figures should update correctly at the ProductGroup level. The ‘Initialize Planning Area’ job is the key piece that’s often overlooked in the documentation.
I’ve seen this behavior when the attribute values in master data don’t align with the new planning level. Check your Product to ProductGroup assignments in master data - if products aren’t properly assigned to groups, the key figures won’t aggregate correctly. The calculation view activation alone won’t fix data alignment issues. You might need to reload master data after fixing the assignments.
Check your planning operator’s input and output key figure definitions. If the operator is still configured to read/write at the Product/Location level, it won’t respect your new planning level assignment. You need to update the operator configuration to match the new Product/ProductGroup/Location structure. Also, existing key figure data at the old planning level won’t automatically convert - you may need to delete old data and regenerate.
Did you check if the attribute mapping in the calculation view matches your new planning level structure? Sometimes the view definition doesn’t automatically update when you change planning levels. Also verify that your key figure has the correct aggregation settings for the new ProductGroup level.