Results for “cs_repairs_u3”

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

Overview

CS.CS_REPAIRS_ALL is the central transactional table in the Oracle E-Business Suite Depot Repair module (schema CS). It stores repair order lines, representing the individual units of product received from a customer for diagnosis, repair, replacement, or return. Each row corresponds to a single repair line identified by REPAIR_LINE_ID and captures the full lifecycle of that unit — from receipt through diagnosis, work-in-process completion, and shipment back to the customer. The table is physically stored in the APPS_TS_ARCHIVE tablespace with a PCTFREE of 10 and comprises 68 documented columns, consistent across EBS 12.1.1 and 12.2.2.

The ETRM metadata classifies CS_REPAIRS_ALL heuristically as standalone in Data Vault terms. This classification reflects the fact that the table carries its own business keys (REPAIR_NUMBER, ESTIMATE_BUSINESS_GROUP_ID) alongside foreign references, rather than functioning purely as a hub, link, or satellite. In a Data Vault model it could reasonably be treated as a hub-satellite hybrid anchored on REPAIR_LINE_ID, with descriptive attributes such as STATUS and REPAIR_DURATION forming the satellite payload.

Key Information Stored

The surrogate primary key is REPAIR_LINE_ID (NUMBER(15)), which is also the leading column of unique index CS_REPAIRS_U1 — the object referenced by the user's search. Two additional unique indexes act as business-key candidates: CS_REPAIRS_U2 on ESTIMATE_BUSINESS_GROUP_ID and CS_REPAIRS_U3 on REPAIR_NUMBER. Ten non-unique indexes (CS_REPAIRS_N1 through N14) support access paths on foreign-key and status columns.

The most operationally significant columns include:

• REPAIR_NUMBER — the human-readable repair order identifier.
• RMA_HEADER_ID / RMA_LINE_ID / RMA_NUMBER / RMA_LINE_NUMBER / RMA_CUSTOMER_ID — links to the originating Return Material Authorization.
• CUSTOMER_PRODUCT_ID / INVENTORY_ITEM_ID / SERIAL_NUMBER — identify the specific customer unit and item being repaired.
• WIP_ENTITY_ID / REPAIR_HEADER_ID / REPAIR_ORDER_LINE_ID — associate the line with a work order and repair header.
• STATUS — the workflow status driving the repair lifecycle.
• QUANTITY_RECEIVED / QUANTITY_COMPLETE / QUANTITY_SCRAPPED / QUANTITY_REPLACED — quantitative outcomes of the repair.
• RECEIVED_DATE / SHIPPED_DATE / PROMISED_DELIVERY_DATE / JOB_COMPLETION_DATE — key dates for turnaround reporting.
• ORG_ID / ORGANIZATION_ID / ESTIMATE_BUSINESS_GROUP_ID — multi-org and business group context.

Common Use Cases and Queries

Depot Repair users query this table to track open repairs, measure repair turnaround time, and reconcile RMA receipts against shipments. A typical query retrieving all lines for a customer RMA is:

• SELECT repair_number, serial_number, status, received_date FROM cs.cs_repairs_all WHERE rma_header_id = :p_rma_header_id;
• SELECT r.repair_number, r.status, r.promised_delivery_date FROM cs.cs_repairs_all r WHERE r.org_id = :p_org AND r.status IN ('AWAITING_REPAIR','IN_REPAIR');
• SELECT r.repair_number, r.received_date, r.shipped_date, (r.shipped_date - r.received_date) turnaround FROM cs.cs_repairs_all r WHERE r.job_completion_date BETWEEN :from_date AND :to_date;

Reporting use cases include depot repair aging, technician productivity (via DIAGNOSED_BY_ID), and WIP-to-shipment reconciliation using WIP_ENTITY_ID.

Related Objects

The documented foreign keys establish the following significant relationships:

• CSD_REPAIRS — joined on REPAIR_LINE_ID; the detail/denormalized repair record.
• JAI_OM_OE_RMA_LINES — joined on RMA_LINE_ID; the originating RMA line.
• EAM_CONSTRUCTION_ESTIMATES — joined on ESTIMATE_ID; the estimate authorizing work.
• Supporting lookup targets include WIP entities (WIP_ENTITY_ID), incidents (INCIDENT_ID), and diagnoses (DIAGNOSIS_ID), each serviced by a dedicated non-unique index.

Application logic accessing this table is exposed principally through the Depot Repair forms and the public CS_Service APIs, which perform DML against CS_REPAIRS_ALL for repair line creation, update, and closure.