Results for “fte_load_details”

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

Overview

FTE_LOAD_DETAILS is a core transactional table in the Oracle E-Business Suite Transportation Execution (FTE) module. It stores the line-level details describing the contents of a shipment or load. Where the parent header record (FTE_LOAD_HEADERS) captures the shipment as a whole, FTE_LOAD_DETAILS records the individual items, handling units, or order lines that make up that shipment, along with the pricing and charge context attached to each line.

Within the Oracle EBS 12.1.1 and 12.2.2 data model, this table functions as the child entity in a master-detail relationship with the load header and serves as the parent for charges, pricing attributes, and shipment-line associations. The heuristic Data Vault classification mined from its foreign key structure is hub-leaning, suggesting it behaves as a central business concept around which dependent satellites and links cluster. Note that the ETRM metadata indicates this table is not implemented in the reference database, meaning it is documented structurally but may be absent in a given installation.

Key Information Stored

The table is anchored by a single-column surrogate primary key, defined through the constraint FTE_LOAD_DETAILS_PK. The most significant columns documented in the metadata are:

• LOAD_DETAIL_ID — Surrogate primary key uniquely identifying each shipment content line.
• LOAD_ID — Foreign key to FTE_LOAD_HEADERS, tying each detail line to its owning shipment or load.
• PARENT_LOAD_DETAIL_ID — Self-referencing foreign key establishing a hierarchical structure among detail lines, allowing nested packaging or grouping (for example, an item within a container within a shipment).

The self-referential PARENT_LOAD_DETAIL_ID is significant: it makes FTE_LOAD_DETAILS both a hub-leaning entity and a recursive hierarchy. No separate unique business key column is documented in the supplied metadata, so the surrogate key is the authoritative identifier. Business-key candidates would typically be composite in nature (LOAD_ID combined with line sequence or item reference), but such columns are not enumerated in the provided extract.

Common Use Cases and Queries

Typical reporting and integration scenarios involve retrieving all content lines for a given shipment, reconstructing the nested hierarchy of packaging, or aggregating charges per detail line.

• Listing content lines for a load: SELECT LOAD_DETAIL_ID, LOAD_ID, PARENT_LOAD_DETAIL_ID FROM FTE_LOAD_DETAILS WHERE LOAD_ID = :load_id;
• Traversing the hierarchy using a recursive query (CONNECT BY or recursive WITH clause) starting from PARENT_LOAD_DETAIL_ID IS NULL to walk top-level lines and their descendants.
• Joining to FTE_LOAD_CHARGES and FTE_LOAD_PRC_ATTRIBUTES on LOAD_DETAIL_ID to report freight and accessory charges per line item.
• Correlating shipment content to planning/shipping records through FTE_PA_SHIP_DETAILS.DETAIL_ID.
• Counting or summing detail lines per header for load utilization and shipping volume dashboards.

Because the table is hub-leaning, queries frequently use it as the central anchor and join outward to charge and attribute satellites for analytical reporting.

Related Objects

The relationship metadata identifies the following significant related objects:

• FTE_LOAD_HEADERS — Parent shipment header; joined via FTE_LOAD_DETAILS.LOAD_ID = FTE_LOAD_HEADERS.LOAD_ID.
• FTE_LOAD_DETAILS (self) — Recursive parent/child relationship via FTE_LOAD_DETAILS.PARENT_LOAD_DETAIL_ID.
• FTE_LOAD_CHARGES — Charge lines referencing each detail through FTE_LOAD_CHARGES.LOAD_DETAIL_ID = FTE_LOAD_DETAILS.LOAD_DETAIL_ID.
• FTE_LOAD_PRC_ATTRIBUTES — Pricing attributes per detail via FTE_LOAD_PRC_ATTRIBUTES.LOAD_DETAIL_ID = FTE_LOAD_DETAILS.LOAD_DETAIL_ID.
• FTE_PA_SHIP_DETAILS — Shipping/planning detail association via FTE_PA_SHIP_DETAILS.DETAIL_ID = FTE_LOAD_DETAILS.LOAD_DETAIL_ID.

These relationships confirm that FTE_LOAD_DETAILS acts as the operational bridge between shipment headers and downstream charge, pricing, and planning entities within the Transportation Execution module.