Search Results get_total_base_price

Overview

FTE_QP_ENGINE is an Oracle E-Business Suite package body owned by APPS that encapsulates all Oracle Advanced Pricing (QP) engine interactions performed by the Oracle Freight and Transportation Execution (FTE) module. Its principal business function is to construct the input records that the pricing engine requires, invoke the engine, and interpret the resulting output so that freight charges can be calculated for shipments, lines, and sets. The package maintains engine input and output data in global PL/SQL tables on a per-event basis, retaining engine defaults in a package-level table (g_engine_defaults_tab) so that each pricing event can be processed consistently.

The header comment dates the source file to release 115.21 (December 2003), and the unit remains the pricing integration point for freight costing in both EBS 12.1.1 and 12.2.2. Documented metadata classifies the package as "OTHER" rather than a formal public API, indicating it is intended for internal use by the FTE pricing flow rather than direct customer invocation.

Key Procedures and Functions

• CREATE_CONTROL_RECORD — builds the control-level record passed to the pricing engine for an event.
• CREATE_LINE_RECORD — constructs the line-level engine input record from shipment or freight line data.
• CREATE_QUAL_RECORD — creates qualifier records used by the engine to select applicable price lists and modifiers.
• CREATE_ATTR_RECORD — assembles attribute records (pricing attributes) attached to the engine request.
• PREPARE_QP_LINE_QUALIFIERS — prepares the line qualifier set required before an engine call.
• ADD_QP_OUTPUT_DETAIL — appends detail rows to the stored engine output structures.
• CALL_QP_API — invokes the QP pricing API with the prepared input payload.
• GET_QP_OUTPUT — retrieves and returns the engine results for downstream processing.
• GET_TOTAL_BASE_PRICE — computes the total base price of a shipment for a given set by multiplying unit price by line quantity; the price is returned in the priced currency. The searched term "get_total_base_price" corresponds to this procedure.
• APPLY_NEW_BASE_PRICE — applies a recalculated base price back to the pricing structures.
• PREPARE_NEXT_EVENT_REQUEST — readies the input structures for the subsequent pricing event in a sequence.
• ANALYSE_OUTPUT_FOR_DEFICIT_WT — examines engine output in relation to deficit weight calculations.
• DELETE_SET_FROM_LINE_EVENT — removes a set from a line event during housekeeping or reprocessing.
• DELETE_LINES — deletes line entries from the global input/output tables.
• CLEAR_QP_INPUT — resets the engine input global tables between events.
• PRINT_QP_INPUT and PRINT_QP_OUTPUT — diagnostic routines that emit the engine input and output for debugging.
• CHECK_QP_OUTPUT_ERRORS, CHECK_TL_QP_OUTPUT_ERRORS, and CHECK_PARCEL_OUTPUT_ERRORS — validate engine output at the overall, transportation-line, and parcel levels respectively.

Tables Accessed

The documented table reference for this package is the APPS synonym PLITBLM, a standard pricing interface table used to stage engine input and output rows. Access to this table supports the creation of engine records and the retrieval of pricing results. The package also relies extensively on package-level global PL/SQL tables — notably engine input line extras and engine output lines (g_I_line_extras_tbl and g_O_line_tbl), together with the per-event defaults table — rather than persistent database tables for its intermediate state.

Usage Notes

FTE_QP_ENGINE is an internal engine-integration package rather than an end-user API. It is referenced by three other packaged units within the FTE pricing flow and is typically invoked from freight pricing logic that needs to evaluate charges for a shipment or set. Calls originate from the FTE pricing process itself (for example, when a shipment's freight charges are calculated), and not from standard Oracle Forms or concurrent programs directly. Debugging output can be enabled through the fte_freight_pricing_util logging utilities, whose G_DBG level and print_msg routine are used throughout, allowing support personnel to trace input set numbers, unit prices, and cumulative prices during troubleshooting.