SAP STATUS_GET_CHANGE_FLAG Function Module for
STATUS_GET_CHANGE_FLAG is a standard status get change flag 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 get change flag FM, simply by entering the name STATUS_GET_CHANGE_FLAG into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSVA
Program Name: SAPLBSVA
Main Program: SAPLBSVA
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STATUS_GET_CHANGE_FLAG 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_GET_CHANGE_FLAG'".
EXPORTING
* CLIENT = SY-MANDT "
IMPORTING
FLG_CHANGE = "Indicator that status changes were made
TABLES
* OBJNR_TABLE = "
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_GET_CHANGE_FLAG
CLIENT -
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STATUS_GET_CHANGE_FLAG
FLG_CHANGE - Indicator that status changes were made
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for STATUS_GET_CHANGE_FLAG
OBJNR_TABLE -
Data type: JSTO_PREOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STATUS_GET_CHANGE_FLAG 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_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_flg_change | TYPE XFELD, " | |||
| lt_objnr_table | TYPE STANDARD TABLE OF JSTO_PRE. " |
|   CALL FUNCTION 'STATUS_GET_CHANGE_FLAG' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| IMPORTING | ||
| FLG_CHANGE | = lv_flg_change | |
| TABLES | ||
| OBJNR_TABLE | = lt_objnr_table | |
| . " STATUS_GET_CHANGE_FLAG | ||
ABAP code using 7.40 inline data declarations to call FM STATUS_GET_CHANGE_FLAG
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.| "SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
Search for further information about these or an SAP related objects