Results for “bic_fctv_sr_total”

4 results




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

Overview

The view BIC_FCTV_SR_TOTAL is a reporting construct belonging to the BIC – Customer Intelligence product family, a module now classified as Obsolete within Oracle E-Business Suite. In the Oracle EBS 12.1.1 and 12.2.2 release context, this view was designed to expose a denormalized, read-only fact set that combines Service Request (incident) transaction data with customer, time, and resource dimensions. Its role was to feed the Customer Intelligence analytics layer, allowing service-request activity to be summarized and sliced against customer attributes, fiscal/accounting time periods, incident severity, incident type, and the owning resource.

Because the view is defined WITH READ ONLY, it is strictly a query surface — no DML is possible. The ETRM metadata explicitly notes that the object is “Not implemented in this database,” meaning that in the database where this documentation was generated, the view does not physically exist. This is consistent with its Obsolete classification; organizations upgrading to 12.2.2 may find the object absent or unsupported, and any dependent custom reports, concurrent programs, or BI Publisher datasets referencing it must be remediated.

Underlying Base Objects

Although the documented view metadata lists no referenced base objects, the supplied view text reveals the complete FROM clause. The view is defined over the following objects:

  • CS_INCIDENTS_ALL_B (aliased INC) — the core service request/incident table, source of incident identity, ownership, status, severity, type, and dates.
  • JTF_RS_RESOURCE_EXTNS (aliased PF) — resource extension information, joined on INC.INCIDENT_OWNER_ID = PF.RESOURCE_ID (+) using an outer join to preserve incidents without a resolvable owner.
  • CS_INCIDENT_STATUSES (aliased STAT) — incident status reference, supplying the CLOSE_FLAG.
  • CS_INCIDENT_SEVERITIES (aliased ISEV) — severity name and description lookups.
  • CS_INCIDENT_TYPES (aliased ITYP) — incident type name and description lookups.
  • BIC_DIMV_TIME (aliased DT) — a Customer Intelligence time dimension used to derive accounting period and calendar attributes.
  • BIC_DIMV_CUSTOMERS (aliased DC) — a Customer Intelligence customer dimension supplying party, geography, category, and market segment attributes.

The time join is range-based: INC.INCIDENT_DATE BETWEEN DT.ACT_PERIOD_START_DATE AND DT.ACT_PERIOD_END_DATE, which maps each incident to an accounting period row rather than a single key lookup.

Key Columns

The view exposes a mix of foreign keys, descriptive attributes, and dimensional context. Notable columns include:

Common Use Cases and Queries

Typical usage involved summarizing service-request volumes by customer segment, severity, or accounting period, and correlating incident activity with the tenure of the owning resource via EMPLOYEE_START_DATE. A representative query follows:

SELECT DT.ACT_PERIOD_NAME,
       DC.COUNTRY,
       ISEV.NAME AS INCIDENT_SEVERITY,
       ITYP.NAME AS INCIDENT_TYPE,
       COUNT(INC.INCIDENT_ID) AS INCIDENT_COUNT
  FROM BIC_FCTV_SR_TOTAL INC
 WHERE INC.ACT_YEAR = :p_year
 GROUP BY DT.ACT_PERIOD_NAME, DC.COUNTRY, ISEV.NAME, ITYP.NAME;

A tenure-oriented query might filter on the resource start date:

SELECT INC.INCIDENT_ID,
       INC.EMPLOYEE_START_DATE,
       INC.INCIDENT_DATE,
       INC.INCIDENT_SEVERITY
  FROM BIC_FCTV_SR_TOTAL INC
 WHERE INC.EMPLOYEE_START_DATE >= :p_start_date
 ORDER BY INC.EMPLOYEE_START_DATE;

Given the Obsolete status and the documented “Not implemented” note, any 12.1.1/12.2.2 environment still relying on this view should treat it as a deprecation risk and migrate equivalent reporting to supported CS_ and BIC_ dimensional sources.