STATUS_ARCHIVE_OBJECT SAP Function module - Archive Status Objects

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

Associated Function Group: BSVB
Released Date: 23.07.1999
Processing type: Normal fucntion module

Pattern for FM STATUS_ARCHIVE_OBJECT - STATUS ARCHIVE OBJECT

CALL FUNCTION 'STATUS_ARCHIVE_OBJECT' "Archive Status Objects
  EXPORTING
    archive_handle =            " sy-tabix      Archive in Which Status Object is Written
*   object_delete_flag = 'X'    " c             Deletion Indicator
*   i_mandt = SY-MANDT          " sy-mandt      Client
*   i_objnr = SPACE             " jsto-objnr    Object number
* TABLES
*   t_objnr =                   " ionrb         Object Number Table
  EXCEPTIONS
    WRONG_ACCESS_TO_ARCHIVE = 1  "              Archive not Open for Writing
    .  "  STATUS_ARCHIVE_OBJECT

ABAP code example for Function Module STATUS_ARCHIVE_OBJECT

The ABAP code below is a full code listing to execute function module STATUS_ARCHIVE_OBJECT 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:
it_t_objnr  
 
 TYPE STANDARD TABLE OF IONRB,"TABLES PARAM
wa_t_objnr
 
 LIKE LINE OF it_t_objnr
.


DATA(ld_archive_handle) = '123 '.

DATA(ld_object_delete_flag) = '123 '.

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

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

 

"populate fields of struture and append to itab
append wa_t_objnr to it_t_objnr.
.

CALL FUNCTION 'STATUS_ARCHIVE_OBJECT'
  EXPORTING
    archive_handle =             ld_archive_handle
*   object_delete_flag =         ld_object_delete_flag
*   i_mandt =                    ld_i_mandt
*   i_objnr =                    ld_i_objnr
* TABLES
*   t_objnr =                    it_t_objnr
  EXCEPTIONS
    WRONG_ACCESS_TO_ARCHIVE =    1
    .  "  STATUS_ARCHIVE_OBJECT

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_archive_handle
 
 TYPE SY-TABIX ,
it_t_objnr
 
 TYPE STANDARD TABLE OF IONRB ,
wa_t_objnr
 
 LIKE LINE OF it_t_objnr,
ld_object_delete_flag
 
 TYPE C ,
ld_i_mandt
 
 TYPE SY-MANDT ,
ld_i_objnr
 
 TYPE JSTO-OBJNR .


ld_archive_handle = '123 '. 

"populate fields of struture and append to itab
append wa_t_objnr to it_t_objnr.
ld_object_delete_flag = '123 '.
ld_i_mandt = 'Check type of data required'.

SELECT single OBJNR 
  FROM JSTO 
  INTO ld_i_objnr.

SAP Documentation for FM STATUS_ARCHIVE_OBJECT