Search Results source_solution_name

Overview

CSD_RO_SERVICE_CODES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the CSD (Depot Repair) product family. Its stated purpose is to display service codes that are associated with repair orders. In practice, the view denormalizes the intersection of repair lines, their assigned service codes, source metadata, and knowledge-base solution linkage into a single flattened result set, so that concurrent programs, Oracle Reports layouts, OAF pages, and custom SQL do not need to reconstruct the joins repeatedly.

The view carries a status of VALID and is available in both the 12.1.1 and 12.2.2 releases. Because it resolves several descriptive attributes (service code name, description, lookup meanings, solution numbers), it is most often used for read-only presentation rather than transactional DML. The column ROW_ID is exposed for tooling that requires a row identifier, but updates should be directed at the base table CSD_RO_SERVICE_CODES rather than this view.

Underlying Base Objects

The view is defined over the following objects, using ANSI-style outer joins marked with the (+) operator:

• CSD_RO_SERVICE_CODES (aliased CRSC) — the driving entity, supplying the repair-line-to-service-code association and all descriptive flexfield attributes.
• CSD_SERVICE_CODES_VL (aliased CSC) — the service code master, supplying SERVICE_CODE, NAME, DESCRIPTION, ACTIVE_FROM, and ACTIVE_TO. This is a translated (VL) view, so the returned name and description follow the session language.
• CSD_REPAIRS_V (aliased CR) — supplies the human-readable REPAIR_NUMBER.
• CS_KB_LINKED_SOLUTIONS_VIEW (aliased KB) — an outer-joined knowledge-base source, matched when OBJECT_CODE = 'DR' and the solution set ID matches SOURCE_SOLUTION_ID.
• FND_LOOKUPS (FND) — decodes SOURCE_TYPE_CODE against lookup type CSD_SOURCE_TYPE.
• FND_LOOKUPS (FND2) — an outer join decoding REC_TYPE_CODE against lookup type CSD_SC_RECOMMENDATION_TYPES.

Additional dependencies referenced by the underlying objects include CS_KB_SECURITY_PVT, CS_STD, FND_GLOBAL, FND_PROFILE, and the PA security and project utility packages (PA_SECURITY, PA_PROJECT_UTILS, PA_TASK_UTILS, PA_CROSS_BUSINESS_GRP), which enforce organizational and knowledge-base access control at query time.

Key Columns

• RO_SERVICE_CODE_ID — primary key of the underlying association record; the join key back to CSD_RO_SERVICE_CODES.
• REPAIR_LINE_ID / REPAIR_NUMBER — the repair order line to which the service code applies.
• SERVICE_CODE_ID, SERVICE_CODE, SERVICE_CODE_NAME, SERVICE_CODE_DESC, SERVICE_CODE_ACTIVE_FROM, SERVICE_CODE_ACTIVE_TO — the service code definition and its effective dating.
• APPLICABLE_FLAG — indicates whether the service code is currently applicable to the repair line.
• SOURCE_TYPE_CODE / SOURCE_TYPE_MEANING — how the service code was introduced (for example, manual entry versus recommendation), decoded from CSD_SOURCE_TYPE.
• REC_TYPE_CODE — the recommendation type lookup code. This is the column most frequently searched on; it is joined to CSD_SC_RECOMMENDATION_TYPES and is the mechanism by which recommended service codes are categorized. It is outer-joined, so rows without a recommendation type return NULL.
• SOURCE_SOLUTION_ID, SOURCE_SOLUTION_NUMBER, SOURCE_SOLUTION_NAME — the linked knowledge-base solution that generated the recommendation.
• APPLIED_TO_EST_FLAG, APPLIED_TO_WORK_FLAG — whether the service code has been applied to the estimate and to the work order respectively.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield context and segments for the association record.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and optimistic-locking columns.

Common Use Cases and Queries

The most frequent requirement is to enumerate each asso