The collector for virtual forge - code profiler is named: /DVD/MON_VF_CL_COL_CP
The KPIs are defined via KPI definition and input table /DVD/MON_VF_CCFG.
Input table /DVD/MON_VF_CCFG sets extended KPI definition with following fields:

KPI	KPI name
Rule number	KPI rule number
App level	Approval Level
Find type	Finding Type
Impact	Impact
TC domain	Test Case Domain
TC name	Test Case name
Status	Finding status
Source type	Finding source type
Package	Package
Object	Object Type
Object name	Object Name in Object Directory
PU type	Program Unit Type
PU name	Program Unit Name
Add to detail	Add relevant records to details
Active	Is KPI rule active?
Changed by	Last changed by user [automatically filled]
Changed at	Last changed date [automatically filled]
Created by	Created by user [automatically filled]
Created at	Created date [automatically filled]

In collector parameters needs to be defined:

Parameter name	Description
VF_CP_SCENARIO	CodeProfiler Scenario Name

The collector provides also detailed output in detail table for relevant KPIs. The detail table is called: VirtualForge CF findings - /DVD/MON_VF_S_DETAIL_FINDIN with following fields:

Test Case Domain

Impact

Test Case Name

Object type

Object Name in Object Directory

Program Unit Type

Program Unit Name

CodeProfiler Scenario Name

KPI name

Some KPIs are provided in standard delivery with collector as examples:

KPI name	Description	Unit
VFORGE_CP_AUTH	Missing AUTHORITY-CHECK in Reports
VFORGE_CP_DB_MOD	Direct Database Modification
VFORGE_CP_INJECT	ABAP Command injection
VFORGE_CP_OS_INJ	OS Command Injection
VF_TD_COMP	CP Test Domain: Compliance findings
VF_TD_DLP	CP Test Domain: Data-Loss Prevention findings
VF_TD_MNT	CP Test Domain: Maintainability findings
VF_TD_PERF	CP Test Domain: Performance findings
VF_TD_ROB	CP Test Domain: Robustness findings
VF_TD_SECUR	CP Test Domain: Security findings

Browser not supported