STATUS_SET_USER_STATUS_DIALOG SAP Function module - Popup with Possibility of Setting User Status Manually

STATUS_SET_USER_STATUS_DIALOG 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_SET_USER_STATUS_DIALOG 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_SET_USER_STATUS_DIALOG - STATUS SET USER STATUS DIALOG

CALL FUNCTION 'STATUS_SET_USER_STATUS_DIALOG' "Popup with Possibility of Setting User Status Manually
  EXPORTING
    object_number =             " jsto-objnr    Object Number
*   client = SY-MANDT           " sy-mandt      Client (Only for Exceptional Cases)
*   only_display = SPACE        " xfeld         'Display Only' Flag
*   set_chgkz =                 " jsto-chgkz    'Activate Change Documents' Flag
  IMPORTING
    stonr =                     " tj30-stonr    Status Number
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "               Status Object Not Found
    NO_STATUS_SCHEME_GIVEN = 2  "               Status Object not Assigned to Any Status Profile
    .  "  STATUS_SET_USER_STATUS_DIALOG

ABAP code example for Function Module STATUS_SET_USER_STATUS_DIALOG

The ABAP code below is a full code listing to execute function module STATUS_SET_USER_STATUS_DIALOG 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
.

 

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


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

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

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

.

CALL FUNCTION 'STATUS_SET_USER_STATUS_DIALOG'
  EXPORTING
    object_number =              ld_object_number
*   client =                     ld_client
*   only_display =               ld_only_display
*   set_chgkz =                  ld_set_chgkz
  IMPORTING
    stonr =                      ld_stonr
  EXCEPTIONS
    OBJECT_NOT_FOUND =           1
    NO_STATUS_SCHEME_GIVEN =     2
    .  "  STATUS_SET_USER_STATUS_DIALOG

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
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_object_number
 
 TYPE JSTO-OBJNR ,
ld_client
 
 TYPE SY-MANDT ,
ld_only_display
 
 TYPE XFELD ,
ld_set_chgkz
 
 TYPE JSTO-CHGKZ .



SELECT single OBJNR 
  FROM JSTO 
  INTO ld_object_number.

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

SELECT single CHGKZ 
  FROM JSTO 
  INTO ld_set_chgkz.

SAP Documentation for FM STATUS_SET_USER_STATUS_DIALOG