Search Results csd_repair_actuals




Overview
Explore in AI Chat

Overview

The CSD_REPAIR_ACTUALS table is a core data structure within the Oracle E-Business Suite (EBS) Depot Repair (CSD) module, specifically in versions 12.1.1 and 12.2.2. It functions as the primary header table for recording and managing the actual costs, charges, and other financial or operational outcomes associated with a completed repair transaction. This table is essential for capturing the realized financial impact of repair activities, moving beyond estimates to the final, auditable record of what was expended and charged. Its existence is critical for cost analysis, profitability reporting, customer billing, and inventory reconciliation within the service supply chain.

Key Information Stored

As a header table, CSD_REPAIR_ACTUALS stores high-level identifiers and summary information for a repair actuals transaction. The primary column is the REPAIR_ACTUAL_ID, which serves as the unique system-generated identifier for each actuals header record. A crucial foreign key is the REPAIR_LINE_ID, which links the actuals header directly back to its source repair order line in the CSD_REPAIRS table. While the provided metadata does not list all columns, typical data stored in such a header table would include creation dates, last update dates, status flags, and potentially summary totals for costs and charges, which are then detailed in the associated lines table.

Common Use Cases and Queries

This table is central to post-repair financial processes. A common use case is generating a report of all final costs for repairs completed within a specific period for managerial review. Another is feeding actual cost data into general ledger interfaces for accounting period closes. Development or support tasks often involve querying this table to troubleshoot billing issues or validate data integrity. A fundamental query pattern joins the actuals header to the repair order and its lines to analyze cost performance.

Sample Query:
SELECT ra.repair_actual_id, r.repair_number, ra.creation_date
FROM csd_repair_actuals ra,
csd_repairs r
WHERE ra.repair_line_id = r.repair_line_id
AND ra.creation_date BETWEEN :p_start_date AND :p_end_date
ORDER BY ra.creation_date DESC;

Related Objects

The CSD_REPAIR_ACTUALS table sits at the center of a key relationship hierarchy within the Depot Repair schema, as documented in the provided metadata.

  • Parent Table (Foreign Key Reference): The table references CSD_REPAIRS via the column CSD_REPAIR_ACTUALS.REPAIR_LINE_ID. This enforces that every repair actuals header must be associated with a valid repair order line.
  • Child Table (Referenced by Foreign Key): The table is referenced by CSD_REPAIR_ACTUAL_LINES via the column CSD_REPAIR_ACTUAL_LINES.REPAIR_ACTUAL_ID. This establishes a one-to-many relationship where a single actuals header record can have multiple detailed line items for parts, labor, and other expenses.

This structure clearly delineates the data model: a repair order (CSD_REPAIRS) has one or more repair actuals headers (CSD_REPAIR_ACTUALS), each of which contains numerous detailed actual cost lines (CSD_REPAIR_ACTUAL_LINES).