Search Results fte_load_prc_attributes




Overview
Explore in AI Chat

Overview

The FTE_LOAD_PRC_ATTRIBUTES table is a core data repository within the Oracle E-Business Suite Transportation Execution (FTE) module. It functions as an audit and reference table, permanently storing the specific qualifiers and pricing attributes that were applied during the freight rating and pricing process for a shipment. This table is critical for traceability, as it provides a detailed historical record of the exact business rules and data points—such as service levels, accessorials, or commodity codes—that determined the final freight cost for a given load and its constituent details. Its existence allows users to understand not just the final charge, but the precise logic that generated it, which is essential for customer billing, carrier negotiations, and internal freight cost analysis.

Key Information Stored

The table's structure is designed to link pricing determinants directly to the priced transportation entities. Its primary key is a composite of LOAD_ID, LOAD_SCHEDULE_ID, and LOAD_DETAIL_ID, creating a unique record for each combination of these objects and their associated pricing attribute. While the provided ETRM excerpt does not list the specific attribute columns, tables of this nature typically contain columns such as ATTRIBUTE_TYPE, ATTRIBUTE_CODE, ATTRIBUTE_VALUE, and potentially OPERAND or MODIFIER fields. These columns store the actual qualifier names (e.g., 'SHIPMENT_PRIORITY') and their applied values (e.g., 'URGENT'). The foreign keys to FTE_LOAD_HEADERS, FTE_LOAD_SCHEDULES, and FTE_LOAD_DETAILS are fundamental, ensuring data integrity by tethering every pricing attribute record to a valid load, schedule, and detail line.

Common Use Cases and Queries

The primary use case is investigating the root cause of a specific freight charge on a shipment. Analysts can query this table to retrieve all pricing attributes that contributed to a particular load's cost. A common reporting requirement is to compare pricing determinants across shipments to identify inconsistencies or validate contract compliance. A sample SQL pattern to audit pricing for a specific load would be:

  • SELECT * FROM FTE_LOAD_PRC_ATTRIBUTES WHERE load_id = <LOAD_ID> ORDER BY load_detail_id;

Another critical use case is supporting dispute resolution with carriers or customers by providing documented evidence of the rated attributes. Integration with business intelligence tools often involves joining this table to load header and detail tables to create enriched datasets for spend analysis, correlating cost with specific service attributes.

Related Objects

The FTE_LOAD_PRC_ATTRIBUTES table sits at the intersection of several key FTE transactional tables, as defined by its foreign key relationships. It is directly dependent on FTE_LOAD_HEADERS (which defines the overall shipment), FTE_LOAD_SCHEDULES (which defines the specific shipment schedule), and FTE_LOAD_DETAILS (which defines the individual lines being shipped). This table is a child of these entities. While not listed in the excerpt, it is logically related to the FTE_RATE_ATTRIBUTES or similar setup tables that define the available qualifiers for the pricing engine. Data is typically populated by the FTE pricing engine's internal APIs during the rate request and shipment creation processes, not via direct user entry.