Results for “exception_date”

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

Overview

FTE_SHIPMENT_STATUS_EXCEPTIONS is a Transportation Execution (FTE) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the exception portion of the ShowShipment message, capturing any exception conditions raised against a shipment status record during the transportation execution lifecycle. In practical terms, the table functions as the exception detail child of the shipment status structure: each row records a discrete exception—such as a lading quantity discrepancy or a reason-coded delay—that occurred against a specific shipment status detail line.

From a data modeling perspective, the FK structure and the presence of an independent unique key on EXCEPTION_ID suggest a satellite-leaning classification: the table carries descriptive, event-oriented attributes that qualify a parent business transaction rather than defining an entity in its own right. This heuristic means the table is best treated as a dependent detail store whose lifecycle is governed by the shipment status records it enriches.

Key Information Stored

The table is documented with 13 columns. The most significant are outlined below.

• EXCEPTION_ID — Surrogate primary key, enforced by FTE_SHIPMENT_STATUS_EXCEP_PK and reinforced by the unique index FTE_SHIPMENT_STATUS_EXCEPS_U1. This is the definitive identifier for an exception row.
• DETAIL_ID — Foreign key to FTE_SHIPMENT_STATUS_DETAILS, tying each exception to its parent shipment status detail line.
• EXCEPTION_DATE — The date the exception condition was recorded or detected.
• DESCRIPTION — Free-text narrative describing the exception.
• REASON_CODE — Coded classification of the exception reason, supporting standardized reporting and aggregation.
• LADING_QUANTITY and LADING_QUANTITY_UOM — Quantity and unit of measure associated with the exception, typically used for quantity-variance exceptions against the bill of lading.
• TRANSACTION_ID — Correlation identifier linking the exception to the originating transaction context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing auditability of row creation and modification.

The surrogate key (EXCEPTION_ID) is distinct from any business-key candidates; the only documented unique index is on EXCEPTION_ID itself, so no separate natural business key is enforced by the schema.

Common Use Cases and Queries

The primary use case is exception reporting and shipment status diagnostics. Because exceptions are children of status details, the most common pattern joins the two tables to present exceptions within their shipment context:

• Listing all exceptions for a given detail line: SELECT * FROM fte.fte_shipment_status_exceptions WHERE detail_id = :p_detail_id ORDER BY exception_date DESC;
• Aggregating exceptions by reason code for operational dashboards: SELECT reason_code, COUNT(*) FROM fte.fte_shipment_status_exceptions GROUP BY reason_code;
• Detecting quantity discrepancies: SELECT exception_id, lading_quantity, lading_quantity_uom FROM fte.fte_shipment_status_exceptions WHERE lading_quantity IS NOT NULL;
• Audit and trend analysis over time by filtering on exception_date or the WHO columns.

Reporting use cases center on carrier performance, shipment delay analysis, and reconciliation of stated versus actual lading quantities.

Related Objects

The direct parent in the FK relationship is FTE_SHIPMENT_STATUS_DETAILS, joined on FTE_SHIPMENT_STATUS_EXCEPTIONS.DETAIL_ID = FTE_SHIPMENT_STATUS_DETAILS detail identifier. Beyond this documented relationship, the table is typically consumed alongside the shipment status header structure and the shipment itself within the FTE schema. The ShowShipment message context indicates integration with Transportation Execution messaging and the shipment status update process. Analysts should join through the status detail to reach shipment-level headers when building end-to-end shipment exception reports.