Purpose

This document defines the conversion approach for migrating Sales (V1) and Billing (V3) output condition records from SAP ECC to SAP S/4HANA, based on a new BRF+-driven output management strategy.

This document introduces a new approach to migrating output management, shifting from the legacy ECC output condition record model to a simplified, rules-driven BRF+ framework. It describes the end-to-end migration process, covering data extraction and transformation (by Syniti), functional transformation (by the Functional Team), and loading into BRF+ decision tables (by the functional team)—ensuring alignment with overall project governance and design principles.

New Approach: BRF+ Output Simplification

• Merge multiple legacy ECC output types (e.g., ZC10,ZC11,ZARM...) into a single BRF+-driven output type, e.g. ORDER_CONFIRMATION to simplify maintenance and governance.

• Global template layout per output type (as much as possible)

• Minimize the creation of outputs that are rarely triggered, focusing on high-value and frequently triggered scenarios.

• Avoid using business partners or email addresses as decision table input parameters. Instead, leverage business partner attributes to determine the appropriate outputs and channels. This approach requires that the relevant attributes be maintained during Business Partner migration, aligned with the existing output conditions.

Key Implications:

• There will be no direct one-to-one mapping between ECC output condition records and BRF+ decision tables. Instead, this approach will use a  rules-based model that covers the majority of business scenarios and reduces operational complexity.

• The new model will establish and maintain output determination records—including email recipients, output channels, and Business Partner–related output conditions—within BRF+.

• The transformation builds upon the configuration and master data currently maintained under the Classic Output Management (NAST framework) in ECC, adapting it to the BRF+ governance structure in S/4HANA.

• The tables referenced in this document are intended to illustrate the rationale behind the BRF+ decision tables.

• Similarly, the legacy tables extracted from ECC will not be migrated as-is. Instead, they will serve as a reference to support the migration and transformation of the relevant objects into the S/4HANA target design.

Conversion Scope

The conversion scope covers the extraction, transformation, and loading of output determination data from Classic Output Management (NAST-based framework) into BRF+ Output Parameter Determination (OPD) in S/4HANA, ensuring both initial migration and interim synchronization until full adoption of BRF+ is achieved.

The scope includes:

• Extraction of customer-related output condition records (e.g., for Sales Orders, Scheduling Agreements, Invoice and Credit and Debit memos) from Classic Output Management, including associated communication details such as email addresses, language, and output channels;
• Mapping of Classic condition record keys (application, condition type, key combination) to BRF+ OPD parameters (e.g.,  Document Type, Output Type, Sales Organization,);
• Transformation of medium and dispatch settings from Classic (e.g., NAST medium codes) to BRF+ equivalent channels (e.g., Email, Print, EDI), ensuring compatibility with S/4HANA Output Management settings;
• Initial Load of the transformed dataset into BRF+ Output Parameter Determination using the OPD framework and/or BRF+ application data load methods;
• Validation to ensure that migrated BRF+ records produce identical output results as their Classic counterparts for equivalent sales scenarios.

Out of Scope:

• Migration of output determination for applications outside of sales (e.g., MM Purchasing outputs);
• Migration of outputs no longer managed in S/4: Quotations and Contracts (Managed in Salesforce)
• Migration of output no longer in scope of Sales (V1): SDB outputs (managed in Delivery)
• Modifications to customer master data beyond the email and communication fields required for BRF+;
• Changes to output form templates (Smartforms/Adobe Forms) beyond what is required for enabling BRF+.

The data from legacy system includes:

1. Active output condition records for Sales (Application V1 and V3) linked to customers (Partner Function SP, BP,PY, CONTACTS) with maintained communication details (email address, fax, etc.)
   1. Output types relevant for Sales Orders, Invoices and memos and Scheduling Agreements that are in active use in the business process
2. Records with valid medium settings (e.g., Email, Print, EDI) compatible with S/4HANA BRF+ output channels
3. Active records where the deletion indicator (LOEKZ) is initial.
4. Language assignments that are valid in the target system

The data from legacy system excludes:

1. Obsolete, expired, or logically deleted output condition records
2. Output condition records for customers not in scope of the  CNV-3003 Business Partners - Customer (Sales and Service) - FLCU01 
3. Output condition records  for Sales areas not in scope.
4. Output types not used in the current or target S/4HANA sales processes
5. Records with incomplete or invalid communication data (e.g., missing email for email output medium)
6. Condition records belonging to applications other than sales (e.g., LE, MM, FI outputs)

Data Profiling

The table below based on the entries in the table NAST outlines the legacy configuration values and numbers. Its purpose is to demonstrate how these values inform the design and logic of the BRF+ decision tables. 

In addition, the table figures highlight the data that needs to be extracted from ECC systems, even though it will not be migrated into the target S/4HANA target .

Additional Information

Multi-language Requirement

Output texts and messages will be migrated for all relevant languages (EN, FR, NL, PT, etc.).

Document Management

All deliverables, SQL extractions, and DT Templates will be version-controlled in Confluence and Jira.

Legal Requirement

N/A

Special Requirements

N/A

Target Design

In S/4HANA Output Management (via BRF+), decision tables replace the condition technique. Each BRF+ decision table acts like a flexible rule set:

Input Parameters → Decision Logic → Output Parameters (Result)

They determine:

1. Output Type (e.g., ORDER_CONFIRMATION, BILLING_OUTPUT)
2. Output Channel (Email, Print, EDI, IDoc)
3. Form Template (Adobe Form)
4. Receiver (Partner Function)
5. Language

The decision tables below depict the typical structures of BRF+ tables and are based on the current design within the Toolkit.  Please note that these tables will change once the final design  has been confirmed.

SALES DECISION TABLES:

BILLING DECISION TABLES:

Data Cleansing

N/A

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

All data extracted must be anonymized and handled according to data protection policies.

• Copy 1:1 (keep Legacy)

Extraction

Data will be extracted from ECC using SQL-based queries executed directly on the source database.

The extraction process is required to join those B* condition tables—which contain a link to a business partner (KUNNR, KUNAG, KUNRE, KUNRG) or  contain a large number of entries for a single output type—to the NACH table. This approach enables identification of the output medium and the output language and ensures that all relevant configuration records are captured.

The extracted data will not be migrated directly; instead, it will be used to:

• Update the business partner attributes that determine the appropriate outputs and channels. 
• Populate the data collection files based on the BRF+ decision table setup.

Relevancy criteria will be applied to include only active, valid, and in scope records.

There will therefore be 2 different sets of Data collection Reports (RT)

• An initial set  based on the legacy BXXX tables that will include all relevant information to facilitate the subsequent uploads. It will be referred to "RT_OUTPUT_CONDITIONS"
  • The RT_OUTPUT_CONDITIONS can be used in CNV-3003 Business Partners - Customer (Sales and Service) - FLCU0  to set up default outputs channels. (TBC)
• A subsequent set of OPD DT tables, referred to as DT_OPD_DECISION_TABLES

Source Tables to be extracted:

Following Bxxx tables relate to output conditions linked to business partners as well as tables with  multiple entries. The whole table needs to be extracted:

BXXX TABLES

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads (relevant sales Organisation

NACH TABLE

Extraction Run Sheet

Selection Screen

RT_OUTPUT_CONDITIONS

The legacy output conditions from the B table will be combined with their  corresponding medium / partner and language from table NACH  in a report Table called RT_OUPUT_CONDITIONS.   An additional column will be added to cater for following exceptions:

• a table / table entry without a Sales organisation
• a table / table entry without a customer 
• A duplicate (or more) entry for a customer number (if possible)

As  we are dealing with multiple tables with different number of fields, the customer number can be in different positions, and have a  different field  name: 

 The customer  in the BXXX table can be 

• KUNNR
• KNDNR
• KUNAG
• KUNRE
• KUNRG
• KUNWE

The customer number field will be referred to at CUSTNO and depending on the B table will be mapped as follows: (eg. B_TABLE-CUSTNO = B_TABLE-KNDNR if table = B001, B006 etc..)

Data Transformation:

RT_OUTPUT_CONDITIONS

The target audience for the Output Conditions Report is:

• the L2C functional team responsible for uploading the various OPD decision tables. These tables will be reviewed by the business.

• the L2C data team as the L2C functional team may need to update the Business Partners sales view. (TBC)
  • Each BP's default Medium will be held in Customer Group 4 (sales) and 5 (billing)  rather than being an entry in the Decision table  (TBC)

  • The extraction will allow the following:

    • a table entry that leads to multiple  output Mediums in NACH for the same partner  
    • a table entry that leads to multiple  output Mediums in NACH and partner depending on the condition type
  • New rules need to be agreed by the business and added to manage multiple table entries 

RT_OPD_DECISION_TABLES

The L2C functional team is responsible for uploading the information in the OPD decision tables. Some tables are mainly replacing the legacy condition configuration, and will be populated with predefined values first for business review and update

BRF+ provides a built-in feature to download and upload decision tables as Excel files. 

Steps:

1. Go to BRF+ application in transaction BRF+ 

2. Open the Decision Table object.

3. From the Table Maintenance screen:

   • Click on “Download to Excel” → system exports the current content and structure.

   • Fill in or update the Excel file offline.

   • Use “Upload from Excel” to import back.

Note: 

• Each table must be handled individually. 
• The creation of Data collection template must be aligned with BRF+ configurations .  For now, the following Templates are based on interim configurations (from S/4HANA sandbox).  This will be replaced once the configuration is ready. The same applies to the contents of the DTs, they are here as examples of how the entries look like and will be replaced by real objects .

1. DT_OUTPUT_TYPE
2. DT_RECEIVER
3. DT_OUTPUT_CHANNEL
4. DT_EMAIL_SETTING
5. DT_EMAIL_RECEIVER
6. DT_OUTPUT_RELEVANCE
7. DT_FORM_TEMPLATE

SALES DECISION TABLES

DT_OUTPUT_TYPE: 

DT Rules:

DT Template: 

DT_RECEIVER: (Partner)

DT Rules:

DT Template:

DT__CHANNEL:     (Medium)

DT Rules:

DT Template:

DT__EMAIL_RECEIVER:

DT Rules:

DT Template:

DT__EMAIL_SETTING:

DT Rules:

DT Template:

DT__OUTPUT_RELEVANCE:

DT Rules:

DT Template:

DT__FORM_TEMPLATE:

DT_Rules

DT Template:

BILLING DECISION TABLES

DT_OUTPUT_TYPE: 

DT Rules:

DT Template: 

DT_RECEIVER: (Partner)

DT Rules:

DT Template:

DT_CHANNEL: (Medium)

DT Rules:

DT_PRINTER

DT Rules:

DT_EMAIL_SETTING

DT Rules:

DT_EMAIL_RECEIVER

DT Rules:

DT_FORM_TEMPLATE: ()

DT Rules:

DT Template:

DT_OUTPUT_RELEVANCE: ()

DT Rules:

DT Template:

Extraction Dependencies

Transformation

There will be no transformation on the legacy data. The data will be used to help design / complete the new decision tables in S/4 Hana.

Transformation Run Sheet

Legacy condition tables setup:

Please note that there is no direct mapping between the output condition types and the BRF+ output types. Not all Communication medium will be used in OPD. The tables below are used as guidelines as how the outputs will be managed in S/4.

Legacy Communication Medium to OPD Channel:

The table below contains  the list of legacy output conditions that were triggered between 1st and 15th Nov 2025. Please also note that conditions no longer associated to V1 have been excluded.  .