Output management · OPD Guard
Decision table does not cover a combination of its own condition values
- Default severity
- Major
- Finding code:
- OPD_INCOMPLETE_COVERAGE
- Engine version:
- 3.0.0
What this finding means
OPD Guard reports this finding with the default severity “Major”.
About the engine: S/4HANA Output Parameter Determination rules & BRFplus
How to fix it
Add a row for the uncovered combination (the witness lists the condition values) or a wildcard fallback row; the listed documents are output-relevant but no row of this step matches them.
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
- CriticalOutput determination step has no matching rule
- MajorSimulated determination differs from the expected result
- MinorDecision table has no default (catch-all) rule
- CriticalDetermined output channel is inactive or unsupported
- MajorOverlapping decision table rows return different outcomes
- MajorPRINT channel without a print queue
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.