RCRR_CONTROL_LCL_IMP is a standard ABAP INCLUDE 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 RCRR_CONTROL_LCL_IMP into the relevant SAP transactions such as SE38 or SE80
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.
Title: Include RCRR_CONTROL_LCL_IMP
No INCLUDES are used within this REPORT code!
No SAP DATABASE tables are accessed within this REPORT code!
DOCU_GET call function 'DOCU_GET' exporting id = 'DT' langu = sy-langu object = lv_object tables line = lt_text exceptions no_docu_on_screen = 1 no_docu_self_def = 2 no_docu_temp = 3 ret_code = 4 others = 5.
LVC_FIELDCATALOG_MERGE call function 'LVC_FIELDCATALOG_MERGE' exporting i_structure_name = 'CRRTASKINFO' changing ct_fieldcat = rt_fieldcat exceptions others = 3.
LVC_FIELDCATALOG_MERGE call function 'LVC_FIELDCATALOG_MERGE' exporting i_structure_name = 'CRR_TRACKHDR_UI_S' changing ct_fieldcat = rt_fieldcat exceptions others = 3.
LVC_FIELDCATALOG_MERGE call function 'LVC_FIELDCATALOG_MERGE' exporting i_structure_name = 'CRR_REPLAY_TRACK_UI_S' changing ct_fieldcat = rt_fieldcat exceptions others = 3.
LVC_FIELDCATALOG_MERGE call function 'LVC_FIELDCATALOG_MERGE' exporting i_structure_name = 'CRR_MESSAGE_UI_S' changing ct_fieldcat = rt_fieldcat exceptions others = 3.
POPUP_TO_CONFIRM call function 'POPUP_TO_CONFIRM' exporting text_question = text-004 default_button = '2' importing answer = lv_answer exceptions text_not_found = 1 others = 2.
POPUP_TO_CONFIRM call function 'POPUP_TO_CONFIRM' exporting text_question = text-006 default_button = '2' importing answer = lv_answer exceptions text_not_found = 1 others = 2.
JOB_OPEN call function 'JOB_OPEN' exporting jobname = gc_jobname importing jobcount = lif_scenario~mv_jobnumber exceptions cant_create_job = 1 invalid_job_data = 2 jobname_missing = 3 others = 4.
JOB_CLOSE call function 'JOB_CLOSE' exporting jobcount = lif_scenario~mv_jobnumber jobname = gc_jobname strtimmed = 'X' * targetsystem = host importing job_was_released = jobreleased exceptions cant_start_immediate = 1 invalid_startdate = 2 jobname_missing = 3 job_close_failed = 4 job_nosteps = 5 job_notex = 6 lock_failed = 7 others = 8.
JOB_OPEN call function 'JOB_OPEN' exporting jobname = gc_jobname jobclass = 'A' importing jobcount = lif_scenario~mv_jobnumber exceptions cant_create_job = 1 invalid_job_data = 2 jobname_missing = 3 others = 4.
JOB_CLOSE call function 'JOB_CLOSE' exporting jobcount = lif_scenario~mv_jobnumber jobname = gc_jobname strtimmed = 'X' * targetsystem = host importing job_was_released = jobreleased exceptions cant_start_immediate = 1 invalid_startdate = 2 jobname_missing = 3 job_close_failed = 4 job_nosteps = 5 job_notex = 6 lock_failed = 7 others = 8.
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.