Results for “delivery_leg_total”

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

Overview

The view APPS.FTE_PRC_VIEW_PRICE_UI_V is a reporting and integration construct within the Oracle E-Business Suite Freight and Transportation Execution (FTE) module, part of the ETRM (E-Business Suite Transportation Management) family. It exposes freight pricing information derived from the pricing engine, presenting it in a flat, UI-friendly format suitable for display in the Freight Pricing user interface, for downstream reporting, and for integration with external systems. The view consolidates charges stored in WSH_FREIGHT_COSTS with delivery detail, item, and delivery assignment attributes, producing a unified price presentation that includes both line-level pricing detail and delivery-leg totals. In Oracle EBS 12.1.1 and 12.2.2, this view is owned by the APPS schema and is typically referenced through synonyms for read-only consumption.

Underlying Base Objects

The view is defined over several core transportation and inventory objects, documented as follows:

• WSH_FREIGHT_COSTS — the primary fact table holding computed freight charges, with the filter line_type_code IN ('PRICE','SUMMARY') and charge_source_code = 'PRICING_ENGINE'.
• WSH_DELIVERY_DETAILS — supplies delivery detail identifiers, inventory item, organization, container flag, weights, volumes, and UOM codes.
• MTL_SYSTEM_ITEMS_KFV — provides concatenated item segments, description, and container type code.
• WSH_DELIVERY_ASSIGNMENTS — links delivery details to delivery legs and provides the parent delivery detail via parent_delivery_detail_id.
• WSH_DELIVERY_LEGS and WSH_NEW_DELIVERIES — referenced for delivery-leg context and header-level attributes.
• WSH_FREIGHT_COST_TYPES — supports cost type lookups used in the union branch.
• FTE_FREIGHT_PRICING_UTIL — a PL/SQL package whose get_lookup_meaning function resolves lookup codes (e.g., CONTAINER_TYPE, FTE_PRC_UI_COST_TYPE) into human-readable meanings.

The view is constructed as a UNION of two branches: a detail branch joining delivery details, items, and assignments, and a summary branch keyed on delivery_leg_id representing the delivery-leg total.

Key Columns

• entity_id — in the detail branch, the delivery_detail_id; in the summary branch, the delivery_leg_id.
• parent_entity_id — the parent delivery detail or delivery leg, or -1 for delivery-leg totals.
• delivery_leg_id — the delivery leg to which the charge pertains.
• entity_name — a character representation of the delivery detail ID, or the lookup meaning for DELIVERY_LEG_TOTAL in the summary branch.
• item_name — concatenated item segments from MTL_SYSTEM_ITEMS_KFV.
• container_type — decoded container type meaning.
• weight and volume — formatted with their UOM codes, using gross weight for container-flagged records.
• price — the total amount concatenated with the currency code.
• Audit columns — creation_date, created_by, last_update_date, last_updated_by, last_update_login, program_application_id, program_id, program_update_date, and request_id.

The user search term delivery_leg_total corresponds to the summary branch, where get_lookup_meaning('FTE_PRC_UI_COST_TYPE','DELIVERY_LEG_TOTAL') yields the entity_name for aggregated leg totals.

Common Use Cases and Queries

Typical uses include Freight Pricing UI display, freight cost reconciliation, and integration extracts. A representative query returning leg totals is:

• SELECT entity_id, delivery_leg_id, entity_name, price FROM apps.fte_prc_view_price_ui_v WHERE entity_name = 'Delivery Leg Total';
• Detail pricing by delivery leg: SELECT delivery_leg_id, item_name, price FROM apps.fte_prc_view_price_ui_v WHERE entity_name <> 'Delivery Leg Total';
• Audit tracing: SELECT request_id, created_by, creation_date, price FROM apps.fte_prc_view_price_ui_v WHERE delivery_leg_id = :leg_id;

Because the view performs string concatenation of amounts and UOMs, consumers requiring numeric aggregation should parse the value or query WSH_FREIGHT_COSTS directly.