SAP SO_STATE_SEND Function Module for

Search SAP Function Modules

SO_STATE_SEND is a standard so state 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 state send FM, simply by entering the name SO_STATE_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_STATE_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_STATE_SEND'"
 IMPORTING
   SCOM_ID =  "Communications ID between the systems
   SNDART =  "
   STATE_RECEIVER =  "

TABLES
   RECEIVERS =  "Recipient table: Recipient of the statuses

EXCEPTIONS
   NOTHING_FOUND = 1    RECEIVER_NOT_FOUND = 2    SCOM_ID_NOT_FOUND = 3    X_ERROR = 4 

.

EXPORTING Parameters details for SO_STATE_SEND

SCOM_ID - Communications ID between the systems

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

SNDART -

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

STATE_RECEIVER -

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

TABLES Parameters details for SO_STATE_SEND

RECEIVERS - Recipient table: Recipient of the statuses

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

EXCEPTIONS details

NOTHING_FOUND - there is no status for sending

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

RECEIVER_NOT_FOUND - No recipient found for status (DB error)

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

SCOM_ID_NOT_FOUND - No communications ID found (DB error)

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

X_ERROR - Data base inconsistency / unexpected error

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

Copy and paste ABAP code example for SO_STATE_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_STATE_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