Output & extensibility
SAP form problems: Adobe Forms bindings and legacy forms
FormDoctor compares an Adobe Form template (XDP) with the form’s runtime data XML and/or interface schema, and detects legacy SAPscript and Smart Forms that have to be migrated.
Detected by:FormDoctor
Documented problems
- CriticalBound field absent from runtime XML
FORM_FIELD_MISSING_IN_XML
- CriticalRequested field cannot be supplied to the form
FORM_FIELD_UNSUPPORTED
- CriticalLegacy SAPscript detected
FORM_LEGACY_SAPSCRIPT_DETECTED
- CriticalLegacy Smart Form detected
FORM_LEGACY_SMARTFORM_DETECTED
- MajorBinding namespace cannot be resolved unambiguously
FORM_BINDING_NAMESPACE_UNRESOLVED
- MajorField binding path does not match runtime XML
FORM_BINDING_PATH_MISMATCH
- MajorBinding path not declared in the form interface schema
FORM_BINDING_PATH_NOT_IN_XSD
- MajorField format does not match the bound data type
FORM_BINDING_TYPE_MISMATCH
- MajorField declared by the form interface but not populated
FORM_FIELD_NEEDS_BADI
- MajorRequested field does not exist in the business source
FORM_FIELD_NEEDS_CUSTOM_FIELD
- MajorField exists in the business source but not in the form data source
FORM_FIELD_NEEDS_DATA_SOURCE_EXTENSION
- MinorDuplicate field binding
FORM_DUPLICATE_BINDING
- MinorBound field hidden in layout
FORM_FIELD_HIDDEN_IN_LAYOUT
Terms used in this area
Background articles
- 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.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.