Search Results check_product_installed

Overview

GMA_CORE_PKG is a foundational utility package in the Oracle EBS Process Manufacturing (OPM / GMA) product family. It resides in the APPS schema and is classified under the ETRM API classification of OTHER, indicating it is primarily an internal support package rather than a public business API. Its role is to centralize two categories of common operations required throughout the GMA modules: resolution of system date constants (such as the minimum date, maximum date, and the "zero" or null-equivalent date) and verification that a given Oracle application or product is installed in the current environment.

The package body header (version 115.8) references several historical bug fixes, including Bug #2480810, Bug #2607567, and Bug #2626977, which collectively changed the date-constant functions to read values from Oracle profile options rather than hard-coded literals and removed the time component from the zero-date value. This history illustrates the package's role as a stable, shared dependency that other GMA packages rely on. The metadata records that the package is referenced by 11 other packages, confirming its wide internal footprint across the OPM suite.

Key Procedures and Functions

• GET_DATE_CONSTANT — A function that returns a date constant as a formatted VARCHAR2 string. It accepts a constant name and translates it into a display-ready date string in the format DD-MON-YYYY HH24:MI:SS (or DD-MON-YYYY for the zero date). It delegates the underlying date resolution to GET_DATE_CONSTANT_D and applies the appropriate TO_CHAR conversion.
• GET_DATE_CONSTANT_D — A function that returns the same date constants as native DATE values. It resolves the constant by calling FND_PROFILE.VALUE_WNPS against profile options such as SY$MIN_DATE, SY$MAX_DATE, and SY$ZERODATE, then converts the retrieved string using TO_DATE. This function underpins GET_DATE_CONSTANT and is the canonical source for date-constant values within the GMA code base.
• CHECK_PRODUCT_INSTALLED — A procedure that determines whether a specified Oracle application or product is installed. It accepts a product identifier and returns a status value via an OUT parameter. Internally it calls FND_INSTALLATION.GET_APP_INFO, the standard EBS installation-check utility, and discards the additional descriptive outputs through local dummy variables. This procedure is the object users reach for when searching for "check_product_installed."

Tables Accessed

The documented metadata does not list any base tables referenced through APPS synonyms. Both functional areas of the package operate against Oracle EBS framework constructs rather than application data tables. Date-constant resolution is performed through the FND profile option mechanism (FND_PROFILE.VALUE_WNPS), which reads from the profile option tables maintained in the Application Object Library. Product-installation checks are performed through FND_INSTALLATION.GET_APP_INFO, which queries the FND application registration and product installation views (such as FND_APPLICATION and FND_PRODUCT_INSTALLATIONS). Because these accesses are encapsulated inside the called FND utilities, no direct table dependencies are exposed for GMA_CORE_PKG.

Usage Notes

GMA_CORE_PKG is an internal utility package and is not intended for direct end-user or customer invocation. It is most commonly called from within other GMA packages, PL/SQL APIs, and concurrent program logic that require consistent date-boundary values or need to confirm product availability before executing dependent logic. The CHECK_PRODUCT_INSTALLED procedure is typically invoked early in a processing routine to guard against execution when a required OPM or related product is not licensed or installed in the environment.

In Oracle EBS 12.1.1 and 12.2.2, the profile-based date constants (SY$MIN_DATE, SY$MAX_DATE, SY$ZERODATE) must be correctly configured for the date-constant functions to return meaningful values. Customizations should avoid duplicating this logic and instead call GMA_CORE_PKG to ensure consistency with the eleven dependent packages already relying on it.