Search Results rank_list_action_uiwrapper

Overview

The APPS.FTE_CARRIER_RANK_LIST_PVT package is a private (PVT classification) PL/SQL API within the Oracle E-Business Suite Transportation Management / Freight and Trade Execution (FTE) module. It encapsulates the runtime logic used to build, maintain, and evaluate carrier rank lists — prioritized sequences of carriers that the rating and tendering engines consider when assigning a shipment or trip to a service provider. In Oracle EBS 12.1.1 and 12.2.2, this package is a foundational component of the freight rating and carrier selection process, allowing ranking rules (based on rate, service level, allocation, mileage, or user-defined criteria) to be resolved into a concrete ordered list that downstream processes can iterate through.

The package is marked VALID in the APPS schema and references the base persistence table FTE_CARRIER_RANK_LIST along with helper collection types (FTE_ID_TAB_TYPE, FTE_SS_RATE_SORT_TAB_TYPE) and the diagnostic utility WSH_DEBUG_SV. Because it is classified as PVT, it is not a formally supported public interface; it is designed to be called by other FTE/WSH packages rather than directly by customers or integrations.

Key Procedures and Functions

The documented metadata identifies nine procedures/functions exposed by the package body:

• CREATE_RANK_LIST_BULK — Constructs carrier rank list entries in bulk, typically for a set of trips or shipments in a single processing pass.
• RANK_LIST_ACTION — Performs the core action (creation, update, or advancement) against a rank list, forming the primary internal workhorse used by other procedures.
• RANK_LIST_ACTION_UIWRAPPER — A UI-facing wrapper around RANK_LIST_ACTION, adapted for invocation from Oracle Forms or OAF user interfaces.
• DELETE_RANK_LIST_UIWRAPPER — Removes an existing rank list, again exposed for UI-driven deletions.
• GET_RANK_DETAILS — Retrieves the detailed attributes (carrier, position, criteria values, status) for entries within a rank list.
• GET_RANK_LIST — Returns the ordered list of ranked carriers for a given context (e.g., trip or shipment).
• IS_RANK_LIST_EXHAUSTED — Boolean-style check indicating whether all ranked carriers have been consumed or rejected, governing fallback behaviour.
• REMOVE_SERVICE_APPLY_NEXT — Removes a specific service/carrier from the list and advances processing to the next eligible ranked carrier.
• PRINT_RANK_LIST — Outputs or logs a formatted representation of the rank list, useful for diagnostics and debugging.

Tables Accessed

The package operates against the following documented objects (usually via APPS synonyms):

• FTE_CARRIER_RANK_LIST — The primary table storing ranked carrier entries generated and consumed by the package.
• FTE_CARRIER_RANK_LIST_S — A sequence or secondary/summary table supporting rank list identifiers and ordering.
• WSH_TRIPS — The trip header table, providing the shipment grouping context against which carriers are ranked.
• DUAL — Standard Oracle single-row utility table.
• PLITBLM — A PL/SQL table (index-by table) placeholder used internally for collection handling.

Usage Notes

FTE_CARRIER_RANK_LIST_PVT is not invoked directly by end users. It is called by peer packages within the ETRM stack, most notably FTE_TRIP_RATING_GRP — which is the object most closely associated with the user's search term fte_trip_rating_grp — as well as FTE_ACS_TRIP_PKG, FTE_FREIGHT_RATING_DLVY_GRP, FTE_SS_INTERFACE, FTE_TENDER_WF, WSH_FTE_INTEGRATION, and its own internal recursive references. The heavy dependence from FTE_TRIP_RATING_GRP confirms its role during trip rating, where ranked carriers drive rate lookup and selection.

Typical invocation paths include: the carrier ranking step during trip rating within the Transportation Planner / Shipping workbench, the freight rating engine, and the tendering workflow when a primary carrier is rejected and the engine must advance to the next ranked carrier. Because it is a private API, any custom code extending ETRM functionality should treat it as internal and prefer the supported public APIs where available. Signature compatibility across 12.1.1 and 12.2.2 is generally preserved, though customers should validate against their patch level before relying on it in extensions.