SD / O2Cintermediate

SD Output Management Part 2: Classic NAST Output Determination

Key takeaway

Configure classic output: output types, access sequences and condition tables, output determination procedures per document type, condition records (VV11/VV21/VV31), partner function, transmission medium, dispatch time, processing routines (program and form), and the NAST status.

Explanation

📌 KEY POINTS
✅ NAST uses the condition technique: output types with access sequences, condition tables and records.
✅ Output procedures are assigned to document types (sales, delivery, billing) and list the output types to determine.
✅ Condition records define partner function, transmission medium (print, email, EDI) and dispatch time (e.g. immediately on save or by batch).
✅ Processing routines assign print program and form per output type and medium.
⚠️ Output found but not processed usually means dispatch time "by job" without a scheduled job, or a missing processing routine.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced both frameworks. Now classic NAST in detail.

━━━━━━━━━━━━━━━━━━━━
▶ 1. NACE STRUCTURE

Applications: V1 sales, V2 shipping, V3 billing.
Output types, procedures, access sequences, condition tables.

━━━━━━━━━━━━━━━━━━━━
▶ 2. OUTPUT TYPES

BA00 order confirmation, LD00 delivery note, RD00 invoice.
Settings: access sequence, partner functions, default medium, change output behavior.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PROCEDURES AND ASSIGNMENT

Procedure (e.g. V10000 for orders) with output types and requirements.
Assigned to sales document types, delivery types, billing types.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CONDITION RECORDS

VV11 (sales), VV21 (shipping), VV31 (billing).
Key e.g. sales org + customer; partner function, medium, dispatch time, printer, language.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PROCESSING ROUTINES

Per output type + medium: program (e.g. RVADOR01, RVADDN01, RVADIN01) and form (SAPscript/Smart Form/Adobe).
NAST stores output entries and status (processed, error, not processed).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Check RD00 in NACE (V3) and its processing routines.
Maintain VV31 condition record for a customer with medium print, dispatch immediate.
Create an invoice and check output status.
Change dispatch to "by job" and run the output program (e.g. RSNAST00).

✅ CHECKPOINT: the invoice prints on save and the NAST entry shows status processed.

Code example

ABAP Code

===== STEP 1: NACE =====NACE > V1 Sales: BA00 | V2 Shipping: LD00 | V3 Billing: RD00Output type → access sequence → condition tables (e.g. sales org/customer)Procedure V10000 (orders) → assigned to order types ===== STEP 2: condition records =====VV11 (sales) | VV21 (shipping) | VV31 (billing)Key: SOrg 1000 + customer 1000345 → partner function BP, medium 1 print, dispatch time 4 (immediately), printer LOCL ===== STEP 3: processing routines (NACE > output type > processing routines) =====Medium 1 print: program RVADIN01 | form (SAPscript/Smart Form/Adobe)Medium 5 external send (email) | medium 6 EDI ===== STEP 4: batch processing =====Dispatch time 1 → program RSNAST00 job | NAST table for status

Real project scenario

A distribution company configured delivery notes with dispatch time "send with periodically scheduled job" to print in batches for the warehouse, but no job existed in production. Delivery notes stayed unprocessed; trucks left without papers for two days. Scheduling RSNAST00 every 10 minutes for the delivery application and adding a monitor for unprocessed NAST entries resolved it.

Common mistakes

Dispatch time by job without a scheduled job.
Missing processing routine for a medium.
Condition records without partner function or language.
Procedure not assigned to new document types.
Duplicate output after document changes.

Best practices

Align dispatch time with operational need.
Schedule and monitor output jobs.
Maintain records by business keys, not per customer where possible.
Include output in document type checklists.
Control repeat output in output type settings.

Interview angle

Questions: "How is output determined in NAST?", "What are VV11/VV21/VV31?", "Why is output found but not printed?"
Strong answer: output types, access sequences, procedures assigned to document types, condition records with partner, medium, dispatch time, processing routines (program/form), NAST status; batch dispatch needs RSNAST00 jobs.

Practice this lesson

Quick check

1. In NAST, where do you maintain which customer gets invoices by email?

2. Delivery notes are determined in NAST but never printed. Dispatch time is "send with periodically scheduled job". What is missing?

3. What does the processing routine of a NAST output type define?

Interview questions

1. A customer complains that order confirmation output stopped triggering for orders created via a Fiori app, though it works fine when created via VA01. How would you investigate?

Answer it in your own words first, then compare.

2. A new billing type ZF2 was created, but no invoice output is determined in the NAST-based system. What do you check?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.