Search Results check_qp_output_errors

Overview

FTE_QP_ENGINE is a PL/SQL package in the APPS schema that functions as the integration bridge between Oracle Freight and Transportation Execution (FTE) freight pricing logic and the Oracle Advanced Pricing (QP) engine. In Oracle EBS 12.1.1 and 12.2.2, freight charges are not calculated through a simple rate lookup; they are derived by feeding shipment, line, and qualifier data into the QP pricing engine, which applies freight-specific price lists, modifiers, and qualifiers. FTE_QP_ENGINE is the component that builds those inputs, invokes the QP API, and then interprets the returned pricing output for use by freight rating and freight audit processes.

The package is classified as an OTHER API, meaning it is intended primarily for internal consumption by other FTE packages rather than as a public extension point. Its tight coupling with FTE_FREIGHT_PRICING and QP_PREQ_GRP confirms its role as the engine-level worker package that underpins freight pricing calls.

Key Procedures and Functions

The 21 documented procedures and functions divide into several functional groups:

• Input record construction: CREATE_CONTROL_RECORD, CREATE_LINE_RECORD, CREATE_QUAL_RECORD, and CREATE_ATTR_RECORD populate the QP input structures (control, line, qualifier, and attribute records) required by the pricing engine. PREPARE_QP_LINE_QUALIFIERS assembles the qualifier data associated with a given freight line.
• QP invocation and output handling: CALL_QP_API submits the prepared request to the QP pricing engine. GET_QP_OUTPUT, ADD_QP_OUTPUT_DETAIL, and GET_TOTAL_BASE_PRICE retrieve and interpret the results. CHECK_QP_OUTPUT_ERRORS, CHECK_TL_QP_OUTPUT_ERRORS, and CHECK_PARCEL_OUTPUT_ERRORS validate engine responses across the standard, transportation/landed-cost, and parcel pricing paths respectively.
• Price adjustment: APPLY_NEW_BASE_PRICE and GET_TOTAL_BASE_PRICE support recalculation of the base freight charge, while ANALYSE_OUTPUT_FOR_DEFICIT_WT evaluates results against deficit weight thresholds.
• Iteration and lifecycle control: PREPARE_NEXT_EVENT_REQUEST advances processing to the next pricing event; DELETE_SET_FROM_LINE_EVENT and DELETE_LINES remove obsolete input data; CLEAR_QP_INPUT resets the working structures; PRINT_QP_INPUT and PRINT_QP_OUTPUT provide diagnostic output of the engine input and output.

Tables Accessed

The package accesses the PLITBLM table through an APPS synonym. PLITBLM is the QP pricing engine's input line table, which stores the pricing request lines constructed for each freight calculation, and its corresponding output rows. Writing to PLITBLM and reading the resulting priced rows is the mechanism by which FTE submits freight lines to QP and retrieves the calculated charges. All other data manipulation is performed through package-to-package calls rather than direct table access, notably through QP_PREQ_GRP, the QP pricing request group package.

Usage Notes

FTE_QP_ENGINE is not invoked directly by end users. It is called programmatically by FTE_FREIGHT_PRICING, FTE_FREIGHT_PRICING_SPECIAL, and FTE_TL_CORE, which in turn are triggered during shipment confirmation, freight rating, freight audit, and landed cost calculation workflows. Within Oracle Transportation Management–integrated or native FTE freight pricing setups, the package executes as part of the pricing event cycle, handling multi-event and multi-line pricing requests and deficit-weight logic. For the 12.1.1 to 12.2.2 upgrade, the package is shipped VALID in the APPS schema and requires no customer modification. Because it is classified as OTHER rather than a public API, customizations should target the calling packages (FTE_FREIGHT_PRICING) or QP modifier setups rather than this engine package, and any diagnostic use of PRINT_QP_INPUT or PRINT_QP_OUTPUT should be confined to non-production troubleshooting environments.