# SAP PO Print Preview Not Working in ME21N and ME9F > Source: https://netray.co/erp-help/sap-po-print-preview-not-working-me9f-me21n > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System sap ## Erp SAP ERP / S/4HANA ## Module MM Purchasing / Output Determination ## Query sap po print preview not working ## Alternate Queries - ME21N print preview not available - ME9F purchase order output not printing - sap purchase order output type NEU not found - sap po print preview blank ## Applies To SAP ECC 6.0 message determination (NACE, output type NEU) and S/4HANA; S/4HANA also supports the newer output management ## Steps ### How to diagnose a missing PO print preview **Items:** Open 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. In NACE, select application EF (purchase order) and Output Types. Confirm NEU exists and has an access sequence. Check 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. Open 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. Run 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. If 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. ## Sections ### Output determination: why nothing appears **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is the standard output type for a purchase order? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** Only if the PO form is an Adobe form. SAPscript and Smart Forms do not need ADS. ## Search terms sap po print preview not working, me21n print preview, me9f purchase order output, sap output type neu, nace purchase order output, mn04 condition record, sap po output not generated, sap adobe form po preview blank --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json