# SAP MM Form Templates List: PO, RFQ and Goods Receipt Output Forms > Source: https://netray.co/tools/sap-mm-output-form-templates-list-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A searchable starter list of SAP MM output documents and the output type, application and form technology behind each one. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP MM consultant - ABAP form developer - Procurement key user ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Document **Key:** document **Type:** text #### NACE application **Key:** application **Type:** text #### Standard output type **Key:** output_type **Type:** text #### Output processing **Key:** tcode **Type:** text #### Form technology **Key:** forms **Type:** text #### Note **Key:** note **Type:** text **Rows:** **Document:** Purchase order **Application:** EF **Output type:** NEU **Tcode:** ME9F (message output), ME21N (output tab) **Forms:** SAPscript form, Smartform or Adobe form (customer choice) **Note:** Print program usually a copy of the standard purchase order print program **Document:** Request for quotation (RFQ) **Application:** EA **Output type:** NEU **Tcode:** ME9A **Forms:** SAPscript, Smartform or Adobe form **Note:** Sent to vendors from ME41 or ME42 **Document:** Scheduling agreement **Application:** EL **Output type:** NEU **Tcode:** ME9E **Forms:** SAPscript, Smartform or Adobe form **Note:** Schedule lines print as delivery schedule **Document:** Contract (quantity or value) **Application:** EV **Output type:** NEU **Tcode:** ME9K **Forms:** SAPscript, Smartform or Adobe form **Note:** Outline agreement printout for vendor **Document:** Release order against scheduling agreement **Application:** EL **Output type:** LPET or similar **Tcode:** ME84, ME9E **Forms:** SAPscript or Smartform **Note:** Check the output types configured in your system **Document:** Goods receipt slip **Application:** Goods movements (MIGO print) **Output type:** Set in MIGO print settings **Tcode:** MIGO, MB90 for output processing **Forms:** SAPscript or Smartform **Note:** Configured via the message determination for goods movements **Document:** Pallet or handling unit label **Application:** Goods movements **Output type:** Customer defined **Tcode:** MIGO **Forms:** Smartform or label printer format **Note:** Often replaced by label printing in a warehouse or labeling solution **Document:** Purchase requisition **Application:** Usually not printed **Output type:** None in standard **Tcode:** ME51N **Forms:** Not applicable **Note:** Normally approved through release strategy and workflow instead of paper **Document:** Reminder or expediter (dunning) **Application:** EF **Output type:** MAHN **Tcode:** ME91F **Forms:** SAPscript or Smartform **Note:** Urgency reminders to vendors **Document:** Vendor evaluation report **Application:** Not NACE **Output type:** Not output type based **Tcode:** ME6H **Forms:** ALV list **Note:** Report rather than printed form **Document:** Invoice (logistics invoice verification) **Application:** Not applicable **Output type:** None **Tcode:** MIRO **Forms:** Not applicable **Note:** Document is incoming from vendor, there is no outbound print **Document:** S/4HANA purchase order output **Application:** Output management **Output type:** Output management configuration **Tcode:** Fiori: Manage Purchase Orders **Forms:** Adobe Forms based templates **Note:** S/4HANA uses output management with BRF+ based determination, check the release you run **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the list **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the standard SAP output type for a purchase order? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms form templates in sap mm pdf, sap mm forms list, sap po output type neu, sap smartforms mm, sap adobe forms purchase order, sap rfq output form, sap goods receipt slip form, nace output types mm --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json