Results for “bic_service_request_summary_v”

4 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIC_SERVICE_REQUEST_SUMMARY_V is a reporting view historically shipped with the Oracle E-Business Suite Customer Intelligence (BIC) module. It presents a consolidated, read-only summary of service requests — internally stored as incidents in the Oracle TeleService / Service (CS) schema — enriched with account and party information drawn from the Customer Intelligence layer. The view is classified as obsolete in ETRM documentation for release 12.1.1 and 12.2.2, and the metadata explicitly records that it is "not implemented in this database." Consequently, it should be treated as a legacy artifact: DBAs upgrading to 12.1.1 or 12.2.2 will typically find it absent, and any custom code, concurrent program, or BI Publisher data template that references it will fail at parse time with an ORA-00942 error.

Its functional role was to flatten the normalized service request data model into a denormalized projection suitable for downstream analytics and extract feeds — for example, loading a data warehouse or a Customer Intelligence dashboard. Because the definition is declared WITH READ ONLY, no DML is permitted through the view.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the published view text unambiguously identifies the tables joined. The driving table is CS_INCIDENTS_ALL_VL, the multilingual (translated) incidents view that stores service request header information, including incident number, summary text, dates, and the foreign keys to severity, status, account, and inventory item. Supporting lookups include CS_INCIDENT_SEVERITIES and CS_INCIDENT_STATUSES, both constrained to the incident subtype INC to filter out other CS subtype rows. Party and account context is supplied by BIC_PARTIES_V, joined with an outer ((+)) join on CUST_ACCOUNT_ID. Escalation data is resolved through JTF_TASK_REFERENCES_B (reference code ESC, object type SR) to JTF_TASKS_B, restricted to task type 22, again via outer joins so that service requests without escalations are not dropped. All joins are effectively outer on the peripheral tables, preserving every incident in CS_INCIDENTS_ALL_VL.

Key Columns

Common Use Cases and Queries

Typical usage centered on service request volume, severity mix, closure performance, and escalation tracking by account. A representative query:

  • SELECT ACCOUNT_NUMBER, REQUEST_NUMBER, SEVERITY, STATUS, SR_CREATION_CHANNEL, CREATION_DATE, CLOSE_DATE FROM BIC_SERVICE_REQUEST_SUMMARY_V WHERE TRUNC(CREATION_DATE) >= TRUNC(SYSDATE)-30 ORDER BY CREATION_DATE DESC;
  • SELECT STATUS, COUNT(*) FROM BIC_SERVICE_REQUEST_SUMMARY_V GROUP BY STATUS; — for open/closed distribution reporting.
  • SELECT ACCOUNT_NUMBER, COUNT(*) FROM BIC_SERVICE_REQUEST_SUMMARY_V WHERE ESCALATION_DATE IS NOT NULL GROUP BY ACCOUNT_NUMBER; — escalated request analysis.

Because the object is obsolete and not implemented, equivalent reporting should be re-pointed at supported CS views such as CS_INCIDENTS_ALL_VL joined directly to the severity and status lookup tables, or at the current Service Request reporting views delivered in the TeleService module.