Search Results csd_repairs_interface

Overview

CSD_REPAIRS_INTERFACE is a standalone interface table in the CSD (Depot Repair) product schema of Oracle E-Business Suite. Its documented purpose is to enable the bulk creation of repair orders. Rather than requiring users to enter depot repair transactions one at a time through the Depot Repair forms, the table acts as a staging area into which external systems or batch processes populate repair order attributes; a concurrent program then validates and processes those rows to produce live repair records.

The object is owned by the CSD schema and is marked VALID in the ETRM documentation for both release 12.1.1 and 12.2.2, with a documented physical schema of 118 columns. From a Data Vault modeling perspective, the provided heuristic classification is standalone, meaning the table is not modeled as a strict hub, link, or satellite but rather as an integration-stage entity that references several parent tables without being a central business hub itself. It is best treated as a transient interface layer rather than a source-of-truth transactional table.

Key Information Stored

The table carries a wide attribute set spanning repair order header details, service request context, and manufacturing/fulfillment fields. The most significant columns include:

• TRANSACTION_ID — the primary surrogate identifier for each interface row.
• GROUP_ID — groups rows that belong to the same bulk interface batch.
• REPAIR_NUMBER — the business identifier for the repair order being created.
• REPAIR_LINE_ID and ORDER_LINE_ID — foreign keys linking the staged row to the target repair line (referencing CSD_REPAIRS).
• REPAIR_TYPE_ID — references CSD_REPAIR_TYPES_B, identifying the type of repair to perform.
• REPAIR_GROUP_ID — references CSD_REPAIR_ORDER_GROUPS, tying the row to a repair order group.
• INVENTORY_ITEM_ID, SERIAL_NUMBER, ITEM_REVISION, LOT_NUMBER — item and instance identifiers for the unit under repair.
• CUSTOMER_PRODUCT_ID and INSTANCE_ID — link the repair to the installed base record.
• QUANTITY, UNIT_OF_MEASURE — quantity and UOM of the repair.
• SR_INCIDENT_ID, SR_ACCOUNT_ID, SR_PARTY_ID — service request context for the repair.
• STATUS, STATUS_REASON_CODE, RO_TXN_STATUS — lifecycle and processing status flags.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS for row-level access control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle descriptive flexfield columns used to carry user-defined data.

The surrogate primary key is TRANSACTION_ID; business-key candidates in the schema include REPAIR_NUMBER combined with batch context. The FK structure confirms parent references to CSD_REPAIRS, CSD_REPAIR_TYPES_B, CSD_REPAIR_ORDER_GROUPS, and FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is bulk repair order creation: an external system, legacy migration, or batch loader inserts rows into CSD_REPAIRS_INTERFACE, and a Depot Repair concurrent program reads, validates, and converts them into CSD_REPAIRS records. Reporting use cases include monitoring interface processing success and identifying failed or stuck rows.

A typical pattern for inspecting pending rows is:

• SELECT transaction_id, repair_number, repair_type_id, status FROM csd.csd_repairs_interface WHERE group_id = :batch;
• Joining to parent types: SELECT i.repair_number, t.name FROM csd.csd_repairs_interface i, csd.csd_repair_types_b t WHERE i.repair_type_id = t.repair_type_id;
• Filtering by status to isolate unprocessed rows: WHERE status IS NULL OR status = 'NEW';

Because the table is a staging interface, rows are typically purged after successful processing, so queries should generally target open batches rather than historical data.

Related Objects

The following tables and objects are most closely related, per the documented FK relationships:

• CSD_REPAIRS — the target table populated from this interface, joined on REPAIR_LINE_ID.
• CSD_REPAIR_TYPES_B — lookup of repair types, joined on REPAIR_TYPE_ID.
• CSD_REPAIR_ORDER_GROUPS — repair order grouping entity, joined on REPAIR_GROUP_ID.
• FND_SECURITY_GROUPS — security group reference, joined on SECURITY_GROUP_ID.
• CSD_Repairs_Interface concurrent processing program — the standard EBS process that consumes these rows.
• Depot Repair open/update interfaces and the service request tables flowing through SR_INCIDENT_ID and SR_ACCOUNT_ID.

These relationships confirm the interface table's role as a bridge between external data sources and the core depot repair transaction tables.