SO_NEW_DOCUMENT_SEND_API1 — Send a Classic SAPoffice Document or Email
Creates and sends a classic SAPoffice document to internal or external recipients through the SAPconnect/SAPoffice communication stack. It is widely used in older custom email code for text messages without complex BCS objects. Sending is asynchronous through SAPconnect, so a successful call does not prove final SMTP delivery.
Practitioner reference for SO_NEW_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· 606 words
What it does
Creates and sends a classic SAPoffice document to internal or external recipients through the SAPconnect/SAPoffice communication stack. It is widely used in older custom email code for text messages without complex BCS objects. Sending is asynchronous through SAPconnect, so a successful call does not prove final SMTP delivery. 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, DOCUMENT_CONTENT, RECEIVERS and PUT_IN_OUTBOX are key concepts; COMMIT/dispatch behavior must be understood with SCOT/SOST processing.
- 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.
- Invalid recipients, missing SAPconnect node/configuration, send-request creation errors, or assuming 'sent to SAPconnect' equals recipient delivery 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
The function remains callable in S/4HANA on-premise, but CL_BCS is the preferred classic OO API and cloud scenarios use released mail services. 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-new-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.