SD / O2Cintermediate

SD Output Management Part 3: S/4HANA Output Management with BRF+

Key takeaway

Configure S/4HANA output management (output control): output types, BRF+ output parameter determination (output type, receiver, channel, printer, email, form template), Adobe form templates with Adobe Document Services, activating the framework per application object, and viewing output items in documents.

Explanation

📌 KEY POINTS
✅ S/4HANA output management uses output types plus BRF+ decision tables (output parameter determination) instead of NAST condition records.
✅ Determination steps: output type, receiver, channel, printer settings, email settings/receivers, form template (and output relevance).
✅ Forms are Adobe form templates rendered by Adobe Document Services (ADS); email templates for mail bodies.
✅ The framework is activated per application object type (e.g. billing document, sales document, delivery) — NAST remains possible where not switched.
⚠️ Missing BRF+ rows for a sales org or document type means no output — silently, unless monitored.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered NAST. Now the S/4HANA framework.

━━━━━━━━━━━━━━━━━━━━
▶ 1. OUTPUT CONTROL SETUP

Define output types per application object type (e.g. BILLING_DOCUMENT).
Assign form templates, email templates, channels allowed.

━━━━━━━━━━━━━━━━━━━━
▶ 2. BRF+ DETERMINATION

App "Output Parameter Determination" (names per release).
Decision tables per step with conditions (sales org, document type, customer, country…).

━━━━━━━━━━━━━━━━━━━━
▶ 3. STEPS

Output type: which outputs for this document.
Receiver: partner role.
Channel: print, email, XML, IDoc.
Printer/email settings, form template.

━━━━━━━━━━━━━━━━━━━━
▶ 4. FORMS AND ADS

Adobe form templates (fragment-based or standard).
Adobe Document Services must be configured (on-premise or cloud).

━━━━━━━━━━━━━━━━━━━━
▶ 5. ACTIVATION AND DOCUMENTS

Application object type activation decides NAST vs new OM.
Output items shown in the document; status and reprocessing.

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

Check activation for billing documents.
Maintain BRF+ tables for invoice output type.
Assign form template and printer.
Create an invoice and check the output item.

✅ CHECKPOINT: the invoice is emailed as PDF with the correct form and the output item shows success.

Code example

ABAP Code

===== STEP 1: activation =====SPRO > Cross-Application Components > Output Control > Manage Application Object Type ActivationBILLING_DOCUMENT → S/4HANA output management | SALES_DOCUMENT / OUTBOUND_DELIVERY → per project decision ===== STEP 2: BRF+ output parameter determination (decision tables) =====Output Type : Sales Org 1000, Billing Type F2 → BILLING_DOCUMENT (invoice)Receiver    : partner role BP (bill-to)Channel     : customer group 01 → EMAIL; else → PRINTPrinter     : output type + sales org → printer LP01Email       : sender, templateForm Template: country DE → ZINV_DE; else → SDBIL_CI_STANDARD (example) ===== STEP 3: forms =====Adobe form templates + Adobe Document Services (ADS) | email templates for body text

Real project scenario

A consumer goods company went live on S/4HANA with new output management for invoices. Three countries received no invoices: BRF+ tables contained rows only for the pilot sales org. Adding rows and a default fallback row, plus a daily report of billing documents without output items, closed the gap before month-end.

Common mistakes

Missing BRF+ rows for new sales orgs or document types.
ADS not configured, so forms fail.
Mixing NAST and new OM without documentation.
No fallback rules.
Hard-coding logic in forms instead of determination.

Best practices

Maintain BRF+ tables centrally with fallbacks.
Configure and monitor ADS.
Document activation per application object.
Keep forms simple, logic in determination.
Monitor documents without output.

Interview angle

Questions: "How does S/4HANA output management work?", "What are the BRF+ determination steps?", "What is needed for Adobe forms?"
Strong answer: output types per application object, BRF+ output parameter determination steps (type, receiver, channel, printer, email, form), Adobe forms with ADS, activation per object type, output items and status.

Practice this lesson

Quick check

1. Which determination steps exist in S/4HANA output parameter determination?

2. How is it decided whether a document type uses NAST or S/4HANA output management?

3. After go-live with S/4HANA output management, invoices for two sales orgs produce no output. What is the most likely cause?

Interview questions

1. Design BRF+ output parameter determination for invoices in five countries with email for most customers, EDI for key accounts and country-specific forms.

Answer it in your own words first, then compare.

2. A global rollout requires that invoice output (print/PDF/EDI) be triggered only after the billing document successfully posts to FI, but currently some outputs fire before FI posting completes, causing customer complaints about mismatched documents. How would you architect a fix?

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.