SO_DOCUMENT_SEND_API1 — Send an Existing or Prepared SAPoffice Document
Sends SAPoffice document content and recipient information through the classic communication services API and can support RFC-oriented document transfer scenarios. It predates CL_BCS and should be treated as legacy integration code rather than the preferred API for new email development.
Practitioner reference for SO_DOCUMENT_SEND_API1, 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· 660 words
What it does
Sends SAPoffice document content and recipient information through the classic communication services API and can support RFC-oriented document transfer scenarios. It predates CL_BCS and should be treated as legacy integration code rather than the preferred API for new email development. 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.
- DOCUMENT_DATA/content tables and receiver list are the core concepts; exact attachment/body tables depend on 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 recipient/address data, authorization, SAPconnect configuration, or misinterpreting returned send status as final external delivery are the main failure modes.
- 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.
For a legacy SAPoffice mail incident, record sender, recipient type/address, document header, content-table format and requested send mode. Distinguish successful creation of a SAPoffice send request from external SMTP delivery: inspect SCOT scheduling and SOST processing status after the call. Test non-ASCII message bodies and attachment conversion in a safe mailbox before production. For new implementations, assess CL_BCS or an approved released communication API; the classic function's continued presence does not guarantee cloud-compatible extensibility.
ECC vs S/4HANA
It may remain available in S/4HANA on-premise, but CL_BCS or released communication services are preferred for new code. 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/so-document-send-api1ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.