Master data strategy vs attribute-based modeling for supplier collaboration in si-2211

SCM SAP IBP
, , , , , , , ,
1

We’re evaluating two different approaches for modeling supplier collaboration data in IBP and would appreciate the community’s experience on the trade-offs.

Approach 1: Centralized Master Data Maintain supplier information as traditional master data entities with hierarchies (Supplier → Supplier Site → Supplier Product). All supplier attributes (lead time, reliability score, capacity) are stored as master data attributes. Planning runs reference these master data records directly.

Approach 2: Attribute-Based Modeling Store minimal supplier master data (just ID and name) and model everything else as planning area attributes and key figures. Supplier lead time becomes a key figure, reliability score is a calculated key figure, capacity is a time-series key figure that can vary by period.

We have about 450 suppliers across multiple tiers. The main factors we’re considering:

  • Data consistency during supplier onboarding
  • Flexibility to model supplier attributes that change over time
  • Integration complexity with source systems
  • Performance impact on planning runs
  • Governance and data quality management

What has worked better in real implementations? Are there specific scenarios where one approach clearly outperforms the other?

2

Having implemented both approaches across multiple projects, here’s my analysis of the strategic trade-offs:

Centralized Master Data Approach - Best Fit Scenarios:

This works well when:

  1. Supplier attributes are relatively stable (change quarterly or less frequently)
  2. You have strong master data governance already established
  3. Integration with ERP/source systems is primarily master data replication
  4. Supplier onboarding process is formal with data quality checks before planning usage
  5. Your planning scenarios don’t require “what-if” analysis on supplier attributes

The key advantage is data consistency. When procurement negotiates a new lead time with a supplier, that change propagates automatically to all planning processes. There’s no risk of planning with outdated supplier data.

However, the limitations become apparent with:

  • Seasonal capacity variations (you mentioned 450 suppliers - if even 20% have seasonal patterns, that’s 90 suppliers with multiple capacity profiles)
  • Scenario planning (comparing current suppliers vs. alternative suppliers requires duplicate master data records)
  • Historical analysis (tracking how supplier reliability evolved over time requires versioning)

Attribute-Based Modeling - Best Fit Scenarios:

This approach excels when:

  1. Supplier attributes are planning variables (capacity changes monthly, lead times vary by season)
  2. You need scenario planning flexibility (evaluate switching suppliers without changing master data)
  3. Historical trending is important (track supplier performance degradation over 24 months)
  4. Integration can support time-series data feeds (not just current-state snapshots)
  5. Your planning team has strong data modeling skills

The flexibility is powerful for supplier collaboration because real-world supplier relationships are dynamic. A supplier’s capacity isn’t a fixed number - it varies based on their other customer commitments, production schedules, and resource availability.

The governance challenge is real but manageable. You need:

  • Clear data ownership (who updates supplier capacity forecasts?)
  • Validation rules on key figures (capacity can’t be negative, lead time has min/max bounds)
  • Change tracking and audit logs (built into IBP key figure history)
  • Documentation of which key figures represent supplier attributes

Hybrid Recommendation for Your Scenario:

Given 450 suppliers and supplier collaboration focus, I recommend:

Master Data: Supplier identification and classification

  • Supplier ID, Name, Address (standard master data)
  • Supplier Tier (1/2/3) - for hierarchy and reporting
  • Supplier Type (Strategic/Preferred/Approved/Conditional) - for sourcing rules
  • Geographic Region - for risk analysis
  • Primary Contact - for collaboration workflows

Planning Area Attributes & Key Figures: Dynamic supplier characteristics

  • SUPPLIER_LEAD_TIME (key figure, days) - can vary by time period
  • SUPPLIER_CAPACITY (key figure, units) - time-series with monthly/quarterly buckets
  • SUPPLIER_RELIABILITY_SCORE (calculated key figure, 0-100) - based on delivery performance
  • SUPPLIER_COST (key figure, currency) - can vary based on volume commitments
  • SUPPLIER_COMMITMENT (key figure, units) - what supplier committed to provide

This hybrid model gives you:

  • Clean supplier onboarding (master data replication from ERP)
  • Flexible planning (capacity and lead times as time-variant key figures)
  • Scenario analysis capability (change key figure values without touching master data)
  • Strong governance (master data team owns supplier entities, planning team owns planning attributes)

Integration Strategy: For supplier onboarding:

  1. ERP creates supplier master data → replicates to IBP master data (standard integration)
  2. Planning team initializes key figures for new supplier (one-time setup with default values)
  3. Ongoing updates: Master data changes → replicate automatically; Planning attributes → planning team or supplier portal updates

Data Consistency Approach: Implement validation rules that cross-check master data and key figures:

  • Alert if SUPPLIER_CAPACITY > 0 for a supplier not marked Active in master data
  • Alert if SUPPLIER_LEAD_TIME changes >50% period-over-period (potential data error)
  • Consistency report showing suppliers with master data but no planning key figures

The key insight is that supplier collaboration requires both stable identity (master data) and dynamic planning attributes (key figures). Neither pure approach handles both requirements elegantly. The hybrid model aligns with how your organization actually thinks about suppliers - they have fixed characteristics (who they are) and variable characteristics (what they can provide when).

3

From a data governance perspective, Approach 1 is cleaner. You have single source of truth for supplier data, clear audit trails for changes, and standard integration patterns from ERP systems. Attribute-based modeling spreads supplier data across planning areas and key figures, making it harder to answer questions like “What’s the current reliability score for Supplier X?” You’d need to query key figures with time filters rather than just looking up a master data record. For 450 suppliers, the governance complexity of Approach 2 seems risky.

4

Integration complexity is a real differentiator. Most ERP systems (SAP, Oracle, etc.) send supplier data as master data records, not as time-series planning data. If you choose Approach 2, you need transformation logic in your integration layer to convert master data updates into key figure loads with proper time bucketing. This adds complexity and potential for errors. With Approach 1, integration is straightforward - master data replication from source to IBP. For supplier onboarding, Approach 1 is definitely simpler. New supplier in ERP → automatic replication to IBP → immediately available for planning.

5

I disagree that Approach 2 is necessarily worse for governance. It depends on your planning requirements. If supplier attributes genuinely change over time (and they do in most industries - lead times fluctuate, capacity changes quarterly), then forcing them into static master data creates version management complexity. You end up maintaining historical versions of master data or using effective dating, which has its own challenges. Attribute-based modeling makes time-variance native. The question is whether your source systems can provide time-series supplier data or just current-state snapshots.

6

We use a hybrid approach that might be relevant. Core supplier identification (ID, name, address, contact) is master data. Planning-relevant attributes (lead time, capacity, cost) are modeled as key figures in the planning area. This gives us the best of both worlds - stable master data for integration and reporting, flexible time-series data for planning. The key is defining the boundary clearly: if an attribute is used for supplier identification or grouping, it’s master data. If it’s used in planning calculations, it’s a key figure.

7

We implemented Approach 1 (centralized master data) for a manufacturing client with 600+ suppliers. The main advantage was clear ownership - master data team manages supplier attributes, planning team focuses on planning logic. However, we hit limitations when suppliers had seasonal capacity variations. Master data attributes are static, so we ended up creating multiple supplier-site combinations to represent different capacity periods, which became a maintenance nightmare. If your supplier attributes are truly static, Approach 1 works well. If they vary by time or scenario, you’ll struggle.