Search Results csd_sc_domains




Overview
Explore in AI Chat

Overview

CSD_SC_DOMAINS is a transactional configuration table owned by the CSD schema within the Oracle E-Business Suite Depot Repair module. Its documented purpose is to store service code domains — the qualifying scope or applicability rules that determine where and to which items a given service code may be applied. In EBS 12.1.1 and 12.2.2, service codes define the billable or warrantable repair activities performed in a depot or field service context, and CSD_SC_DOMAINS provides the domain-level detail that ties those codes to inventory items, item categories, and category sets.

The object is registered as VALID with a documented physical schema of 28 columns in ETRM 12.2.2. The heuristic Data Vault classification mined from its foreign-key structure is standalone, meaning the table is not modelled as a dependent satellite of a parent hub in the mined relationship graph. From a modelling-suggestion perspective, CSD_SC_DOMAINS behaves most like a hub or a richly attributed link in its own right: it carries its own surrogate key, references a service code, and optionally references an item or category, while also acting as the referenced parent for downstream recommendation records. Note that the "standalone" classification reflects the absence of upstream chains beyond a single hop, not a lack of relationships.

Key Information Stored

The table is anchored by the surrogate primary key SC_DOMAIN_ID, enforced through CSD_SC_DOMAINS_PK1, with a unique index CSD_SC_DOMAINS_U1 on the same column. The most significant columns are:

Because the table has no name or description column documented, domain rows are meaningfully identified only through the combination of SERVICE_CODE_ID plus the applicable item or category qualifier.

Common Use Cases and Queries

The primary use case is resolving which service codes apply to a given item or category during depot repair intake, estimate generation, and service-code defaulting. A typical query retrieves all domains for a service code:

  • SELECT sc_domain_id, service_code_id, domain_type_code, inventory_item_id, category_id, category_set_id FROM csd.csd_sc_domains WHERE service_code_id = :p_service_code_id;
  • Joining to the parent to describe the code: SELECT d.*, b.service_code FROM csd.csd_sc_domains d, csd.csd_service_codes_b b WHERE d.service_code_id = b.service_code_id;
  • Item-driven lookup: filter on INVENTORY_ITEM_ID to list all applicable service codes for a repaired item.
  • Category-driven lookup: join CATEGORY_ID/CATEGORY_SET_ID to MTL_CATEGORIES and MTL_CATEGORY_SETS for reporting.
  • Audit reporting using LAST_UPDATE_DATE and LAST_UPDATED_BY to track configuration changes over time.

Related Objects

  • CSD_SERVICE_CODES_B — referenced by CSD_SC_DOMAINS.SERVICE_CODE_ID; the parent service code definition table.
  • CSD_SC_RECOMMENDATIONS_B — references CSD_SC_DOMAINS.SC_DOMAIN_ID, linking recommended actions to a domain.
  • MTL_SYSTEM_ITEMS_B / MTL_CATEGORIES_B / MTL_CATEGORY_SETS_B — supply the item, category, and category-set context for INVENTORY_ITEM_ID, CATEGORY_ID, and CATEGORY_SET_ID.
  • CSD_SC_DOMAINS_PK1 / CSD_SC_DOMAINS_U1 — primary key constraint and unique index on SC_DOMAIN_ID.
  • FND_ATTACHED_DOCUMENTS and standard WHO/FND lookups — support attachments and audit metadata.