SAP Output Determination Checklist (NACE)

0%

0 of 31 items complete

14 critical items still open - these are the highest-risk gaps.

Download checklist:

Design and output types

List of required outputs agreed per application: sales (V1), shipping (V2), billing (V3)CRITICALOutput types selected or copied, for example BA00 order confirmation, LD00 delivery note, RD00 invoiceCRITICALMedium per output type chosen: print, email, EDI, fax, workflowOutput procedure assigned to the document type or headerCRITICALAccess sequence defined with the right condition tablesOutput type partner function defined, such as sold-to or bill-toCRITICALDispatch time chosen: immediately, with application, or scheduledLanguage and country variants listed

Condition records and partners

Condition records created (VV11, VV21, VV31) for every output type neededCRITICALRecords cover the sales organization, customer and document type combinations in scopeCRITICALPrinter, email address or EDI partner maintained in each recordPartner function contacts maintained in the customer masterCRITICALCommunication data checked for email recipientsDefault output device assigned to users where neededMass creation or transport of condition records planned

Forms and printing

Form technology chosen: SAPscript, Smart Forms or Adobe FormsCRITICALPrint program and form assigned to the output typeCRITICALForm tested with long text, many lines and multiple pagesLogos, signatures and legal text approved by the businessOutput devices defined and tested in SPAD or SPRO print setupCRITICALSpool and print authorizations checked for end usersFonts and character sets checked for all languagesArchiving of output considered where regulation needs it

Testing and monitoring

Output status checked in the document (Extras, Output, Header) with analysis of determinationCRITICALNAST records reviewed for processing status and error logCRITICALReprocessing tested through RSNAST00 or the application output screenOutput control reports scheduled for unprocessed outputTest cases cover missing partner, missing record and wrong printerCRITICALS/4HANA output management approach decided: NACE based or new frameworkCRITICALEmail size and attachment format testedMonitoring owner named for failed output

Critical items are the ones that stop output from being found or sent. Resolve those first when output is missing.

Output failure monitor

Optional: we can build a read-only monitor of failed and unprocessed SAP output so the team sees problems before customers do.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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.

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

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.

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

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

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.

Frequently Asked Questions

What is NACE in SAP?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP Output Determination Checklist: NACE, Condition Records and Printing