SAP PO Print Preview Not Working in ME21N and ME9F
sap po print preview not working
Also searched as
- ME21N print preview not available
- ME9F purchase order output not printing
- sap purchase order output type NEU not found
- sap po print preview blank
Short answer
A PO print preview fails because no output was determined for the order, the output type has no valid form or processing routine, or the spool or Adobe Document Services layer is broken. Check the Messages tab of the PO first, then NACE for the output type, then the spool.
Applies to: SAP ECC 6.0 message determination (NACE, output type NEU) and S/4HANA; S/4HANA also supports the newer output management
How to diagnose a missing PO print preview
- 1Open the PO in ME22N and choose Header, Messages. If the list is empty, no output was determined; go to step 2. If NEU is listed, note its status and processing time.
- 2In NACE, select application EF (purchase order) and Output Types. Confirm NEU exists and has an access sequence.
- 3Check condition records with MN04 (create/change) or MN05 (display). A record must match the purchasing organisation, vendor or document type, with a medium and a language.
- 4Open the processing routine for NEU in NACE: it should point to the print program and form. If the form field is empty or the form is inactive, preview fails.
- 5Run ME9F, enter the PO, and use the print preview or output from there. If it works in ME9F but not in ME21N, the problem is in the message line, such as a wrong partner function or medium.
- 6If the form is Adobe-based and shows blank or an error, check Adobe Document Services (ADS) connectivity in SM59 and the ADS user, then retry. If it is SAPscript or Smart Forms, check SP01 for spool errors.
Output determination: why nothing appears
Output determination is a condition technique. NACE holds output types, access sequences and condition records. If no condition record fits the PO, the Messages tab stays empty and there is nothing to preview.
Typical misses are a new purchasing organisation, a new document type, or a vendor that has a language the record does not cover. Fix by creating a record in MN04 for that key and testing again.
On S/4HANA, new installations may use the output management framework rather than NACE. If your system uses that, manage output by the configured application output type and check its BRF+ rule instead.
Form assignment and processing routine
The output type links to a program and form. If someone replaced the form with a copy that has syntax errors, or deactivated the original, the preview fails with a short dump or no output. Check ST22 for ABAP dumps on the preview attempt.
Smart Forms and Adobe forms are tested differently. For Smart Forms use SMARTFORMS to generate and test. For Adobe forms use SFP to test the form with sample data.
Language matters. A vendor in a language without a translated form text may print a blank or partially empty preview.
Spool, printer and Adobe Document Services
Print preview in ME21N depends on the user's output device in SU3 and on how the message is processed. If the user has no default printer, the spool request can fail before it is displayed. Set a default output device and tick output immediately if that matches your process.
For Adobe forms a working ADS connection is required, and an Adobe Reader or PDF viewer integrated in SAP GUI must work on the PC. After a SAP GUI update the viewer integration can break, which shows up as a blank screen on preview only.
Spool failures appear in SP01 and SP02. If the spool request exists but cannot display, the problem is in the device or viewer, not the PO.
Try it here, free
SAP MM Output Form Templates List
A searchable starter list of SAP MM output documents and the output type, application and form technology behind each one.
Common pitfalls
- !Editing the form without a transport leaves production on the old version and masks the real fault.
- !Condition records are client-specific. A record created in test does not exist in production.
- !Messages not yet saved cannot be previewed on a new PO in all releases. Save, then open in change mode.
- !Authorisation objects for output or SAPscript can block preview for one user only. Compare with a colleague who succeeds.
- !Do not use the same output device for preview and for real printing if a printer is offline.
How an ERP-grounded AI assistant handles this
A grounded assistant can read the NACE condition records, the PO header data and the output status table to explain why a specific PO has no output, for example which key combination had no record. It is a diagnostic aid and does not change configuration. Keeping this on-prem means form and vendor data never leave your network.
Frequently asked questions
What is the standard output type for a purchase order?
NEU in application EF is the standard purchase order output type in the classic NACE-based setup. Your system may have a copy with a custom name.
Where do I maintain PO output condition records?
Use MN04 to create or change condition records for the output type and MN05 to display them. They define who receives the output, by which medium and in which language.
Why does ME9F work but ME21N does not?
ME9F can process outputs for existing POs independently. If it works there, the output exists and the form is fine, and the issue is the message line or the display settings in the PO transaction.
Does Adobe Document Services have to run for PO printing?
Only if the PO form is an Adobe form. SAPscript and Smart Forms do not need ADS.
Related
SAP MM Approval Process: Release Strategies, Workflow and Fiori
SAP MM approval is built on release strategies: rules that block a purchase requisition (PR) or purchase order (PO) until the right people release it with release codes. Strategies are configured with classification characteristics and can be released in ME28 or ME29N, through workflow, or in Fiori approval apps. In S/4HANA there are also flexible workflows for PRs.
Error fixRelease Strategy in SAP MM Not Working: A Troubleshooting Checklist
When a release strategy does not trigger, the cause is nearly always in one of five places: the characteristic values do not match the document, the strategy is not assigned to the class (CL24N), the release group or class is wrong for the document type, the document was created before the change, or the user lacks the release code authorization. Work through the checklist in order; each step is a quick check.
How-toHow to Create a Purchase Order in SAP MM (ME21N)
Create a purchase order in SAP with ME21N: enter the vendor and organisational data in the header, add items with material, quantity, plant and price, and save. A PO can also be created from a requisition through ME21N adopt, ME58 or ME59N.
Error fixSAP MM Errors and Solutions: The Common Ones, by Process Step
Most SAP MM errors fall in five places: purchasing document creation and release (ME21N), goods movements (MIGO), period control, invoice verification (MIRO) and account determination. This page lists the ones that come up most, what causes each, and the first fix, with links to detailed pages for the biggest ones.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
AI for ERPGet AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANA
SAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
Stuck on SAP ERP / S/4HANA?
Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP MM Output Form Templates ListA searchable starter list of SAP MM output documents and the output type, application and form technology behind each one.
- SAP Output Determination ChecklistA checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices.
- SAP PO Item Category, Account Assignment and Special Stock ReferenceSearchable list of the codes you choose on a PO line: item category, account assignment category and special stock indicator.
ERP fixes and how-tos
- How to Create a Purchase Order in SAP MM (ME21N)Step-by-step purchase order creation in SAP MM with ME21N: manual PO, PO from requisition, account assignment, release and the order-to-invoice flow.
- SAP MM price determination: pricing procedure, condition types and fixing wrong PO pricesHow SAP MM determines purchase prices: the RM0000 calculation schema, condition types like PB00, schema determination, and how to fix a wrong price in ME21N.
- SAP MM Order Creation: ME21N Step by Step and the Procure-to-Pay ProcessStep-by-step ME21N purchase order creation in SAP MM, plus the procure-to-pay flow around it: requisition, goods receipt, invoice verification and payment.
Runs with your ERP
- Vision33 Saltbox and Adobe Commerce with SAP Business OneHow Vision33 Saltbox connects Adobe Commerce to SAP Business One: orders, items, customers, setup steps, common failures and where a private AI layer helps.
- i95Dev Connect for Adobe Commerce and SAP Business One: store syncHow the i95Dev connector syncs orders, customers, products and inventory between Adobe Commerce (Magento) and SAP Business One on SQL or HANA, and what breaks.
AI on your ERP
- AI for SAP S/4HANA Procurement (MM) That Reads POs, Receipts and Invoices TogetherAI for SAP S/4HANA procurement: query purchase orders, goods receipts and invoice matching in plain English, on-prem if needed, read-only by default.
- AI for SAP Business One Purchasing, From Purchase Request to A/P InvoiceGround AI in SAP Business One purchasing: purchase requests, POs, goods receipts and A/P invoices via Service Layer, read-only, on-prem or private cloud.