# SAP SD Output Tables: NAST, TNAPR, Applications, Media and Output Types

> Source: https://netray.co/tools/sap-ecc-output-determination-nast-tnapr-tables-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Reference of NAST-based output control on SAP ECC 6.0: tables, application codes, transmission media, processing status values and standard output types with driver programs.

## Category

sap

## Erp

SAP ECC 6.0

## Audience

- SAP SD consultant
- ABAP developer
- SAP support analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Section

**Key:** section

**Type:** text

#### Code or table

**Key:** code

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### Key fields or program

**Key:** keys

**Type:** text

#### Where maintained

**Key:** where

**Type:** text

#### Note

**Key:** note

**Type:** text

**Rows:**

**Section:** Tables

**Code:** NAST

**Meaning:** Output status records, one per output per document

**Keys:** KAPPL, OBJKY, KSCHL, SPRAS, PARNR, PARVW, ERDAT, ERUHR; NACHA, VSTAT, DATVR, UHRVR, CMFPNR

**Where:** Created by determination or manually in VA02, VL02N, VF02, ME22N output screens

**Note:** OBJKY holds the document number (e.g. VBELN padded)

**Section:** Tables

**Code:** TNAPR

**Meaning:** Processing programs and forms per output type and medium

**Keys:** KAPPL, KSCHL, NACHA; PGNAM, RONAM, FONAM, SFORM

**Where:** NACE > Output types > Processing routines

**Note:** FONAM is a SAPscript form, SFORM a Smart Form or PDF form

**Section:** Tables

**Code:** T685

**Meaning:** Condition types, including output types (usage B)

**Keys:** KVEWE, KAPPL, KSCHL

**Where:** NACE > Output types

**Note:** Output types share the condition technique with pricing

**Section:** Tables

**Code:** T685B

**Meaning:** Additional output type data: dispatch time, medium, partner

**Keys:** KAPPL, KSCHL; VSZTP (dispatch time), NACHA (medium), PARVW (partner function), PARAB (partner-independent)

**Where:** NACE > Output types > Default values

**Note:** Defaults copied into new NAST records

**Section:** Tables

**Code:** T683

**Meaning:** Procedures (output determination procedures for usage B)

**Keys:** KVEWE, KAPPL, KALSM

**Where:** NACE > Procedures

**Note:** Assigned to order, delivery or billing types

**Section:** Tables

**Code:** T682

**Meaning:** Access sequences

**Keys:** KVEWE, KAPPL, KOZGF

**Where:** NACE > Access sequences

**Note:** Sequence of condition tables searched

**Section:** Tables

**Code:** Bnnn

**Meaning:** Output condition tables holding condition records

**Keys:** KAPPL, KSCHL, key fields of the table

**Where:** VV11/VV12 (sales), VV21 (shipping), VV31 (billing), MN04 (PO); or NACE > Condition records

**Note:** Find the table number in the access sequence

**Section:** Tables

**Code:** CMFP

**Meaning:** Collected error messages from output processing

**Keys:** APLID, NR, MSGTY, MSGNR, MSGV1

**Where:** Read via output processing log in the document output screen

**Note:** NAST-CMFPNR points to CMFP-NR

**Section:** Applications (KAPPL)

**Code:** V1

**Meaning:** Sales

**Keys:** Order confirmation BA00

**Where:** NACE

**Note:** Sales documents VA01 to VA03

**Section:** Applications (KAPPL)

**Code:** V2

**Meaning:** Shipping

**Keys:** Delivery note LD00

**Where:** NACE

**Note:** Outbound deliveries

**Section:** Applications (KAPPL)

**Code:** V3

**Meaning:** Billing

**Keys:** Invoice RD00

**Where:** NACE

**Note:** Billing documents

**Section:** Applications (KAPPL)

**Code:** V5

**Meaning:** Groups

**Keys:** Group output for collective processing

**Where:** NACE

**Note:** Used with VG01 groups

**Section:** Applications (KAPPL)

**Code:** V7

**Meaning:** Transport

**Keys:** Shipment documents

**Where:** NACE

**Note:** VT01N shipments

**Section:** Applications (KAPPL)

**Code:** EA

**Meaning:** Purchasing RFQ

**Keys:** RFQ output

**Where:** NACE

**Note:** ME41 to ME43

**Section:** Applications (KAPPL)

**Code:** EF

**Meaning:** Purchase order

**Keys:** NEU

**Where:** NACE, MN04 to MN06

**Note:** ME21N to ME23N

**Section:** Applications (KAPPL)

**Code:** EL

**Meaning:** Purchasing scheduling agreement

**Keys:** Delivery schedule output

**Where:** NACE

**Note:** ME38, ME9E

**Section:** Applications (KAPPL)

**Code:** EV

**Meaning:** Purchasing outline agreement

**Keys:** Contract output

**Where:** NACE

**Note:** ME31K

**Section:** Applications (KAPPL)

**Code:** ME

**Meaning:** Inventory management

**Keys:** GR/GI slips WE01, WE02, WE03

**Where:** NACE

**Note:** Material document output

**Section:** Media (NACHA)

**Code:** 1

**Meaning:** Print output

**Keys:** Spool via LDEST

**Where:** TNAPR, NAST

**Note:** Most common

**Section:** Media (NACHA)

**Code:** 2

**Meaning:** Fax

**Keys:** SAPconnect

**Where:** TNAPR, NAST

**Note:** Needs fax number on partner

**Section:** Media (NACHA)

**Code:** 5

**Meaning:** External send

**Keys:** SAPconnect (mail, fax)

**Where:** TNAPR, NAST

**Note:** Common for PDF by email

**Section:** Media (NACHA)

**Code:** 6

**Meaning:** EDI

**Keys:** IDoc via partner profile WE20

**Where:** TNAPR, NAST

**Note:** Program RSNASTED with routine EDI_PROCESSING

**Section:** Media (NACHA)

**Code:** 7

**Meaning:** Simple mail

**Keys:** SAP office mail

**Where:** TNAPR, NAST

**Note:** Internal notification

**Section:** Media (NACHA)

**Code:** 8

**Meaning:** Special function

**Keys:** Custom routine in TNAPR

**Where:** TNAPR, NAST

**Note:** Used for custom processing

**Section:** Media (NACHA)

**Code:** 9

**Meaning:** Events (SAP Business Workflow)

**Keys:** Workflow event

**Where:** TNAPR, NAST

**Note:** Triggers a workflow event

**Section:** Media (NACHA)

**Code:** A

**Meaning:** Distribution (ALE)

**Keys:** ALE distribution model

**Where:** TNAPR, NAST

**Note:** Program RSNASTED

**Section:** Media (NACHA)

**Code:** T

**Meaning:** Tasks (SAP Business Workflow)

**Keys:** Workflow task

**Where:** TNAPR, NAST

**Note:** Starts a workflow task

**Section:** Processing status (VSTAT)

**Code:** 0

**Meaning:** Not processed

**Keys:** Waiting for dispatch time or RSNAST00

**Where:** NAST

**Note:** Dispatch time 1 or 2 records wait for RSNAST00

**Section:** Processing status (VSTAT)

**Code:** 1

**Meaning:** Successfully processed

**Keys:** DATVR, UHRVR set

**Where:** NAST

**Note:** Repeat output creates a new record

**Section:** Processing status (VSTAT)

**Code:** 2

**Meaning:** Incorrectly processed

**Keys:** Errors in CMFP

**Where:** NAST

**Note:** Check the processing log

**Section:** Standard output types

**Code:** BA00

**Meaning:** Order confirmation (V1)

**Keys:** RVADOR01, routine ENTRY, form RVORDER01

**Where:** NACE V1

**Note:** Copy to Z before changing

**Section:** Standard output types

**Code:** LD00

**Meaning:** Delivery note (V2)

**Keys:** RVADDN01, routine ENTRY, form RVDELNOTE

**Where:** NACE V2

**Note:** Copy to Z before changing

**Section:** Standard output types

**Code:** RD00

**Meaning:** Invoice (V3)

**Keys:** RVADIN01, routine ENTRY, form RVINVOICE01

**Where:** NACE V3

**Note:** Copy to Z before changing

**Section:** Standard output types

**Code:** NEU

**Meaning:** Purchase order (EF)

**Keys:** SAPFM06P, routine ENTRY_NEU, form MEDRUCK

**Where:** NACE EF

**Note:** Copy to Z before changing

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Which table stores output in SAP SD?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

table for output in sap sd, output type table in sap sd, nast table in sap, tnapr table, tables used in sap sd output, sap nast vstat values, sap output medium codes, sap sd tables pdf

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json