Search Results fte_pa_ship_details_pk

Overview

The FTE_PA_SHIP_DETAILS table is a core data object within the Oracle E-Business Suite Transportation Execution (FTE) module. Its primary function is to store transactional data required for the formatting and processing of partial acceptance events for tendered shipments. In transportation logistics, a partial acceptance occurs when a carrier accepts only a portion of a planned shipment or load. This table acts as a detailed repository, linking the partially accepted quantities back to the original shipment planning data, thereby enabling accurate tracking, reconciliation, and financial settlement for partially fulfilled transportation tenders. Its role is critical for maintaining data integrity in complex, multi-stop, or multi-leg shipping scenarios where full acceptance is not always feasible.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which dictate the critical data points it holds. The primary key, FTE_PA_SHIP_DETAILS_PK, is a composite key consisting of DETAIL_ID, LOAD_ID, and LOAD_SCHEDULE_ID. These columns serve as the unique identifier for each partial acceptance record and establish the essential links to the parent shipment entities. The DETAIL_ID references the specific line item from the shipment detail, LOAD_ID points to the main shipment header, and LOAD_SCHEDULE_ID connects to the scheduled shipment plan. An additional notable column is SUB_LOAD_ID, which further allows for granular tracking within complex load structures. While the provided metadata does not list specific attribute columns (like accepted quantity or status), the table's purpose implies it stores the transactional details of what was partially accepted against the original tender.

Common Use Cases and Queries

This table is central to operational and analytical processes involving partial shipment acceptances. A common use case is generating a report to reconcile tendered versus accepted quantities for a specific carrier or shipment, which is vital for freight audit and payment. Another scenario involves querying the table to understand the fulfillment rate for planned loads, aiding in carrier performance analysis. A typical SQL query might join FTE_PA_SHIP_DETAILS with FTE_LOAD_HEADERS and FTE_LOAD_DETAILS to retrieve a summary of partially accepted shipments:

• SELECT lh.load_number, ld.detail_id, pa.* FROM fte_pa_ship_details pa JOIN fte_load_headers lh ON pa.load_id = lh.load_id JOIN fte_load_details ld ON pa.detail_id = ld.detail_id WHERE lh.carrier_id = &carrier_id;

This data is also crucial for downstream interfaces and processes that adjust inventory, billing, and planning systems based on the actual shipped quantities.

Related Objects

The FTE_PA_SHIP_DETAILS table maintains strong referential integrity with several key FTE tables, as documented by its foreign key constraints. These relationships are fundamental to its operation:

• FTE_LOAD_DETAILS: Linked via the DETAIL_ID column. This relationship ties each partial acceptance record to a specific line item (e.g., a product or order line) on the original shipment.
• FTE_LOAD_HEADERS: Linked via two columns: LOAD_ID and SUB_LOAD_ID. This connects the partial acceptance to the primary shipment header and any subordinate load structures.
• FTE_LOAD_SCHEDULES: Linked via the LOAD_SCHEDULE_ID column. This relationship associates the partial acceptance with the scheduled shipment plan, providing a link to the temporal and routing aspects of the tender.

These relationships ensure that partial acceptance data is always contextualized within the complete shipment lifecycle, from planning and tendering through to execution.