Output Determination for Inventory Management in SAP MM | Complete Guide with end to end config

Video Topic

A complete end-to-end guide to Output Determination in SAP MM (Inventory Management)—including configuration and hands-on demos for generating material document outputs (goods receipt and goods issue) using message types/output types and condition records.

Key Concepts & Configuration Flow (Inventory Management)

1. Message Type / Output Type (Central Element)

For inventory, outputs are mainly printed for:

• Goods receipt (GR) → output goes to warehouse/internal stakeholders
• Goods issue (GI) → output goes to plant/internal stakeholders

Different message/output types apply to different scenarios, such as:

• GR vs GI
• Individual vs collective slips
• Inspection text variations
• Other scenario-based differences

2. Condition Tables (Item-Level / Material Document Item)

Outputs are generated at material document item level (not header).

Configuration starts by creating/using condition tables containing fields relevant from the material document item.

Example standard table mentioned:

• Table 72 (goods receipt/goods issue slip combinations)
  • Fields:
    • Transaction/Event type
    • Print version
    • Print item

3. Access Sequence

After condition tables exist, maintain them in access sequences to control how the system searches condition records.

• The access sequence includes the key fields used by the condition tables (e.g., transaction type + print version + print item).

4. Message Determination Schema (Procedure)

Maintain the message determination schema for application Inventory Management (application ME).

• Recommended: use SAP standard schema
• Contains multiple message types
• Some message types are triggered using requirement routines

5. Maintain Output Types

Standard output types discussed for inventory:

• Goods issue: WA01, WA02, WA03
• Goods receipt: WE01, WE02, WE03

Common behaviors/configuration attributes include:

• Access sequence reference
• Partner independent output (typical for inventory)
• Default dispatch time & transmission medium
  • Transmission medium defaults to print
  • Dispatch time controls whether output is processed immediately or later (e.g., via job)
• Processing routines impact output
  • Output generation uses print program + form routine + form to format the slip

6. Output Determination Procedure and Requirements

SAP standard procedure:

• ME0001 assigned to inventory application ME

The procedure lists output/message types and may include requirements.

Key example:

• For collective slip output types (version “3”), requirement 173 ensures output is only generated for the first line item of the material document, because output is normally item-level.

7. Maintain Condition Records (MN21 / MN22 / MN23)

Condition records are maintained per output type using combination keys.

T-codes:

• MN21 create
• MN22 change
• MN23 display

When saving a condition record, the system shows the available tables/fields based on the access sequence.

---

Standard Demo: Deriving Fields Used in Output Determination

The demo repeatedly shows how three fields drive output selection.

1. Transaction / Event Type

• Determined from the movement type posting.
• Example:
  • Movement type 101 (GR) → transaction/event type WE
• Validation shown via:
  • MB51 and table/field display

2. Print Item

• Configured at the movement type level (via customizing for movement type).
• Examples:
  • Movement type 101 → print item 1 (GR material document printout)
  • Movement type 122 (return delivery) → print item 2

3. Print Version

Selected in MIGO during posting/triggering:

• Version 1 = individual slip
• Version 2 = individual slip with inspection text
• Version 3 = collective slip

---

Hands-On Outputs: Goods Receipt (GR) Scenarios

1. GR Individual Slip

Configure condition record for output type WE01 with:

• transaction/event type WE
• print version 1
• print item matching movement type (example: 1 for GR 101)

Then:

• In material document display, select “Print via output control” to trigger output determination.
• Use determination analysis to check:
  • output found / not found / ignored (requirement not met)

2. GR Return Delivery Changes Output via Print Item

• Posting movement type 122 changes print item to 2
• Maintain condition record for WE01, but set:
  • print item = 2
• Result:
  • Same output type key (WE01)
  • Slip content changes (return delivery reason code shown)

3. GR Individual Slip with Inspection Text

• Configure WE02:
  • print version 2
  • print item 1 (for GR 101)
• Add inspection text in material master (via MM03 → inspection text)
• Select version 2 in MIGO to trigger correct output
• Printed slip includes material inspection instructions

4. GR Collective Slip

• Configure WE03 with:
  • print version 3
• When posting multiple line items:
  • system generates output only for item 1
  • slip contains all line items
• Verified via requirement 173 in the output determination procedure

---

Hands-On Outputs: Goods Issue (GI) Scenarios

1. Initial Failure When Condition Records Are Missing

Goods issue output initially fails because:

• condition records for goods issue output types (WA01/WA02/WA03) were not maintained.

2. Configure Goods Issue Individual Slip (WA01)

• Transaction/event type for GI is WA
• Print version 1
• Print item derived from movement type 201 config (example: print item = 1)

3. Re-run Output Determination

• Re-run output determination in MIGO
• Output should then be successfully determined and generated.

4. Processing Output with MB90

Uses MB90 and dispatch time logic:

• dispatch time 3 → unprocessed; run MB90 to process
• dispatch time 4 → processed immediately upon save/posting

---

Custom Configuration (Create Your Own Output Behavior)

The video demonstrates extending the standard framework to build a custom output type.

1. Custom Condition Table

Example created:

• condition table 902
• Key fields:
  • Material code + Plant + Movement type

2. Custom Access Sequence

Example created:

• access sequence Z001
• Uses custom condition table 902

3. Custom Output Type

• Copy standard output type WE01 into ZE01
• Change access sequence to Z001

4. Add Custom Output Type to Output Determination Procedure

• Add ZE01 into standard procedure ME0001 control data

5. Maintain Condition Record for ZE01

• Maintain using movement type / plant / material combination

6. Demo Result

After posting GR:

• standard output type(s) still found (e.g., WE01)
• custom output type ZE01 also found when the condition record matches
• dispatch time can be configured to auto-process

---

Advanced Controls in Document Processing

1. Manually Add Output Types to a Material Document

• On the output tab, a user can manually add an output type.
• The output type must exist in the output determination procedure.
• Example: manually add WE02 and set dispatch/transmission/printer manually.

2. Repeat Output

• In MB90, set processing mode = 2 for repeat processing.
• The system shows previously processed outputs and allows re-execution.

---

Main Speakers / Sources

• Speaker: the video creator/instructor (a single presenter demonstrating SAP MM configuration)
• Source material:
  • SAP standard configuration elements for Inventory Management application ME
  • Standard output determination procedure ME0001
  • Standard output types: WA01/WA02/WA03 and WE01/WE02/WE03
  • Standard condition/access/message determination framework in SAP MM