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:
- CS_INCIDENTS_ALL_B — the primary transactional source of incident records (aliased INC), providing ID, owner, status, severity, type, incident date, close date, customer, and ORG_ID.
- CS_INCIDENT_SEVERITIES — severity lookup, joined on INCIDENT_SEVERITY_ID.
- CS_INCIDENT_TYPES — incident type lookup, joined on INCIDENT_TYPE_ID.
- CS_INCIDENT_STATUSES — status lookup supplying CLOSE_FLAG.
- BIC_DIMV_TIME — time dimension, restricting rows to the period in which the incident closed.
- BIC_DIMV_CUSTOMERS — customer dimension, outer-joined on PARTY_ID.
- JTF_RS_RESOURCE_EXTNS — resource extension table, outer-joined on RESOURCE_ID to the incident owner.
The documented metadata lists no formally referenced base objects, so the join relationships above are derived from the embedded view text.
Key Columns
- INCIDENT_SEVERITY_FK — the severity foreign key, aliased from INCIDENT_SEVERITY_ID; the primary key for grouping closed incidents by severity.
- INCIDENT_ID, INCIDENT_OWNER_FK, INCIDENT_STATUS_FK, INCIDENT_TYPE_FK — identifiers for the incident, its owner, status, and type.
- CLOSE_DATE, CLOSE_FLAG — the closure timestamp and the status-derived indicator of whether the incident is closed.
- INCIDENT_SEVERITY, SEVERITY_DESC — the severity name and description from CS_INCIDENT_SEVERITIES.
- INCIDENT_TYPE, INC_TYPE_DESC — the incident type name and description.
- PARTY_ID, COUNTRY, CITY, STATE, CUSTOMER_CATEGORY_FK, MARKET_SEGMENT_FK — customer dimensional attributes, possibly null due to the outer join.
- ACT_PERIOD_NAME, ACT_YEAR, ACT_QUARTER, ACT_HALF_YEAR and associated start/end dates — time dimension attributes for period-based reporting.
- LAST_NAME, FIRST_NAME, FULL_NAME — placeholders returned as NULL in the view text.
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.
-
View: BIC_FCTV_SR_CLOSE 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_FCTV_SR_CLOSE 12.1.1
Not implemented in this database·Explore BIC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1