Search Results get_lkup_meaning
Overview
GMO_UTILITIES is a shared PL/SQL utility package in the APPS schema that supports the Oracle Process Manufacturing (OPM) suite, now delivered within the E-Business Suite under the ETRM (Enterprise Trade and Manufacturing) product family. The package body supplies a centralized library of reusable helper routines that other OPM and ETRM modules call to resolve common reference data—user identity, lookup meanings, and organization context—without each calling program having to re-implement the same queries. Its API classification in the ETRM 12.2.2 metadata is OTHER, indicating it is an internal technical utility rather than a public business API intended for external integration. In Oracle EBS 12.1.1 and 12.2.2 it resides in the APPS schema with status VALID and is graded as a foundational dependency rather than a standalone business process component.
Key Procedures and Functions
The ETRM metadata documents nine procedures and functions. Six are named explicitly:
- GET_WHO_COLUMNS — returns the standard "WHO" audit column values (creation/update user, date, and related attributes) used by OPM tables, so callers can populate audit fields consistently.
- GET_USER_DISPLAY_NAME — resolves a user identifier to a display name, typically sourced from FND_USER and Workflow directory information.
- GET_MFG_LOOKUP — retrieves manufacturing lookup values, drawing on the MFG_LOOKUPS reference table.
- GET_LOOKUP_MEANING — returns the meaning (description) associated with a lookup code, providing user-facing text for a stored value.
- GET_LOOKUP — the general lookup accessor that underlies the more specific lookup routines, resolving codes and meanings from the lookup tables (FND_LOOKUPS and MFG_LOOKUPS).
- GET_ORGANIZATION — returns organization context, generally respecting the organization access established for the current session through ORG_ACCESS_VIEW.
The remaining three documented routines are not individually named in the available excerpt; they follow the same pattern of shared reference-data resolution.
Tables Accessed
Documented table access, through APPS synonyms, covers FND_USER and GME_BATCH_HEADER, supplemented by the dependency list, which also names FND_GLOBAL, FND_LOOKUPS, MFG_LOOKUPS, ORG_ACCESS_VIEW, and WF_DIRECTORY. The pattern is read-oriented: FND_USER and WF_DIRECTORY supply user names; FND_LOOKUPS and MFG_LOOKUPS supply lookup codes and meanings; ORG_ACCESS_VIEW and FND_GLOBAL supply organization and session context; and GME_BATCH_HEADER is referenced so utility routines can align with the OPM batch header structure used throughout process manufacturing. The package does not serve as a transactional writer of business data.
Usage Notes
GMO_UTILITIES is invoked as a supporting dependency by other OPM and ETRM packages rather than being called directly by end users. The metadata records it as referenced by seven other packages while referencing none of its own callers, corroborating its role as a low-level shared library. It is typically reached from forms, concurrent programs, and internal package logic that need consistent user, lookup, or organization resolution. Because it is an internal utility rather than a formalized public API, customizations should avoid binding directly to its signatures across releases; developers extending ETRM functionality should treat it as subject to change and prefer documented, supported APIs where available.
-
APPS.IGS_AD_IMP_028 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.GMO_UTILITIES
12.2.2
-
PACKAGE BODY: APPS.GMO_UTILITIES
12.1.1
-
APPS.GMO_UTILITIES SQL Statements
12.1.1
-
APPS.GMO_UTILITIES SQL Statements
12.2.2
-
PACKAGE BODY: APPS.IGS_AD_IMP_028
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_003
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_027
12.1.1
-
PACKAGE BODY: APPS.IGR_IMP_003
12.1.1
-
PACKAGE BODY: APPS.IGR_IMP_002
12.1.1
-
APPS.IGS_AD_IMP_024 SQL Statements
12.1.1
-
APPS.IGS_AD_IMP_001 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_015
12.1.1
-
APPS.IGS_AD_IMP_004 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_024
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_016
12.1.1
-
PACKAGE BODY: APPS.EDR_STANDARD
12.2.2
-
PACKAGE BODY: APPS.IGS_AD_IMP_010
12.1.1
-
PACKAGE BODY: APPS.EDR_STANDARD
12.1.1
-
PACKAGE: APPS.IGS_PS_VALIDATE_LGCY_PKG
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_001
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_004
12.1.1
-
PACKAGE BODY: APPS.IGS_PE_VISAPASS_PUB
12.1.1
-
APPS.IGR_IMP_002 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGR_IMP_004
12.1.1
-
APPS.IGS_AD_IMP_013 SQL Statements
12.1.1
-
PACKAGE: APPS.IGS_AD_GEN_016
12.1.1
-
PACKAGE BODY: APPS.CN_API
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_014
12.1.1
-
PACKAGE BODY: APPS.CN_API
12.2.2
-
PACKAGE: APPS.CN_API
12.2.2
-
PACKAGE: APPS.CN_API
12.1.1
-
PACKAGE BODY: APPS.IGS_PE_WF_GEN
12.1.1
-
PACKAGE BODY: APPS.IGS_DA_TRNS_IMP
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_IMP_013
12.1.1
-
APPS.IGS_AD_IMP_027 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_016 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_PE_VISAPASS_PUB dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGR_IMP_003 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_024 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_028 dependencies on IGS_AD_GEN_016
12.1.1
-
PACKAGE BODY: APPS.IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_001 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_010 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.GMO_UTILITIES dependencies on MFG_LOOKUPS
12.2.2
-
APPS.IGS_AD_IMP_013 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_DA_TRNS_IMP dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.IGS_AD_IMP_004 dependencies on IGS_AD_GEN_016
12.1.1
-
APPS.CN_API dependencies on CN_LOOKUPS
12.2.2
-
APPS.CN_API dependencies on FND_MESSAGE
12.2.2