MM / P2Padvanced

MM Purchase Order Part 5: Approval, Output, Change Control and Troubleshooting

Key takeaway

Control and communicate POs: release strategies or flexible workflow for approvals, output to suppliers (print, email, EDI) in classic NAST or S/4HANA output management, change management with version management and change documents, and troubleshooting when POs are blocked, not sent or wrong.

Explanation

📌 KEY POINTS
✅ Approval: classic release strategy or flexible workflow; unreleased POs can't be output.
✅ Output: classic NAST (e.g. NEU, ME9F) or S/4HANA output management with BRF+ determination.
✅ Changes after output: change output, version management, change documents.
✅ Troubleshooting: release status, output status/log, supplier email/EDI setup.
⚠️ Suppliers often don't receive POs because output failed silently — monitor output status.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered follow-ons. Now control and communication.

━━━━━━━━━━━━━━━━━━━━
▶ 1. APPROVAL

Release strategy (classification, codes) or flexible workflow (conditions/agents).

━━━━━━━━━━━━━━━━━━━━
▶ 2. OUTPUT

Print, email, EDI (ORDERS/ORDCHG).
NAST condition records or BRF+ output parameter determination.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CHANGE CONTROL

Change output to supplier, version management, change documents (ME23N header).

━━━━━━━━━━━━━━━━━━━━
▶ 4. TROUBLESHOOTING

Not released, output error, missing supplier email, EDI partner profile.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MONITORING

Unsent POs, failed output, overdue confirmations.

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

Create a PO above release threshold; release it.
Check output status and log.
Change quantity and check change output.

✅ CHECKPOINT: every released PO has successful output within the SLA.

Code example

ABAP Code

===== STEP 1: approval =====Release strategy (ME28/ME29N) or flexible workflow (My Inbox) ===== STEP 2: output =====Classic: output type NEU, condition records MN04, ME9F reprint/sendS/4HANA OM: output type PURCHASE_ORDER, BRF+ determination, email/EDI channels ===== STEP 3: changes =====Change → change output | version management (if active) | change documents in ME23N

Real project scenario

A supplier did not receive an urgent PO. Output status showed an error: the supplier's email address was missing in BP communication data. The team added email to supplier onboarding requirements and a daily report of failed PO outputs.

Common mistakes

Not monitoring output.
Missing supplier email/EDI data.
Outputting unreleased POs manually.
No change output rules.
Ignoring version management.

Best practices

Monitor output daily.
Maintain supplier communication data.
Enforce release before output.
Define change output rules.
Use change documents in audits.

Interview angle

Questions: "How are POs approved?", "How is PO output determined?", "A supplier didn't get the PO — what do you check?"
Strong answer: release strategy/flexible workflow, NAST/BRF+ output, change control, troubleshooting release/output/communication data.

Practice this lesson

Quick check

1. A supplier did not receive an urgent PO. What should be checked first?

2. Where can you see who changed a PO quantity and when?

3. A PO above the approval threshold cannot be sent to the supplier. Why?

Interview questions

1. A vendor's purchase order output was transmitted via EDI (message type ORDERS) but never reached the vendor due to an interface failure, and goods are needed urgently. Walk through the fallback and reissue process to get the PO to the vendor without creating a duplicate order.

Answer it in your own words first, then compare.

2. How does the purchasing document type influence output determination for purchase orders?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.