FVD_ARC_GET_OBJ_DATA SAP Function module - Get all the archived tables for the specified archiving object

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

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

Pattern for FM FVD_ARC_GET_OBJ_DATA - FVD ARC GET OBJ DATA

CALL FUNCTION 'FVD_ARC_GET_OBJ_DATA' "Get all the archived tables for the specified archiving object
  EXPORTING
    i_arch_obj =                " objct_tr01    Archiving Object
    i_obj_id =                  " datobj_id     Data object Identifier
    i_obj_key =                 " arkey         Key for Archive File
    i_obj_offset =              " admi_offst    Archive file data object offset
  IMPORTING
    o_obj_data =                " as_t_tablebuffer  AS: Table Buffer Table
  EXCEPTIONS
    ARCHIVE_READ_OBJECT = 1     "               Error while reading the particular object
    ARCHIVE_READ_OBJECT_BY_HANDLE = 2  "        Error while reading the object via handle
    .  "  FVD_ARC_GET_OBJ_DATA

ABAP code example for Function Module FVD_ARC_GET_OBJ_DATA

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


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

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

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

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

CALL FUNCTION 'FVD_ARC_GET_OBJ_DATA'
  EXPORTING
    i_arch_obj =                 ld_i_arch_obj
    i_obj_id =                   ld_i_obj_id
    i_obj_key =                  ld_i_obj_key
    i_obj_offset =               ld_i_obj_offset
  IMPORTING
    o_obj_data =                 ld_o_obj_data
  EXCEPTIONS
    ARCHIVE_READ_OBJECT =        1
    ARCHIVE_READ_OBJECT_BY_HANDLE =    2
    .  "  FVD_ARC_GET_OBJ_DATA

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_o_obj_data
 
 TYPE AS_T_TABLEBUFFER ,
ld_i_arch_obj
 
 TYPE OBJCT_TR01 ,
ld_i_obj_id
 
 TYPE DATOBJ_ID ,
ld_i_obj_key
 
 TYPE ARKEY ,
ld_i_obj_offset
 
 TYPE ADMI_OFFST .


ld_i_arch_obj = 'Check type of data required'.
ld_i_obj_id = 'Check type of data required'.
ld_i_obj_key = 'Check type of data required'.
ld_i_obj_offset = 'Check type of data required'.