Search Results csd_sc_recommendations_b




Overview
Explore in AI Chat

Overview

The CSD_SC_RECOMMENDATIONS_B table is a base (transaction) table in the Oracle E-Business Suite Depot Repair module (product code CSD). It stores service code recommendations — the suggested service codes that might be applied to a service request, repair order, or returned item during the depot repair lifecycle. The "_B" suffix indicates that this is the base table underlying a translated (_TL) entity, meaning any descriptive/displayable attributes may be maintained in a corresponding translations table keyed on the same primary key and language.

The table is owned by the CSD schema and is reported as VALID in the ETRM metadata. Its documented physical content lists 11 columns. A heuristic Data Vault classification, mined from the FK structure, places this object as a standalone relation. In Data Vault modeling terms, this would most naturally resolve into a satellite-like construct hung off the CSD_SC_DOMAINS hub, with the dependent-child relationship to the domain expressing the recommendation context, rather than a classic hub or link entity.

Key Information Stored

The most significant of the 11 documented columns are:

  • SC_RECOMMENDATION_ID — the surrogate primary key that uniquely identifies each service code recommendation record.
  • SC_DOMAIN_ID — a foreign key to CSD_SC_DOMAINS, associating the recommendation with its owning service code domain. This is the principal business-key candidate driving the recommendation context.
  • RECOMMENDATION_TYPE_CODE — a lookup-style code classifying the recommendation (for example, the category or rule by which the service code is suggested).
  • ACTIVE_FROM and ACTIVE_TO — effective-dating columns defining the window in which the recommendation is valid and eligible for application.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column used by the framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard 5 WHO columns capturing audit who/when information for insert and last update.

The surrogate key (SC_RECOMMENDATION_ID) is clearly distinguishable from business identifiers; the documented metadata does not list a unique business index, but the combination of SC_DOMAIN_ID plus RECOMMENDATION_TYPE_CODE and the effective dates forms the natural business identifier.

Common Use Cases and Queries

Typical uses include listing currently-active recommendations for a given service domain, joining recommendations to their domain for reporting, and validating that a recommendation is within its effective window at time of application.

SELECT r.sc_recommendation_id, r.sc_domain_id,
       r.recommendation_type_code, r.active_from, r.active_to
FROM   csd.csd_sc_recommendations_b r
WHERE  r.sc_domain_id = :domain_id
AND    TRUNC(SYSDATE) BETWEEN r.active_from AND NVL(r.active_to, TRUNC(SYSDATE));

A second common pattern joins the domain master to expose descriptive context, and a third filters by RECOMMENDATION_TYPE_CODE for reporting on recommendation activity by type and period.

Related Objects

The documented FK relationship is the anchor for related objects:

  • CSD_SC_DOMAINS — referenced via SC_DOMAIN_ID; the primary parent of this table.
  • CSD_SC_RECOMMENDATIONS_TL — the translations (child) table, keyed on SC_RECOMMENDATION_ID plus language.
  • Service code and depot repair domain APIs and concurrent programs that consume recommendation data.
  • Reporting views in the CSD schema that project recommendations alongside domain attributes.

The table functions primarily as a configuration/reference repository that supports the automated or assisted selection of service codes during depot repair processing.