Search Results get_date_constant




Overview
Explore in AI Chat

Overview

GMA_CORE_PKG is a foundational utility package in the Oracle EBS Process Manufacturing (GMA) application family, owned by the APPS schema and classified by ETRM as an "OTHER" API. Unlike the large business-flow APIs that drive transactions, GMA_CORE_PKG provides low-level helper routines used broadly across the GMA module. Its principal role is to expose standardized date constants and to report whether a particular product or feature has been installed in the current environment. Because the specification is declared AUTHID CURRENT_USER, the package executes with the privileges of the invoking user, and the schema-qualified APPS synonyms resolve against the caller's accessible objects. The package also declares PRAGMA RESTRICT_REFERENCES purity assertions on its two date functions, signalling that those routines read no package state (WNPS) and write no database state (WNDS), which makes them safe to call from SQL statements and from other packages that enforce purity rules. ETRM records that GMA_CORE_PKG is referenced by eleven other packages, confirming its status as shared infrastructure rather than an end-user entry point.

Key Procedures and Functions

  • GET_DATE_CONSTANT — Takes a constant identifier and returns its value as a character string. This is the item surfaced by the user's search term "get_date_constant." It supplies a common lookup mechanism so that callers need not hard-code literal dates.
  • GET_DATE_CONSTANT_D — The date-typed counterpart, returning a DATE value for the same conceptual constant. The source header notes this function was added under Bug #2626977, indicating it was introduced to provide native date semantics alongside the original character-returning version.
  • CHECK_PRODUCT_INSTALLED — A procedure receiving a constant identifier as input and returning a status value through an OUT parameter. It reports whether the referenced product or feature is installed in the current instance, allowing dependent code to branch on installation state rather than failing at runtime.

No parameter lists beyond those shown in the specification excerpt are documented here.

Tables Accessed

The ETRM metadata does not enumerate any tables referenced through APPS synonyms for this package. The two date-constant functions carry purity pragmas asserting no database writes, and the absence of documented table references is consistent with a helper whose values are largely intrinsic or derived from installation metadata. CHECK_PRODUCT_INSTALLED may consult installation-status data, but the documented metadata records no specific table dependencies. No assumptions about undocumented tables should be made.

Usage Notes

GMA_CORE_PKG is typically invoked indirectly. Its eleven documented dependents call the date-constant and product-installation helpers to establish environment context before performing their own work. Because GET_DATE_CONSTANT and GET_DATE_CONSTANT_D carry WNPS and WNDS pragmas, they may be embedded in SQL expressions and in PL/SQL that enforces purity constraints. CHECK_PRODUCT_INSTALLED is suited to conditional initialisation logic — for example, enabling optional Process Manufacturing behaviour only when the corresponding product is present. Custom extensions and Forms personalisations in the GMA module may call these routines directly when they need the same constants or installation checks used by Oracle's seeded code, but developers should treat the package as internal infrastructure and verify behaviour against the target release, since the source header dates from an earlier GMA code line.