Search Results actual_resolution_date

Overview

CSF_SR_HIST_V is a service history extension view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSF (Field Service) product family. It is documented as the "Service History Extension View" and exposes a flattened, reporting-oriented projection of service request (SR) incident data. Rather than presenting raw transactional rows, the view joins the core incident entity in CS_INCIDENTS_ALL_B with its translated lookups, customer product references, contact points, item master descriptions, and timezone information, producing a single denormalized result set suitable for extraction, operational reporting, and downstream integration.

Because the view resolves translated names (type, severity, status, urgency) at query time using USERENV('LANG'), it returns language-appropriate descriptions for the session. It is read-only in practice and should be treated as a reporting artifact rather than a DML target. In 12.1.1 and 12.2.2 the object is listed as VALID, so it can be relied upon by custom concurrent programs, BI Publisher data templates, and OBIEE/OTBI extracts without recompilation.

Underlying Base Objects

The ETRM metadata lists the following referenced base objects:

• CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL — the master incident/SR tables providing the incident ID, org, status, type, urgency, severity, owner, resource, problem code, resolution dates, and descriptive flexfield attributes.
• CS_INCIDENT_TYPES_TL, CS_INCIDENT_SEVERITIES_TL, CS_INCIDENT_STATUSES_TL, CS_INCIDENT_URGENCIES_TL — translated lookup tables supplying the human-readable NAME values via correlated scalar subqueries.
• CSF_SR_TASKS_V — a field service tasks view, supplying task-related context for the incident.
• CSI_ITEM_INSTANCES — installed base item instances, linking the SR to the customer product.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield item view, resolving INVENTORY_ITEM_ID to a concatenated item description.
• HZ_PARTIES, HZ_CONTACT_POINTS, HZ_TIMEZONES, CS_HZ_SR_CONTACT_POINTS — trading community and contact point objects providing party, contact, and timezone context.

The view is therefore centered on CS_INCIDENTS_ALL_B; all other objects are joined to enrich the incident row with descriptive and relational context. Note that CP.REFERENCE_NUMBER in the view text originates from the customer product source, and INC.CUSTOMER_PRODUCT_ID is the join vector.

Key Columns

• INCIDENT_ID, INCIDENT_NUMBER — primary identifier and the SR number; INCIDENT_NUMBER_N is an aliased duplicate.
• ORG_ID — operating unit, essential for multi-org security and reporting.
• INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID and their translated counterparts STATUS_CODE, INCIDENT_TYPE, URGENCY, SEVERITY.
• SUMMARY — the SR summary text from the TL table.
• CUSTOMER_PRODUCT_ID and REFERENCE_NUMBER — the installed-base product link and its reference.
• INCIDENT_ATTRIBUTE_1 through INCIDENT_ATTRIBUTE_15 — descriptive flexfield segments.
• EXPECTED_RESOLUTION_DATE, ACTUAL_RESOLUTION_DATE, INCIDENT_DATE — key service lifecycle timestamps.
• RECORD_IS_VALID_FLAG, INTERFACED_TO_DEPOT_FLAG — status/processing indicators.
• ROW_ID — the underlying ROWID of the incident row, useful for de-duplication.

Common Use Cases and Queries

Typical usage includes SR aging reports, status/severity dashboards, and integration extracts feeding data warehouses. A representative query:

SELECT INCIDENT_NUMBER, STATUS_CODE, SEVERITY, INCIDENT_TYPE, SUMMARY, REFERENCE_NUMBER FROM APPS.CSF_SR_HIST_V WHERE ORG_ID = :p_org AND INCIDENT_DATE >= :p_from_date ORDER BY INCIDENT_DATE DESC;

Filtering by INCIDENT_SEVERITY_ID or STATUS_CODE supports SLA monitoring, while joins on CUSTOMER_PRODUCT_ID or REFERENCE_NUMBER enable installed-base analysis. Because translations are resolved dynamically, consumers should run extracts under a session language consistent with the target audience.