Search Results tl_core_multiple

Overview

FTE_TL_CORE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM as OTHER. The prefix "FTE" denotes the Transportation Execution module, and "TL" denotes Truckload, identifying this package as a core component of the Oracle Transportation Execution / freight rating engine. Its role in the EBS architecture is to provide the central computational routines that support truckload transit-time calculation and rating logic. Rather than a user-facing module, FTE_TL_CORE functions as an internal engine layer called by other transportation execution packages. The ETRM record for this object shows a VALID status with both a package specification and package body present, confirming that it is a compiled, deployable database component in the APPS schema. The package depends on FTE_TL_CACHE, SYS.STANDARD, WSH_GLOBAL_PARAMETERS, DBMS_UTILITY, and PLITBLM, and it is referenced by FTE_TL_RATING and recursively by FTE_TL_CORE itself. This dependency pattern is typical of a shared utility package that centralizes route and transit computations for reuse across related truckload rating programs.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions within FTE_TL_CORE: TL_CORE and TL_CORE_MULTIPLE. The naming convention indicates a single-item routine paired with a set-based, multi-record variant. Both are treated as undocumented in the public interface sense, categorized under OTHER rather than a published API classification, meaning Oracle does not guarantee their signatures for external integration use.

• TL_CORE — The core computational routine of the package. It performs the primary transit-time or rating calculation for a single truckload movement. As the foundational entry point, it encapsulates the logic that the rest of the FTE truckload rating stack ultimately invokes.
• TL_CORE_MULTIPLE — The multi-record counterpart to TL_CORE. It applies the same core logic across a collection or set of movements in a single invocation, reducing context-switching and round trips when processing batches of shipments. This pattern is common in EBS rating engines where large volumes of lanes or order lines must be evaluated efficiently.

Parameter lists are not published in the ETRM excerpt and should not be assumed; developers must inspect the package specification in the database before invoking these routines directly.

Tables Accessed

The documented table references are WSH_GLOBAL_PARAMETERS, DBMS_UTILITY, and PLITBLM. WSH_GLOBAL_PARAMETERS is the shipping execution global parameters table, and FTE_TL_CORE reads it to obtain system-level configuration and defaults that influence truckload calculation behavior, such as parameter settings controlling transportation execution mode. DBMS_UTILITY is the standard Oracle supplied package rather than an application table; the package references it for generic utilities, most plausibly for dependency-aware compilation or formatting. PLITBLM is the internal PL/SQL implementation table used by DBMS_OUTPUT and similar built-ins for buffering, which suggests the package performs diagnostic or debug output during execution. In addition, the dependency listing shows FTE_TL_CORE referencing FTE_TL_CACHE, which retains computed truckload results for reuse, and being referenced by FTE_TL_RATING, the rating facade that consumes the core calculations.

Usage Notes

FTE_TL_CORE is an internal engine package and is not designed as a public integration API. It is normally invoked indirectly: FTE_TL_RATING calls into FTE_TL_CORE, which in turn consults FTE_TL_CACHE before performing fresh calculations and writes results back to the cache. Consequently, most functional flows that reach this package originate in Transportation Execution rating activity — planning, shipment rating, or transit-time determination — rather than from a direct concurrent program submission. Custom code that attempts to call TL_CORE or TL_CORE_MULTIPLE directly should do so only after reviewing the actual package specification, since the procedures are documented as OTHER and Oracle may change them without notice, particularly across the 12.1.1 and 12.2.2 releases. When debugging rating anomalies, DBAs and developers commonly inspect this package's dependencies and its use of DBMS_UTILITY and PLITBLM as an indicator of diagnostic output. Because the package is VALID in the APPS schema and heavily referenced, it should be treated as read-only in production and never recompiled or wrapped without Oracle Support guidance.