Results for “csd_sc_recommendation_types”

8 results




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

Overview

The view APPS.CSD_RO_SERVICE_CODES_V exposes service codes that have been associated with repair order lines in Oracle E-Business Suite. It sits at the intersection of the Depot Repair module (CSD — Customer Service Depot Repair) and the Knowledge Base solution linkage. The view is a denormalized reporting layer that joins repair order service code assignments to the repair header, the service code definition, the linked knowledge base solution, and two lookup translations.

Its primary role is to present a human-readable, integration-ready record of which service codes were recommended or applied to each repair line, why they were selected (source type and recommendation type), and whether they were applied to the estimate, the work order, or both. Because it resolves foreign keys for lookup_code values and knowledge base set identifiers, it is the preferred object for reports, OBIEE/BI Publisher extracts, and downstream interfaces that must avoid re-implementing the lookup joins.

Note on search resolution: the term csd_sc_recommendation_types resolves to the lookup type CSD_SC_RECOMMENDATION_TYPES. This view is the documented consumer of that lookup — the rec_type_code column is translated via FND_LOOKUPS using exactly that lookup type.

Underlying Base Objects

The view is defined over four direct objects and several supporting packages referenced by the underlying views:

  • CSD_RO_SERVICE_CODES (referenced via a synonym) — the driving table, holding the repair-line-to-service-code assignment, source information, applicability, and the DFF attribute columns.
  • CSD_SERVICE_CODES_VL — supplies the service code, name, description, and active date range. Joined on service_code_id.
  • CSD_REPAIRS_V — supplies repair_number. Joined on repair_line_id.
  • CS_KB_LINKED_SOLUTIONS_VIEW — supplies the knowledge base set_number and set_name. Joined with an outer join on repair_line_id = other_id and object_code = 'DR', and further on source_solution_id = set_id.
  • FND_LOOKUPS — joined twice: once for CSD_SOURCE_TYPE (source_type_code) and once for CSD_SC_RECOMMENDATION_TYPES (rec_type_code, outer join).

Referenced supporting packages on the base objects include CS_KB_SECURITY_PVT, CS_STD, FND_GLOBAL, FND_PROFILE, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY, and PA_TASK_UTILS. These enforce organization/project security and responsibility context, so query results can be filtered by the run-time security profile of the querying user.

Key Columns

  • ro_service_code_id — primary key of the assignment record; object_version_number supports optimistic locking.
  • repair_line_id, repair_number — identify the repair order line the service code was applied to.
  • service_code_id, service_code, name, description — the service code definition and its descriptive text.
  • active_from, active_to — effective dates of the service code.
  • applicable_flag, applied_to_est_flag, applied_to_work_flag — indicate whether the code applies to the repair and whether it was applied to the estimate and/or the work order.
  • source_type_code and its MEANING (aliased from the first FND_LOOKUPS join) — how the code originated (for example, a knowledge base suggestion).
  • rec_type_code and its MEANING (from CSD_SC_RECOMMENDATION_TYPES) — the recommendation classification associated with the code.
  • source_solution_id, set_number, set_name — the linked Knowledge Base solution, when one exists.
  • attribute_category and attribute1–attribute15 — the descriptive flexfield context and segments.
  • WHO columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) and rowid.

Common Use Cases and Queries

Typical reporting needs include listing all recommended service codes on a repair order, analyzing which recommendation types drive applied estimate or work lines, and extracting knowledge-base-linked solutions for a repair. Because the view already resolves lookup meanings, queries remain simple:

SELECT repair_number, service_code, name, meaning, active_from, active_to FROM apps.csd_ro_service_codes_v WHERE repair_number = :p_repair_number;

To analyze recommendation type frequency against the csd_sc_recommendation_types lookup:

SELECT rec_type_code, meaning, COUNT(*) FROM apps.csd_ro_service_codes_v WHERE rec_type_code IS NOT NULL GROUP BY rec_type_code, meaning ORDER BY 3 DESC;

To isolate codes actually applied to the work order and linked to a knowledge base solution:

SELECT repair_number, service_code, set_name, applied_to_work_flag FROM apps.csd_ro_service_codes_v WHERE applied_to_work_flag = 'Y' AND set_number IS NOT NULL;

When integrating with external systems, callers should filter by the view's indexed identifiers (ro_service_code_id, repair_line_id) rather than by meaning, and should be aware that Knowledge Base columns may be null due to the outer join.