Results for “csd_repair_orders_f”

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

Overview

CSD_REPAIR_ORDERS_F is a table within the CSD (Depot Repair) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The ETRM metadata describes it as a table that stores an aggregated count of closed repair orders, positioning it as a summary or denormalized structure rather than the transactional repair-order master itself. In the Depot Repair workflow, where repair lines move through receive, diagnose, estimate, repair, and close stages, this table provides a pre-aggregated view of closure activity, enabling faster reporting on repair volumes without scanning the full transactional detail. Its role is best understood as a supporting read-optimized layer for closure metrics, typically refreshed or maintained by concurrent programs rather than by direct user data entry.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this table as standalone, meaning it does not participate in the hub-and-link network typically associated with core master data. This classification suggests treating CSD_REPAIR_ORDERS_F as a satellite-like or derived fact structure anchored to CSD_REPAIRS rather than as a hub in its own right. The single documented foreign key, REPAIR_LINE_ID to CSD_REPAIRS, reinforces that the table's grain is the repair line, with the aggregated measures attached to it.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• REPAIR_LINE_ID — The documented unique index (CSD_REPAIR_ORDERS_F_U1) identifies this as the business-key candidate and effectively the grain of the table. It also serves as the foreign key to CSD_REPAIRS, linking each aggregated row to its originating repair line.
• INVENTORY_ITEM_ID — Identifies the item associated with the repair line, enabling item-level rollups of closure activity.
• PRIMARY_QUANTITY and PRIMARY_UOM_CODE — Capture the quantity and unit of measure for the aggregated repair count, providing the quantitative measure and its context.
• RO_CREATION_DATE and DATE_CLOSED — The two principal date dimensions, supporting cycle-time and period-based analysis of repair orders from creation through closure.
• STATUS — The status of the aggregated repair order record, typically reflecting the closed state indicated in the table's description.
• Audit and program columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID follow standard EBS audit and concurrent-program conventions, identifying who or what process created and last modified each row.

No surrogate system-generated primary key column is separately documented; REPAIR_LINE_ID functions as the practical unique identifier through the U1 index.

Common Use Cases and Queries

The primary use case is closed-repair-order reporting. Analysts typically aggregate counts by item, status, or time period. A representative pattern joins to the repair master and filters on closure dates:

• Count of closed repair orders per item: SELECT INVENTORY_ITEM_ID, SUM(PRIMARY_QUANTITY) FROM CSD.CSD_REPAIR_ORDERS_F GROUP BY INVENTORY_ITEM_ID;
• Closure trends by month: SELECT TRUNC(DATE_CLOSED,'MM'), COUNT(*) FROM CSD.CSD_REPAIR_ORDERS_F GROUP BY TRUNC(DATE_CLOSED,'MM');
• Cycle-time analysis: compare RO_CREATION_DATE against DATE_CLOSED to derive average turnaround.
• Linking to detail: join REPAIR_LINE_ID to CSD_REPAIRS to enrich aggregated rows with repair-line attributes such as customer, organization, or repair type.

Because the table is summarized, it is well suited to BI Publisher reports, Oracle Discoverer worksheets, and OBIEE/OTBI-style dashboards where performance on large repair volumes matters. Queries should avoid treating the rows as transaction detail; reconciliation to CSD_REPAIRS is advisable when precision is required.

Related Objects

The documented relationship network is intentionally narrow:

• CSD_REPAIRS — The sole documented foreign key parent. CSD_REPAIR_ORDERS_F.REPAIR_LINE_ID references CSD_REPAIRS, anchoring the aggregated rows to the transactional repair-line master and enabling joins for detail enrichment.
• MTL_SYSTEM_ITEMS_B — Referenced indirectly through INVENTORY_ITEM_ID for item descriptions and attributes.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — Referenced through PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID to trace the concurrent program that populated or refreshed the aggregate.
• FND_USER — Referenced through CREATED_BY, LAST_UPDATED_BY, and PROGRAM_LOGIN_ID for audit attribution.

No additional dependent views or APIs are documented in the ETRM metadata for this object; implementers should treat it as a downstream reporting companion to CSD_REPAIRS rather than an integration entry point.