SAP Reports / Programs

CNV_CDMC_UCIA_USAGE_ANALYSIS SAP ABAP Report - CDMC UCIA: Usage Analysis







CNV_CDMC_UCIA_USAGE_ANALYSIS 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 CNV_CDMC_UCIA_USAGE_ANALYSIS 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 CNV_CDMC_UCIA_USAGE_ANALYSIS. "Basic submit
SUBMIT CNV_CDMC_UCIA_USAGE_ANALYSIS AND RETURN. "Return to original report after report execution complete
SUBMIT CNV_CDMC_UCIA_USAGE_ANALYSIS 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_ACTID = Activity ID
Selection Text: P_ADHOC = AD-Hoc Analysis
Selection Text: P_PROJ = Project Specific Analysis
Selection Text: P_PROJID = Project ID
Selection Text: S_PROGS = D Program name
Title: CDMC UCIA: Usage Analysis
Text Symbol: 001 = Selection screen for Usage Analysis


INCLUDES used within this REPORT CNV_CDMC_UCIA_USAGE_ANALYSIS

INCLUDE CNV_CDMC_UCIA_USG_ANAL_TOP.
INCLUDE CNV_CDMC_CC_STATUS_MACROS.
INCLUDE CNV_CDMC_CC_APPLICATION_LOG.


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:

REUSE_ALV_FIELDCATALOG_MERGE CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_program_name = lv_progname i_structure_name = 'ENVI_TYPES' CHANGING ct_fieldcat = lt_fieldcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3.

REPOSITORY_ENVIRONMENT_SET CALL FUNCTION 'REPOSITORY_ENVIRONMENT_SET' EXPORTING obj_type = is_object-object environment_types = is_envi object_name = is_object-obj_name TABLES environment = xt_senvi EXCEPTIONS batch = 1 batchjob_error = 2 not_executed = 3 OTHERS = 4.

CNV_CDMC_CC_FUNC_INCLUDE_INFO CALL FUNCTION 'CNV_CDMC_CC_FUNC_INCLUDE_INFO' EXPORTING iv_funcname = lv_func_name IMPORTING ev_group = lv_func_group EXCEPTIONS communication_failure = 1 system_failure = 2 function_not_exists = 3 include_not_exists = 4 group_not_exists = 5 no_selections = 6 no_function_include = 7 OTHERS = 8.

SUSR_USER_PARAMETERS_GET CALL FUNCTION 'SUSR_USER_PARAMETERS_GET' EXPORTING user_name = sy-uname TABLES user_parameters = lt_usrpara EXCEPTIONS user_name_not_exist = 1 OTHERS = 2.

PUT_CHECK_NAME_CLASS CALL FUNCTION 'PUT_CHECK_NAME_CLASS' EXPORTING wi_object = lv_objtype wi_objname = lv_objname wi_pgmid = lv_pgmid IMPORTING we_name_class = lv_nameclass.

TRINT_OBJECT_NAMESPACE_INFO CALL FUNCTION 'TRINT_OBJECT_NAMESPACE_INFO' EXPORTING iv_pgmid = lv_pgmid iv_object = lv_objtype iv_objname = lv_objname IMPORTING ev_nameclass = lv_nameclass ev_namespace = lv_namespace EXCEPTIONS namespace_not_existing = 1 namespace_use_rejected = 2 invalid_object = 3 OTHERS = 4.



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