Create views for request types and table components

Operational Reporting for PPM creates views for request types and table components. A request type or a table component is mapped to a view in Operational Reporting. The view contains all the data of the request type or the table component, including custom data.

The name of the view created for a request type is in the format: RPT_REQ_<request_type>, while the name of the view created for a table component is in the format: RPT_TC_table_component>.

In this topic:

Example: view created for request type

The request type Bug has the following custom fields:

Prompt	Token
Module	MODULE
Difficulty	DIFFICULT
Platform	PLATFORM
Estimated Time to Complete	COMP_TYPE
Impact	IMPACT
Error Log	ERROR_LOG
Reproducible	REPRO
Resolution	RESOLUTION
Steps To Replicate	REPLICATE
Duplicate ID	DUP_ID
Resolution Summary	RESOL_SUM

Operational Reporting creates the view RPT_REQ_BUG for this request type as follows:

RPT_REQ_BUG

 (
  REQUEST_ID,
   REQUEST_TYPE_ID,
   MODULE,
   PLATFORM,
   IMPACT,
   ERROR_LOG,
   REPRO,
   REPLICATE,
   DIFFICULT,
   COMP_TYPE,
   RESOLUTION,
   DUP_ID,
   RESOL_SUM
)

Back to top

Example: view created for table component

The table component FINANCIAL_SCOPE has the following custom fields:

Prompt	Token
Raised by	RAISED_BY
Status	STATUS
Change Category	CHANGE_CATEGORY
Change Description	CHANGE_DESCRIPTION
Cost of Impact	COST_IMPACT
Estimated Effort	EFFORT_DAYS
Create Date	CREATE_DATE

Operational Reporting creates the view RPT_TC_FINANCIAL_SCOPE for this table component as follows:

RPT_TC_FINALCIAL_SCOPE
(
   REQUEST_ID,
   PARAMETER_TOKEN,
   ROW_SEQUENCE_NUMBER,
   RAISED_BY,
   STATUS,
   CHANGE_CATEGORY,
   CHANGE_DESCRIPTION,
   COST_IMPACT,
   EFFORT_DAYS,
   CREATE_DATE
)

Back to top