Results for “repair_type_id”

50+ results




Overview
Explore in AI Chat

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

Overview

The CSD.CSD_REPAIR_TYPES_SAR table is a Depot Repair (CSD) module object within Oracle E-Business Suite, validated in both release 12.1.1 and 12.2.2. Its documented purpose is to save search attributes associated with repair type configuration. Functionally, it acts as an association or cross-reference table that binds a repair type to one or more transaction billing types, allowing the Depot Repair application to determine which billing type applies to a given repair type during search, validation, and transaction-processing operations. The primary key is defined by the constraint CSD_REPAIR_TYPES_SAR_PK, keyed on REPAIR_TXN_BILLING_TYPE_ID.

Under the heuristic Data Vault classification derived from the foreign key topology, this table is satellite-leaning. In Data Vault modeling terms, it behaves less like a pure hub (which would hold only a business key) and more like a satellite or link-satellite structure: it carries descriptive and keyed attributes that depend on parent entities in CSD_REPAIR_TYPES_B and other reference tables, rather than owning an independent business identity. This classification should be treated as a modeling suggestion, not a normative statement of the physical design.

Key Information Stored

The documented physical schema contains ten columns. The columns of primary analytical importance are:

There is no documented unique index separate from the primary key, so the natural business key is effectively the combination of REPAIR_TYPE_ID and TXN_BILLING_TYPE_ID.

Common Use Cases and Queries

Typical usage centers on resolving which billing types are available for a given repair type during order entry, estimate generation, or billing validation in Depot Repair. A common reporting pattern joins the association table to its master repair type table:

  • Listing billing types per repair type: SELECT b.repair_type_id, b.name, s.txn_billing_type_id FROM csd_repair_types_b b, csd_repair_types_sar s WHERE b.repair_type_id = s.repair_type_id;
  • Resolving billing type descriptions: join TXN_BILLING_TYPE_ID to CS_TXN_BILLING_TYPES to obtain human-readable billing type names.
  • Auditing changes: query LAST_UPDATED_BY and LAST_UPDATE_DATE to trace configuration changes to repair type billing mappings.
  • Multi-org filtering: restrict results by SECURITY_GROUP_ID to respect operating unit data segregation.

Because the table governs configuration rather than high-volume transaction data, query volumes are typically low and results are well-suited to setup validation and diagnostic reports.

Related Objects

The most significant related objects are the parent and reference tables referenced by its foreign keys:

  • CSD_REPAIR_TYPES_B — master repair type table, joined via REPAIR_TYPE_ID.
  • CS_TXN_BILLING_TYPES — billing type reference table, joined via TXN_BILLING_TYPE_ID.
  • FND_SECURITY_GROUPS — security group definitions, joined via SECURITY_GROUP_ID.
  • CSD_REPAIR_TYPES_TL — translated repair type names, commonly joined through CSD_REPAIR_TYPES_B for reporting.
  • The CSD_REPAIR_TYPES_SAR_PK constraint and related indexes, which enforce row uniqueness.

These relationships confirm the table's role as a configuration bridge between repair types and billing types within the Depot Repair module.