Search Results sr_rslv

Overview

APPS.CS_SR_REPORT_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates service request (SR) incident data into a single, denormalized result set suitable for operational reporting, ad hoc querying, and integration extracts. Within the Oracle TeleService and Service Request Management modules, incident records are stored across normalized tables for statuses, severities, urgencies, types, lookup codes, customer products, and party information. This view joins those sources and translates internal identifiers into human-readable values, exposing codes and their meanings side by side.

The view is owned by the APPS schema and is intended for read-only consumption. It surfaces both the coded value (for example, PROBLEM_CODE) and the corresponding descriptive text (PROBLEM_CODE_MEANING, PROBLEM_CODE_DESCRIPTION), which simplifies reporting against Service Request problem, resolution, and status lookups. The user query reference "sr_prob" maps directly to the problem-code join in this view, where the CS_LOOKUPS aliased SR_PROB supplies the REQUEST_PROBLEM_CODE lookup values.

Underlying Base Objects

The view is defined over the following documented base objects:

• CS_INCIDENTS_ALL_VL (view) — the primary incident/service-request source, providing incident numbers, dates, customer, product, serial, and status/severity/urgency foreign keys.
• MTL_SYSTEM_ITEMS_KFV (synonym) — supplies inventory item concatenated segments and descriptions for the product.
• CS_INCIDENT_TYPES_TL, CS_INCIDENT_SEVERITIES_TL, CS_INCIDENT_URGENCIES_TL (synonyms) — translated names for incident type, severity, and urgency.
• CS_INCIDENT_STATUSES_VL (view) — status name and the CLOSE_FLAG used to derive the CLOSED_FLAG column.
• CS_LOOKUPS (view) — referenced twice for the REQUEST_PROBLEM_CODE and REQUEST_RESOLUTION_CODE lookups.
• CS_CUSTOMER_PRODUCTS (view) and HZ_PARTIES (synonym) — customer product reference number and party number/name.
• JTF_RS_RESOURCE_EXTNS_VL (view) — resource name of the incident owner.
• FND_USER (synonym) — user name of the person who logged the incident.
• FND_GLOBAL and CSICUMPI_PUB (packages) — support environment/user context and incident processing.

Most joins are outer joins (denoted by (+)), allowing incidents to appear even when the associated product, lookup, party, or owner is absent.

Key Columns

• INCIDENT_ID, INCIDENT_NUMBER — internal and displayed service request identifiers.
• INVENTORY_ITEM_ID, PRODUCT_NAME, PRODUCT_DESCRIPTION — the product associated with the request.
• INCIDENT_DATE, CLOSE_DATE, DATE_CLOSED, CLOSED_FLAG — lifecycle dates and closure indicator.
• CUSTOMER_ID, CUSTOMER_NUMBER, COMPANY_NAME — party identifiers and party name.
• CURRENT_SERIAL_NUMBER, CUSTOMER_PRODUCT_ID, REFERENCE_NUMBER — installed/base details.
• PROBLEM_CODE, PROBLEM_CODE_MEANING, PROBLEM_CODE_DESCRIPTION — the SR_PROB lookup values.
• RESOLUTION_CODE, RESOLUTION_CODE_MEANING, RESOLUTION_CODE_DESCRIPTION — the SR_RSLV lookup values.
• INCIDENT_TYPE, SEVERITY, STATUS_CODE, URGENCY — classifications.
• OWNER, SUMMARY, LOGGED_BY_NAME, RECORD_IS_VALID_FLAG — ownership, narrative, and audit flags.

Common Use Cases and Queries

Typical scenarios include problem-code trend reporting, open-incident aging, product failure analysis, and closure SLA monitoring. A representative query filtering on problem code is:

• SELECT incident_number, product_name, problem_code, problem_code_meaning, status_code, owner, incident_date FROM apps.cs_sr_report_v WHERE problem_code = '&sr_prob' AND closed_flag = 'N' ORDER BY incident_date DESC;

An aggregate variant counts incidents by problem and severity:

• SELECT problem_code, problem_code_meaning, severity, COUNT(*) FROM apps.cs_sr_report_v GROUP BY problem_code, problem_code_meaning, severity;

Because the view exposes codes and meanings together, it is well suited to BI Publisher reports, Discoverer worksheets, and OBIEE extracts without additional lookup resolution.