SAP STATUS_READ_ARCHIVE_OBJECT Function Module for Read Status Objects from Archive









STATUS_READ_ARCHIVE_OBJECT is a standard status read archive object 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 Status Objects from Archive 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 archive object FM, simply by entering the name STATUS_READ_ARCHIVE_OBJECT into the relevant SAP transaction such as SE37 or SE38.

Function Group: BSVB
Program Name: SAPLBSVB
Main Program:
Appliation area: K
Release date: 23-Jul-1999
Mode(Normal, Remote etc): Normal Function Module
Update:



Function STATUS_READ_ARCHIVE_OBJECT 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_ARCHIVE_OBJECT'"Read Status Objects from Archive
EXPORTING
* ARCHIVE_HANDLE = 0 "Archive to be Read
* I_MANDT = SY-MANDT "Client
* I_OBJNR = ' ' "Status Object Number
* I_APPEND = ' ' "'X' -> Results Appended

TABLES
* T_JSTO = "Status Object Headers(s)
* T_JCDO = "Status Object Change Documents
* T_JEST = "Individual Object Status
* T_JCDS = "Individual Status Change Documents
* T_DJEST = "Key-Date Based Management

EXCEPTIONS
WRONG_ACCESS_TO_ARCHIVE = 1 NOT_ENOUGH_INFO = 2
.



IMPORTING Parameters details for STATUS_READ_ARCHIVE_OBJECT

ARCHIVE_HANDLE - Archive to be Read

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

I_MANDT - Client

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

I_OBJNR - Status Object Number

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

I_APPEND - 'X' -> Results Appended

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

TABLES Parameters details for STATUS_READ_ARCHIVE_OBJECT

T_JSTO - Status Object Headers(s)

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

T_JCDO - Status Object Change Documents

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

T_JEST - Individual Object Status

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

T_JCDS - Individual Status Change Documents

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

T_DJEST - Key-Date Based Management

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

EXCEPTIONS details

WRONG_ACCESS_TO_ARCHIVE - Archive not Opened for Reading

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

NOT_ENOUGH_INFO - DB Read Specified Insufficiently

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

Copy and paste ABAP code example for STATUS_READ_ARCHIVE_OBJECT 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:
lt_t_jsto  TYPE STANDARD TABLE OF JSTO, "   
lv_archive_handle  TYPE SY-TABIX, "   0
lv_wrong_access_to_archive  TYPE SY, "   
lt_t_jcdo  TYPE STANDARD TABLE OF JCDO, "   
lv_i_mandt  TYPE SY-MANDT, "   SY-MANDT
lv_not_enough_info  TYPE SY, "   
lt_t_jest  TYPE STANDARD TABLE OF JEST, "   
lv_i_objnr  TYPE JSTO-OBJNR, "   SPACE
lt_t_jcds  TYPE STANDARD TABLE OF JCDS, "   
lv_i_append  TYPE C, "   SPACE
lt_t_djest  TYPE STANDARD TABLE OF DJEST. "   

  CALL FUNCTION 'STATUS_READ_ARCHIVE_OBJECT'  "Read Status Objects from Archive
    EXPORTING
         ARCHIVE_HANDLE = lv_archive_handle
         I_MANDT = lv_i_mandt
         I_OBJNR = lv_i_objnr
         I_APPEND = lv_i_append
    TABLES
         T_JSTO = lt_t_jsto
         T_JCDO = lt_t_jcdo
         T_JEST = lt_t_jest
         T_JCDS = lt_t_jcds
         T_DJEST = lt_t_djest
    EXCEPTIONS
        WRONG_ACCESS_TO_ARCHIVE = 1
        NOT_ENOUGH_INFO = 2
. " STATUS_READ_ARCHIVE_OBJECT




ABAP code using 7.40 inline data declarations to call FM STATUS_READ_ARCHIVE_OBJECT

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 TABIX FROM SY INTO @DATA(ld_archive_handle).
 
 
 
"SELECT single MANDT FROM SY INTO @DATA(ld_i_mandt).
DATA(ld_i_mandt) = SY-MANDT.
 
 
 
"SELECT single OBJNR FROM JSTO INTO @DATA(ld_i_objnr).
DATA(ld_i_objnr) = ' '.
 
 
DATA(ld_i_append) = ' '.
 
 


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!