SAP BKK_ARCH_ARCHIVE_OBJECT Function Module for Archive Data for each Archiving Object









BKK_ARCH_ARCHIVE_OBJECT is a standard bkk arch 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 Archive Data for each Archiving Object 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 bkk arch archive object FM, simply by entering the name BKK_ARCH_ARCHIVE_OBJECT into the relevant SAP transaction such as SE37 or SE38.

Function Group: FB0ARCH
Program Name: SAPLFB0ARCH
Main Program: SAPLFB0ARCH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BKK_ARCH_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 'BKK_ARCH_ARCHIVE_OBJECT'"Archive Data for each Archiving Object
EXPORTING
I_ARCHOBJECT = "
I_HANDLE = "
I_OBJECTID = "
I_TAB_RECORDS = "
* I_S_PARAM = "
* I_XTEST = 'X' "
* I_ARCHOBJGRPID = "
* I_DATE = "

IMPORTING
E_XVALID = "
E_XARCHIVED = "

CHANGING
* C_TAB_STATISTIC = "

EXCEPTIONS
TERMINATION_REQUESTED = 1
.



IMPORTING Parameters details for BKK_ARCH_ARCHIVE_OBJECT

I_ARCHOBJECT -

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

I_HANDLE -

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

I_OBJECTID -

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

I_TAB_RECORDS -

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

I_S_PARAM -

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

I_XTEST -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ARCHOBJGRPID -

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

I_DATE -

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

EXPORTING Parameters details for BKK_ARCH_ARCHIVE_OBJECT

E_XVALID -

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

E_XARCHIVED -

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

CHANGING Parameters details for BKK_ARCH_ARCHIVE_OBJECT

C_TAB_STATISTIC -

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

EXCEPTIONS details

TERMINATION_REQUESTED - Termination of Archiving Was Requested

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BKK_ARCH_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:
lv_e_xvalid  TYPE BOOLE-BOOLE, "   
lv_i_archobject  TYPE BKK_ARCH_OBJECT, "   
lv_c_tab_statistic  TYPE BKK_TAB_ARCHSTATISTIC, "   
lv_termination_requested  TYPE BKK_TAB_ARCHSTATISTIC, "   
lv_i_handle  TYPE SY-TABIX, "   
lv_e_xarchived  TYPE BOOLE-BOOLE, "   
lv_i_objectid  TYPE BKK_ARCH_OBJECTID, "   
lv_i_tab_records  TYPE BKK_TAB_ARCHBUFFER, "   
lv_i_s_param  TYPE BKK_TAB_ARCHBUFFER, "   
lv_i_xtest  TYPE BOOLE-BOOLE, "   'X'
lv_i_archobjgrpid  TYPE BKK_ARCHOBJGRPID, "   
lv_i_date  TYPE SY-DATUM. "   

  CALL FUNCTION 'BKK_ARCH_ARCHIVE_OBJECT'  "Archive Data for each Archiving Object
    EXPORTING
         I_ARCHOBJECT = lv_i_archobject
         I_HANDLE = lv_i_handle
         I_OBJECTID = lv_i_objectid
         I_TAB_RECORDS = lv_i_tab_records
         I_S_PARAM = lv_i_s_param
         I_XTEST = lv_i_xtest
         I_ARCHOBJGRPID = lv_i_archobjgrpid
         I_DATE = lv_i_date
    IMPORTING
         E_XVALID = lv_e_xvalid
         E_XARCHIVED = lv_e_xarchived
    CHANGING
         C_TAB_STATISTIC = lv_c_tab_statistic
    EXCEPTIONS
        TERMINATION_REQUESTED = 1
. " BKK_ARCH_ARCHIVE_OBJECT




ABAP code using 7.40 inline data declarations to call FM BKK_ARCH_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 BOOLE FROM BOOLE INTO @DATA(ld_e_xvalid).
 
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_i_handle).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_xarchived).
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xtest).
DATA(ld_i_xtest) = 'X'.
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
 


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!