SAP Reports / Programs | Project System | Structures | Operative Structures(PS-ST-OPR) SAP PS

RCNCC910 SAP ABAP Report - Master data check report: Message output







RCNCC910 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 RCNCC910 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 RCNCC910. "Basic submit
SUBMIT RCNCC910 AND RETURN. "Return to original report after report execution complete
SUBMIT RCNCC910 VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
    See more syntax options for the ABAP SUBMIT statement


Text pool values


Title: Master data check report: Message output
Text Symbol: 001 = FitsIntoPattern
Text Symbol: 002 = Does Not Fit Pattern
Text Symbol: 003 = LiesWithinInterval
Text Symbol: 004 = Lies Outside Interval
Text Symbol: BL1 = Basic list
Text Symbol: BL2 = Level of detail:
Text Symbol: DL1 = Detail list
Text Symbol: LTT = Message description
Text Symbol: SFD = Fields
Text Symbol: SOB = Objects
Text Symbol: SPD = Project
Text Symbol: SPR = WBS element
Text Symbol: SST = Settings
Text Symbol: SV1 = Start values
Text Symbol: SVB = Sales document


INCLUDES used within this REPORT RCNCC910

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:

CO_SF_GET_AUFNR_FROM_AUFPL CALL FUNCTION 'CO_SF_GET_AUFNR_FROM_AUFPL' EXPORTING aufpl_imp = afvc-aufpl IMPORTING aufnr_exp = l_aufnr.

HELPSCREEN_NA_CREATE CALL FUNCTION 'HELPSCREEN_NA_CREATE' EXPORTING meldung = l_meldung meld_id = p_msg-arbgb meld_nr = l_meld_nr msgv1 = p_msg-msgv1 msgv2 = p_msg-msgv2 msgv3 = p_msg-msgv3 msgv4 = p_msg-msgv4 titel = l_titel.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_callback_program = gv_repid i_callback_pf_status_set = 'PF_STATUS' is_layout = gs_layout it_fieldcat = gt_fieldcat it_events = gt_events TABLES t_outtab = gt_outtab1 " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_callback_program = gv_repid i_callback_pf_status_set = 'PF_STATUS' is_layout = gs_layout it_fieldcat = gt_fieldcat it_events = gt_events IMPORTING es_exit_caused_by_user = gs_user_command TABLES t_outtab = gt_outtab2 " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_callback_program = gv_repid i_callback_pf_status_set = 'PF_STATUS' is_layout = gs_layout it_fieldcat = gt_fieldcat it_events = gt_events IMPORTING es_exit_caused_by_user = gs_user_command TABLES t_outtab = gt_outtab3 " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_callback_program = gv_repid i_callback_pf_status_set = 'PF_STATUS' is_layout = gs_layout it_fieldcat = gt_fieldcat it_events = gt_events IMPORTING es_exit_caused_by_user = gs_user_command TABLES t_outtab = gt_outtab4 " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2.

REUSE_ALV_FIELDCATALOG_MERGE CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_program_name = gv_repid i_structure_name = gc_mesg CHANGING ct_fieldcat = gt_fieldcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

REUSE_ALV_EVENTS_GET CALL FUNCTION 'REUSE_ALV_EVENTS_GET' EXPORTING i_list_type = 0 IMPORTING et_events = gt_events.

REUSE_ALV_LIST_DISPLAY CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY' EXPORTING i_callback_program = gv_repid is_layout = gs_layout it_fieldcat = gt_fieldcat * i_save = gc_a it_events = gt_events is_print = gs_print "n_908709 IMPORTING es_exit_caused_by_user = gs_user_command TABLES t_outtab = gt_outtab " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2 .

REUSE_ALV_FIELDCATALOG_MERGE CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_program_name = gv_repid i_structure_name = gc_mesg CHANGING ct_fieldcat = gt_fieldcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

REUSE_ALV_EVENTS_GET CALL FUNCTION 'REUSE_ALV_EVENTS_GET' EXPORTING i_list_type = 0 IMPORTING et_events = gt_events.

REUSE_ALV_GRID_DISPLAY CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING i_callback_program = gv_repid is_layout = gs_layout it_fieldcat = gt_fieldcat * i_save = gc_a it_events = gt_events IMPORTING es_exit_caused_by_user = gs_user_command TABLES t_outtab = gt_outtab " lv_outtab EXCEPTIONS program_error = 1 OTHERS = 2 .

REUSE_ALV_EVENTS_GET CALL FUNCTION 'REUSE_ALV_EVENTS_GET' EXPORTING i_list_type = 0 IMPORTING et_events = gt_events.



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