Results for “comparison_request_id”

30 results




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

Overview

FTE_PRC_LANE_COMP_UI_V is an APPS-owned database view within the Oracle E-Business Suite Transportation Execution (FTE) module. Its documented purpose is to support the price comparison user interface, presenting consolidated freight pricing, lane and schedule information in a single flattened structure suitable for display. The view is classified as VALID and is available in both EBS 12.1.1 and 12.2.2 environments, where it is referenced through the APPS schema.

Functionally, the view reconciles delivery detail records against the freight cost temporary table and enriches them with descriptive attributes such as service level meaning, container type meaning, weight, volume and formatted price. Because the view exposes both surrogate identifiers and human-readable descriptions, it serves as a bridging layer between the transactional freight costing data and the user-facing comparison grid. The user search term "service_type" maps directly to the SERVICE_TYPE column, which is derived through the FTE_FREIGHT_PRICING_UTIL.GET_LOOKUP_MEANING function call.

Underlying Base Objects

The view is defined over several documented base objects. The primary driver is the synonym FTE_FREIGHT_COSTS_TEMP, aliased WFCTMP, which stores the temporary freight cost and comparison request records. It is joined to WSH_DELIVERY_DETAILS (WDD) on DELIVERY_DETAIL_ID, to MTL_SYSTEM_ITEMS_KFV (MSIK) on inventory item and organization, and to WSH_DELIVERY_ASSIGNMENTS (WDA) on delivery detail. Additional documented references include FTE_LANES, WSH_FREIGHT_COST_TYPES and the package FTE_FREIGHT_PRICING_UTIL.

The joins enforce that only delivery details with valid inventory item definitions and delivery assignments are returned. The WHERE clause restricts results to rows where LINE_TYPE_CODE is either 'PRICE' or 'SUMMARY' and a specific CHARGE_SOURCE_CODE applies, ensuring the comparison view surfaces only pricing-relevant records rather than the full temporary costing population.

Key Columns

Common Use Cases and Queries

Typical use cases include freight price comparison reporting, validation of lane and schedule pricing, and diagnostic queries on service type assignment. A representative query filters by service type description:

  • SELECT ENTITY_ID, ITEM_NAME, SERVICE_TYPE, PRICE FROM FTE_PRC_LANE_COMP_UI_V WHERE SERVICE_TYPE = 'Ground';
  • SELECT LANE_SCHED_ID, COMPARISON_REQUEST_ID, SERVICE_TYPE, WEIGHT, VOLUME, PRICE FROM FTE_PRC_LANE_COMP_UI_V WHERE COMPARISON_REQUEST_ID = :request_id ORDER BY LANE_SCHED_ID;
  • SELECT SERVICE_TYPE, COUNT(*), SUM(TOTAL_AMOUNT) FROM FTE_PRC_LANE_COMP_UI_V GROUP BY SERVICE_TYPE;

Because SERVICE_TYPE is derived from a lookup meaning function, queries filtering on the code itself must reference the underlying FTE_FREIGHT_COSTS_TEMP table or apply the lookup translation explicitly. Reporting tools should treat this view as read-only and expect transient data, since it draws from a temporary costing table.