Results for “csd_ro_soln_sc_v”

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

Overview

CSD_RO_SOLN_SC_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Depot Repair (CSD) module. Its primary purpose is to associate a depot repair solution with the applicable service codes and knowledge-base metadata. In Depot Repair, repair lines are frequently linked to solution documents stored in the knowledge base (cs_kb_sets), and those solutions may themselves be associated with standard service codes represented by AHL_MR_HEADERS_V records. This view flattens that multi-table relationship into a single, query-friendly structure, exposing solution identity, the repair line to which it applies, and the corresponding service code.

The view is especially relevant when a user searches on service_code, since SERVICE_CODE is a first-class column in the projection. It is documented in the ETRM 12.2.2 metadata as not implemented in the reference database, meaning it exists as a defined object whose text is supplied but which may not be physically instantiated in every environment. This is common for views whose deployment depends on configuration or specific patch levels in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view text is defined over four source objects:

• CS_KB_SETS_VL — the knowledge-base solution/set view, supplying solution identity, number, and title.
• CSD_RO_SOLUTIONS — the Depot Repair solutions entity linking a repair line to a solution number.
• AHL_MR_HEADERS_V — the service code (maintenance requirement header) view, supplying SERVICE_CODE_ID, SERVICE_CODE (MR.TITLE), effective dates, and status.
• CS_KB_SET_LINKS — the link table joining sets to their related objects, used here to tie solutions (OBJECT_CODE = 'DRSD') to service codes and to resolve the current set for a repair line (OBJECT_CODE = 'DR', LINK_TYPE = 'S').

Joins are driven on SET_NUMBER = SOLUTION_NUMBER, SET_ID, and OTHER_ID = MR_HEADER_ID. A correlated subquery selects the maximum SET_ID for the repair line to ensure only the applicable solution-to-set association is returned.

Key Columns

• SOLUTION_ID / SOLUTION_NUMBER / SOLUTION_TITLE — identity and label of the knowledge-base solution linked to the repair.
• REPAIR_LINE_ID — the Depot Repair line the solution pertains to.
• SERVICE_CODE_ID — surrogate key to the maintenance-requirement header (MR_HEADER_ID).
• SERVICE_CODE — the human-readable service code title, the column most often filtered or searched.
• EFFECTIVE_FROM / EFFECTIVE_TO — validity window of the service code.
• STATUS — current state of the associated service code record.

Common Use Cases and Queries

Typical scenarios include identifying all solutions tied to a given service code, auditing repair-line-to-service-code linkages, or driving downstream reports on valid service codes. A representative query is:

SELECT solution_number, service_code, effective_from, effective_to
FROM csd_ro_soln_sc_v
WHERE service_code = :p_service_code
AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE);

This view serves as a convenient join layer, sparing report developers from reconstructing the cs_kb_set_links relationships manually.