Scenario 22 — Output Determination (Print/Email PO Form)
📊 Business Case
Output determination is SAP's framework for automatically routing a document — here a purchase order — to the vendor via the right medium (print, email, fax, or EDI) the moment it's created or changed. Instead of a buyer manually printing and emailing every PO, condition records tell the system "for this purch org + vendor + doc type, send by email immediately." Here PakSteel automates dispatching the PO so vendors get it instantly with a full audit trail.
🕐 When to use it
Whenever documents must reliably reach a partner — POs to vendors, order confirmations, reminders. Any time manual printing/emailing is slow, inconsistent, or risks a missed order.
❓ Why it matters
It makes dispatch automatic, consistent and auditable. The system records what was sent, when and how, so nothing is forgotten and every transmission is traceable for compliance.
👤 Who triggers it
An MM consultant configures output types and condition records (NACE, MN04); the PO then proposes the output automatically, and ME9F (often a background job) dispatches it.
🔁 The key distinction
This is config, not a posting — no money moves. Its value is speed and audit: faster vendor turnaround, no missed orders, and a complete record of every PO sent.
💰 Financial Impact — The Easy-Money Example
Output determination is configuration, so the payoff is processing time saved and orders never missed, not a posting. Picture a buyer creating 40 POs a day: manually printing, attaching and emailing each costs minutes and invites mistakes; automated output sends them all in seconds.
No direct posting here — output determination doesn't touch FI. But by guaranteeing the PO actually reaches the vendor (and logging it), it removes the delays and disputes that do cost money: late deliveries, duplicate orders, and "we never received the PO" arguments at invoice time.
🇵🇰 The Business Story
When a PO is created/changed, PakSteel needs to:
- Print a hardcopy for vendor (signed + stamped, Pakistani business norm)
- Email PDF to vendor's procurement contact
- Send fax (some legacy vendors still use this)
- For internal: post to a shared printer at procurement desk
Output Determination = SAP's framework for routing PO docs to printers/email/fax/EDI.
🎯 What you'll learn
- Output Types (NACE): NEU (New PO print), MAHN (reminder), etc. Each = an output trigger
- Access Sequence: where SAP looks for output condition records
- Condition Records (MN04): per Purch Org + Vendor + Doc Type → "use medium 1 (printer)" or "5 (email)"
- Procedure: ordered list of output types applicable to doc
- Smart Form / Adobe Form: the actual PDF layout (developed in SE71 / SFP)
🔧 Step-by-Step
⚙️ Config Steps
22.1 — Output Type Setup · NACE Application EF (Purchasing)
- NACE · Application
EF· Output Types - Default type NEU exists — review settings (Medium 1 = Print, 5 = Email/EDI)
- Optional: copy to Z_NEU for custom logic
22.2 — Maintain Condition Records · MN04
- MN04 · Output Type NEU
- Key combination: Doc Type + Purch Org + Vendor
- Add row: NB · PKLO · MUGHAL21 → Medium
5(Email) · Vendor's email · Time3(immediate) - Save
22.3 — Process Output · ME9F
ME9F runs to dispatch pending output. Real systems run this as background job hourly.
✅ Verification
| # | T-code | Check |
|---|---|---|
| 1 | NACE | Application EF shows output type NEU with media 1 (Print) and 5 (Email) defined |
| 2 | MN04 | Condition record NB · PKLO · MUGHAL21 → medium 5, time 3 exists |
| 3 | ME21N | Create a PO for that vendor → Messages shows NEU proposed automatically (medium 5) |
| 4 | ME9F | Run output processing → PO message status turns green (successfully processed/sent) |
🎓 Interview-Ready Answers
Q: What is output determination and which objects make it up?
It's the condition-technique framework that decides how a document is issued. Components: output type (e.g. NEU = new PO), access sequence (where to search for records), condition records (the actual "send this combination by this medium"), the output procedure (ordered list of output types for the document), and the form/program (Smart Form or Adobe form that renders the layout). For purchasing it lives under application EF.
Q: What do the medium and timing settings on a condition record mean?
The medium is the channel: 1 = Print output, 2 = Fax, 5 = External send (email/EDI), 6 = EDI, etc. The dispatch time controls when it goes: 1 = with periodic job (e.g. RSNAST00 / ME9F batch), 3 = send immediately (when the document is saved), 4 = on explicit request. PakSteel uses medium 5, time 3 to email the PO the instant it is saved.
Q: How do you process and re-send PO output, and where do you check status?
ME9F processes purchase-order messages (usually scheduled as a background job). You can check and reprocess an individual PO's output under Messages in ME22N/ME23N — green means sent, yellow means not yet processed, red means error. ME9F lets you reissue or repeat output if needed.