FP_JOB_CLOSE — Close an Adobe Form Output Job

Closes the Adobe form output job opened with FP_JOB_OPEN, finalizing spool/PDF/output processing after the generated Adobe form function has been called. It is mandatory lifecycle cleanup and should be reached even when the caller handles form-level errors carefully. 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.

The function remains part of the Adobe form runtime lifecycle in S/4HANA. 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 FP_JOB_CLOSE 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.

FP_JOB_CLOSE completes an Adobe Forms output job after the generated form function runs. A PDF preview working while a background spool remains incomplete can indicate a missing close or incorrect output parameters. Track one FP_JOB_OPEN invocation and the exact number of generated form calls, then execute FP_JOB_CLOSE under the same runtime context; inspect returned status, spool or PDF and ADS errors. Test a normal one-page form, bundled output if supported, and a failure inside the form body requiring safe cleanup. Closing twice or closing without an opened job should not be hidden under a generic OTHERS success path. The final business check confirms the intended document and language were printed or generated exactly once, with output status reconciled in the supported spool monitor and sensitive customer data protected.