MREQ_<Request Type Name>

Contains request type-specific information.

When the Reporting Meta Layer is synchronized, a view is created for every request type defined in the system. The name of each view is defined on the request type screen in the Meta Layer View field. It defaults to a prefix MREQ_ and a suffix that defaults to the first 20 alphanumeric characters of the corresponding request type name. For example, if there are three request types defined in Demand Management named Support Ticket, Bug, and Work Order, then three corresponding Meta Layer views would exist: MREQ_SUPPORT_TICKET, MREQ_BUG, and MREQ_WORK_ORDER.

The view columns are identical to those of the general MREQ_ALL_REQUESTS view (including the global request user data fields), and they also include additional columns for each custom request detail field for the request type. This allows a report designer to create a report that implements business logic based on customer-defined request detail fields.

Sample 1

For example, consider the Work Order request type. This request type might have custom detail fields with tokens like CUSTOMER, TIME_ESTIMATE, and ACTUAL_TIME. The corresponding view MREQ_WORK_ORDER would contain columns with these names:

SQL> desc mreq_work_order;

Results 1

Name                            Null?    Type
------------------------------- -------- ----
REQUEST_ID                      NOT NULL NUMBER
CUSTOMER                                 VARCHAR2(200)
TIME_ESTIMATE                            VARCHAR2(200)
ACTUAL_TIME                              VARCHAR2(200)

Sample 2

A report is needed that will list information about work order requests in which the actual time was more than one day longer than the estimated time.

An SQL query such as the following would handle this:

SELECT request_number REQUEST_NUM,
       status_name CURRENT_STATUS,
       customer CUSTOMER,
       (actual_time – time_estimate) EXTRA_DAYS_WORKED
FROM   mreq_work_order
WHERE  time_estimate IS NOT NULL
AND    actual_time IS NOT NULL
AND    (actual_time – time_estimate) > 1
ORDER BY request_number;