ABAP Developmentintermediate

SFP Form Design

Interface, context and layout in three-tier form design.

Explanation

An Adobe Form has three parts: the Interface (import parameters), the Context (bindings between interface and form fields), and the Layout (designed in Adobe LiveCycle Designer). The generated function module receives the interface data and renders the PDF via ADS (Adobe Document Services).

Code example

ABAP Code

CALL FUNCTION 'FP_JOB_OPEN' CHANGING ie_outputparams = ls_out.CALL FUNCTION lv_fm_name EXPORTING /1bcdwb/docparams = ls_docpar                                    is_header       = ls_header.CALL FUNCTION 'FP_JOB_CLOSE'.

Real project scenario

A German insurer replaced 50 SmartForms with Adobe Forms to leverage native barcode support and pixel-accurate print for regulatory filings.

Common mistakes

Missing ADS configuration in SM59 (FP_ICF_DATA_ADS); forgetting FP_JOB_OPEN/CLOSE brackets; embedding logic in layout instead of interface.

Best practices

Keep interface small; move computations to the driver; version the layout with the transport.

Interview angle

How does the generated FM name relate to the form name?