Results for “incident_status_id”

50+ results




Overview
Explore in AI Chat

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

Overview

CS_SR_REPORT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Service (CS) product family. It is a denormalized, read-only projection over Service Request (incident) data, and its stated purpose is to feed the Service Request Summary and Detail reports. The view consolidates fields that would otherwise require many joins — incident header information, customer and party details, product context, and the code/meaning/description triplets for problem classification and resolution — into a single row per incident, keyed by INCIDENT_ID.

The view is documented in ETRM with status VALID for both 12.1.1 and 12.2.2. In 12.2.2 the metadata lists it as defined over a mixture of views, synonyms, and packages, reflecting the standard EBS layering in which APPS synonyms abstract the underlying _ALL base tables. The column PROBLEM_CODE that prompted this lookup is one of the classification attributes exposed directly by the view.

Underlying Base Objects

The documented base objects for CS_SR_REPORT_V are:

Most joins to descriptive tables are outer joins ((+)), so incidents missing a product, customer product, party, problem code, or resolution code still return a row with nulls in the affected columns.

Key Columns

Common Use Cases and Queries

The view is typically consumed by the seeded Service Request Summary/Detail reports and by custom extracts that need a flattened service request picture. Querying by problem code is a common analyst task:

  • SELECT incident_number, problem_code, problem_code_meaning, company_name, status_code FROM cs_sr_report_v WHERE problem_code = 'HARDWARE_FAILURE';
  • Counts by problem classification: SELECT problem_code, problem_code_meaning, COUNT(*) FROM cs_sr_report_v GROUP BY problem_code, problem_code_meaning ORDER BY 3 DESC;
  • Resolution trending: SELECT resolution_code, resolution_code_meaning, COUNT(*) FROM cs_sr_report_v WHERE closed_flag = 'Y' GROUP BY resolution_code, resolution_code_meaning;
  • Customer-facing detail: SELECT incident_number, summary, product_name, owner, date_closed FROM cs_sr_report_v WHERE customer_number = :party_number;

Because the view joins only outer-joined descriptive tables and language-filtered lookups, users should be aware that rows may contain nulls for product, customer, or code attributes, and that meanings depend on the session language. It is a reporting construct only and should not be used for DML.