BUS_ARCH_DATA_GET SAP Function module

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

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

Pattern for FM BUS_ARCH_DATA_GET - BUS ARCH DATA GET

CALL FUNCTION 'BUS_ARCH_DATA_GET' "
  EXPORTING
    iv_objap =                  " tbz1-objap    BDT: Application Object
    iv_objectid =               "               char120
  IMPORTING
    ev_archhandle =             " sy-tabix      Internal Tables; Current Line Index
  TABLES
    it_table =                  " bus_table     BDT: Transfer Structure for Tables
    et_record =                 " bussarcyes    BDT Archiving: Data Already Archived - Free for Deletion
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  BUS_ARCH_DATA_GET

ABAP code example for Function Module BUS_ARCH_DATA_GET

The ABAP code below is a full code listing to execute function module BUS_ARCH_DATA_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_ev_archhandle  
 
 TYPE SY-TABIX
,
it_it_table  
 
 TYPE STANDARD TABLE OF BUS_TABLE,"TABLES PARAM
wa_it_table
 
 LIKE LINE OF it_it_table
,
it_et_record  
 
 TYPE STANDARD TABLE OF BUSSARCYES,"TABLES PARAM
wa_et_record
 
 LIKE LINE OF it_et_record
.

 

SELECT single OBJAP 
  FROM TBZ1 
  INTO @DATA(ld_iv_objap).


DATA(ld_iv_objectid) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_it_table to it_it_table.
 

"populate fields of struture and append to itab
append wa_et_record to it_et_record.
.

CALL FUNCTION 'BUS_ARCH_DATA_GET'
  EXPORTING
    iv_objap =                   ld_iv_objap
    iv_objectid =                ld_iv_objectid
  IMPORTING
    ev_archhandle =              ld_ev_archhandle
  TABLES
    it_table =                   it_it_table
    et_record =                  it_et_record
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  BUS_ARCH_DATA_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_ev_archhandle
 
 TYPE SY-TABIX ,
ld_iv_objap
 
 TYPE TBZ1-OBJAP ,
it_it_table
 
 TYPE STANDARD TABLE OF BUS_TABLE ,
wa_it_table
 
 LIKE LINE OF it_it_table,
ld_iv_objectid
 
 TYPE STRING ,
it_et_record
 
 TYPE STANDARD TABLE OF BUSSARCYES ,
wa_et_record
 
 LIKE LINE OF it_et_record.



SELECT single OBJAP 
  FROM TBZ1 
  INTO ld_iv_objap.
 

"populate fields of struture and append to itab
append wa_it_table to it_it_table.
ld_iv_objectid = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_record to it_et_record.