Search Results csd_repair_types_b_u1

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

Overview

CSD.CSD_REPAIR_TYPES_B is the foundational setup table for repair processing in Oracle E-Business Suite's Depot Repair module (part of the CSD schema / TeleService–Depot Repair family). Each row defines a distinct repair type — the highest-level classification that governs how a repair order is processed, including which workflow drives it, how it is priced and billed, and whether it can be interfaced to Order Management for sales order creation. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the APPS_TS_SEED tablespace, which correctly reflects its role as seeded/reference configuration data rather than high-volume transactional data.

The table is the base ("_B") table of a translated entity: descriptive text is held separately in CSD_REPAIR_TYPES_TL, while this table stores the language-independent attributes and operational flags. Under the multi-tenant referenced architecture introduced for 12.2.x-style schemas, the CSD_REPAIR_TYPES_SAR table stores security-assignment records, and the physical schema includes a ZD_EDITION_NAME column alongside REPAIR_TYPE_ID in the unique index CSD_REPAIR_TYPES_B_U1.

The metadata's heuristic Data Vault classification is hub-leaning. This is consistent with the structure: REPAIR_TYPE_ID is a stable surrogate key that acts as the enterprise-wide business key for a repair type, and most surrounding tables (repairs, order groups, flow statuses, and materialized views) reference it via a foreign key. A Data Vault modeler would therefore treat CSD_REPAIR_TYPES_B as a hub, with the workflow, billing, price-list, and date-activity attributes forming a satellite.

Key Information Stored

• REPAIR_TYPE_ID — NUMBER(15). The unique, system-generated surrogate identifier for the repair type. This is the primary key (CSD_REPAIR_TYPES_B_PK) and the primary unique-index candidate in CSD_REPAIR_TYPES_B_U1. All downstream repair tables join on this column.
• ZD_EDITION_NAME — the edition discriminator that, together with REPAIR_TYPE_ID, completes the documented unique index used in the 12.2.2 physical schema.
• WORKFLOW_ITEM_TYPE — VARCHAR2. The workflow item type associated with the repair type; this is the driver that determines the process flow applied to repairs of that type. Indexed by the non-unique index CSD_REPAIR_TYPES_B_N1 and referenced against WF_ITEM_TYPES.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective-dating pair controlling when the repair type is valid and selectable; standard Oracle date-track convention.
• REPAIR_MODE, REPAIR_TYPE_REF, SEEDED_FLAG — operational mode, an external reference identifier, and the flag distinguishing Oracle-seeded rows from user-defined rows.
• BUSINESS_PROCESS_ID, SECURITY_GROUP_ID, PRICE_LIST_HEADER_ID — foreign keys to CS_BUSINESS_PROCESSES, FND_SECURITY_GROUPS, and QP_LIST_HEADERS_B, controlling service/repair business process, security grouping, and price-list pricing respectively.
• CPR_TXN_BILLING_TYPE_ID, CPS_TXN_BILLING_TYPE_ID, LS_TXN_BILLING_TYPE_ID, LR_TXN_BILLING_TYPE_ID, MTL_TXN_BILLING_TYPE_ID, LBR_TXN_BILling_TYPE_ID, EXP_TXN_BILLING_TYPE_ID, plus THIRD_RMA_TXN_BILLING_TYPE_ID and THIRD_SHIP_TXN_BILLING_TYPE_ID — the per-transaction-class billing type foreign keys (raised by Customer, material, labor, expense, third-party RMA/shipment, etc.), each referencing CS_TXN_BILLING_TYPES.
• AUTO_PROCESS_RMA, INTERFACE_TO_OM_FLAG, BOOK_SALES_ORDER_FLAG, RELEASE_SALES_ORDER_FLAG, SHIP_SALES_ORDER_FLAG, INTERNAL_ORDER_FLAG, THIRD_PARTY_FLAG — boolean control flags governing automatic RMA processing and Order Management / fulfillment integration behavior.
• START_FLOW_STATUS_ID, RES_DT_CALC_POINT — starting flow status and the point at which resolution/repair duration is measured.
• columns and ATTRIBUTE_CATEGORY — the descriptive flexfield structure and up to fifteen seeded DFF segments for customer-specific extension.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus OBJECT_VERSION_NUMBER for optimistic locking.

The business-key candidate is REPAIR_TYPE_ID (a surrogate that also functions as the natural integration key); the unique index CSD_REPAIR_TYPES_B_U1 enforces its uniqueness (together with the edition column), distinguishing it from the non-unique access path CSD_REPAIR_TYPES_B_N1 on WORKFLOW_ITEM_TYPE.

Common Use Cases and Queries

The table is queried wherever repair setup, repair order entry, or repair reporting needs the definition or attributes of a repair type. Common patterns include:

• Looking up active repair types for a repair order — joining the base table to its translation table to retrieve user-visible names, filtered by the effective-dating columns:

SELECT b.repair_type_id
     , t.name
     , b.workflow_item_type
     , b.repair_mode
     , b.seeded_flag
  FROM csd.csd_repair_types_b b
     , csd.csd_repair_types_tl t
 WHERE b.repair_type_id = t.repair_type_id
   AND NVL(t.language, USERENV('LANG')) = USERENV('LANG')
   AND b.start_date_active <= SYSDATE
   AND NVL(b.end_date_active, SYSDATE) >= SYSDATE;

• Identifying repair types driving a specific workflow — the workflow item type is the most frequent lookup predicate and is served by the non-unique index CSD_REPAIR_TYPES_B_N1:

SELECT repair_type_id, workflow_item_type
  FROM csd.csd_repair_types_b
 WHERE workflow_item_type = :p_item_type;

• Order Management integration reporting — repair types flagged for OM interfacing are surfaced by:

SELECT repair_type_id, interface_to_om_flag, book_sales_order_flag
  FROM csd.csd_repair_types_b
 WHERE interface_to_om_flag = 'Y' AND seeded_flag = 'N';

• Pricing and billing configuration audits — joining PRICE_LIST_HEADER_ID to QP_LIST_HEADERS_B and the billing-type FKs to CS_TXN_BILLING_TYPES to verify which price lists and billing types are attached per repair type.
• Reporting / analytics — the ISC Depot Repair materialized views (ISC_DR_CURR_01_MV, ISC_DR_BKLG_01_MV, ISC_DR_COSTS_01_MV, ISC_DR_MTTR_01_MV, etc.) all key on REPAIR_TYPE_ID, making this table a required dimension in backlog, cost, MTTR, and charges reporting.

Related Objects

• CSD_REPAIRS — the principal transactional child; joins via REPAIR_TYPE_ID. Every repair order is classified by exactly one repair type.
• CSD_REPAIR_ORDER_GROUPS — groups repair orders and references REPAIR_TYPE_ID, used in grouping/consolidation scenarios.
• CSD_REPAIR_TYPES_TL — the translated child holding name and description in each installed language; always joined with the base table for user-facing lists.
• CSD_REPAIR_TYPES_SAR — the security-assignment child that restricts repair-type visibility by role/user.
• CSD_FLWSTS_TRANS_B — flow-status transactions reference repair type; used in repair flow/status progression logic.
• WF_ITEM_TYPES — referenced by WORKFLOW_ITEM_TYPE; identifies the workflow driving the repair type.
• CS_BUSINESS_PROCESSES — referenced by BUSINESS_PROCESS_ID; defines the business process context for the repair type.
• QP_LIST_HEADERS_B — referenced by PRICE_LIST_HEADER_ID; supplies the price list used for pricing repair transactions.
• CS_TXN_BILLING_TYPES — referenced by the family of *_TXN_BILLING_TYPE_ID columns; defines how each repair transaction class is billed.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs multi-org / security group assignment.
• ISC_DR_* materialized views — the complete set of Depot Repair reporting MVs (ISC_DR_CURR_01_MV, ISC_DR_BKLG_01_MV, ISC_DR_COSTS_01_MV, ISC_DR_CHARGES_01_MV, ISC_DR_MTTR_01_MV, ISC_DR_SERVICE_CODE_MV, and their _02 variants) reference REPAIR_TYPE_ID and rely on this table as a reporting dimension.

Because the table is seeded/reference data, direct DML is normally performed through the Depot Repair setup forms and concurrent programs rather than ad hoc SQL; developers should preserve the standard WHO columns, OBJECT_VERSION_NUMBER, and the unique business key when building integrations.