START_FORM — Start a SAPscript Form Within an Open Output Session

Starts a SAPscript form, optionally allowing multiple form instances to be written in one OPEN_FORM output session. It establishes the active form/page context for subsequent WRITE_FORM calls and is paired with END_FORM before another form instance or CLOSE_FORM. Use it only inside the runtime it was designed for: frontend, application server, spool, form composer, SAPoffice, or Application Log. The function does not automatically provide the business authorization, retention, content security, or transaction semantics of the application that calls it.

The page records only high-value interface elements. Exact typing, optional flags, and table structures must be taken from the active SE37 signature before implementation because these classic Basis/ABAP services have accumulated release-specific options.

Technical failures in these services are usually actionable and should not be collapsed into OTHERS. Preserve enough context to distinguish missing configuration from authorization, frontend/runtime availability, data conversion, or persistence problems.

Identify the runtime first: dialog versus background, frontend versus application server, text versus binary, and in-memory versus persisted state. Call with the smallest required dataset, check the returned handle/ID/length, and perform follow-on close/save/dispatch steps only in the documented sequence. Never make a destructive file or repository call from unchecked user input.

For multi-form SAPscript output, confirm OPEN_FORM has already initialized the output session, then select the correct form and language for the first form instance. START_FORM and END_FORM bound one form within the active session; mixing different form layouts without resetting the expected window state can change the output. In a test print, verify each form begins where intended and the final CLOSE_FORM completes the request. A generated spool identifier proves that output was queued, not that a physical printer successfully produced pages.

It remains part of legacy SAPscript processing in S/4HANA; new output should use supported modern form technologies. A function module being present in S/4HANA does not make it an ABAP Cloud-released API. For new clean-core work, prefer released classes, form/output services, content APIs, or Integration Suite patterns where SAP provides them.

ABAP owns correct lifecycle, typing, and exception handling. Basis owns spool devices, filesystem access, SAPconnect, ADS, and platform services. Functional/output teams own form choice and business content. Security/compliance owners define whether files, emails, attachments, or logs are permitted to contain the data being processed.

Inspect START_FORM in SE37 and TFDIR first. Then follow the relevant operational monitor: SP01 for spool, SMARTFORMS or SFP for forms, SCOT/SOST for outbound mail, SLG1 with BALHDR/BALDAT for Application Log, or the application-server/frontend file context for file utilities.