SAP STATUS_CHANGE_EXTERN Function Module for Set User Status
STATUS_CHANGE_EXTERN is a standard status change extern SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set User Status 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 change extern FM, simply by entering the name STATUS_CHANGE_EXTERN into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSVA
Program Name: SAPLBSVA
Main Program: SAPLBSVA
Appliation area: S
Release date: 05-Jan-2000
Mode(Normal, Remote etc): Normal Function Module
Update:
Function STATUS_CHANGE_EXTERN 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_CHANGE_EXTERN'"Set User Status.
EXPORTING
* CHECK_ONLY = ' ' "Check Permissibility Only
* CLIENT = SY-MANDT "Client (Only for Exceptional Cases!)
OBJNR = "Object Number of Status Object
USER_STATUS = "User Status to be Set in Internal Format
* SET_INACT = ' ' "'Deactivate Status' Flag
* SET_CHGKZ = "'Activate Change Documents' Flag
* NO_CHECK = ' ' "Checkbox Field
IMPORTING
STONR = "Status Number
EXCEPTIONS
OBJECT_NOT_FOUND = 1 STATUS_INCONSISTENT = 2 STATUS_NOT_ALLOWED = 3
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_CHANGE_EXTERN
CHECK_ONLY - Check Permissibility Only
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client (Only for Exceptional Cases!)
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJNR - Object Number of Status Object
Data type: JSTO-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
USER_STATUS - User Status to be Set in Internal Format
Data type: JEST-STATOptional: No
Call by Reference: No ( called with pass by value option)
SET_INACT - 'Deactivate Status' Flag
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
SET_CHGKZ - 'Activate Change Documents' Flag
Data type: JSTO-CHGKZOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_CHECK - Checkbox Field
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STATUS_CHANGE_EXTERN
STONR - Status Number
Data type: TJ30-STONROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND - Status Object does not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_INCONSISTENT - Status Situation is Inconsistent
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_NOT_ALLOWED - User Status Not Allowed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STATUS_CHANGE_EXTERN 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_stonr | TYPE TJ30-STONR, " | |||
lv_check_only | TYPE XFELD, " ' ' | |||
lv_object_not_found | TYPE XFELD, " | |||
lv_client | TYPE SY-MANDT, " SY-MANDT | |||
lv_status_inconsistent | TYPE SY, " | |||
lv_objnr | TYPE JSTO-OBJNR, " | |||
lv_status_not_allowed | TYPE JSTO, " | |||
lv_user_status | TYPE JEST-STAT, " | |||
lv_set_inact | TYPE XFELD, " ' ' | |||
lv_set_chgkz | TYPE JSTO-CHGKZ, " | |||
lv_no_check | TYPE XFELD. " ' ' |
  CALL FUNCTION 'STATUS_CHANGE_EXTERN' "Set User Status |
EXPORTING | ||
CHECK_ONLY | = lv_check_only | |
CLIENT | = lv_client | |
OBJNR | = lv_objnr | |
USER_STATUS | = lv_user_status | |
SET_INACT | = lv_set_inact | |
SET_CHGKZ | = lv_set_chgkz | |
NO_CHECK | = lv_no_check | |
IMPORTING | ||
STONR | = lv_stonr | |
EXCEPTIONS | ||
OBJECT_NOT_FOUND = 1 | ||
STATUS_INCONSISTENT = 2 | ||
STATUS_NOT_ALLOWED = 3 | ||
. " STATUS_CHANGE_EXTERN |
ABAP code using 7.40 inline data declarations to call FM STATUS_CHANGE_EXTERN
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 STONR FROM TJ30 INTO @DATA(ld_stonr). | ||||
DATA(ld_check_only) | = ' '. | |||
"SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
DATA(ld_client) | = SY-MANDT. | |||
"SELECT single OBJNR FROM JSTO INTO @DATA(ld_objnr). | ||||
"SELECT single STAT FROM JEST INTO @DATA(ld_user_status). | ||||
DATA(ld_set_inact) | = ' '. | |||
"SELECT single CHGKZ FROM JSTO INTO @DATA(ld_set_chgkz). | ||||
DATA(ld_no_check) | = ' '. | |||
Search for further information about these or an SAP related objects