SAP SO_OBJECT_IMPORT_FOR_RECEIVE Function Module for

Search SAP Function Modules

SO_OBJECT_IMPORT_FOR_RECEIVE is a standard so object import for receive 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 import for receive FM, simply by entering the name SO_OBJECT_IMPORT_FOR_RECEIVE 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): Remote-Enabled
Update:

Function SO_OBJECT_IMPORT_FOR_RECEIVE 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_IMPORT_FOR_RECEIVE'"
  EXPORTING
   HEADER =  "General header of the send process
   SCOM_ID =  "
   SNDART =  "Transmission type (X400, SAP-SAP and similar)

 IMPORTING
   SCOM_ID =  "

TABLES
   BODY_HEADER =  "Headers of the individual body parts
   BODY_PART =  "The individual body parts (offset in header)
   RECEIVERS =  "Recipient and copy list

EXCEPTIONS
   NOT_SEND = 1    NO_RECEIVERS_FOUND = 2    PARAMETER_ERROR = 3    X_ERROR = 4 

.

IMPORTING Parameters details for SO_OBJECT_IMPORT_FOR_RECEIVE

HEADER - General header of the send process

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

SCOM_ID -

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

SNDART - Transmission type (X400, SAP-SAP and similar)

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

EXPORTING Parameters details for SO_OBJECT_IMPORT_FOR_RECEIVE

SCOM_ID -

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

TABLES Parameters details for SO_OBJECT_IMPORT_FOR_RECEIVE

BODY_HEADER - Headers of the individual body parts

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

BODY_PART - The individual body parts (offset in header)

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

RECEIVERS - Recipient and copy list

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

EXCEPTIONS details

NOT_SEND - Object could not be sent

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

NO_RECEIVERS_FOUND - None of the recipients exists (found)

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

PARAMETER_ERROR - Incorrect or unreasonable transfer of 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_IMPORT_FOR_RECEIVE 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_IMPORT_FOR_RECEIVE

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