Search Results incident_number_n




Overview
Explore in AI Chat

Overview

APPS.CSF_SR_HIST_V is a service request history view in Oracle E-Business Suite, exposed under the APPS schema and available in both 12.1.1 and 12.2.2. It presents a denormalized, presentation-ready projection of service request (SR) incident data, joining the core incident tables with customer, contact, product, and reference-code lookups. As a view rather than a table, it holds no data of its own; it derives its result set at query time from the underlying incident, instance, party, and item objects.

The view exists primarily to support service request history reporting, inquiry screens, and integration extracts where a single flat structure covering incident number, summary, status, severity, product, and customer context is preferable to assembling the underlying joins manually. Because it resolves translated reference-code names dynamically using the session language, the view returns locale-appropriate type, severity, status, and urgency descriptions.

Underlying Base Objects

The view is defined over the following documented base objects:

Joins to the item instance, item flexfield, and product-related objects are outer joins, so incidents without a linked product or instance still return a row.

Key Columns

The projection includes identity, classification, and party attributes:

  • row_id, incident_id, org_id — unique row locator, incident primary key, and operating unit.
  • incident_number and incident_number_n — the displayed incident number and a second aliased copy of the same column. The alias incident_number_n is the exact term used in the search that led to this object; it is a duplicate projection of inc.incident_number.
  • summary — the incident summary text from the translation table.
  • incident_type, severity, status_code, urgency — descriptive names resolved from the translation tables in the session language.
  • product_name, product_description, instance_number — item flexfield segments and installed base instance.
  • company_name, customer_number, contact_name, phone, email, contact_number — customer and contact details from HZ_PARTIES and HZ_CONTACT_POINTS.
  • time_zone_name, country, caller_type, group_type — supporting context attributes.

Common Use Cases and Queries

Typical usage retrieves history for a given incident or customer, or extracts SR data for reporting. A representative query filters on the aliased incident number:

SELECT incident_number_n, summary, status_code, severity, product_name, contact_name
FROM   apps.csf_sr_hist_v
WHERE  org_id = :p_org_id
AND    incident_number_n = :p_incident_number;

The view is also used for listing all service requests for a customer or installed instance, and for feeding service history into downstream dashboards or integration interfaces where the flattened structure reduces join complexity. Because the language-dependent lookups use USERENV('LANG'), results honor the querying session's language setting.