STATUS_CHANGE_EXTERN SAP Function module - Set User Status

STATUS_CHANGE_EXTERN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name STATUS_CHANGE_EXTERN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BSVA
Released Date: 05.01.2000
Processing type: Normal fucntion module

Pattern for FM STATUS_CHANGE_EXTERN - STATUS CHANGE EXTERN

CALL FUNCTION 'STATUS_CHANGE_EXTERN' "Set User Status
  EXPORTING
*   check_only = ' '            " xfeld         Check Permissibility Only
*   client = SY-MANDT           " sy-mandt      Client (Only for Exceptional Cases!)
    objnr =                     " jsto-objnr    Object Number of Status Object
    user_status =               " jest-stat     User Status to be Set in Internal Format
*   set_inact = ' '             " xfeld         'Deactivate Status' Flag
*   set_chgkz =                 " jsto-chgkz    'Activate Change Documents' Flag
*   no_check = ' '              " xfeld         Checkbox Field
  IMPORTING
    stonr =                     " tj30-stonr    Status Number
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "               Status Object does not Exist
    STATUS_INCONSISTENT = 2     "               Status Situation is Inconsistent
    STATUS_NOT_ALLOWED = 3      "               User Status Not Allowed
    .  "  STATUS_CHANGE_EXTERN

ABAP code example for Function Module STATUS_CHANGE_EXTERN

The ABAP code below is a full code listing to execute function module STATUS_CHANGE_EXTERN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_stonr  
 
 TYPE TJ30-STONR
.


DATA(ld_check_only) = 'Check type of data required'.

DATA(ld_client) = 'Check type of data required'.
 

SELECT single OBJNR 
  FROM JSTO 
  INTO @DATA(ld_objnr).

 

SELECT single STAT 
  FROM JEST 
  INTO @DATA(ld_user_status).


DATA(ld_set_inact) = 'Check type of data required'.
 

SELECT single CHGKZ 
  FROM JSTO 
  INTO @DATA(ld_set_chgkz).


DATA(ld_no_check) = 'Check type of data required'.
.

CALL FUNCTION 'STATUS_CHANGE_EXTERN'
  EXPORTING
*   check_only =                 ld_check_only
*   client =                     ld_client
    objnr =                      ld_objnr
    user_status =                ld_user_status
*   set_inact =                  ld_set_inact
*   set_chgkz =                  ld_set_chgkz
*   no_check =                   ld_no_check
  IMPORTING
    stonr =                      ld_stonr
  EXCEPTIONS
    OBJECT_NOT_FOUND =           1
    STATUS_INCONSISTENT =        2
    STATUS_NOT_ALLOWED =         3
    .  "  STATUS_CHANGE_EXTERN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_stonr
 
 TYPE TJ30-STONR ,
ld_check_only
 
 TYPE XFELD ,
ld_client
 
 TYPE SY-MANDT ,
ld_objnr
 
 TYPE JSTO-OBJNR ,
ld_user_status
 
 TYPE JEST-STAT ,
ld_set_inact
 
 TYPE XFELD ,
ld_set_chgkz
 
 TYPE JSTO-CHGKZ ,
ld_no_check
 
 TYPE XFELD .


ld_check_only = 'Check type of data required'.
ld_client = 'Check type of data required'.

SELECT single OBJNR 
  FROM JSTO 
  INTO ld_objnr.


SELECT single STAT 
  FROM JEST 
  INTO ld_user_status.

ld_set_inact = 'Check type of data required'.

SELECT single CHGKZ 
  FROM JSTO 
  INTO ld_set_chgkz.

ld_no_check = 'Check type of data required'.

SAP Documentation for FM STATUS_CHANGE_EXTERN