SAP STATUS_READ Function Module for Read Object Status (JSTO and JEST)









STATUS_READ is a standard status read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Object Status (JSTO and JEST) 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 read FM, simply by entering the name STATUS_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: BSVA
Program Name: SAPLBSVA
Main Program: SAPLBSVA
Appliation area:
Release date: 11-Sep-1998
Mode(Normal, Remote etc): Normal Function Module
Update:



Function STATUS_READ 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_READ'"Read Object Status (JSTO and JEST)
EXPORTING
* CLIENT = SY-MANDT "Client
OBJNR = "Object Number
* ONLY_ACTIVE = ' ' "'Transfer Active Statuses Only' Flag

IMPORTING
OBTYP = "Object Category
STSMA = "Status Profile
STONR = "Status Number

TABLES
* STATUS = "Table of Individual Statuses for the Object

EXCEPTIONS
OBJECT_NOT_FOUND = 1
.




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_READ

CLIENT - Client

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJNR - Object Number

Data type: JSTO-OBJNR
Optional: No
Call by Reference: No ( called with pass by value option)

ONLY_ACTIVE - 'Transfer Active Statuses Only' Flag

Data type: JEST-INACT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for STATUS_READ

OBTYP - Object Category

Data type: JSTO-OBTYP
Optional: No
Call by Reference: No ( called with pass by value option)

STSMA - Status Profile

Data type: JSTO-STSMA
Optional: No
Call by Reference: No ( called with pass by value option)

STONR - Status Number

Data type: TJ30-STONR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for STATUS_READ

STATUS - Table of Individual Statuses for the Object

Data type: JSTAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OBJECT_NOT_FOUND - Status Object Not Found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for STATUS_READ 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_obtyp  TYPE JSTO-OBTYP, "   
lv_client  TYPE SY-MANDT, "   SY-MANDT
lt_status  TYPE STANDARD TABLE OF JSTAT, "   
lv_object_not_found  TYPE JSTAT, "   
lv_objnr  TYPE JSTO-OBJNR, "   
lv_stsma  TYPE JSTO-STSMA, "   
lv_stonr  TYPE TJ30-STONR, "   
lv_only_active  TYPE JEST-INACT. "   SPACE

  CALL FUNCTION 'STATUS_READ'  "Read Object Status (JSTO and JEST)
    EXPORTING
         CLIENT = lv_client
         OBJNR = lv_objnr
         ONLY_ACTIVE = lv_only_active
    IMPORTING
         OBTYP = lv_obtyp
         STSMA = lv_stsma
         STONR = lv_stonr
    TABLES
         STATUS = lt_status
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
. " STATUS_READ




ABAP code using 7.40 inline data declarations to call FM STATUS_READ

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 OBTYP FROM JSTO INTO @DATA(ld_obtyp).
 
"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 STSMA FROM JSTO INTO @DATA(ld_stsma).
 
"SELECT single STONR FROM TJ30 INTO @DATA(ld_stonr).
 
"SELECT single INACT FROM JEST INTO @DATA(ld_only_active).
DATA(ld_only_active) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!