Study guide

9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST

SAP S/4HANA Sales C_TS462

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure

1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration

2 Chapter 2: The Order-to-Cash Process and Sales Master Data

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements

3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries

4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs

4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders

5 Chapter 5: Pricing and the Condition Technique

5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement

6 Chapter 6: Availability Check (ATP) and Delivery Scheduling

6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

7 Chapter 7: Delivery Processing and Embedded EWM

7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries

8 Chapter 8: Billing and Integration with Financial Accounting

8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output

9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables

10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core

10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels

11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition

11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM

9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST

Key Takeaways Explain This Topic AI

SAP S/4HANA introduces modern Output Parameter Determination (OPD) powered by BRFplus decision tables, replacing the classical NAST condition technique for order and billing documents.

Output parameter determination has eight determination steps (output type, recipient, channel, printer settings, email settings, email recipient, form template, output relevance), each with its own decision table.

Form templates combine a data source (OData service) with an Adobe LiveCycle layout; SAP S/4HANA Output Management supports SAPscript, Smart Forms, and PDF-based forms, and recommends PDF-based print forms with fragments.

The Master Form Template architecture standardizes corporate branding—logos, headers, and legal footer blocks—allowing application forms to focus strictly on transactional payloads.

SAP S/4HANA Output Management is active by default; for sales documents it can be deactivated per application object type (for example SALES_DOCUMENT) to use condition-technique output determination, and the change applies only to new documents.

Last updated: October 2026

Output Management: Modern BRFplus Architecture and Migration from Classical NAST

In enterprise Order-to-Cash processing, generating business correspondence—order confirmations, delivery notes, packing lists, commercial invoices, and electronic data interchange (EDI) dispatches—is critical to commercial operations. For over three decades in SAP R/3 and ECC, output was governed exclusively by the classical NAST message control framework.

With the architectural evolution to SAP S/4HANA , SAP introduced a redesigned output management framework (SAP S/4HANA Output Management, component CA-GTF-OC ) powered by Business Rules Framework Plus (BRFplus) and configured via central transaction OPD ( Output Parameter Determination ). Understanding modern output management, its decision table hierarchy, its Adobe Document Services (ADS) integration, and its migration coexistence with NAST is a cornerstone of the S/4HANA Sales certification.

Classical NAST vs. Modern S/4HANA Output Management

To grasp why S/4HANA overhauled output management, one must contrast the legacy and modern architectures: ┌─────────────────────────────────────────┐ ┌─────────────────────────────────────────┐

  • │ CLASSICAL NAST FRAMEWORK │ │ MODERN BRFplus / OPD FRAMEWORK │
  • │ • Relational Table NAST │ │ • Business Rules Framework Plus (OPD) │
  • │ • Condition Technique (VV11, VV31) │ │ • Decision Tables (Sequential Steps) │
  • │ • ABAP Print Driver Programs (TNAPR) │ vs. │ • Core Data Services (CDS Views) │
  • │ • SAPscript & Smart Forms │ │ • Adobe Document Services (ADS / PDF) │
  • │ • Dispatch Job: RSNAST00 │ │ • Asynchronous BgRFC & Cloud-Ready │
  • │ • Separate setup per applicatio │ │ • Master Form / Content Form Separation │
  • └─────────────────────────────────────────┘ └─────────────────────────────────────────┘
  • Limits of Classical NAST

Separate setup per application : Each application had its own output determination with condition records, print programs, and forms, so similar outputs were configured several times.

Coupled print programs and forms : Data retrieval and layout logic were often combined in driver programs ( TNAPR ) and SAPscript or Smart Forms, which made changes and extensions harder.

No use in the public cloud : SAP S/4HANA Cloud Public Edition supports only SAP S/4HANA Output Management.

Advantages of Modern S/4HANA Output Management

Business Rules Driven : Business analysts configure and adjust business rules in BRFplus decision tables ( OPD ) without writing ABAP code or transporting condition records.

Extensibility : Broad use of CDS views and form data services, and a unified solution across SD, MM, FIN, and other applications.

Channels : For sales documents, PRINT , EMAIL , and EDI (IDoc or SOA/XML messages); state-of-the-art email support with templates and multiple recipients.

SAP Fiori integration : Output items can be checked and previewed directly in the sales document apps.

Architecture of Output Parameter Determination (Transaction OPD)

The administrative cockpit for modern output management is transaction OPD (Output Parameter Determination). OPD evaluates business rules through a series of BRFplus Decision Tables executed in strict sequence for each Application Object Type (e.g. SALES_DOCUMENT , BILLING_DOCUMENT ): Transaction OPD: Decision Table Hierarchy

  • │
  • Step 1: Output Type (e.g., ORDER_CONFIRMATION, BILLING_DOCUMENT)
  • │
  • Step 2: Receiver (e.g., Partner Function SP, BP, PY)
  • │
  • Step 3: Channel (e.g., PRINT, EMAIL, EDI)
  • │
  • Step 4: Printer Settings (PRINT channel: printer, number of copies)
  • Step 5: Email Settings (EMAIL channel: sender, email template)
  • │
  • Step 6: Email Recipient (e.g., email address, TO/CC/BCC)
  • │
  • Step 7: Form Template (form and master form template)
  • │
  • Step 8: Output Relevance (e.g., only complete documents)
  • The Step-by-Step Decision Table Evaluation Trace
  • 1. Output Type

Determines which commercial business document type is triggered. For application object SALES_DOCUMENT , condition rows evaluate document category and sales document type ( OR , QT , IN ) to determine output type ORDER_CONFIRMATION .

2. Receiver

Identifies who receives the document by querying the document's partner functions. For an order confirmation, the receiver is typically the Sold-to Party ( SP ); for a billing document, it is the Bill-to Party ( BP ) or Payer ( PY ).

3. Channel

Determines the transmission medium for each receiver. Possible channels include:

PRINT — Physical spool output via ADS.

EMAIL — Automated email dispatch with PDF attachment.

EDI — Messages as IDoc or SOA (XML) message. According to the official course, the IDoc format is intended only for internal billing, and the XML format is designed for integration with SAP Ariba.

4. Printer Settings / Email Settings

Depending on the active channel, the system evaluates secondary decision tables:

For PRINT : Evaluates the output printer queue (e.g. LP01 ), number of copies, and print immediately flags.

For EMAIL : Derives the sender email address and the email template.

5. Email Receiver

When the EMAIL channel is selected, this table maps the recipient partner function's email address from the Business Partner master data ( BUT000 / ADR6 ) and designates whether they are placed on the TO , CC , or BCC line.

6. Form Template

Assigns the form template (and master form template) to use, for example depending on the sales organization and document type.

7. Output Relevance (Gatekeeper Step)

The final and most critical evaluation step. Output Relevance acts as an automated boolean filter ( TRUE / FALSE ). Even if all preceding tables determine an output type and channel, the document will not be emitted if the output relevance rule evaluates to FALSE .

Example Rules from the official course : issue outputs only for complete documents (incompleteness check), or issue no output if the materials are not available (availability check). An output item that is not relevant stays in preparation .

Form Templates and the Master Form Architecture

In classical ERP, each company modified independent Smart Forms or SAPscript forms, resulting in duplicate headers, logos, and bank footers across dozens of separate documents. In S/4HANA, output formatting is decoupled into two structural layers: ┌────────────────────────────────────────────────────────────────────────┐

  • │ MASTER FORM TEMPLATE │
  • │ ┌──────────────────────────────────────────────────────────────────┐ │
  • │ │ Corporate Logo Sender Address Header │ │
  • │ └──────────────────────────────────────────────────────────────────┘ │
  • │ ┌──────────────────────────────────────────────────────────────────┐ │
  • │ │ Recipient Address Window (Fold-Mark Compliant) │ │
  • │ └──────────────────────────────────────────────────────────────────┘ │
  • │ ┌──────────────────────────────────────────────────────────────────┐ │
  • │ │ │ │
  • │ │ APPLICATION CONTENT FORM TEMPLATE │ │
  • │ │ (e.g., SD_SLS_ORDER_CONF) │ │
  • │ │ │ │
  • │ │ • Sales Order Number & Date │ │
  • │ │ • Line Item Table: Material, Qty, Unit Price, Net Value │ │
  • │ │ • Pricing Condition Breakdown & Tax Summary │ │
  • │ │ │ │
  • │ └──────────────────────────────────────────────────────────────────┘ │
  • │ ┌──────────────────────────────────────────────────────────────────┐ │
  • │ │ Corporate Footer: Bank Accounts, IBAN/BIC, VAT IDs, Legal Reg │ │
  • │ └──────────────────────────────────────────────────────────────────┘ │
  • └────────────────────────────────────────────────────────────────────────┘
  • 1. Master Form Template

Defines the unified corporate identity: company logo, top sender line, recipient address window (positioned for standard windowed envelopes), and multi-column footer blocks (bank accounts, IBAN/BIC, commercial register numbers, VAT IDs, executive board names).

Evaluated dynamically in BRFplus based on Company Code, Sales Organization, or Country.

2. Application Content Form Template

Contains purely transaction-specific payload tables: document number, purchase order reference, line item grid (materials, descriptions, quantities, net prices, delivery dates), tax totals, and item notes.

Content forms are designed with Adobe LiveCycle Designer.

3. Data Source and Supported Form Technologies

A form template used to generate a PDF contains a data source (OData service) and a layout (Adobe LiveCycle Designer document) . At runtime, the OData service reads the document data and the result is merged with the layout to render the PDF. SAP S/4HANA Output Management supports the classic form technologies SAPscript, Smart Forms, and PDF-based print forms without fragments , plus PDF-based print forms with fragments , which SAP recommends. The forms and their print programs must be compatible with Output Management.

Coexistence and Migration from NAST to BRFplus

A critical exam topic is managing the transition from legacy NAST to modern BRFplus:

Public Cloud vs. On-Premise / Private Cloud

SAP S/4HANA Cloud Public Edition : Exclusively utilizes modern BRFplus output management ( OPD ). Classical NAST is completely removed.

SAP S/4HANA On-Premise & Cloud Private Edition : Supports dual coexistence . Customers can choose on an application-by-application basis whether to use modern BRFplus or retain legacy NAST.

Managing Coexistence in Customizing

In SPRO under Cross-Application Components → \rightarrow → Output Control → \rightarrow → Manage Application Object Type Activation , administrators manage the active framework per application object type. SAP S/4HANA Output Management is active by default; a change of the activation status applies only to new documents, while existing documents keep the framework that was active when they were created. For billing documents, Output Management is also the default, and NAST can be enabled again with a specific Customizing parameter (SAP Note 2267376). The table shows an example landscape:

  • Application Object Type Description Status in Customizing Active Output Framework
  • SALES_DOCUMENT Sales Inquiries, Quotes, Orders Active Modern BRFplus ( OPD )
  • BILLING_DOCUMENT Customer Invoices, Credit Memos Deactivated Classical NAST ( VV31 / NAST )
  • OUTBOUND_DELIVERY Shipping Deliveries, Picking Lists Deactivated Classical NAST ( VV21 / NAST )

Warning

If Output Management is active for an application object type, output condition records of the condition-technique framework (such as VV11 for sales documents) are not used for new documents of that object type. Existing Smart Forms or SAPscript forms are not automatically lost: they can be used in Output Management if they and their print programs are compatible with it.

Migration Strategy for Brownfield Implementations

Enterprises with extensive libraries of custom Smart Forms often execute a phased migration:

Keep NAST for billing documents during the initial go-live if the existing output programs are not yet compatible with Output Management.

Activate SALES_DOCUMENT for modern output to leverage BRFplus automated PDF emailing for sales order confirmations.

Gradually move forms to PDF-based print forms with fragments, test them, and activate Output Management for the remaining object types.

Loading diagram... S/4HANA Modern Output Management OPD Execution Flow