BRFplus
Business Rule Framework plus
SAP’s rules engine for decision tables and expressions. Output determination and many custom business decisions are modelled in it.
A BRFplus decision table maps condition columns — for example document type or sales organisation — to results. In output determination each step returns the first matching row, so a row placed after a more general row can never be reached.
Decision table content is configuration: it is maintained per system and has to be transported consistently to test and production.
In ERP Preflight
OPD Guard reads decision tables exported as CSV, XML, XLSX or JSON, reports gaps, conflicts and unreachable rows and can check expected determinations for given scenarios.
Problems that involve BRFplus
- CriticalOutput determination step has no matching rule
- MinorDecision table row shadowed by an earlier row
- CriticalLegacy SAPscript detected
- CriticalDetermined output channel is inactive or unsupported
- MajorOverlapping decision table rows return different outcomes
- MajorSimulated determination differs from the expected result
- MajorDecision table does not cover a combination of its own condition values
- MajorPRINT channel without a print queue
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Background articles
- How output parameter determination with BRFplus works in SAP S/4HANAWhy 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.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.