Results for “bic_fctv_sr_close”

4 results




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

Overview

BIC_FCTV_SR_CLOSE is a read-only reporting view within the Oracle E-Business Suite Customer Intelligence (BIC) module, a component of the ETRM (Enterprise Territory and Resource Management) analytics layer. The view presents a denormalized fact-style record set describing service request (SR) closures, combining incident header attributes with conformed dimensional lookups for time, customer, severity, type, and status. Its role is to support closed-incident analytics — trending, severity distribution, ownership, and customer segmentation — without requiring report authors to re-derive join logic against the transactional CS_INCIDENTS_ALL_B table.

The view is declared WITH READ ONLY, confirming it is intended strictly for query and extraction rather than DML. In the documented ETRM metadata the view is flagged as not implemented in the reference database and BIC Customer Intelligence is marked obsolete, meaning it predates the current Oracle Business Intelligence Applications data model and is retained for legacy report compatibility. The user's search term incident_severity_fk maps directly to the column alias assigned to CS_INCIDENTS_ALL_B.INCIDENT_SEVERITY_ID in this view, and is the foreign key linking a closed service request to its severity classification.

Underlying Base Objects

The view is defined over a mix of transactional and dimensional objects:

The documented metadata lists no formally referenced base objects, so the join relationships above are derived from the embedded view text.

Key Columns

Common Use Cases and Queries

Typical uses include severity distribution of closed incidents by period, close-rate analysis by owner, and customer-segmented trending. A representative query filtering on severity is:

  • SELECT act_period_name, incident_severity, COUNT(*) FROM bic_fctv_sr_close WHERE incident_severity_fk = :severity_id GROUP BY act_period_name, incident_severity;
  • SELECT org_id, incident_type, COUNT(*) FROM bic_fctv_sr_close WHERE act_year = 2024 GROUP BY org_id, incident_type;
  • SELECT country, customer_category_fk, COUNT(*) FROM bic_fctv_sr_close GROUP BY country, customer_category_fk;

Because the row set is already filtered to closed incidents within valid time periods, consumers do not need to re-apply the close-date to time-dimension interval predicate.