SAP Reports / Programs

BC_SFLIGHT_WRI SAP ABAP Report - Archiving Flights: Write Program (Example ADK Archiving)







BC_SFLIGHT_WRI 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 BC_SFLIGHT_WRI 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 BC_SFLIGHT_WRI. "Basic submit
SUBMIT BC_SFLIGHT_WRI AND RETURN. "Return to original report after report execution complete
SUBMIT BC_SFLIGHT_WRI 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: O_CARRID = D .
Selection Text: O_CONNID = D .
Selection Text: O_FLDATE = D .
Selection Text: O_PLNTPE = D .
Selection Text: P_AR_ILM = D .
Selection Text: P_COMENT = D .
Selection Text: P_DELTST = D .
Selection Text: P_DEST = D .
Selection Text: P_PROT = D .
Selection Text: P_PROT_O = D .
Selection Text: P_SNAP = D .
Selection Text: P_WRIPRD = D .
Selection Text: P_WRITST = D .
Title: Archiving Flights: Write Program (Example ADK Archiving)
Text Symbol: 000 = Flights
Text Symbol: 002 = &1% (&2 of &3) of the flights have been processed
Text Symbol: 010 = Fight was archived
Text Symbol: 013 = Snapshot Created For Flight
Text Symbol: 014 = Flight was Deleted


INCLUDES used within this REPORT BC_SFLIGHT_WRI

No INCLUDES are used within this REPORT code!


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_PROTOCOL_LINE_DETAIL CALL FUNCTION 'ARCHIVE_PROTOCOL_LINE_DETAIL'.

ARCHIVE_PROTOCOL_INIT CALL FUNCTION 'ARCHIVE_PROTOCOL_INIT' EXPORTING i_detailprotocol = p_prot i_protocol_output = p_prot_o.

ARCHIVE_OPEN_FOR_WRITE CALL FUNCTION 'ARCHIVE_OPEN_FOR_WRITE' EXPORTING call_delete_job_in_test_mode = p_deltst "delete job for the archiving action in test mode create_archive_file = p_wriprd "archiving action object = 'BC_SFLIGHT' comments = p_coment do_not_delete_data = p_snap "snapshot action destroy = p_dest "destroy action IMPORTING archive_handle = lv_handle.

ARCHIVE_NEW_OBJECT CALL FUNCTION 'ARCHIVE_NEW_OBJECT' EXPORTING archive_handle = lv_handle.

ARCHIVE_PUT_RECORD CALL FUNCTION 'ARCHIVE_PUT_RECORD' EXPORTING archive_handle = lv_handle record = lw_sflight record_structure = 'SFLIGHT'.

ARCHIVE_PUT_TABLE CALL FUNCTION 'ARCHIVE_PUT_TABLE' EXPORTING archive_handle = lv_handle record_structure = 'SBOOK' TABLES table = lt_sbook.

BC_DEMO_ARCHIVE_OBJECT CALL FUNCTION 'BC_DEMO_ARCHIVE_OBJECT' EXPORTING archive_handle = lv_handle bc_demo_key = lw_bc_demo_key object_delete_flag = 'X'.

ARCHIVE_SAVE_OBJECT CALL FUNCTION 'ARCHIVE_SAVE_OBJECT' EXPORTING archive_handle = lv_handle EXCEPTIONS data_object_not_saved = 1 termination_requested = 2.

ARCHIVE_PROTOCOL_COLLECT CALL FUNCTION 'ARCHIVE_PROTOCOL_COLLECT' EXPORTING i_object = lv_object_id i_text = lv_action_text i_msgtype = 1.

ARCHIVE_PROTOCOL_COLLECT CALL FUNCTION 'ARCHIVE_PROTOCOL_COLLECT' EXPORTING i_object = lv_object_id i_msgtype = 2 i_msgid = sy-msgid i_msgno = sy-msgno i_msgv1 = sy-msgv1 i_msgv2 = sy-msgv2 i_msgv3 = sy-msgv3 i_msgv4 = sy-msgv4.

PROGRESS_INDICATOR CALL FUNCTION 'PROGRESS_INDICATOR' EXPORTING i_text = '&1% (&2 of &3) of the flights processed'(002) "#EC * "text shall be understandable for EN-speaking coleagues i_processed = lv_objects_processed i_total = lv_total_of_objects IMPORTING e_progress_sent = lv_progress_send.

DB_COMMIT CALL FUNCTION 'DB_COMMIT'. "otherwise messag will not appear in the job-log

PROGRESS_INDICATOR CALL FUNCTION 'PROGRESS_INDICATOR' EXPORTING i_text = '&1% (&2 of &3) of the flights processed'(002) "#EC * "text shall be understandable for EN-speaking coleagues i_processed = lv_objects_processed i_total = lv_total_of_objects i_output_immediately = 'X'. "force the progress output (but only during the last call!) in order to send the very last progress indication

ARCHIVE_WRITE_STATISTICS CALL FUNCTION 'ARCHIVE_WRITE_STATISTICS' EXPORTING archive_handle = lv_handle.

ARCHIVE_PROTOCOL_WRITE CALL FUNCTION 'ARCHIVE_PROTOCOL_WRITE'.

ARCHIVE_CLOSE_FILE CALL FUNCTION 'ARCHIVE_CLOSE_FILE' EXPORTING archive_handle = lv_handle.

ARCHIVE_PROTOCOL_COLLECT CALL FUNCTION 'ARCHIVE_PROTOCOL_COLLECT' EXPORTING i_object = lv_object_identifier i_msgtype = 2 i_msgid = 'BA' i_msgno = '701' i_msgv1 = lv_sbook_key i_callback_parameter = lw_callback_param. "optional: for object and message details



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 BC_SFLIGHT_WRI or its description.