RFKKBIXBIT4_ARCHIVE is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). It is used for This report carries out the first step in archiving billable items...see full standard documentation available for this report. Also check out the submitted Comments related to this SAP report and the details below to see which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC.
If you would like to execute this report or see the full code listing simply enter RFKKBIXBIT4_ARCHIVE into the relevant SAP transactions such as SE38 or SE80
Below is a list of transaction codes which are relevant to this SAP report
FKKBIXBIT4_ARCH - Archiving of Billed Items
This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.
Selection Text: S_CRDATE = D .
Selection Text: P_WRITST = D .
Selection Text: P_WRIPRD = D .
Selection Text: P_SNAP = D .
Selection Text: P_PROT_O = D .
Selection Text: P_PROT = D .
Selection Text: P_PERINV = D .
Selection Text: P_PERBI = D .
Selection Text: P_DEST = D .
Selection Text: P_DELTST = D .
Selection Text: P_COMENT = D .
Selection Text: P_BITCAT = D .
Selection Text: P_AR_ILM = D .
Selection Text: S_SUFFP = D .
Selection Text: P_FIX = Alternative To-Date
Selection Text: P_CUST = To-Date per Customizing
Title: Archive Billed Items
Text Symbol: S02 = Restrictions
Text Symbol: S01 = Billable Item Class
Text Symbol: 004 = Alternative Retention Period
Text Symbol: 003 = Determination of Retention Period
Text Symbol: 001 = &2 billed items processed
INCLUDE RFKKBIXBIT4_ARCHIVE_TOP.
INCLUDE RFKKBIXBIT4_ARCHIVE_F01.
INCLUDE ARCH_WRITE_PRG_STANDARD2.
No SAP DATABASE tables are accessed within this REPORT code!
FKK_BIX_ARCH_AUTH_CHECK call function 'FKK_BIX_ARCH_AUTH_CHECK'.
FKK_BIX_BITCAT_CONFIG_GET call function 'FKK_BIX_BITCAT_CONFIG_GET' exporting i_bitcat = p_bitcat importing e_bitcat_confstat = lv_bitcat_confstat exceptions not_found = 1 others = 2.
FKK_BIX_BITCAT_CHECK_GET call function 'FKK_BIX_BITCAT_CHECK_GET' exporting i_bitcat = p_bitcat exceptions not_found = 1 not_active = 2 not_productive = 3 others = 4.
FKK_BIX_BIT_GET_OBJNAMES call function 'FKK_BIX_BIT_GET_OBJNAMES' exporting iv_bitcat = ls_bit4_tab_set-bitcat iv_status = cl_fkkbix_co=>gc_bitstatus_4 iv_bit4_suffix = ls_bit4_tab_set-bit4_tab_suffix importing es_tabnames = ls_tabnames exceptions object_not_found = 1 others = 2.
FKK_BIX_BITCAT_CALL_EVENT_40 call function 'FKK_BIX_BITCAT_CALL_EVENT_40' exporting iv_billdocno = lv_billdocno iv_bitcat = p_bitcat it_bit4_it = lt_bit4_it it_bit4_py = lt_bit4_py it_bit4_tx = lt_bit4_tx it_bit4_tt = lt_bit4_tt importing ev_no_archiving = lv_no_archiving exceptions customer_error = 1 others = 2.
PROGRESS_INDICATOR call function 'PROGRESS_INDICATOR' exporting i_text = text-001 i_processed = l_num_entries_processed i_output_immediately = space importing e_progress_sent = lv_progress_send.
PROGRESS_INDICATOR call function 'PROGRESS_INDICATOR' exporting i_text = text-001 i_processed = l_num_entries_processed i_output_immediately = 'X' importing e_progress_sent = lv_progress_send.
DB_COMMIT call function 'DB_COMMIT'. "otherwise message will not appear in the job-log
ARCHIVE_PROTOCOL_LINE_DETAIL call function 'ARCHIVE_PROTOCOL_LINE_DETAIL'.
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.