Results for “write_logfile”

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

Overview

FTE_UTIL_PKG is a general-purpose PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Freight and Transportation Execution (FTE) product family. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the package owner, so callers must themselves have access to the underlying objects (typically through APPS synonyms). The package is not a business API in the transactional sense; the ETRM classification lists it as OTHER. Instead, it bundles low-level helper routines that other FTE and logistics components rely on: string tokenization, message lookup with token substitution, numeric canonicalization, lookup and reference-data resolution, debug and log file handling, and a family of "get" functions that translate human-readable names into internal identifiers. The GET_CARRIER_ID function that prompted this search is a representative example: it converts a carrier name into the numeric carrier identifier used by downstream shipping and freight logic, sparing callers from writing ad hoc joins against the carrier tables. Because roughly twelve other packages reference FTE_UTIL_PKG, changes to it have a wide blast radius, and it should be treated as a shared infrastructure object.

Key Procedures and Functions

The ETRM metadata documents twenty-one procedures and functions. Most are convenience accessors that resolve a descriptive value into its internal code.

• TOKENIZE_STRING — Splits an input string into its component tokens using a caller-supplied delimiter.
• GET_MSG — Returns a message text after substituting token values, supporting localized or parameterized messages.
• CANONICALIZE_NUMBER — Normalizes a numeric value into a standard representation.
• GET_CARRIER_ID / GET_CARRIER_NAME — Bidirectional conversion between a carrier's name and its internal identifier; GET_CARRIER_ID is the name-to-ID direction.
• GET_LOOKUP_CODE — Resolves a lookup meaning or description into its lookup code.
• GET_UOM_CODE — Returns the unit-of-measure code for a given UOM.
• GET_DATA — A generic data-retrieval helper.
• GET_VEHICLE_TYPE — Resolves a vehicle type from the FTE vehicle type definitions.
• GET_CATEGORY_ID / GET_CATG_ID — Return category identifiers from the item category structures.
• GET_FND_CURRENCY — Resolves currency information from FND_CURRENCIES.
• GET_CATEGORY_MESSAGE — Returns a message associated with a category context.
• WRITE_LOGFILE / WRITE_OUTFILE — Write diagnostic or output text to log and out files.
• INIT_DEBUG / ENTER_DEBUG / EXIT_DEBUG — Manage a debug tracing context, initializing it and bracketing entry and exit of traced code.

The metadata does not document every parameter list, and any signature beyond what is shown should be confirmed directly against the package specification in the target instance.

Tables Accessed

The package reads reference and setup data through APPS synonyms rather than owning data itself. WSH_CARRIERS underpins the carrier name/ID conversion, with WSH_SHIPPING_PARAMETERS supplying shipping configuration. HZ_PARTIES is used to resolve party-level information, since carriers are modeled as parties in the Trading Community Architecture. MTL_UNITS_OF_MEASURE supports GET_UOM_CODE, while MTL_CATEGORIES_KFV, MTL_CATEGORY_SETS, and MTL_SYSTEM_ITEMS_KFV back the category and item resolution functions. FND_CURRENCIES supports currency lookups, and FND_ID_FLEX_STRUCTURES provides key flexfield structure metadata. FTE_VEHICLE_TYPES holds FTE-specific vehicle definitions. PLITBLM is the standard EBS PL/SQL table type used for string arrays. The package is essentially read-only against these tables.

Usage Notes

FTE_UTIL_PKG is invoked from forms, concurrent programs, and custom PL/SQL in the logistics and freight domain. Typical calls include using GET_CARRIER_ID to convert a carrier name captured on a form or interface into the numeric ID required by shipping tables, or using TOKENIZE_STRING and GET_MSG to build user-facing messages. The debug routines (INIT_DEBUG, ENTER_DEBUG, EXIT_DEBUG) and the file writers (WRITE_LOGFILE, WRITE_OUTFILE) are primarily for troubleshooting and should be used cautiously in production, since file paths depend on the concurrent manager or application server environment. Because the package uses AUTHID CURRENT_USER, custom code that calls it must have direct grants on the referenced tables or valid APPS synonyms. Given its role as shared infrastructure referenced by many packages, it should be modified only through Oracle-supported patches; custom wrappers are preferable to direct edits.