Skip to end of metadata
Go to start of metadata

1. Objectives

This article explains how to use the OCC Custom Code Management (CCM) data provider .

2. Metric instance creation

For the CCM data provider, in the OCC Dashboard, we visualize the history of created metric instance in the CCM Webdynpro application: /STDF/WD_CCM

We can access to the CCM Webdynpro application using this URL: https://<Server>:<port>/sap/bc/webdynpro/stdf/wd_ccm

Here is the CCM metrics list :

  1. Custom code objects used
  2. Custom code objects not used
  3. Custom code objects without Quality issues
  4. Custom code objects created
  5. Custom code objects updated
  6. Custom code objects quantity
  7. Custom code objects with Quality issues
  8. Number of quality issues
  9. Nb. standard and custom code objects used

Note that we have to create a metric instance for each metric figuring in the CCM webdynpro in order to use it with the CCM DP in the OCC dashboard.

Here is the steps to follow in order to create a metric instance :

1. Click on "Edit" button

 

2. Click on "New" button

3. Check that the ID the metric instance is incremented by one

4. Enter the Instance name

5. Select a metric from the metrics list

6. Click on "Save" button


7. Add the appropriate parameters :  In our case, we keep the default configuration of parameters for this metric.

3. Supported Renderers

The CCM data provider supports the following list of renderers:

  • Line Chart
  • Pie Chart
  • Donut Chart
  • Line-Column Chart
  • Dual Line Chart
  • Dual Line-Column
  • Dual Bar-Column
  • Stack Bar Chart
  • Stack Column Chart
  • Stack Column Chart2Label
  • Waterfall Chart
  • Column Chart
  • Bar Chart
  • Table History Renderer
  • Trend Table Renderer
  • Dynamic Table (not supported for the metric "Nb. standard and custom code objects used" )

CCM

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=1 |LIVE_COLLECT=TRUE|display_value=false

Period / Resolution : Last Month / Week 

4. Validation

For the CCM metrics from 1 to 8, the validation source is the BW Web Application :https://<server>:<port>/sap/bw/BEx?sap-language=EN&bsplanguage=EN&CMD=LDOC& TEMPLATE_ID=0TPL_CCLM_BW_REPORTING

PS: In order to check the displayed results in the OCC dashboardwe have to configure BW Web Application as shown in the screenshot below :We should enter in Snapshot Day field the date of yesterday before pressing the Execute button.

For the last metric, the sources are the cubes listed below:

  • 0CCMAW is used when the Object Type = Transaction )
  • 0SM_UPLMD ( is used when the Object Type <> Transaction )

Here are some examples of the CCM metrics validation:

4.1 Custom code objects used 

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=32 |LIVE_COLLECT=TRUE|display_value=false

In the settings tab, we have selected to display the data on the following period 31.10.2017|day and for the used metric instance we have the following parameters:

So, the following list of filters should be set in the BW Web application:

The returned result is :

4.2 Custom code objects not used

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=39 |LIVE_COLLECT=TRUE|display_value=false

In the settings tab, we have selected to display the data on the following period Yesterday|Day and for the used metric instance we have the following parameters

So, the following list of filters should be set in the BW Web application:

   

The returned result is :

4.3 Number of quality issues

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=19 |LIVE_COLLECT=TRUE|display_value=false

We have the following parameters for the used metric instance:


So, the following list of filters should be set in the BW Web application:

The returned result is :

At this stage, it seems that we get a wrong value (The result returned by the BW Web application is not equal to the result returned by the CCM DP).

In order to get the right result we have to apply, in addition, a drilldown on the mentionned fields as shown in the screenshot below :

To get the exact resultwe have to sum the QUAL_PRIO_1_MSGS+QUAL_PRIO_2_MSGS+QUAL_PRIO_3_MSGS so the result is 28+0+0=28

4.4 Custom code objects created

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=28 |LIVE_COLLECT=TRUE|display_value=false

We have the following parameters for the used metric instance:

So, the following list of filters should be set in the BW Web application:

The returned result is :


4.5 Custom code objects updated

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=35 |LIVE_COLLECT=TRUE|display_value=false


We have the following parameters for the used metric instance:

So, the following list of filters should be set in the BW Web application:

The returned result is :

4.6 Custom code objects quantity

Query: 

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=22 |LIVE_COLLECT=TRUE|display_value=false

We have the following parameters for the used metric instance:


So, the following list of filters should be set in the BW Web application:

The returned result is :

4.7 Custom code objects without Quality issues

Query

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=15 |LIVE_COLLECT=TRUE|display_value=false

We have the following parameters for the used metric instance:


So, the following list of filters should be set in the BW Web application:

The returned result is :

4.8 Custom code objects with Quality issues

The Custom code objects without Quality issues metric value can be checked with this formula :

Custom Code Objects with Quality issues = Custom Code Objects Quantity – Custom Code Objects without Quality issues

Query

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=25 |LIVE_COLLECT=TRUE|display_value=false

The table below shows the list of applied filters on this test case:

Custom Code Objects Quantity    

The table below shows the list of applied filters on this test case:

 


                      

Custom Code Objects without Quality issues

The table below shows the list of applied filters on this test case:

We can check the displayed result of the Custom code objects with Quality issues through this formula :


Custom Code Objects with Quality issues = Custom Code Objects Quantity – Custom Code Objects without Quality issues = 10287 - 9039

So Custom Code Objects with Quality issues = 1248

4.9 Nb. standard and custom code objects used

The Nb. Standard and CC objects used metric value can be checked with this formula :

Nb. Standard and CC objects used = Nb. Used transactions + Nb.Used objects

Note that to get the Nb.Used transactionswe have to use the /STDF/QD_TRANS_PERF_D query and tget the Nb.Used objectswe have to use the 0SM_UPLMD cube.

Query :

/STDF/DP_CCM:COLOR=#1f77b4|legend=CCM|OCC_JUMP_IN=|SLA=|TREND=|G2Y=|Y2R=|COLOR_RATING=|DISPLAY_ATTRIBUTES=|visible=true|Metric_Instances=29 |LIVE_COLLECT=TRUE|display_value=false



Nb.Used transactions

Nb.Used objects

Nb.Used objects is equal to the rows number minus 1 because the first row is a header

We can check the displayed result of the Custom code objects with Quality issues through this formula :

Nb. Standard and CC objects used = Nb. Used transactions + Nb.Used objects = 80+ (302-1)

= 80 + 301

So Nb. Standard and CC objects used = 381









  • No labels