SAP STATUS_CHECK_MULTI Function Module for Checks Several Objects, Whether Status is Active
STATUS_CHECK_MULTI is a standard status check multi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks Several Objects, Whether Status is Active processing and below is the pattern details for this FM, 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 status check multi FM, simply by entering the name STATUS_CHECK_MULTI into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSVA
Program Name: SAPLBSVA
Main Program: SAPLBSVA
Appliation area: C
Release date: 05-Jan-2000
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STATUS_CHECK_MULTI 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 'STATUS_CHECK_MULTI'"Checks Several Objects, Whether Status is Active.
EXPORTING
* BYPASS_BUFFER = ' ' "'Read Status from Database (Avoid Buffer)' Flag
* CLIENT = SY-MANDT "Client
STATUS = "Status which is to be Checked for Active
* FLG_EXCLUDE = ' ' "Status Should not be Active
IMPORTING
OBJECTS_DELETED = "Object Numbers have been Deleted
TABLES
OBJECTS = "Table of Object Numbers
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLBSVA_001 User Exit PP Order Processing (Non-Order-Type-Specific)
IMPORTING Parameters details for STATUS_CHECK_MULTI
BYPASS_BUFFER - 'Read Status from Database (Avoid Buffer)' Flag
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client
Data type: JEST-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
STATUS - Status which is to be Checked for Active
Data type: JEST-STATOptional: No
Call by Reference: No ( called with pass by value option)
FLG_EXCLUDE - Status Should not be Active
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STATUS_CHECK_MULTI
OBJECTS_DELETED - Object Numbers have been Deleted
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for STATUS_CHECK_MULTI
OBJECTS - Table of Object Numbers
Data type: JSTO_PREOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STATUS_CHECK_MULTI 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: | ||||
| lt_objects | TYPE STANDARD TABLE OF JSTO_PRE, " | |||
| lv_bypass_buffer | TYPE XFELD, " SPACE | |||
| lv_objects_deleted | TYPE XFELD, " | |||
| lv_client | TYPE JEST-MANDT, " SY-MANDT | |||
| lv_status | TYPE JEST-STAT, " | |||
| lv_flg_exclude | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'STATUS_CHECK_MULTI' "Checks Several Objects, Whether Status is Active |
| EXPORTING | ||
| BYPASS_BUFFER | = lv_bypass_buffer | |
| CLIENT | = lv_client | |
| STATUS | = lv_status | |
| FLG_EXCLUDE | = lv_flg_exclude | |
| IMPORTING | ||
| OBJECTS_DELETED | = lv_objects_deleted | |
| TABLES | ||
| OBJECTS | = lt_objects | |
| . " STATUS_CHECK_MULTI | ||
ABAP code using 7.40 inline data declarations to call FM STATUS_CHECK_MULTI
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.| DATA(ld_bypass_buffer) | = ' '. | |||
| "SELECT single MANDT FROM JEST INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_status). | ||||
| DATA(ld_flg_exclude) | = ' '. | |||
Search for further information about these or an SAP related objects