Material Status Configuration, Key Fields and Output Format in SAP MM

Main ideas / lessons

1) Material Status Configuration (SAP MM Material Master)

• Purpose: Material master status configuration controls how a material is treated in different applications and business processes.
• Business goal example: If a material becomes obsolete, the company may want to:
  • Block procurement (prevent purchase orders / external procurement)
  • Block inventory management (prevent inventory-related activities)

Mechanism

• The MM consultant configures material statuses.
• During transactions, the system uses these statuses to produce:
  • No message
  • Warning message
  • Error message

Per-application behavior

• Each status can be configured separately for many process areas (purchasing, BOM, inventory, etc.).
• When a process is configured as error (B), the system blocks the action.

---

Configuration and assignment concept

• Material statuses are configured in SPRO → SAP Reference IMG → Logistics → General → Material Master → [settings] for key fields.
• The configured status becomes a key field available in the material master for selection (typically via drop-downs).

---

Levels where material status can be maintained

• Cross-plant / client level

  • Appears on MM03 → Basic Data 1
  • Called cross-plant material status
  • Applies to all plants in the client.

• Plant level

  • Appears on MM03 → Purchasing tab for a specific plant
  • Called material status
  • Applies only to the selected plant.

Underlying tables (as explained in the video)

• Client-level field (cross-plant) is linked to table M
• Plant-level field is linked to table MRC

---

What the “message types” mean (core logic)

For each application/process section in the material status configuration, the status controls a message flag:

• Blank = no message
• A = warning
• B = error

If a process is configured as B (error) for that status, users cannot proceed with that business activity.

---

2) Detailed methodology / step-by-step examples shown (material status)

A. Example: “Blocked for procurement” status

• In configuration, purchasing behavior is set so that:
  • Purchasing message = B (error) for that status
• Effect demonstrated:
  • If the material status is set in Basic Data 1 (cross-plant) → purchase order creation is blocked for all plants
  • If the status is set in Plant-level Purchasing tab → purchase order creation is blocked only for that plant; other plants can still create POs.

B. Example: “Blocked for inventory management” status

• Another status is configured similarly, but for inventory management application checks.
• Effect:
  • If set in cross-plant field → inventory actions are blocked across all plants
  • If set in plant-level field → inventory actions are blocked only for that plant.

C. Combined blocking (procurement + inventory)

• The video shows creating/using a status (example: material status 09) with descriptions like:
  • “blocked for procurement or inventory management”
• In configuration:
  • Purchasing = error (B)
  • Inventory = error (B)
• Result:
  • The material is blocked for both procurement and inventory activities, depending on whether the status is entered cross-plant or plant-specific.

---

3) Key Fields Concept (Material Master)

• Definition: Key fields are material master fields configured by the MM consultant so end users can only choose from predefined allowed values (typically via drop-down lists).
• End-user rule: Users cannot type arbitrary values; they must select from allowed entries.
• Where configured: In the same general SAP IMG area under settings for key fields.
• Material status is itself one such key field (explicitly noted in the video).

Examples of other key fields described

• Material groups (client-level; appears on Basic Data 1)
• External material groups
• Divisions (client-level; used in SD module for sales area creation and related functions)
  • Video mentions entries can be marked hidden so they do not appear in the drop-down.
• ABC indicators / other indicators (customizable)
• Laboratories and offices
  • Can be configured for valid/invalid/duplicated behavior, affecting availability in the drop-down.
• Storage conditions (used in Storage 1 tab)

Core implementation takeaway

• The MM consultant must ask the client what entries they need for each key field, then configure them accordingly.

---

4) Material Output Format (Material Number Formatting)

• Meaning: Output format configuration determines how material numbers are generated/displayed.
• Internal vs external number ranges:
  • Internal: system automatically generates numeric material numbers
  • External: user provides material numbers (may be numeric or non-numeric)

Example behavior explained

• System-generated number 206 became 0000 + 206.
• This was attributed to leading zeros configuration inside material number output format.

---

5) Detailed methodology / configuration steps shown (material number output format)

Key configuration: “Define output format of material numbers”

The video highlights major options configured here:

Material number length

• SAP S/4HANA supports up to 40 characters (especially for alphanumeric material numbers).
• For numeric material numbers, limit remains 18 digits.
• Important note: after S/4 or an upgrade, the system may default to allow only up to 18 unless extended fields are activated.

Enable extended material number length (beyond 18 up to 40)

• Conceptual path shown:
  • SPRO → SAP Reference IMG → Cross-Application Components → General Application Functions → Field Length Extension
• Action:
  • Enable the checkbox to activate extended fields
• If not enabled:
  • material length beyond 18 will not be allowed.

Material number length setting effect (example: length = 7)

• If configured length is greater than the digits of the internally generated number:
  • system can add leading zeros to reach configured length
• If not configured to add leading zeros (depending on related checkbox settings):
  • material number remains at the exact generated digit length.

Material number template

• Used to enforce a pattern in the material number.
• Template syntax described:
  • underscores for variable positions
  • special characters at fixed positions (example: placing “*” at a specific index)
• Effect:
  • On new material creation, system applies the template pattern.
• Risk/behavior note:
  • Once implemented, changing templates can affect existing material codes automatically.

Lexicographical storage checkbox

• Purpose:
  • treat digits as characters/labels rather than numeric values for comparison/storage.
• Benefit described:
  • helps when external assignments include numeric-like values that must be treated differently (e.g., keeping distinctions such as 123 vs 01 23)
• Comparison logic:
  • Numeric (non-lexicographical): numeric comparison rules apply
  • Lexicographical: compares digit-by-digit as characters
• Constraints noted:
  • This checkbox is mutually exclusive with another related checkbox for non-lexicographical handling.
  • Once numeric material numbers exist, the video states you cannot activate lexicographical behavior.
  • After deactivating, system changes how leading zeros are handled and how numbers display.

---

Speakers / sources featured

• Primary speaker: The YouTube creator/instructor addressing viewers as “Hey everyone” and guiding SAP configuration demonstrations.
• Source system referenced: SAP (SPRO, SAP Reference IMG, SAP MM transactions like MM03/MM02/ME21N, and mention of database tables M and MRC).
• Named informational source: A SAP Note link is mentioned (no specific note number provided in subtitles).