Search Results csd_repairs




Overview
Explore in AI Chat

Overview

The CSD_REPAIRS table is the central transactional entity within the Oracle E-Business Suite Depot Repair (CSD) module. It serves as the master repository for all repair orders, commonly referred to as Repair Lines, created within the system. Every repair transaction, from initial intake and estimation through final completion and billing, is anchored to a record in this table. Its role is fundamental to the repair lifecycle, acting as the primary hub that integrates core business functions such as service contracts, installed base management, project accounting, and order management by linking to their respective transactional entities.

Key Information Stored

Each record in CSD_REPAIRS represents a single repair order. The table is uniquely identified by the primary key column, REPAIR_LINE_ID. A second unique key, REPAIR_NUMBER, ensures business-level uniqueness for the repair order identifier. The table's structure is defined by its critical foreign key relationships, which store the essential context for each repair. Key columns include CUSTOMER_PRODUCT_ID (linking to the CSI_ITEM_INSTANCES or CS_CUSTOMER_PRODUCTS tables to identify the serviced item), REPAIR_TYPE_ID (classifying the repair), and INCIDENT_ID (linking to the associated service request). It also holds references to financial and planning objects such as CONTRACT_LINE_ID, ORDER_LINE_ID, PROJECT_ID, and TASK_ID, enabling integrated cost tracking and revenue recognition.

Common Use Cases and Queries

This table is central to operational reporting, process tracking, and data integration. Common use cases include generating open repair backlog reports, analyzing repair cycle times, and reconciling repair costs against estimates or service contracts. Technical consultants often query this table to troubleshoot data issues or build custom interfaces. A typical pattern for fetching core repair data involves joining to its primary referenced tables:

  • Tracking Repair Status: SELECT repair_number, creation_date, status_code FROM csd_repairs WHERE status_code NOT IN ('CLOSED', 'CANCELLED') ORDER BY creation_date;
  • Linking Repair to Item and Contract: SELECT cr.repair_number, csi.serial_number, okc.line_number FROM csd_repairs cr, csi_item_instances csi, okc_k_lines_b okc WHERE cr.customer_product_id = csi.instance_id AND cr.contract_line_id = okc.id AND cr.repair_line_id = :p_repair_line_id;

Related Objects

CSD_REPAIRS has extensive relationships, acting as a parent to numerous child transactional tables and being a child to several master tables. Key dependent child tables, which store detailed information for a repair line, include CSD_REPAIR_ESTIMATE (for cost estimates), CSD_REPAIR_ACTUALS (for actual costs incurred), CSD_REPAIR_HISTORY (for audit trail), and CSD_PRODUCT_TRANSACTIONS (for material issues). As indicated by the foreign keys, it references master data from modules like Service (CS_INCIDENTS_ALL_B), Installed Base (CSI_ITEM_INSTANCES), Order Management (OE_ORDER_LINES_ALL), Service Contracts (OKC_K_LINES_B), and Resource Management (JTF_RS_RESOURCE_EXTNS).