Search Results get_ranked_results

Overview

FTE_ACS_TRIP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the integration between Oracle Freight and Transportation Execution (FTE) and Oracle Warehouse Management's shipping and trip functionality. Its primary business purpose is to evaluate freight selection rules, rank eligible carriers, and construct outbound trips that satisfy the transportation and rating criteria maintained in FTE. In Oracle EBS versions 12.1.1 and 12.2.2 this package operates as a supporting component of a broader carrier-selection and trip-building flow rather than as a standalone user-facing API; it is invoked indirectly by the integration layer that synchronizes warehouse shipping activity with transportation planning.

The user search term wsh_fte_integration is directly relevant: the ETRM dependency metadata confirms a bidirectional dependency between FTE_ACS_TRIP_PKG and WSH_FTE_INTEGRATION, indicating that this package is called by the WSH-side integration package and also references it. The package also depends on FTE_CARRIER_RANK_LIST_PVT, a private helper for ranking carriers, and on SYS.STANDARD for standard PL/SQL utilities. Its documented API classification is OTHER, meaning it is not an Open Interface, public API, or concurrent program in its own right.

Key Procedures and Functions

The ETRM documentation lists two documented procedures or functions, described below. Parameter lists are intentionally not reproduced here.

• CARRIER_SEL_CREATE_TRIP — The principal procedure of the package. It combines carrier selection with trip creation, evaluating the applicable freight selection rules and then building a trip record in the WSH schema. It is the entry point invoked by the integration layer when a shipment or delivery requires a transportation trip to be generated on the basis of FTE rules.
• GET_RANKED_RESULTS — Returns the ranked outcome of carrier evaluation. It works in conjunction with FTE_CARRIER_RANK_LIST_PVT to produce an ordered list of candidate carriers so that the highest-ranked eligible carrier can be applied during trip creation. It may be called internally by CARRIER_SEL_CREATE_TRIP or directly by the integration package.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• FTE_SEL_RULES — Stores freight selection rules that define how carriers are matched to a shipment or delivery. The package reads these rules to determine which carriers are eligible before ranking and trip creation.
• WSH_NEW_DELIVERIES — The warehouse delivery table. It provides the delivery context (ship-from, ship-to, items, weights, and quantities) that drives carrier eligibility and trip assignment, and it may be updated as part of trip association.
• WSH_TRIPS — The trip header table in Warehouse Management. The package inserts or updates records here to create the outbound trip resulting from carrier selection.
• PLITBLM — A standard Oracle PL/SQL index-by table type used for in-memory collections (such as ranked carrier lists and rule result sets) rather than as a persistent application table.

Usage Notes

FTE_ACS_TRIP_PKG is not typically invoked directly by end users. Its documented referencing package count is one, and that reference is WSH_FTE_INTEGRATION, which serves as the orchestration layer between Oracle Warehouse Management shipping processes and the FTE carrier-selection engine. As a result, the package is normally executed indirectly when the integration layer reacts to shipping events — for example, when a delivery is confirmed or a shipment is readied — and needs to select a carrier and create a corresponding trip.

Because the package manipulates WSH_TRIPS and WSH_NEW_DELIVERIES, any custom code that calls it directly must run in a transaction that respects Warehouse Management's concurrency and commit conventions, and should be aware that the package is designed for the 12.1.1 and 12.2.2 code levels of FTE and WSH. It is not exposed through a concurrent program or a form in the documented metadata, so customizations should invoke it only through the supported integration path or a carefully tested wrapper that mirrors the behavior of WSH_FTE_INTEGRATION.