SAP SO_ASYNCHRON_STATUS_UPDATE Function Module for









SO_ASYNCHRON_STATUS_UPDATE is a standard so asynchron status update 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 asynchron status update FM, simply by entering the name SO_ASYNCHRON_STATUS_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SO_ASYNCHRON_STATUS_UPDATE 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_ASYNCHRON_STATUS_UPDATE'"
EXPORTING
REPLY_TO = "
RECEIVERS = "
* NO_STATUSMAIL = "

EXCEPTIONS
DATA_NOT_FOUND = 1
.



IMPORTING Parameters details for SO_ASYNCHRON_STATUS_UPDATE

REPLY_TO -

Data type: SO_RPLY_ID
Optional: No
Call by Reference: Yes

RECEIVERS -

Data type: SX_RECEIVERS_TAB
Optional: No
Call by Reference: Yes

NO_STATUSMAIL -

Data type: OS_BOOLEAN
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SO_ASYNCHRON_STATUS_UPDATE 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.

DATA:
lv_reply_to  TYPE SO_RPLY_ID, "   
lv_data_not_found  TYPE SO_RPLY_ID, "   
lv_receivers  TYPE SX_RECEIVERS_TAB, "   
lv_no_statusmail  TYPE OS_BOOLEAN. "   

  CALL FUNCTION 'SO_ASYNCHRON_STATUS_UPDATE'  "
    EXPORTING
         REPLY_TO = lv_reply_to
         RECEIVERS = lv_receivers
         NO_STATUSMAIL = lv_no_statusmail
    EXCEPTIONS
        DATA_NOT_FOUND = 1
. " SO_ASYNCHRON_STATUS_UPDATE




ABAP code using 7.40 inline data declarations to call FM SO_ASYNCHRON_STATUS_UPDATE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!