STATUS_PROPERTIES_GET SAP Function module - Determine Current State of a Status

STATUS_PROPERTIES_GET 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_PROPERTIES_GET into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM STATUS_PROPERTIES_GET - STATUS PROPERTIES GET

CALL FUNCTION 'STATUS_PROPERTIES_GET' "Determine Current State of a Status
  EXPORTING
*   bypass_buffer = SPACE       " xfeld         'Read Status from Database (Avoid Buffer)' Flag
*   client = SY-MANDT           " jest-mandt    Client
    objnr =                     " jest-objnr    Object Number
    status =                    " jest-stat     Status
  IMPORTING
    active =                    " sy-batch      'Status Active' Flag
    deactivated =               " sy-batch      'Status Deactivated' Flag
    never_active =              " sy-batch      'Status was Never Active' Flag
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "               Status Object Does Not Exist
    .  "  STATUS_PROPERTIES_GET

ABAP code example for Function Module STATUS_PROPERTIES_GET

The ABAP code below is a full code listing to execute function module STATUS_PROPERTIES_GET 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_active  
 
 TYPE SY-BATCH
,
ld_deactivated  
 
 TYPE SY-BATCH
,
ld_never_active  
 
 TYPE SY-BATCH
.


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

SELECT single MANDT 
  FROM JEST 
  INTO @DATA(ld_client).

 

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

 

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

.

CALL FUNCTION 'STATUS_PROPERTIES_GET'
  EXPORTING
*   bypass_buffer =              ld_bypass_buffer
*   client =                     ld_client
    objnr =                      ld_objnr
    status =                     ld_status
  IMPORTING
    active =                     ld_active
    deactivated =                ld_deactivated
    never_active =               ld_never_active
  EXCEPTIONS
    OBJECT_NOT_FOUND =           1
    .  "  STATUS_PROPERTIES_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_active
 
 TYPE SY-BATCH ,
ld_bypass_buffer
 
 TYPE XFELD ,
ld_deactivated
 
 TYPE SY-BATCH ,
ld_client
 
 TYPE JEST-MANDT ,
ld_never_active
 
 TYPE SY-BATCH ,
ld_objnr
 
 TYPE JEST-OBJNR ,
ld_status
 
 TYPE JEST-STAT .


ld_bypass_buffer = 'Check type of data required'.

SELECT single MANDT 
  FROM JEST 
  INTO ld_client.


SELECT single OBJNR 
  FROM JEST 
  INTO ld_objnr.


SELECT single STAT 
  FROM JEST 
  INTO ld_status.

SAP Documentation for FM STATUS_PROPERTIES_GET