SAP SD Output Tables: NAST, TNAPR, Applications, Media and Output Types
A searchable reference of NAST-based output control on SAP ECC 6.0 for SD and MM: the tables, application codes, transmission media, processing status values and standard output types with driver programs. Use it when an invoice did not print or an EDI order response did not leave.
| Section | Code or table | Meaning | Key fields or program | Where maintained | Note |
|---|---|---|---|---|---|
Tables | NAST | Output status records, one per output per document | KAPPL, OBJKY, KSCHL, SPRAS, PARNR, PARVW, ERDAT, ERUHR; NACHA, VSTAT, DATVR, UHRVR, CMFPNR | Created by determination or manually in VA02, VL02N, VF02, ME22N output screens | OBJKY holds the document number (e.g. VBELN padded) |
Tables | TNAPR | Processing programs and forms per output type and medium | KAPPL, KSCHL, NACHA; PGNAM, RONAM, FONAM, SFORM | NACE > Output types > Processing routines | FONAM is a SAPscript form, SFORM a Smart Form or PDF form |
Tables | T685 | Condition types, including output types (usage B) | KVEWE, KAPPL, KSCHL | NACE > Output types | Output types share the condition technique with pricing |
Tables | T685B | Additional output type data: dispatch time, medium, partner | KAPPL, KSCHL; VSZTP (dispatch time), NACHA (medium), PARVW (partner function), PARAB (partner-independent) | NACE > Output types > Default values | Defaults copied into new NAST records |
Tables | T683 | Procedures (output determination procedures for usage B) | KVEWE, KAPPL, KALSM | NACE > Procedures | Assigned to order, delivery or billing types |
Tables | T682 | Access sequences | KVEWE, KAPPL, KOZGF | NACE > Access sequences | Sequence of condition tables searched |
Tables | Bnnn | Output condition tables holding condition records | KAPPL, KSCHL, key fields of the table | VV11/VV12 (sales), VV21 (shipping), VV31 (billing), MN04 (PO); or NACE > Condition records | Find the table number in the access sequence |
Tables | CMFP | Collected error messages from output processing | APLID, NR, MSGTY, MSGNR, MSGV1 | Read via output processing log in the document output screen | NAST-CMFPNR points to CMFP-NR |
Applications (KAPPL) | V1 | Sales | Order confirmation BA00 | NACE | Sales documents VA01 to VA03 |
Applications (KAPPL) | V2 | Shipping | Delivery note LD00 | NACE | Outbound deliveries |
Applications (KAPPL) | V3 | Billing | Invoice RD00 | NACE | Billing documents |
Applications (KAPPL) | V5 | Groups | Group output for collective processing | NACE | Used with VG01 groups |
Applications (KAPPL) | V7 | Transport | Shipment documents | NACE | VT01N shipments |
Applications (KAPPL) | EA | Purchasing RFQ | RFQ output | NACE | ME41 to ME43 |
Applications (KAPPL) | EF | Purchase order | NEU | NACE, MN04 to MN06 | ME21N to ME23N |
Applications (KAPPL) | EL | Purchasing scheduling agreement | Delivery schedule output | NACE | ME38, ME9E |
Applications (KAPPL) | EV | Purchasing outline agreement | Contract output | NACE | ME31K |
Applications (KAPPL) | ME | Inventory management | GR/GI slips WE01, WE02, WE03 | NACE | Material document output |
Media (NACHA) | 1 | Print output | Spool via LDEST | TNAPR, NAST | Most common |
Media (NACHA) | 2 | Fax | SAPconnect | TNAPR, NAST | Needs fax number on partner |
Media (NACHA) | 5 | External send | SAPconnect (mail, fax) | TNAPR, NAST | Common for PDF by email |
Media (NACHA) | 6 | EDI | IDoc via partner profile WE20 | TNAPR, NAST | Program RSNASTED with routine EDI_PROCESSING |
Media (NACHA) | 7 | Simple mail | SAP office mail | TNAPR, NAST | Internal notification |
Media (NACHA) | 8 | Special function | Custom routine in TNAPR | TNAPR, NAST | Used for custom processing |
Media (NACHA) | 9 | Events (SAP Business Workflow) | Workflow event | TNAPR, NAST | Triggers a workflow event |
Media (NACHA) | A | Distribution (ALE) | ALE distribution model | TNAPR, NAST | Program RSNASTED |
Media (NACHA) | T | Tasks (SAP Business Workflow) | Workflow task | TNAPR, NAST | Starts a workflow task |
Processing status (VSTAT) | 0 | Not processed | Waiting for dispatch time or RSNAST00 | NAST | Dispatch time 1 or 2 records wait for RSNAST00 |
Processing status (VSTAT) | 1 | Successfully processed | DATVR, UHRVR set | NAST | Repeat output creates a new record |
Processing status (VSTAT) | 2 | Incorrectly processed | Errors in CMFP | NAST | Check the processing log |
Standard output types | BA00 | Order confirmation (V1) | RVADOR01, routine ENTRY, form RVORDER01 | NACE V1 | Copy to Z before changing |
Standard output types | LD00 | Delivery note (V2) | RVADDN01, routine ENTRY, form RVDELNOTE | NACE V2 | Copy to Z before changing |
Standard output types | RD00 | Invoice (V3) | RVADIN01, routine ENTRY, form RVINVOICE01 | NACE V3 | Copy to Z before changing |
Standard output types | NEU | Purchase order (EF) | SAPFM06P, routine ENTRY_NEU, form MEDRUCK | NACE EF | Copy to Z before changing |
Media 4 (telex) also exists in the NACHA domain but is no longer used. Program RSNAST00 processes NAST records that wait for dispatch time 1 or 2 and can reprocess records in background. Confirm driver programs in TNAPR on your system: many installations replace forms with Z Smart Forms.
Get your output setup checked
Send us extracts of NAST errors and TNAPR for your SD and MM output types and we will point out dispatch, form and EDI issues.
Optional. The tool and every export work without this. No spam.
How to use it
Filter by Section. To trace one document, query NAST with KAPPL and OBJKY equal to the document number, padded with leading zeros to 10 digits. VSTAT tells you whether it was processed, NACHA which medium, and CMFPNR points to the error log in CMFP. Then read TNAPR with KAPPL, KSCHL and NACHA to see which program, routine and form ran. The configuration chain (procedure in T683, output type in T685/T685B, access sequence in T682, condition records in Bnnn) explains why a record was or was not determined.
Where this lives in ECC
NACE is the central transaction: choose the application (V1, V2, V3, EF and so on), then output types, procedures, access sequences and condition records. Condition records can also be maintained per area: VV11 to VV13 for sales, VV21 to VV23 for shipping, VV31 to VV33 for billing and MN04 to MN06 for purchase orders. Determination procedures are assigned to document types in SPRO under each module's output control. In each document, the output screen (Extras > Output) shows the NAST records and the Determination analysis button shows which access succeeded.
- NACE: all output configuration by application
- VV11, VV21, VV31, MN04: condition records
- RSNAST00: process or reprocess output in background
- Determination analysis: why a record was or was not created
Worked example: invoice not printed
A user reports that invoice 90012345 did not print. NAST with KAPPL V3, OBJKY 0090012345 shows KSCHL RD00, NACHA 1, VSTAT 0 and dispatch time 1. Nothing is wrong with the form: the record waits for RSNAST00, which is not scheduled for V3 in this client. If VSTAT is 2, open the processing log from VF02 output screen or read CMFP with NR = NAST-CMFPNR to see the message, often a missing output device or form error. If no NAST row exists, run determination analysis to see which condition record is missing.
Gotchas
OBJKY is character, so selections must use the padded number. A repeated output creates a new NAST row rather than updating the old one, so expect several rows per document. EDI output (medium 6) succeeds in NAST when the IDoc is created, not when it reaches the partner; check WE02 for IDoc status. Changing SAP standard forms or RVADIN01 directly is a modification; copy to Z names and point TNAPR at them. In S/4HANA, BRF+ output management can replace NAST for some documents, which this table does not cover.
Frequently Asked Questions
Which table stores output in SAP SD?
NAST stores the output status records for sales orders, deliveries, billing and purchasing documents, keyed by application (KAPPL), object key (OBJKY), output type (KSCHL), language and partner. TNAPR holds the processing program and form per output type and medium.
Which table stores output types in SAP?
Output types are condition types with usage B in T685, with additional default data such as dispatch time and medium in T685B. Processing programs and forms are in TNAPR. All are maintained in NACE by application.
What do the NAST VSTAT values mean?
VSTAT 0 means not processed yet (often waiting for RSNAST00 because of dispatch time), 1 means successfully processed and 2 means processed with errors. For errors, NAST-CMFPNR points to the message log in CMFP, also visible in the document's output processing log.
What are the output medium codes in NAST?
NACHA values: 1 print output, 2 fax, 4 telex, 5 external send, 6 EDI, 7 simple mail, 8 special function, 9 events (workflow), A distribution (ALE) and T tasks (workflow). The medium decides which TNAPR row and program run.
If you want support staff to ask why an invoice or PO did not go out and get the NAST and log answer in plain English on your own servers, we can build that.
Related Tools
SAP Output Determination Checklist
A checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices.
SAPSAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
Lookup table of the classic SD user exit FORM routines for sales orders, deliveries and billing on SAP ECC 6.0: include, transaction, when it fires, structures available and the usual gotcha.
SAPSAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
Reference of the tables behind SM37 on SAP ECC 6.0: job header, steps, schedules, events, spool and variants, with joins, plus the TBTCO-STATUS values.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
- SAP ECC Movement Type to OBYC Transaction Key and GBB Account Modifier Reference
- SAP ECC 6.0 Enhancement Packages and Maintenance Dates Reference (EHP1 to EHP8, 2027, 2030, 2033)
- SAP ECC ORDERS05 IDoc Segments and Qualifiers Reference
Keep exploring
Free tools
- SAP Output Determination ChecklistA checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices.
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)Reference of the tables behind SM37 on SAP ECC 6.0: job header, steps, schedules, events, spool and variants, with joins, plus the TBTCO-STATUS values.
- SAP ECC MRP Tables and MRP Element (DELKZ) Codes ReferenceThe SAP ECC tables behind MRP (planning file, MRP areas, controllers, groups, planned orders) and the DELKZ codes for each MRP element with its source table.
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.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
- SAP MM price determination: pricing procedure, condition types and fixing wrong PO pricesHow SAP MM determines purchase prices: the RM0000 calculation schema, condition types like PB00, schema determination, and how to fix a wrong price in ME21N.
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 connect Power BI to SAP ECC 6.0Connect Power BI to SAP ECC 6.0: SAP ERP connector, BW and warehouse options, on-prem data gateway, key manufacturing dashboards, and adding natural-language Q&A.