Results for “fte_mls_wrapper”

50+ results




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

Overview

FTE_MLS_WRAPPER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as a centralized wrapper and dispatch layer for multi-leg shipment (MLS) processing within the Oracle Transportation Execution module. The package abstracts the interaction between Oracle Freight and Transportation Execution (FTE) business logic and the underlying Workbench Shipping (WSH) data model, allowing higher-level FTE processes to manipulate trips, stops, deliveries, and delivery details without directly coupling to WSH private APIs. It is classified as a general-purpose API (API classification: OTHER) and exposes a documented surface of twenty-four procedures and functions. Because the object is validated and referenced by eight other packages, it functions as a shared utility rather than an entry-point program, and changes to its behavior can ripple across the entire FTE shipment execution stack.

Key Procedures and Functions

The documented procedures cluster around four functional areas:

Each routine is designed to be invoked with the various FTE record and table types that define the package dependencies, including action parameter records, attribute tables, and ID/name table types.

Tables Accessed

Through APPS synonyms, the package touches a broad set of WSH, HZ, and HR tables. WSH_TRIPS, WSH_TRIP_STOPS, WSH_DELIVERY_LEGS, and WSH_LOCATIONS form the operational core for trip and stop state. WSH_CARRIER_SITES and WSH_ORG_CARRIER_SITES support carrier assignment validation. Customer and contact data is sourced from HZ_PARTIES, HZ_PARTY_SITES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS, while HR_ALL_ORGANIZATION_UNITS provides organization context. PLITBLM is referenced as part of the PL/SQL table handling used by INIT_STOPS_PLS_TABLE and related stop processing routines. These reads and writes supply the data payloads consumed and returned by the wrapper procedures.

Usage Notes

FTE_MLS_WRAPPER is not typically invoked directly by end users. It is called by higher-level FTE packages such as FTE_TENDER_PVT, FTE_DELIVERY_LEGS_PVT, FTE_CARRIER_RANK_LIST_PVT, FTE_FREIGHT_RATING_DLVY_GRP, FTE_SS_INTERFACE, FTE_TENDER_WF, and WSH_FTE_INTEGRATION, as well as recursively by itself. These callers drive trip building, carrier tendering, rating, and integration flows exposed through Transportation Execution forms, concurrent programs, and workflow activities. Custom code that needs to drive MLS trip or stop manipulation should prefer calling the parent business packages rather than this wrapper, since the wrapper does not enforce business validation on its own. Its dependencies on FND_API and WSH_DEBUG_SV confirm standard EBS API error handling and debug logging conventions are used throughout.