Search Results init_sqlerrmmsg

Overview

APPS.IEC_COMMON_UTIL_PVT is a shared private utility package body within the Oracle EBS Internet Expense / iExpenses (IEC) module family, operating in both 12.1.1 and 12.2.2 environments. Its principal business function is to centralize a set of low-level helper operations — schema resolution, row-level locking of expense submission schedules, error-message initialization, and lookup of list, subset, and schedule identifiers — so that multiple IEC components can share identical logic rather than duplicating it. The package is classified as a PVT (private) API, meaning it is not intended as a public integration surface but as an internal building block consumed by other IEC packages.

A distinguishing characteristic of the package is its error-handling design. The package body declares global message holders (g_error_message and g_encoded_message) and deliberately avoids logging errors itself, delegating that responsibility to the calling program so that messages are recorded against the caller's module name. The Init_SqlErrmMsg procedure, along with related initializers such as Init_SourceTypeNotSupportedMsg and Init_SourceTypeDoesNotExistMsg, populates these globals with translated and FND_MESSAGE-encoded text for later retrieval.

Key Procedures and Functions

• GET_SOURCETYPEVIEW — Returns the view name associated with a given source type, allowing callers to resolve the correct data source dynamically.
• LOCK_SCHEDULE — Acquires a lock on an expense submission schedule, supporting serialized access to schedule data.
• UNLOCK_SCHEDULE — Releases the lock previously acquired by LOCK_SCHEDULE.
• GET_SUBSETNAME — Retrieves the name of a subset definition used by the expense module.
• GET_LISTNAME — Retrieves the name of a list definition.
• GET_SCHEDULENAME — Returns the descriptive name for a schedule identifier.
• GET_SCHEDULEID — Returns the numeric identifier for a schedule, the inverse of the name lookup.
• GET_LISTID — Returns the numeric identifier for a list definition.
• Get_AppsSchemaName — Reads FND_ORACLE_USERID to resolve the APPS schema name, raising a standard unexpected-error exception on failure.

The documented metadata lists nine procedures/functions in total; the initializer routines share the common pattern of delegating to IEC_OCS_LOG_PVT to populate the package globals.

Tables Accessed

• FND_ORACLE_USERID — Queried by Get_AppsSchemaName to determine the read-only APPS schema name.
• AMS_LIST_HEADERS_ALL — Provides list header definitions supporting the list name and ID lookups.
• IEC_G_LIST_LOCK_STATES and IEC_G_LIST_LOCK_STATES_S — Maintain lock state information used by the LOCK_SCHEDULE and UNLOCK_SCHEDULE procedures.
• IEO_SVR_RT_INFO, IEO_SVR_SERVERS, and IEO_SVR_TYPES_B — iExpenses server configuration tables consulted for source type and schedule resolution.
• DBMS_LOCK — Invoked for Oracle-level locking support underlying the schedule lock operations.

Usage Notes

Because IEC_COMMON_UTIL_PVT is a private package, it is not called directly by end users. It is referenced by five other packages within the IEC application family, which invoke its lookup and locking routines to avoid redundant SQL and inconsistent lock handling. The error-initialization procedures are typically invoked at the start of exception handlers so that the caller can raise or log the translated message with its own module attribution. Typical execution contexts include iExpenses expense report submission flows in Oracle Forms, concurrent programs that process schedules and lists, and custom extensions that require the same schedule/list resolution logic. Developers extending iExpenses should call the appropriate wrapper package rather than this internal utility wherever a public API exists.