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

How SAP Adobe Forms bind data

In SAP S/4HANA output management, Adobe Document Services (ADS) renders PDF documents from an XDP form template and an XML data payload supplied by a form data provider (commonly an OData service based on CDS views or a classic interface).

Each visual element on the form layout uses a dataRef binding path that points to a node or attribute in the data connection schema.

Why fields stay empty or fail at runtime

When a field is populated in the database but missing on the rendered PDF, the cause is usually one of these:

1. Broken dataRef path. A subform or field binds to a node name that was renamed, moved to another hierarchy level or removed from the form data provider.
2. Unbound layout field. The field was placed on the canvas in Adobe LiveCycle Designer with binding set to None instead of Use name or an explicit schema path.
3. Master page vs body page context. Fields on master pages evaluate against the root context unless repeated subform bindings are configured explicitly.
4. Script exceptions in FormCalc or JavaScript. A calculation or visibility script references a null node, halting script execution for subsequent fields on the same subform.

How to verify XDP templates systematically

• Compare every bind.ref expression in the XDP XML against the active schema of the form data provider.
• Check repeating subforms and table rows to ensure their binding includes the wildcard occurrence selector.
• Inspect FormCalc and JavaScript events for null-unsafe property access and hidden visibility overrides.
• Validate that custom fields enabled via key user extensibility are exposed in the form data service and bound in the active template version.

ERP Preflight's Form Doctor parses XDP templates and form data schemas deterministically to report broken bindings, unbound controls and script risks with exact line and snippet evidence. See Output & Extensibility.