# SAP Output Determination Checklist: NACE, Condition Records and Printing > Source: https://netray.co/tools/sap-output-determination-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP SD consultant - SAP basis and print admin - Functional analyst ## Tool **Kind:** checklist **Scoring Note:** Critical items are the ones that stop output from being found or sent. Resolve those first when output is missing. **Groups:** #### Design and output types **Items:** **Text:** List of required outputs agreed per application: sales (V1), shipping (V2), billing (V3) **Critical:** true **Text:** Output types selected or copied, for example BA00 order confirmation, LD00 delivery note, RD00 invoice **Critical:** true Medium per output type chosen: print, email, EDI, fax, workflow **Text:** Output procedure assigned to the document type or header **Critical:** true Access sequence defined with the right condition tables **Text:** Output type partner function defined, such as sold-to or bill-to **Critical:** true Dispatch time chosen: immediately, with application, or scheduled Language and country variants listed #### Condition records and partners **Items:** **Text:** Condition records created (VV11, VV21, VV31) for every output type needed **Critical:** true **Text:** Records cover the sales organization, customer and document type combinations in scope **Critical:** true Printer, email address or EDI partner maintained in each record **Text:** Partner function contacts maintained in the customer master **Critical:** true Communication data checked for email recipients Default output device assigned to users where needed Mass creation or transport of condition records planned #### Forms and printing **Items:** **Text:** Form technology chosen: SAPscript, Smart Forms or Adobe Forms **Critical:** true **Text:** Print program and form assigned to the output type **Critical:** true Form tested with long text, many lines and multiple pages Logos, signatures and legal text approved by the business **Text:** Output devices defined and tested in SPAD or SPRO print setup **Critical:** true Spool and print authorizations checked for end users Fonts and character sets checked for all languages Archiving of output considered where regulation needs it #### Testing and monitoring **Items:** **Text:** Output status checked in the document (Extras, Output, Header) with analysis of determination **Critical:** true **Text:** NAST records reviewed for processing status and error log **Critical:** true Reprocessing tested through RSNAST00 or the application output screen Output control reports scheduled for unprocessed output **Text:** Test cases cover missing partner, missing record and wrong printer **Critical:** true **Text:** S/4HANA output management approach decided: NACE based or new framework **Critical:** true Email size and attachment format tested Monitoring owner named for failed output ## Content **Intro:** Output determination is how SAP decides which documents to send to whom, by which medium and when. It uses the condition technique, so failures usually come from missing records, wrong partners or a procedure that was never assigned. **Sections:** #### How to use the checklist **Body:** Use the first two groups when you design or build output, and the last two when you test or troubleshoot. For a live problem, jump to the critical items: first check that a record exists, then that the partner and device are filled, then the processing status in NAST. Export the finished checklist as PDF to attach to a test sign-off. **Bullets:** - Run through it for each document type in scope - Use the critical items as a troubleshooting order - Keep a copy per application: V1, V2 and V3 - Add country specific output such as e-invoicing #### How determination works **Body:** In classic SAP, output is configured in NACE. Each application, such as V1 sales, V2 shipping and V3 billing, has output types, an access sequence and an output procedure. When a document is saved, SAP runs the procedure, reads the condition records (created with VV11 for sales, VV21 for shipping and VV31 for billing), and writes the matching entries into table NAST with their medium and dispatch time. The processing program then creates the print, email or EDI message. **Bullets:** - Output type: what is sent, such as BA00 or RD00 - Access sequence: how records are searched - Output procedure: which types a document tries - NAST: the log of what was determined and processed #### Troubleshooting order **Body:** When output is missing, open the document and use the output screen's analysis function. It tells you whether the type was not in the procedure, no record was found, a requirement failed or the partner was missing. If the output exists but is not printed, check the processing log, the output device and the spool request. Most issues are a missing condition record for a new sales area or a missing partner address. #### Common mistakes **Body:** Teams often copy a standard output type but forget to assign the new type to the output procedure. They also create records for one sales organization and forget the rest, or test with a user whose default printer hides a missing device in the record. In S/4HANA, check whether your release uses the newer output management based on BRF+ and adaptation of forms, as the setup and the monitoring screens differ. **Cta:** If missing or failed outputs are found by customers before your team, we can build a read-only monitor that lists unprocessed output from NAST with age and cause. **Faq:** #### What is NACE in SAP? **Answer:** NACE is the transaction for maintaining output determination customizing. For each application, such as sales, shipping or billing, you define output types, access sequences, output procedures and the assignment to documents. Condition records themselves are then created in VV11, VV21 or VV31. #### Where is output status stored? **Answer:** Determined and processed output is stored in table NAST, which holds the application, object key, output type, medium, status and dispatch time. In the document you reach it through Extras, Output, Header or Item, where you can see the processing log. #### Why was no output proposed on my order? **Answer:** The usual reasons are that the output type is not in the assigned procedure, no condition record matches the sales area or partner, a requirement routine failed, or the partner needed does not exist. The analysis function in the output screen shows which. #### Is NACE still used in S/4HANA? **Answer:** Many S/4HANA systems still run NACE based output, especially after conversion. SAP also offers a newer output management framework. Which one you use depends on the release and the choice made in the project, so confirm it early in the design. ## Search terms sap output determination, sap output determination checklist, NACE output types, sap output condition records VV11, sap BA00 LD00 RD00 output, sap output not printing, sap NAST output status, sap condition technique output --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json