SD Item Categories Part 5: Architecting a Scalable Item Category Strategy for Global Templates

📌 KEY POINTS
✅ A template needs a canonical catalogue of item categories with fixed meaning (stock, third-party, IPO, MTO, service, free-of-charge, BOM, returns, credit/debit).
✅ Item category groups are master data rules: derive them from material type, sourcing and business model, and validate at material creation.
✅ The VOV4 matrix is a controlled template artifact — every change affects all countries using the document types.
✅ A new item category is justified by different control (billing relevance, schedule lines, pricing, procedures) — not by reporting or naming.
⚠️ Item categories carry dependencies: schedule line determination, copy control at item level, billing, account determination and output — each new category multiplies test effort.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 covered controls, determination, special processes and structures. This part is the template view.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CANONICAL CATALOGUE

• One item category per behavior pattern, same key in every country.
• Document which process each category supports and which item category group leads to it.
• Local needs handled via conditions, output or customer data where possible.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ITEM CATEGORY GROUP GOVERNANCE

• Rules: material type + sourcing (stock, vendor direct, individual procurement) + service → group.
• Validation in material creation (MDG or creation checklist).
• Sales-org-specific groups (MVKE) only where business models differ by market.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DETERMINATION MATRIX

• VOV4 matrix: document types × item category groups × usages × higher-level categories.
• Maintained centrally; changes via design authority.
• Automated comparison between template and country systems/clients.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DEPENDENCIES

• Schedule line category determination (item category + MRP type).
• Copy control item level (VTAA, VTLA, VTFL).
• Billing relevance and account determination, output and incompletion.
• Every dependency part of the regression test suite.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION

• Analyse legacy Z item categories by usage and control settings.
• Map to canonical categories; retire duplicates.
• Correct item category groups on materials before migration of open orders.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Build the canonical catalogue with purpose and control summary.
2. Define item category group derivation rules and validations.
3. Publish the VOV4 matrix as a controlled document.
4. Link each category to its dependency list and tests.
5. Review usage yearly and retire unused categories.

✅ CHECKPOINT: a new material type or process can be mapped to an existing item category without new configuration in most cases.

On an eight-market template, each wave added local item categories: a German "tender" item, a French "promo" item and a US "sample" item — all behaving like TANN or TAN with small field differences. Copy control and billing tests multiplied, and a VOV4 change for one country broke item determination in another. The architect consolidated to a canonical catalogue of 14 categories, moved tender and promo variants to condition types and order reasons, and made the VOV4 matrix a controlled artifact reviewed by the design authority. New markets in later waves needed no new item categories.

• Creating country-specific item categories for pricing or reporting variants.
• No rule for item category group derivation, leading to inconsistent material setup.
• Changing VOV4 for one country without checking the shared template.
• Adding categories without the dependency chain (copy control, schedule lines, billing).
• Migrating all legacy item categories 1:1.

• Keep a canonical item category catalogue with documented purpose.
• Govern item category groups through material master rules.
• Treat VOV4 as a controlled template artifact.
• Require a control-difference justification for new categories.
• Rationalize item categories during migrations.

Questions: "How would you design item categories for a global template?", "When is a new item category justified?", "How do you govern item category groups?"
Strong answer: canonical catalogue with fixed meanings, item category group derivation rules validated in material creation, VOV4 matrix as controlled artifact, new categories only for control differences, dependency management (schedule lines, copy control, billing, account determination) and regression tests; rationalization during migration.