Results for “event_code”

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

Overview

CSD_REPAIR_HISTORY is a transaction and event-audit table within the Oracle E-Business Suite Depot Repair (CSD) module. It records all events associated with a repair order throughout its lifecycle, such as "Broken Product Received," "Job Created," "Repair Order Created," and "Product Shipped." Each row captures a discrete event keyed to a specific repair line, making the table the primary chronological record of repair activity for reporting and operational tracking.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table carries a repair-line foreign key into CSD_REPAIRS together with descriptive event attributes (event code, event date, quantity), which is characteristic of a satellite capturing descriptive history and context around a repair-order business key rather than a hub or a link. It does not introduce independent business keys of its own, reinforcing its subordinate, descriptive role.

The table resides in the CSD schema and is documented with 62 columns in ETRM 12.2.2. Its primary key, CSD_REPAIR_HISTORY_PK, is defined on REPAIR_HISTORY_ID.

Key Information Stored

The most significant columns include:

• REPAIR_HISTORY_ID — the surrogate primary key (CSD_REPAIR_HISTORY_PK) uniquely identifying each history event row. A unique index (CSD_REPAIR_HISTORY_U1) also exists on this column.
• REPAIR_LINE_ID — the foreign key linking the event to the parent repair line in CSD_REPAIRS. This defines which repair order/line the history pertains to.
• EVENT_CODE — encoded identifier describing the nature of the event (e.g. receipt, job creation, shipment).
• EVENT_DATE — timestamp marking when the event occurred, enabling chronological ordering and duration analysis.
• QUANTITY — quantity associated with the event, where relevant.
• PARAMN1–PARAMN10 — generic numeric parameters storing event-specific numeric context.
• PARAMC1–PARAMC10 — generic character parameters storing event-specific textual context.
• PARAMD1–PARAMD10 — generic date parameters capturing additional event-relevant dates.
• SECURITY_GROUP_ID — foreign key into FND_SECURITY_GROUPS, supporting multi-tenant data security.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns for custom extensibility.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the process that created the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — who/when audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework.

The surrogate key (REPAIR_HISTORY_ID) is distinct from any business-key candidate; the only documented unique index reinforces the surrogate identity rather than defining an alternate natural key.

Common Use Cases and Queries

CSD_REPAIR_HISTORY supports repair order status timelines, cycle-time measurement between events, and audit trails of repair processing. Typical reporting joins the history to its parent repair line and to the underlying repair order to reconstruct the full path of a returned unit.

• Repair timeline for a specific line:

  SELECT h.EVENT_CODE, h.EVENT_DATE, h.QUANTITY
  FROM   CSD.CSD_REPAIR_HISTORY h
  WHERE  h.REPAIR_LINE_ID = :repair_line_id
  ORDER  BY h.EVENT_DATE;
  

• Cycle-time analysis between receipt and shipment: join the event rows for a line, filtering on the receipt and shipment EVENT_CODE values, and compute the interval between their EVENT_DATEs.
• Volume by event type: aggregate COUNT(*) grouped by EVENT_CODE over a date range to trend repair activity.
• Audit of a repair order: join to CSD_REPAIRS via REPAIR_LINE_ID to filter by a given repair order or customer.

Related Objects

• CSD_REPAIRS — the parent repair-line table; joined via CSD_REPAIR_HISTORY.REPAIR_LINE_ID = CSD_REPAIRS.REPAIR_LINE_ID. This is the principal relationship.
• FND_SECURITY_GROUPS — referenced through CSD_REPAIR_HISTORY.SECURITY_GROUP_ID for row-level security resolution.
• FND_CONCURRENT_REQUESTS — relates through REQUEST_ID for concurrent program audit tracing.
• FND_USER — relates through CREATED_BY / LAST_UPDATED_BY for user attribution.
• CSD_REPAIR_ORDERS — reached through CSD_REPAIRS to associate history events with the higher-level repair order.
• FND_DESCR_FLEX_COLUMN_USAGES / DFF definitions — for interpreting ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.

Together these relationships position CSD_REPAIR_HISTORY as the central chronological record underpinning Depot Repair tracking, audit, and cycle-time reporting within Oracle EBS 12.1.1 and 12.2.2.