SAP MM Form Templates List: PO, RFQ and Goods Receipt Output Forms
This is a starter list of the output forms most SAP MM teams ask for: purchase order, RFQ, contract, scheduling agreement, reminder and goods receipt slip. For each it shows the NACE application, the standard output type, where to process it and what form technology you will likely use.
| Document | NACE application | Standard output type | Output processing | Form technology | Note |
|---|---|---|---|---|---|
Purchase order | EF | NEU | ME9F (message output), ME21N (output tab) | SAPscript form, Smartform or Adobe form (customer choice) | Print program usually a copy of the standard purchase order print program |
Request for quotation (RFQ) | EA | NEU | ME9A | SAPscript, Smartform or Adobe form | Sent to vendors from ME41 or ME42 |
Scheduling agreement | EL | NEU | ME9E | SAPscript, Smartform or Adobe form | Schedule lines print as delivery schedule |
Contract (quantity or value) | EV | NEU | ME9K | SAPscript, Smartform or Adobe form | Outline agreement printout for vendor |
Release order against scheduling agreement | EL | LPET or similar | ME84, ME9E | SAPscript or Smartform | Check the output types configured in your system |
Goods receipt slip | Goods movements (MIGO print) | Set in MIGO print settings | MIGO, MB90 for output processing | SAPscript or Smartform | Configured via the message determination for goods movements |
Pallet or handling unit label | Goods movements | Customer defined | MIGO | Smartform or label printer format | Often replaced by label printing in a warehouse or labeling solution |
Purchase requisition | Usually not printed | None in standard | ME51N | Not applicable | Normally approved through release strategy and workflow instead of paper |
Reminder or expediter (dunning) | EF | MAHN | ME91F | SAPscript or Smartform | Urgency reminders to vendors |
Vendor evaluation report | Not NACE | Not output type based | ME6H | ALV list | Report rather than printed form |
Invoice (logistics invoice verification) | Not applicable | None | MIRO | Not applicable | Document is incoming from vendor, there is no outbound print |
S/4HANA purchase order output | Output management | Output management configuration | Fiori: Manage Purchase Orders | Adobe Forms based templates | S/4HANA uses output management with BRF+ based determination, check the release you run |
This is a starter list of common standard defaults, not a replacement for your own configuration. Output types, programs and forms are customised heavily. Check your system with NACE for application and output type settings, and confirm which form technology your release supports. Output determination in S/4HANA uses output management for newer applications.
Review your forms scope
Send your list of documents and we will suggest which forms need rebuilding. Optional.
Optional. The tool and every export work without this. No spam.
How to use the list
Search for the document you need and read across: application tells you where to look in NACE, output type is the standard SAP default, and the transaction is where you process or check the message. Use the list to scope a forms workstream, to brief an ABAP form developer, or to check what you must test at go-live. Export to Excel to add your own columns such as form name, owner and status.
- Application: EF purchase order, EA RFQ, EL scheduling agreement, EV contract
- Output type: NEU is the standard delivered type for these
- Form: SAPscript, Smartform or Adobe form
SAPscript, Smartforms and Adobe forms
SAPscript is the oldest technology and still present in many ECC systems. Smartforms replaced it with a graphical editor and are common in ECC projects. Adobe Forms, using Adobe LiveCycle Designer, support richer layout and PDF output and are the base for modern output. In S/4HANA new applications use output management with form templates, so check what applies to your release before planning to copy and modify a legacy form.
Planning a forms workstream
List every document that leaves the company or is printed for the shop floor, then classify each as use standard, adapt layout, or rebuild. Collect sample outputs and legal text from the business, including logos, bank data and terms. Treat the PO as the highest priority since vendors see it. Decide the number of language variants up front, as each language adds text and test effort.
Common mistakes
Teams often start form development before output determination is agreed, so documents never reach the right vendor channel. Another mistake is hard coding company text in the form rather than using text modules or customizing. Finally, the PDF looks right in the test client but fails in production because the printer or spool setup was not tested.
Frequently Asked Questions
What is the standard SAP output type for a purchase order?
NEU is the output type delivered by SAP for the purchase order, under message application EF. Many companies copy it to a Z type and attach their own form and print program.
Which form technology should I use?
For new development use Adobe Forms where supported, since they give better layout and PDF output. Smartforms and SAPscript remain in many existing systems and are acceptable to maintain. In S/4HANA follow output management for supported documents.
Where do I configure output for MM documents?
In NACE for classic message control, with condition records maintained in the document specific transaction such as MN04 for purchase orders. In S/4HANA output management uses a different configuration, so check your release.
Can I download the SAP MM forms list as PDF?
Yes. Use the export buttons to get this list as PDF, Excel, Word or CSV. You can then add your own forms and owners before sharing with the team.
Netray can help your team add a private AI layer on your own servers that reads your form specifications and output configuration, so consultants can ask which output type and form applies to a given document.
Related Tools
SAP Output Determination Checklist
A checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices.
SAPSAP Purchase Order Example, Format and Document Types
A sample SAP purchase order layout with header, item and delivery data, plus a quick reference of PO document types such as NB, FO and UB.
SAPSAP MM Transaction Codes Reference
Searchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
SAPSAP MM BPML Business Process Master List Template
An editable MM business process master list with process IDs, transaction codes, owners and in or out of scope status, exportable to Excel.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
- SAP SD Pricing Condition Types Reference (PR00, K004, MWST)
Keep exploring
Free tools
- SAP MM and QM BAPI and API List ReferenceA searchable list of the common SAP MM and QM BAPIs and S/4HANA OData APIs, what each does, and whether it needs a commit.
- SAP MM Tables and Key Fields ReferenceSearchable list of the core SAP MM tables with their primary key fields and what each stores, including S/4HANA changes.
- SAP MM Transaction Codes ReferenceSearchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
ERP fixes and how-tos
- SAP PO Print Preview Not Working in ME21N and ME9FFix SAP purchase order print preview not working in ME21N and ME9F: output type NEU, NACE condition records, form assignment, spool and Adobe Document Services.
- Freight Cost in SAP MM: Planned and Unplanned Delivery CostsHow to handle inbound freight in SAP MM: planned delivery costs on the PO, freight condition types, unplanned costs in MIRO, and the GR/IR and stock impact.
- SAP Error Message MM899 and the Most Common MM Error MessagesWhat SAP message MM899 means, how to read the real error behind it with SE91 and long text, and a practical guide to the most common MM, M7 and ME messages.
Integrations
- How to add WhatsApp to SAP ECC 6.0How to connect WhatsApp Business to SAP ECC 6.0 using BAPIs, IDocs and output determination: order status, shipment alerts, approvals and supplier replies.
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.