Search Results csd_service_codes_b_pk1

Overview

CSD_SERVICE_CODES_B is the base (or "B") table that stores all service codes within the Oracle E-Business Suite Depot Repair module (product code CSD). Service codes represent the standardized categories of repair work performed on customer assets — for example, component-level repair, board replacement, calibration, or preventative maintenance. Because Depot Repair relies on service codes to drive pricing, resource planning, and work-order classification, this table functions as a foundational reference object that numerous downstream transactions depend upon.

Using the heuristic Data Vault classification mined from the documented foreign-key structure, CSD_SERVICE_CODES_B can be characterized as a hub-leaning table. In Data Vault modelling terms, it behaves as a business hub: it holds a stable business key (SERVICE_CODE) and a surrogate identifier, and it is referenced by many surrounding link and transactional structures rather than carrying the foreign keys itself. This is consistent with a reference-data object that is defined once and consumed broadly.

Key Information Stored

The table is owned by the CSD schema and, in the documented 12.2.2 physical schema, contains 26 columns. The most significant are:

• SERVICE_CODE_ID — the surrogate primary key, enforced by CSD_SERVICE_CODES_B_PK1. This is the column referenced by all foreign keys pointing to this table.
• SERVICE_CODE — the business key, enforced by the unique index CSD_SERVICE_CODES_B_U2. This is the user-visible code that identifies the service.
• ACTIVE_FROM / ACTIVE_TO — date-range columns defining the effective window during which the service code is valid.
• OBJECT_VERSION_NUMBER — the optimistic-locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns that capture audit and ownership information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexible descriptive flexfield columns, allowing installations to store additional, site-specific service code attributes without schema changes.

Note that the surrogate key (SERVICE_CODE_ID) and the business key (SERVICE_CODE) are distinct; both are backed by unique indexes and should not be conflated when joining or querying.

Common Use Cases and Queries

Typical scenarios include validating that a selected service code is currently active, populating LOVs in repair order entry, and joining service codes to the transactions that reference them.

• Resolving active service codes: SELECT SERVICE_CODE_ID, SERVICE_CODE FROM CSD.CSD_SERVICE_CODES_B WHERE SYSDATE BETWEEN NVL(ACTIVE_FROM, SYSDATE) AND NVL(ACTIVE_TO, SYSDATE);
• Enriching repair job data: joining CSD_REPAIR_JOB_XREF.SERVICE_CODE_ID to CSD_SERVICE_CODES_B.SERVICE_CODE_ID to obtain the human-readable code.
• Reporting flexfield usage: grouping by ATTRIBUTE_CATEGORY to assess how descriptive flexfields are populated across service codes.
• Audit reporting: filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent maintenance of reference data.

Related Objects

The following objects reference CSD_SERVICE_CODES_B through SERVICE_CODE_ID and are among the most significant dependencies:

• CSD_BULLETIN_SCS — links service bulletins to service codes (CSD_BULLETIN_SCS.SERVICE_CODE_ID).
• CSD_SC_WORK_ENTITIES — associates service codes with work entities.
• CSD_REPAIR_JOB_XREF — cross-reference of repair jobs to service codes.
• CSD_RO_SERVICE_CODES — repair-order level service code assignments.
• CSD_SC_DOMAINS — service code domain associations.
• ISC_DR_SERVICE_CODE_MV — a materialized view surfaced for Depot Repair reporting.

Together these confirm the table's role as a hub of shared reference data that supports bulletins, repair jobs, repair orders, and work entities throughout Depot Repair.