MREQ_REQUEST_TYPES

Accesses configuration details of request types in Demand Management.

You can include request type information in a report by joining the REQUEST_TYPE column in this view with the same column in the general request views (MREQ_REQUESTS and MREQ_<Request Type Name>).

PPM supports user data on request types. All defined request type user data fields are represented in MREQ_REQUEST_TYPES view; there is a column for each request type user data field. The column name for each request type user data field is the same as the token name for that field.

Sample 1

A user data field with token name OWNER is defined for request types, to keep track of a PPM administrator responsible for maintaining each request type configuration.

A corresponding view column named OWNER will be present in MREQ_REQUEST_TYPES view:

SQL> desc mreq_request_types;

Results 1

Name                            Null?    Type
------------------------------- -------- ----
REQUEST_TYPE                    NOT NULL VARCHAR2(30)
REQUEST_TYPE_DESCRIPTION        NOT NULL VARCHAR2(240)
...
INITIAL_STATUS                  NOT NULL VARCHAR2(80)
RESTRICTION                     NOT NULL VARCHAR2(30)
OWNER                                    VARCHAR2(200)
CREATION_DATE                   NOT NULL DATE
CREATED_BY_USERNAME             NOT NULL VARCHAR2(30)
...

Sample 2

An SQL query based on this view might be used to determine how many requests were created prior to a configuration change for a particular request type.

For example, a request type named Work Order has undergone a significant configuration change that invalidates open work order requests that were created before the change. Therefore, a report is needed to determine the status of open work order requests that were created before the changes:

SELECT wo.request_id          REQUEST_NUM,
       wo.request_status      CURRENT_STATUS,
       wo.request_description DESCRIPTION
FROM   mreq_work_order wo, 
       mreq_request_types rt
WHERE  wo.creation_date < rt.last_update_date
AND    rt.request_type = 'Work Order'
ORDER BY 1;

Notice that we do not have to join the explicit request type name to the view MREQ_WORK_ORDER, because it is already implicit in the view definition—only work order requests are returned from that view.