Forms · FormDoctor
Binding path not declared in the form interface schema
- Default severity
- Major
- Finding code:
- FORM_BINDING_PATH_NOT_IN_XSD
- Engine version:
- 3.0.0
What this finding means
FormDoctor reports this finding with the default severity “Major”.
About the engine: SAPscript / Smart Forms to Adobe Forms migration validator
How to fix it
The bound path is not part of the form interface (XSD) the data provider publishes, so the binding is not backed by the interface contract. Re-download the current schema of the form data provider and rebind the field to a declared element, or extend the data source so the element becomes part of it.
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
- FormDoctor
- Accepted formats
- XML, TEXT
- What to export
Adobe Form XDP template together with the form's runtime data XML and/or the form interface schema (XSD) (as artifacts, or data XML in raw_content + configuration.xdp_content / xsd_content), or a SAPscript / Smart Forms source (XML export or text). Optional configuration: business_source_fields, custom_fields [{name, form_enabled, context_supports_forms}], data_source {name, extensible}, form_template, output_type.
- Required input
- XDP template AND runtime data XML or form interface XSD (binding verification)
- or a SAPscript / Smart Forms source (legacy form audit)
- 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
- CriticalBound field absent from runtime XML
- MajorBinding namespace cannot be resolved unambiguously
- MajorField binding path does not match runtime XML
- MinorDuplicate field binding
- CriticalRequested field cannot be supplied to the form
- CriticalLegacy SAPscript detected
Terms used on this page
Background reading
- 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.
- 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.
- Custom fields with key user extensibility: why a field does not appear in the app, form or APIHow 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.