SAP Output Determination and NAST: A Practical Troubleshooting Guide

SAP output determination connects a business document to an output type, a processing method, and an output destination. In classic output control, the system stores the resulting output record in the NAST table. The record then controls when and how a message such as an order confirmation, delivery note, invoice, or purchase order is processed.

This guide focuses on the operational path from document creation to output processing. It also shows how to separate a determination problem from a form, spool, or output-device problem. For the wider architecture, see the SAP print output management overview.

01How NAST fits into output determination

NAST is the persistent record for an output message created by classic output control. A typical record contains information such as the application, output type, partner, transmission medium, processing status, and processing date. The exact business meaning depends on the application using the output framework.

The operational sequence is:

1. A business document is created or changed.
2. The application calls output determination.
3. Condition records are evaluated for the relevant access sequence.
4. The system creates an output record when a condition matches.
5. The output record receives a processing status.
6. Immediate or later processing generates the form, spool request, email, EDI message, or other configured result.

A NAST record therefore proves that output control created a message. It does not by itself prove that the form was rendered successfully or that a printer received the result.

02What an output type controls

An output type defines the business message and its processing behavior. Depending on the application, its configuration can identify the processing program, routine, form technology, transmission medium, partner function, dispatch timing, and language behavior.

Common transmission media include print, fax, external send, EDI, and simple mail. The available options and processing details depend on the application and the output framework assigned to it.

The output type also works with condition technique settings. These settings determine which business fields are relevant, which access sequence is searched, and which condition records can create the output. A correctly configured output type with no matching condition record produces no NAST entry.

Form technology is a separate layer. Smart Forms or Adobe Forms generate the layout after output processing has selected the relevant form and called the processing logic. Use the SAP Smart Forms basics article or SAP Adobe Forms basics article when the NAST record exists but the rendered document is incorrect.

03How condition technique creates a NAST record

Condition technique evaluates business context against condition records. Typical fields can include sales organization, customer, document type, plant, purchasing organization, vendor, or partner function. The application determines which fields are available for its output procedure.

A practical condition-check sequence is:

1. Identify the application and output type used by the document.
2. Check the output procedure assigned to that application.
3. Identify the access sequence assigned to the output type.
4. Review the condition tables searched by each access.
5. Confirm that an active condition record exists for the document data.
6. Check the validity period, partner function, language, and medium.
7. Save or reprocess the document and inspect the resulting output record.

The condition record must match the document at the level defined by the access sequence. A record for one sales area, plant, or partner does not automatically apply to another combination.

04How to inspect NAST records

Start with the business document and identify its application, output type, partner, and processing status. The document’s output or messages view is usually the fastest way to determine whether the system created an output record.

For broader investigation, use an authorized table-display or reporting tool to inspect NAST records with narrow selection criteria. Filter by the relevant application, output type, object key, partner, and creation date. Compare one document that produced the expected output with one that did not.

A useful comparison focuses on:

• Whether a record exists for both documents
• Whether the output type is the same
• Whether the partner and partner function match
• Whether the medium and dispatch time match
• Whether the processing status differs
• Whether the document keys identify the expected business objects

Avoid broad unrestricted selections in production systems. Large NAST volumes can make analysis slow and can obscure the document-specific evidence needed for a safe decision.

05How to read output processing status

The processing status indicates where the output currently stands. A status showing that processing is pending points toward dispatch timing, selection criteria, or a scheduled processing run. A status showing successful processing shifts attention toward the spool request, email route, EDI channel, or receiving system.

A failed status requires the application log, processing log, and related spool or communication evidence. Record the error text before repeating processing, because a retry can replace or add operational evidence.

When reprocessing is appropriate, use the application’s supported output-processing transaction or job. Confirm the selection criteria, processing mode, output type, and date range before execution. Process a small test set first, then verify the resulting status and destination.

06Troubleshoot missing output records

When no NAST record exists, begin with determination rather than form rendering. Check the following in order:

1. The document is saved and has the expected business status.
2. The application has an output procedure assigned.
3. The intended output type is included in that procedure.
4. The access sequence reaches the expected condition table.
5. A valid condition record exists for the document data.
6. The partner function and communication data are complete.
7. The output type is permitted for the document type and organizational data.
8. The document change or creation event invokes output determination.

A missing record commonly results from a condition mismatch, an invalid date range, missing partner data, an inactive output type, or an output procedure that does not include the expected message. Compare the failed document with a known-good document using the same application and output type.

07Troubleshoot a failed output record

When NAST exists but processing fails, follow the output record into its processing layer. Confirm the processing program and routine, form assignment, printer or destination, authorization context, and application log.

For print output, inspect the generated spool request and its device assignment. The SAP spool management basics article covers spool-oriented investigation. For a destination problem, verify the output device and host-spool configuration using the practices described in SAP output device configuration with SPAD.

For email or EDI, inspect the corresponding communication logs and confirm that the partner address, port, RFC destination, or integration endpoint is available. A successful NAST processing status can still leave a downstream delivery problem, so correlate the SAP result with the receiving-system evidence.

08Separate determination from form and device issues

Use the following diagnostic boundaries:

This separation prevents repeated condition-record changes when the actual issue is a printer, spool, form, or external communication problem.

09A controlled reprocessing procedure

Use a controlled procedure when an output must be generated again:

1. Capture the document number, output type, partner, original status, and error text.
2. Confirm that the business reason for reprocessing is valid.
3. Correct the underlying condition, master data, form, or destination issue.
4. Select only the affected document or a tightly bounded set.
5. Run the supported output-processing function with the intended processing mode.
6. Verify the new status, spool request, message log, or communication handoff.
7. Confirm that the recipient received the result and document the outcome.

For duplicate-sensitive documents, coordinate with the business owner before reprocessing. Invoices, delivery documents, purchase orders, and external messages can have downstream consequences when sent twice.

10Operational checks for stable output processing

Monitor output processing as a chain rather than as a single transaction. Review pending and failed output records, recurring condition gaps, spool growth, output-device availability, form errors, and communication failures.

Maintain a small set of known-good test documents for important output types. After a transport, form change, printer change, or partner-data change, process one controlled test document and verify the complete result.

Keep configuration ownership clear. Functional teams typically maintain output requirements and condition records, while technical teams maintain processing infrastructure, forms, spool devices, jobs, and communication routes. Joint troubleshooting is fastest when both teams use the same document number and output record as their evidence.

11A practical decision path

Use this decision path during an incident:

1. Does a NAST record exist? If no, investigate output determination and condition technique.
2. Is the record pending? Check dispatch timing and the output-processing run.
3. Is the record in error? Read the processing log and inspect the assigned processing components.
4. Did processing create a spool or communication handoff? If no, remain in the processing layer. If yes, continue to the destination.
5. Did the destination receive the result? If no, investigate spool, printer, email, EDI, or middleware operations.
6. Is the layout wrong? Investigate the selected form, interface data, and rendering logic.

This sequence narrows the fault domain before configuration is changed and creates a reproducible incident record.

12Key takeaways

NAST is the central evidence point for classic output determination, but it represents an output record rather than proof of final delivery. Condition technique determines whether the record is created; processing configuration determines what happens afterward.

The most efficient troubleshooting approach is to establish whether the record exists, read its processing status, and then follow the result through the form, spool, device, or communication destination. Controlled reprocessing and document-specific comparisons reduce duplicate output and unnecessary configuration changes.