SAP Reports / Programs

RJKSDCQP_DELETE_FROM_DB SAP ABAP Report - Constant Service Archiving: Delete Archived Data







RJKSDCQP_DELETE_FROM_DB is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC. Also check out the submitted Comments related to this SAP report or see any standard documentation available.

If you would like to execute this report or see the full code listing simply enter RJKSDCQP_DELETE_FROM_DB into the relevant SAP transactions such as SE38 or SE80


ABAP code to call this SAP report using the submit statement

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.






SUBMIT RJKSDCQP_DELETE_FROM_DB. "Basic submit
SUBMIT RJKSDCQP_DELETE_FROM_DB AND RETURN. "Return to original report after report execution complete
SUBMIT RJKSDCQP_DELETE_FROM_DB VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
    See more syntax options for the ABAP SUBMIT statement


Text pool values


Selection Text: P_DELPRD = D .
Selection Text: P_DELTST = D .
Title: Constant Service Archiving: Delete Archived Data
Text Symbol: 001 = will be deleted.
Text Symbol: 002 = &1% (&2 of &3) constant services processed


INCLUDES used within this REPORT RJKSDCQP_DELETE_FROM_DB

INCLUDE ARCHCOMO.
INCLUDE RJKSDCQP_ARCH_DATA.
INCLUDE RJKSDCQP_ARCH_FORMS.
INCLUDE ARCH_DELETE_PRG_STANDARD1.


TABLES used within REPORT and the associated SELECT statement:





No SAP DATABASE tables are accessed within this REPORT code!


Function Modules used within report and the associated call statement:

ARCHIVE_OPEN_FOR_DELETE call function 'ARCHIVE_OPEN_FOR_DELETE' exporting object = con_arch_object test_mode = p_deltst importing archive_handle = archive_handle exceptions file_already_open = 1 file_io_error = 2 internal_error = 3 no_files_available = 4 object_not_found = 5 open_error = 6 not_authorized = 7 others = 8.

ARCHIVE_GET_CUSTOMIZING_DATA call function 'ARCHIVE_GET_CUSTOMIZING_DATA' exporting object = con_arch_object importing commit_count_for_delete_prg = gv_commit_count exceptions object_not_found = 1 others = 2.

ARCHIVE_GET_INFORMATION call function 'ARCHIVE_GET_INFORMATION' exporting archive_handle = archive_handle importing object_number_in_file = gv_cnt_proc exceptions internal_error = 1 wrong_access_to_archive = 2 others = 3.

ARCHIVE_GET_NEXT_OBJECT call function 'ARCHIVE_GET_NEXT_OBJECT' exporting archive_handle = archive_handle importing object_id = gv_object_id exceptions end_of_file = 1 file_io_error = 2 internal_error = 3 open_error = 4 wrong_access_to_archive = 5 others = 6.

PROGRESS_INDICATOR call function 'PROGRESS_INDICATOR' exporting i_text = text-002 i_processed = gv_cnt_tot i_total = gv_cnt_proc.

ARCHIVE_GET_NEXT_RECORD call function 'ARCHIVE_GET_NEXT_RECORD' exporting archive_handle = archive_handle importing record_flags = gv_arc_buffer-flags record_structure = gv_arc_buffer-rname record_ref = gv_record_ref exceptions end_of_object = 1 internal_error = 2 wrong_access_to_archive = 3 others = 4.

ARCHIVE_GIVE_STATISTICS call function 'ARCHIVE_GIVE_STATISTICS' exporting archive_handle = archive_handle tables table = gt_statistic.

ARCHIVE_WRITE_STATISTICS call function 'ARCHIVE_WRITE_STATISTICS' exporting archive_handle = archive_handle statistics_only_per_file = 'X'.

PROGRESS_INDICATOR call function 'PROGRESS_INDICATOR' exporting i_text = text-002 i_processed = gv_cnt_tot i_total = gv_cnt_proc i_output_immediately = 'X' importing e_progress_sent = lv_progress_send.

ARCHIVE_CLOSE_FILE call function 'ARCHIVE_CLOSE_FILE' exporting archive_handle = archive_handle exceptions internal_error = 1 wrong_access_to_archive = 2 others = 3.



Contribute (Add Comments)

Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.







The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or anything else you feel is relevant to this report.

This will then be available for everyone to easily find by simply searching on the report name RJKSDCQP_DELETE_FROM_DB or its description.