SAP STATUS_OBJECT_CHECK_MULTI Function Module for

Search SAP Function Modules

STATUS_OBJECT_CHECK_MULTI is a standard status object 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 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 status object check multi FM, simply by entering the name STATUS_OBJECT_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: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STATUS_OBJECT_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_OBJECT_CHECK_MULTI'"
  EXPORTING
*  BYPASS_BUFFER = ' ' "'Read Status from Database (Avoid Buffer)' Flag
*  CHECK_ALREADY_READ = ' ' "Read status from DB if necessary
*  CLIENT = SY-MANDT "Client
   OBJNR =  "Object number

TABLES
   STATUS_CHECK =  "Status table: Inactive are deleted

EXCEPTIONS
   OBJECT_NOT_FOUND = 1 

.

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_OBJECT_CHECK_MULTI

BYPASS_BUFFER - 'Read Status from Database (Avoid Buffer)' Flag

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHECK_ALREADY_READ - Read status from DB if necessary

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLIENT - Client

Data type: JEST-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJNR - Object number

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

TABLES Parameters details for STATUS_OBJECT_CHECK_MULTI

STATUS_CHECK - Status table: Inactive are deleted

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Stat.object does not exist, or was not yet read

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

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

ABAP code using 7.40 inline data declarations to call FM STATUS_OBJECT_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.

Search for further information about these or an SAP related objects