Search Results csd_domain_type_code




Overview
Explore in AI Chat

Overview

APPS.CSD_SC_DOMAINS_V is a reporting and integration view in Oracle E-Business Suite that consolidates domain definitions used by the Service Contracts and depot repair service functionality. It draws from the base table CSD_SC_DOMAINS and enriches each row with descriptive, human-readable values from lookup, item, and category sources. The view is primarily consumed by Oracle's Service Contracts and Field Service applications, as well as by external integrations and custom reports that need to resolve domain records into meaningful business descriptions.

The domain_type_code column, which prompted this search, is a discriminator that distinguishes the kind of domain a row represents — for example ITEM, CATEGORY, or other lookup-defined types. Rather than showing only the raw code, the view joins to FND_LOOKUPS to surface the corresponding MEANING for the lookup type CSD_DOMAIN_TYPE_CODE, making the view considerably more useful for end-user reporting.

Underlying Base Objects

The view is defined over the following documented base objects:

  • CSD_SC_DOMAINS (synonym) — the primary source table holding domain records, including domain_type_code, service_code_id, inventory_item_id, category_id, category_set_id, and the fifteen attribute columns.
  • FND_LOOKUPS (view) — supplies the looked-up MEANING for CSD_DOMAIN_TYPE_CODE.
  • MTL_SYSTEM_ITEMS_KFV (synonym) — key flexfield view providing concatenated_segments and description for inventory items.
  • MTL_CATEGORIES_V (view) — supplies category_concat_segs and description for the referenced category.
  • MTL_CATEGORY_SETS_V (view) — supplies category_set_name and description for the referenced category set.
  • CS_STD (package) — used via cs_std.get_item_valdn_orgzn_id to determine the item validation organization.

All joins to the item and category views are outer joins (+), so a domain row is returned even when the referenced item or category cannot be resolved, which preserves completeness of the domain list.

Key Columns

  • SC_DOMAIN_ID — primary identifier of the domain record.
  • DOMAIN_TYPE_CODE — the discriminator code (e.g. ITEM) driving the lookup join and the item-matching logic.
  • MEANING — the descriptive lookup meaning for the domain type.
  • SERVICE_CODE_ID — the associated service code.
  • INVENTORY_ITEM_ID / CONCATENATED_SEGMENTS / MSI.DESCRIPTION — item identity and its resolved flexfield segments and description.
  • CATEGORY_ID / CATEGORY_CONCAT_SEGS / MC.DESCRIPTION — category identity and description.
  • CATEGORY_SET_ID / CATEGORY_SET_NAME / MCS.DESCRIPTION — category set identity and description.
  • ATTRIBUTE_CATEGORY / ATTRIBUTE1..15 — descriptive flexfield content carried for flexibility.
  • Audit columns — created_by, creation_date, last_updated_by, last_update_date, last_update_login, object_version_number.

Common Use Cases and Queries

Typical uses include resolving domain types to their lookup meanings, joining item and category descriptions onto contract or service setups, and validating which items or categories are configured as domains in a given organization.

Sample query listing domains with descriptions:

  • SELECT domain_type_code, meaning, concatenated_segments, category_concat_segs, category_set_name FROM apps.csd_sc_domains_v WHERE domain_type_code = 'ITEM';
  • SELECT domain_type_code, meaning, COUNT(*) FROM apps.csd_sc_domains_v GROUP BY domain_type_code, meaning ORDER BY 1;
  • SELECT sc_domain_id, inventory_item_id, concatenated_segments FROM apps.csd_sc_domains_v WHERE domain_type_code = 'ITEM' AND inventory_item_id IS NOT NULL;

Because the item, category, and category set joins are outer joins, reports should anticipate NULLs in the descriptive columns and filter accordingly when only fully resolved domains are required.