Search Results csf_debrief_src_numbers_v




Overview
Explore in AI Chat

Overview

The CSF_DEBRIEF_SRC_NUMBERS_V view is an APPS-owned database object within the CSF (Field Service) product family in Oracle EBS 12.1.1 and 12.2.2. It is documented as a VALID view whose stated purpose is to support List of Values (LOV) selection in the Field Service Debrief user interface. The Debrief UI allows field service technicians and dispatchers to record the outcome of a service visit, and the "source number" LOV lets the user associate a debrief line to the originating work object — either a Service Request (SR) or a depot repair order (DR).

The view acts as a lightweight, read-only consolidation layer. Rather than forcing the UI to query the SR and repair schemas separately, the view presents a single, normalized result set in which both source categories share the same column shape. This is a common Oracle EBS design pattern for LOV providers: a UNION query that projects heterogeneous source data into a uniform contract used by the framework's LOV engine. Because it is a view rather than a table, it stores no data and incurs no maintenance or DML considerations; consumers simply SELECT from it.

Underlying Base Objects

The documented view text reveals four referenced objects: CS_INCIDENTS_ALL (synonym), CSD_REPAIRS (synonym), JTF_OBJECTS_VL (view), and JTF_TASKS_VL (view). These are joined in two branches combined by UNION.

  • Service Request branch: joins JTF_TASKS_VL, CS_INCIDENTS_ALL, and JTF_OBJECTS_VL. The task's SOURCE_OBJECT_ID is equated to the incident ID, filtered to SOURCE_OBJECT_TYPE_CODE = 'SR', with the object looked up as OBJECT_CODE = 'SR'. This yields SR-sourced debrief numbers.
  • Depot Repair branch: joins CSD_REPAIRS to JTF_OBJECTS_VL filtered to OBJECT_CODE = 'DR', producing repair-order-sourced rows.

The relationship to JTF_OBJECTS_VL is particularly relevant given the user's search term: that view resolves the JTF object type code to a human-readable NAME, and CSF_DEBRIEF_SRC_NUMBERS_V depends on it to derive the SOURCE_TYPE label. The two UNION branches supply complementary NULLs so that the final projection is column-aligned — SR rows populate INCIDENT_ID and leave REPAIR_LINE_ID null, while DR rows do the reverse, and DESCRIPTION is populated only for SR rows.

Key Columns

  • SOURCE_NUMBER — the user-facing identifier: CSA.INCIDENT_NUMBER for Service Requests, CR.REPAIR_NUMBER for depot repairs. This is the LOV display value.
  • SOURCE_TYPE — the descriptive type name drawn from JTF_OBJECTS_VL.NAME, providing the label shown alongside the number.
  • SOURCE_TYPE_CODE — a hard-coded discriminator, 'SR' or 'DR', identifying which branch produced the row.
  • INCIDENT_ID — the CS_INCIDENTS_ALL.INCIDENT_ID for SR rows; NULL for DR rows.
  • REPAIR_LINE_ID — the CSD_REPAIRS.REPAIR_LINE_ID for DR rows; NULL for SR rows. Note the asymmetry: the DR branch keys on the repair line identifier.
  • DESCRIPTION — the SR summary text for SR rows; NULL for DR rows.

Common Use Cases and Queries

The principal use case is populating the Debrief UI LOV, but the view is also convenient for reporting and integration where a unified list of service source numbers is required. A typical query retrieves all available sources:

  • SELECT source_number, source_type, source_type_code, incident_id, repair_line_id FROM csf_debrief_src_numbers_v ORDER BY 1; — the full LOV set.
  • SELECT * FROM csf_debrief_src_numbers_v WHERE source_type_code = 'SR'; — restricts to Service Requests.
  • SELECT * FROM csf_debrief_src_numbers_v WHERE source_type_code = 'DR'; — restricts to depot repairs.

Because the view joins the JTF and CS schemas without a WHERE clause driving on bind parameters, on large data volumes a developer should constrain by source_type_code or join back to specific incident/repair identifiers rather than scanning the full result set. As with all APPS views, query it through the standard EBS responsibility and security model; do not attempt DML against it.