How output parameter determination with BRFplus works in SAP S/4HANA
Why a purchase order or billing document produces no output, and how the BRFplus decision tables of S/4HANA output management decide output type, recipient, channel and form.
- Last reviewed:
- Target releases:
- SAP S/4HANA, SAP S/4HANA Cloud
- Version:
- 1
- Source provenance:
- Editorial content, technically reviewed
What output parameter determination does
In SAP S/4HANA output management, the output of a business document (for example a purchase order or a billing document) is controlled by output parameter determination. Instead of the condition technique used by classic NAST-based output control, the parameters are determined by BRFplus decision tables that are maintained per application object type.
The determination is organised in steps. Typical steps are:
- Output type — which outputs are required for the document at all;
- Receiver — who receives the output;
- Channel — for example email, print or XML;
- Printer settings and email settings;
- Form and output relevance — which form template is used and whether an output is relevant at a given point in time.
Why no output is created
When a document is saved without the expected output, the cause is usually one of these:
- The decision table of a step has no matching row for the document's attributes (for example a new sales organisation or document type).
- A step is missing or inactive, so the determination stops before a channel or receiver is found.
- The form template referenced in the table does not exist in the target system or is not assigned to the output type.
- The table content exists in the development system but was not transported consistently to test or production.
How to analyse it
- Compare the attributes of the affected document with the conditions of every determination step, in order.
- Check that the rows are active and that a fallback row exists where one is intended.
- Verify that referenced form templates, email templates and output types exist in the target system.
- Treat decision table content as transportable configuration: review which transport carries which change.
ERP Preflight's OPD Guard parses exported BRFplus/decision table content and reports missing steps, unmatched combinations and dangling references with the exact artifact location as evidence. See Output & Extensibility for the related engines.
This article is general information about SAP concepts and does not replace SAP documentation for your specific release.
Sources
Related solution areas
Related engines: OPD Guard, FormDoctor
Related
SAP problems covered by this article
- CriticalDetermined output channel is inactive or unsupported
- CriticalBound field absent from runtime XML
- CriticalOutput determination step has no matching rule
- CriticalRequested field cannot be supplied to the form
- MajorOverlapping decision table rows return different outcomes
- CriticalLegacy SAPscript detected