Output & Forms

Output problems surface late: the billing document is saved, but no email is sent; the custom field is on the screen, but not on the PDF. The causes sit in determination rules, form templates and extension settings that are rarely checked together.

• OPD Guard

  S/4HANA Output Parameter Determination rules & BRFplus

  OPD_GUARD

• FormDoctor

  SAPscript / Smart Forms to Adobe Forms migration validator

  FORM_DOCTOR

• Custom Field Flow Doctor

  Extension field lineage from CDS views through BAPIs to UI

  CUSTOM_FIELD_FLOW_DOCTOR

• BRFplus determination steps without a matching rule for a document combination
• Form templates referenced in determination but missing in the target system
• Custom fields whose usage for forms, APIs or follow-on documents is not enabled
• Form bindings that point to fields missing from the form’s XML data

• Custom fields with key user extensibility: why a field does not appear in the app, form or API

  How custom fields created with key user extensibility reach UIs, reports, forms and APIs, and why a field that exists on one document is missing on the follow-on document.

• 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.

• Troubleshooting SAP Adobe Forms (XDP) data binding and missing fields

  Why 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.

Which engines does the Output & Forms preflight run?

Output & Forms runs 3 deterministic engines: OPD Guard, FormDoctor, and Custom Field Flow Doctor. Each engine documents its rules and input contract in the engine catalog.

Which files do I need for Output & Forms?

The engines in this area accept these file formats: CSV, JSON, TEXT, XLSX, and XML. You create the exports in SAP and upload them; no direct connection to your SAP system is needed. The outbound-only local agent is optional.

Are the findings produced by AI?

No. Findings come from deterministic rules: identical exports produce identical findings. Where AI helps with explanations, the confidence of that content is capped at INFERRED and marked as such.

How is each finding backed?

Findings reference evidence in the uploaded file: its path, the line and column where the format has them, a redacted snippet and the SHA-256 hash of the file. Each finding carries a confidence class (VERIFIED, RULE_DERIVED, INFERRED or UNKNOWN); findings without verifiable evidence are demoted to UNKNOWN.