Our planning team is experiencing issues with custom item attributes not transferring from Product Hub to the Inventory Optimization module. We’ve defined several DFFs on items (lead time category, demand variability class, service level target) that are critical for planning calculations.
The scheduled process “Synchronize Item Data to Planning” completes successfully, but when we check the inventory optimization workspace, all custom attributes show as null. Standard attributes like item number, description, and UOM sync perfectly. We’ve verified DFF registration in Product Information Management, and the attribute groups are properly assigned to items.
The attribute group mapping seems to be the issue - the sync process doesn’t recognize our custom attributes even though they’re visible in the item master. Has anyone successfully mapped DFFs between these modules for planning data?
DFFs need to be registered separately in both modules to sync properly. Just having them in PIM isn’t enough - you need to recreate the same DFF structure in Supply Chain Planning Setup. The sync process only transfers attributes that exist in both source and target registration contexts.
Found the Manage Item Attributes for Planning task. I can see standard attributes in the mapping list, but our custom DFFs aren’t appearing as available options. The DFFs show as “Deployed” status in both PIM and Planning setup.
Could this be a context-sensitivity issue? Our DFFs are context-sensitive based on item class. Maybe the sync process doesn’t support context-sensitive attributes?
Context-sensitive DFFs are supported but require additional configuration. The attribute group mapping needs to specify the context value for sync. If your DFFs use item class as context, the sync process evaluates the context at runtime for each item.
However, there’s a known limitation: if the context segment name differs between PIM and Planning, the mapping breaks. Both modules must use identical context segment names (not just codes). Check your DFF definitions:
SELECT descriptive_flex_context_code, descriptive_flexfield_code
FROM fnd_descr_flex_contexts_vl
WHERE descriptive_flexfield_code IN ('EGP_SYSTEM_ITEMS', 'MSC_SYSTEM_ITEMS')
If the context codes don’t align perfectly, you’ll need to modify one of the registrations. Also ensure your scheduled process includes parameter “Include Context Sensitive Attributes” = Yes.