SAP SO_OBJECT_EXPORT_FOR_SEND Function Module for

Search SAP Function Modules

SO_OBJECT_EXPORT_FOR_SEND is a standard so object export for send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for so object export for send FM, simply by entering the name SO_OBJECT_EXPORT_FOR_SEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: SOA2
Program Name: SAPLSOA2
Main Program: SAPLSOA2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SO_OBJECT_EXPORT_FOR_SEND pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'SO_OBJECT_EXPORT_FOR_SEND'"
  EXPORTING
   SNDART =  "Mode with which the object is to be sent

 IMPORTING
   HEADER =  "general header of the send process
   OFFICE_ID =  "Temporary ID of the link to SAPcom-SAPoffice

TABLES
   BODY_HEADER =  "Header of the individual bodyparts with offset
   BODY_PART =  "SAP bodypart
   RECEIVERS =  "Recipient of the object

EXCEPTIONS
   NOTHING_FOUND = 1    NO_RECEIVER_FOUND = 2    PARAMETER_ERROR = 3    X_ERROR = 4 

.

IMPORTING Parameters details for SO_OBJECT_EXPORT_FOR_SEND

SNDART - Mode with which the object is to be sent

Data type: SOES-SNDART
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SO_OBJECT_EXPORT_FOR_SEND

HEADER - general header of the send process

Data type: SOXEH
Optional: No
Call by Reference: No ( called with pass by value option)

OFFICE_ID - Temporary ID of the link to SAPcom-SAPoffice

Data type: SOXEI
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SO_OBJECT_EXPORT_FOR_SEND

BODY_HEADER - Header of the individual bodyparts with offset

Data type: SOXEB
Optional: No
Call by Reference: No ( called with pass by value option)

BODY_PART - SAP bodypart

Data type: SOLI
Optional: No
Call by Reference: No ( called with pass by value option)

RECEIVERS - Recipient of the object

Data type: SOXER
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOTHING_FOUND - nothing found to send

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_RECEIVER_FOUND - Addressee could not be identified

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARAMETER_ERROR - Incorrect parameters

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

X_ERROR - Internal Error (DB)

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SO_OBJECT_EXPORT_FOR_SEND Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM SO_OBJECT_EXPORT_FOR_SEND

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects