ERPClimb logoERPClimb
Login
SAP function moduleObjectSSF_FIELD_LISTModuleABAP

SSF_FIELD_LIST — Read the Parameters Actually Used by a Smart Form

Returns information about form-interface fields actually referenced by a Smart Form so a driver can limit data selection or perform technical analysis. SAP documents it as an optional helper before calling SSF_FUNCTION_MODULE_NAME and the generated form function. It is metadata assistance, not a substitute for the Smart Form's declared interface.

Practitioner reference for SSF_FIELD_LIST, including the real runtime boundary, important interface concepts, failure handling, lifecycle requirements, and S/4HANA guidance. Exact target-release parameter typing remains anchored to SE37 rather than copied from an unrelated release.

Published 20 Sept 2026· 605 words

What it does

Returns information about form-interface fields actually referenced by a Smart Form so a driver can limit data selection or perform technical analysis. SAP documents it as an optional helper before calling SSF_FUNCTION_MODULE_NAME and the generated form function. It is metadata assistance, not a substitute for the Smart Form's declared interface. 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.

Important parameters

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.

  • Smart Form name is supplied and a list of used fields/parameters is returned according to the interface.
  • Use DDIC-typed structures and binary/text tables that match the function documentation; do not substitute similar-looking generic CHAR tables.
  • For file, spool, form, email, or log processing, carry the returned identifier/handle forward rather than trying to reconstruct it later.

Exceptions

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.

  • Missing/inactive form, generated-interface inconsistencies, or assuming an unused field can always be omitted from application logic are the main risks.
  • Check every declared exception and SY-SUBRC branch in the target release.
  • If a send/render/save call returns a technical success, still validate the returned spool/document/log identifier before telling the application that processing completed.

How to call it safely

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.

ECC vs S/4HANA

It remains part of classic Smart Forms in S/4HANA; newer form services have different metadata/service interfaces. 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.

Common pitfalls

  • Mixing presentation-server and application-server paths or assuming the same filesystem exists on every application-server instance.
  • Treating binary PDF/XSTRING content as text, causing code-page conversion or truncation.
  • Skipping the required OPEN/CLOSE or CREATE/SAVE lifecycle and leaving incomplete spool, form, mail, or log state.
  • Using a GUI popup or frontend file service in background/RFC processing where no interactive SAP GUI exists.
  • Assuming a queued mail/spool/log request proves downstream delivery, printing, or persistence without checking the relevant monitor.

Whose problem this is

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.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-function-modules/ssf-field-listERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.