cancel
Showing results for 
Search instead for 
Did you mean: 

Managing Dynamic Location Assignments in SAP IBP (same part different locations)

0 Kudos
124

Hey Guys! long time listener, first time caller. lol 

I’m seeking advice on handling a unique challenge with SAP IBP regarding dynamic location assignments for components within a BOM structure.

Problem Overview:

We are using Salesforce to send over product ID and location ID combinations at the BOM level. The process is as follows:

  1. Salesforce sends the BOM (e.g., BOM 1234) with associated components, including specific location IDs where each component should be sourced (e.g., Part XYZ from Location ID 10).
  2. Simultaneously, another BOM (e.g., BOM 4567) with the same component (Part XYZ) may require sourcing from a different location (e.g., Location ID 150).
  3. The data is then sent to IBP for Demand Planning, where the BOM structure is broken down to the component level using a custom bom explosion, and the demand is passed to IBP Supply Planning at the product + location level to generate net requirements based on each specific location.

Challenge:

Since SAP IBP master data typically restricts each product ID to a single location ID, I'm facing a constraint: I need to accurately capture and plan for shared components sourced from multiple locations without merging or aggregating the demand across locations. In other words, I need to distinguish between the same component in different BOMs based on location ID dynamically without duplicating master data.

Question:

What are the best approaches for managing dynamic location IDs for shared components across BOMs in SAP IBP? Are there any recommended solutions, such as using Attribute as a Key Figure (AAKF), custom planning levels, or another method that could solve this issue? 

Thanks in advance! 

#SAPIBP#DemandPlanning#SupplyPlanning#MasterData#AttributeAsKeyFigure#BOMPlanning#SalesforceIntegration#DynamicAttributes#PlanningOptimization#LocationManagement

 

Accepted Solutions (0)

Answers (0)