Output management · OPD Guard
Rule change alters the determined outcome
- Default severity
- Info
- Finding code:
- OPD_RULE_CHANGE_ALTERS_OUTCOME
- Engine version:
- 3.0.0
This is an informational finding: it confirms a state or documents a change and needs no fix.
What this finding means
OPD Guard reports this finding with the default severity “Info”.
About the engine: S/4HANA Output Parameter Determination rules & BRFplus
How to fix it
Review the listed inputs whose outcome changes between the baseline and the new decision table version and confirm each change with the business owner before transporting the new version.
How ERP Preflight detects it
The analysis is deterministic: the same exported files and the same knowledge snapshot always produce the same findings. No SAP system connection is required — you upload exports.
- Engine
- OPD Guard
- Accepted formats
- JSON, XML, CSV, XLSX
- What to export
BRFplus output-determination decision tables (CSV with a Step column or '# Step:' sections, XML <Table name=...> export, XLSX with one sheet per step, or JSON {'tables': {step: [rows]}}) plus an optional document 'scenario' with 'expected_determination', a batch 'scenarios' list ([{id, scenario, expected}]), 'baseline_tables' (previous version, for the before/after diff) and a FormDoctor 'form_handoff' block. XML carries batch scenarios as <Scenarios><Scenario id=...>, expectations as <Expected> and the previous version as <BaselineDecisionTables>.
- Required input
- At least one decision table (CSV/XML/XLSX/JSON)
- Evidence
- Each finding points to the artifact path, line and column, the code snippet and the SHA-256 of the uploaded file. Findings without such a pointer are demoted to confidence UNKNOWN.
- Confidence
- The verdict rests on your artifacts only. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN) that shows how strong the evidence is.
- Target releases of the engine
- S4H_2022, S4H_2023, S4HANA_CLOUD_2402, S4HANA_CLOUD_2408
Related findings
- MajorRule change leaves previously determined inputs without a match
- CriticalDetermined output channel is inactive or unsupported
- CriticalOutput determination step has no matching rule
- 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
Terms used on this page
Background reading
- 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.
- Troubleshooting SAP Adobe Forms (XDP) data binding and missing fieldsWhy fields stay blank on printed or emailed PDFs in SAP S/4HANA, how XDP form templates bind to OData or DDIC form data providers, and how to check bindings before transport.