Results for “bic_fctv_sr_response”

4 results




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

Overview

BIC_FCTV_SR_RESPONSE is a read-only reporting view belonging to the BIC – Customer Intelligence product family within Oracle E-Business Suite. In the ETRM 12.2.2 metadata the object is explicitly flagged as obsolete, and the excerpt notes "Not implemented in this database." This indicates that the view was shipped as part of the Customer Intelligence (BIC) analytics schema yet is no longer created or supported in current installations. Its purpose was to present a flattened, denormalized fact set describing service request (SR) response activity, joining incident header data to the specific incident action that represents the first or recorded response. The name derives from the fact-table nomenclature BIC_FCTV (BIC Fact View) combined with SR_RESPONSE, signalling that it fed a dimensional model where incidents were measured against time and customer dimensions. This places the view firmly in the analytical reporting layer rather than the transactional foundation, and it would have been consumed by Customer Intelligence dashboards, service-response KPIs, and time-period trend reports. Users searching for the underlying table cs_incident_actions would arrive at this view because the join to CS_INCIDENT_ACTIONS is what supplies the RESPONSE_DATE column.

Underlying Base Objects

The ETRM metadata records no separately documented base objects, but the embedded view text reveals the full FROM clause. The view is defined over eight objects:

  • CS_INCIDENTS_ALL_B — the incident/service request header (alias INC).
  • CS_INCIDENT_ACTIONS — the action history providing the response event (alias CSA); this is the object referenced by the search term cs_incident_actions.
  • CS_INCIDENT_STATUSES (STAT), CS_INCIDENT_SEVERITIES (ISEV), and CS_INCIDENT_TYPES (ITYP) — the lookup/validation tables supplying status, severity, and type attributes.
  • BIC_DIMV_CUSTOMERS (DC) — the customer dimension view.
  • BIC_DIMV_TIME (DT) — the time dimension view mapping action creation dates to accounting periods, quarters, halves, and years.
  • JTF_RS_RESOURCE_EXTNS (PF) — the resource extension table joined with an outer join ((+)) on INCIDENT_OWNER_ID to resolve the owner and active start date.

The critical join is INC.INCIDENT_ID = CSA.INCIDENT_ID, which ties every incident to its action rows, with CSA.CREATION_DATE BETWEEN DT.ACT_PERIOD_START_DATE AND DT.ACT_PERIOD_END_DATE collapsing the response into a time period. Because the action table can hold many rows per incident, the view is effectively at incident-action grain, and consumers must aggregate to obtain a single response per SR.

Key Columns

The column list mixes foreign keys, degenerate dimensions, and descriptive attributes:

Common Use Cases and Queries

The view supported measuring how quickly service requests received an action, segmented by severity, type, customer, and period. A representative query, adapted to the documented column set, counts responses per accounting period:

  • Response volume by period:
    SELECT ACT_PERIOD_NAME, COUNT(DISTINCT INCIDENT_ID) responses FROM BIC_FCTV_SR_RESPONSE GROUP BY ACT_PERIOD_NAME ORDER BY ACT_PERIOD_NAME;
  • Responses by severity and type:
    SELECT INCIDENT_SEVERITY, INCIDENT_TYPE, COUNT(*) FROM BIC_FCTV_SR_RESPONSE GROUP BY INCIDENT_SEVERITY, INCIDENT_TYPE;
  • Response lag:
    SELECT INCIDENT_ID, RESPONSE_DATE - INCIDENT_DATE days_to_respond FROM BIC_FCTV_SR_RESPONSE;
  • Open versus closed mix:
    SELECT CLOSE_FLAG, COUNT(*) FROM BIC_FCTV_SR_RESPONSE GROUP BY CLOSE_FLAG;

Because the object is obsolete and not implemented, equivalent analysis in EBS 12.1.1 and 12.2.2 must be built directly against CS_INCIDENTS_ALL_B and CS_INCIDENT_ACTIONS, joining BIC or custom dimensions as required.