Results for “cs_repairs_all”

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

Overview

CS_REPAIRS_ALL is the core transactional table within the Oracle E-Business Suite Service (CS) module that stores repair order line information. It represents the individual repair lines processed through the depot repair and service fulfillment lifecycle, capturing the receipt, diagnosis, estimation, execution, and shipment stages of a repair transaction. In EBS 12.1.1 and 12.2.2, this table serves as the central repository linking customer returns (RMA), inventory movements, work-in-process (WIP) entities, and cost estimation records. It is owned by the CS schema and is classified as VALID in the data dictionary.

From a heuristic Data Vault modeling perspective, CS_REPAIRS_ALL is best characterized as a satellite around the repair line business key. The presence of descriptive attributes such as dates, quantities, statuses, and fifteen generic ATTRIBUTE columns, combined with foreign key references outward to hub-like entities (CSD_REPAIRS, JAI_OM_OE_RMA_LINES, EAM_CONSTRUCTION_ESTIMATES), is consistent with a satellite pattern rather than a pure hub or link. The transactional, mutable nature of the columns reinforces this classification as a modeling suggestion.

Key Information Stored

The table contains 68 documented columns. The most operationally significant ones are summarized below, with surrogate and business-key candidates distinguished where the metadata documents them.

• REPAIR_LINE_ID — Surrogate primary key; also the target of unique index CS_REPAIRS_U1, making it the primary business-key candidate. It also serves as the FK to CSD_REPAIRS.
• REPAIR_NUMBER — Human-readable repair order identifier; enforced by unique index CS_REPAIRS_U3.
• ESTIMATE_BUSINESS_GROUP_ID — Business group scoping column; enforced by unique index CS_REPAIRS_U2.
• RMA_LINE_ID, RMA_HEADER_ID, RMA_NUMBER, RMA_DATE — Links the repair line to its originating return authorization.
• ESTIMATE_ID — FK to EAM_CONSTRUCTION_ESTIMATES, connecting repair work to cost estimation.
• INVENTORY_ITEM_ID, SERIAL_NUMBER, CUSTOMER_PRODUCT_ID — Identify the specific product, serialized unit, or installed-base item being repaired.
• QUANTITY_RECEIVED, QUANTITY_COMPLETE, QUANTITY_SCRAPPED, QUANTITY_REPLACED — Quantitative tracking of repair disposition.
• RECEIVED_DATE, SHIPPED_DATE, REPAIR_DURATION — Lifecycle timing for turnaround analysis.
• WIP_ENTITY_ID — Associates the repair with its WIP job.
• STATUS — Current workflow state of the repair line.
• ORG_ID, ORGANIZATION_ID, RECVD_ORGANIZATION_ID — Multi-org and inventory organization context.
• ATTRIBUTE1–ATTRIBUTE15 and CONTEXT — Descriptive flexfield storage.

The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) support audit and concurrent program traceability.

Common Use Cases and Queries

Reporting on repair throughput, turnaround time, and RMA traceability are the primary use cases.

• Open repair lines by organization: select REPAIR_NUMBER, STATUS, RECEIVED_DATE from CS.CS_REPAIRS_ALL where STATUS not in ('CLOSED','SHIPPED') and ORG_ID = :org.
• Turnaround analysis: aggregate REPAIR_DURATION and the difference between RECEIVED_DATE and SHIPPED_DATE grouped by INVENTORY_ITEM_ID.
• RMA linkage reporting: join CS_REPAIRS_ALL r to the RMA tables on r.RMA_LINE_ID to trace source returns.
• Estimate reconciliation: join ESTIMATE_ID to EAM_CONSTRUCTION_ESTIMATES to compare planned versus actual repair cost.
• Scrap and replacement metrics: sum QUANTITY_SCRAPPED and QUANTITY_REPLACED per period.

Related Objects

The following related objects are indicated by the documented foreign key relationships and index structure.

• CSD_REPAIRS — joined via CS_REPAIRS_ALL.REPAIR_LINE_ID = CSD_REPAIRS.REPAIR_LINE_ID; the parent repair entity.
• JAI_OM_OE_RMA_LINES — joined via CS_REPAIRS_ALL.RMA_LINE_ID; source RMA line information.
• EAM_CONSTRUCTION_ESTIMATES — joined via CS_REPAIRS_ALL.ESTIMATE_ID; cost estimation records.
• CS_REPAIR_HEADERS_ALL — related through REPAIR_HEADER_ID for header-level order data.
• MTL_SYSTEM_ITEMS_B — referenced through INVENTORY_ITEM_ID for item master detail.
• WIP_ENTITIES — associated through WIP_ENTITY_ID for work order context.
• CS_INCIDENTS — linked via INCIDENT_ID for service incident tracking.

These relationships position CS_REPAIRS_ALL as a hub of repair-line detail, extending outward to RMA, inventory, WIP, and estimation subsystems across the Service and Manufacturing modules.