Results for “fte_util_pkg”

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

Overview

FTE_UTIL_PKG is a utility package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM taxonomy as an OTHER API. It is not a business-document API in the sense of an interface table processor; rather, it is an internal shared-services library that supports the broader Freight and Transportation Execution (FTE) module set. Its responsibilities span string tokenization and message resolution, canonicalization and formatting of numeric values, lookup and reference-data retrieval against Oracle master and trading-partner tables, and diagnostic file output for debugging concurrent or online processing. The header comment places the last shipped revision at version 120.8, dated 2005, indicating the package has been stable across the 11i, 12.1.1, and 12.2.2 release lines.

The package defines a local associative array type, VARCHAR2_TAB, indexed by BINARY_INTEGER, and several package-level collections used for concatenated flexfield segments and category identifiers. Global debug flags govern whether diagnostic output is emitted, which is central to the write_logfile search that led to this object.

Key Procedures and Functions

Twenty-one documented program units make up the public surface of the package:

• TOKENIZE_STRING — Splits an input string on a supplied delimiter and returns the resulting tokens as a STRINGARRAY, used widely for parsing delimited flexfield concatenations and profile values.
• GET_MSG — Retrieves a formatted message, optionally substituting positional tokens into the message text.
• CANONICALIZE_NUMBER — Normalizes a numeric value into a canonical string representation for comparison or storage.
• GET_CARRIER_ID and GET_CARRIER_NAME — Resolve between carrier identifiers and carrier names for shipping and freight processing.
• GET_LOOKUP_CODE — Returns a lookup code value from the EBS lookup mechanism for a given lookup type.
• GET_UOM_CODE — Resolves the unit-of-measure code associated with an item or UOM definition.
• GET_DATA — Generic retrieval helper used by callers to obtain reference data through the package's consolidated access layer.
• GET_VEHICLE_TYPE — Returns vehicle type information for transportation planning.
• GET_CATEGORY_ID and GET_CATG_ID — Resolve category identifiers, the latter providing an abbreviated variant of the same resolution logic.
• GET_FND_CURRENCY — Returns currency attributes from the FND currency repository.
• WRITE_LOGFILE — The diagnostic routine most relevant to the originating search. It appends formatted debug or trace lines to a log file when the package-level debug flags are enabled.
• WRITE_OUTFILE — Writes generated output to a designated output file, typically used by concurrent-style processing.
• ENTER_DEBUG, EXIT_DEBUG, and INIT_DEBUG — Manage debug session state, including nesting via ENTER/EXIT and initialization via INIT_DEBUG.
• GET_CATEGORY_MESSAGE — Returns a category-related message string.

Tables Accessed

The package reads reference and master data through APPS synonyms: FND_CURRENCIES for currency resolution; FND_ID_FLEX_STRUCTURES for key flexfield structure metadata used when parsing concatenated segments; FTE_VEHICLE_TYPES for transportation vehicle definitions; HZ_PARTIES for trading-partner identity; MTL_CATEGORIES_KFV and MTL_CATEGORY_SETS for item category resolution; MTL_SYSTEM_ITEMS_KFV for item master lookups; MTL_UNITS_OF_MEASURE for UOM codes; WSH_CARRIERS for carrier definitions; and WSH_SHIPPING_PARAMETERS for shipping configuration. PLITBLM is the standard EBS temporary table used for messaging and token buffering, consistent with GET_MSG and TOKENIZE_STRING behavior. Most access is read-only; WRITE_LOGFILE and WRITE_OUTFILE operate on the file system rather than on database tables.

Usage Notes

FTE_UTIL_PKG is referenced by at least twelve other packages in the EBS instance, which confirms its role as shared infrastructure rather than an entry point. It is typically invoked indirectly: FTE forms call higher-level packages that delegate tokenization, lookup resolution, and message formatting to FTE_UTIL_PKG, while concurrent programs use WRITE_LOGFILE and WRITE_OUTFILE to produce trace and output artifacts. Customizations should call the package through its APPS synonym, avoid relying on internal globals such as the debug flags, and treat the collections and VARCHAR2_TAB type as implementation details. Because the package is dependency-heavy, changes to it ripple across the twelve dependent packages, and any debugging activity should be wrapped in INIT_DEBUG, ENTER_DEBUG, and EXIT_DEBUG to preserve correct log nesting.