Results for “solution_id”

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

Overview

The CSD_REPAIR_KB_SOLUTIONS_V view is a reporting construct in the Oracle E-Business Suite Depot Repair (CSD) module, owned by the APPS schema and marked VALID in the ETRM 12.2.2 reference. Its purpose is to surface all Knowledge Base solutions associated with depot repair orders, providing a consolidated, query-ready projection of repair lines joined to the Knowledge Base set assignments that reference them. Rather than requiring report authors to reconstruct the complex join path across the repair order, the Knowledge Base link table, and the multi-versioned Knowledge Base set tables, this view encapsulates that logic and presents a single row per linked solution per repair line.

The view is particularly notable because it internally resolves the ambiguity introduced by the versioned CS_KB_SETS_B base table. A Knowledge Base article typically exists in several version rows sharing the same SET_NUMBER, distinguished by status. This view shields the consumer from that complexity by programmatically selecting the appropriate version.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSD_REPAIRS (SYNONYM) — The depot repair line records; the join condition links KB_SET_LINK.OTHER_ID to CR.REPAIR_LINE_ID.
• CS_KB_SET_LINKS (SYNONYM) — The association table linking a Knowledge Base set to an external object. The view filters this table to OBJECT_CODE = 'DR', meaning the link is to a Depot Repair object.
• CS_KB_SETS_VL (VIEW) — The translated (view-level) Knowledge Base set header, supplying the ROW_ID, SET_ID, SET_NUMBER, and NAME of the solution.
• CS_KB_SET_TYPES_VL (VIEW) — The translated set type reference, joined via SET_TYPE_ID to validate/qualify the set.
• CS_KB_SETS_B (SYNONYM) — The base (untranslated) Knowledge Base set table, referenced only inside the correlated DECODE subqueries that resolve which SET_ID should appear.
• CS_LOOKUPS (VIEW) — Outer-joined on LOOKUP_TYPE = 'CS_KB_LINK_TYPE' to resolve the LINK_TYPE code to its meaning.
• FND_GLOBAL (PACKAGE) — The standard EBS session context package, referenced for the runtime environment (for example, org or user context).

Key Columns

• ROW_ID — The ROW_ID of the Knowledge Base set header, useful as a unique identifier of the solution record.
• SOLUTION_ID — Aliased from KB_SET.SET_ID; the internal identifier of the Knowledge Base set.
• SOLUTION_NUMBER — Aliased from KB_SET.SET_NUMBER; the human-readable article number common across versions.
• SOLUTION_TITLE — Aliased from KB_SET.NAME; the descriptive name of the solution.
• REPAIR_LINE_ID — The Depot Repair line to which the solution is linked, enabling correlation back to the repair order.

Common Use Cases and Queries

Typical use cases include reporting which Knowledge Base solutions have been linked to repair lines, auditing solution usage across repair orders, and embedding solution lookups in custom Depot Repair OAF pages or reports.

Because the SET_ID resolution is handled inside the view, a simple select is sufficient:

• SELECT repair_line_id, solution_number, solution_title FROM csd_repair_kb_solutions_v WHERE repair_line_id = :p_repair_line_id;
• SELECT solution_number, COUNT(*) FROM csd_repair_kb_solutions_v GROUP BY solution_number ORDER BY 2 DESC;
• SELECT r.repair_line_id, v.solution_number, v.solution_title FROM csd_repair_kb_solutions_v v, csd_repairs r WHERE v.repair_line_id = r.repair_line_id AND r.repair_order_id = :p_order;

The version-selection logic uses COUNT subqueries against CS_KB_SETS_B: if exactly one OBS row exists the SET_ID resolves to NULL, if exactly one PUB row exists that SET_ID is returned, and otherwise the maximum SET_ID among rows sharing the SET_NUMBER is used. Understanding this behavior is essential when reconciling report output against Knowledge Base version history.