Search Results g_j_release_level




Overview
Explore in AI Chat

Overview

APPS.CST_RELEASE_GRP is a public PL/SQL package declaration (a specification-only "GRP" or group package) owned by the APPS schema in Oracle E-Business Suite. Its stated purpose in the ETRM metadata is narrow and deliberate: it centralizes the release-level identifiers used by the Cost Management (CST) modules to distinguish between the 11.5.10 (Release 11i) and 12 (Release 12) processing behaviours. The package is declared with AUTHID CURRENT_USER, meaning its executable code inherits the privileges of the invoking user rather than running with definer's rights.

The package header carries the RCS identifier $Header: CSTFPRVS.pls 115.1 2003/08/18 ... anjgupta noship $. Two named constants are published: G_I_Release_Level and G_J_Release_Level. Their literal values are 110509 and 110510 respectively, which correspond to internal release markers for the 11.5.10 -> 11.5.9/11.5.10 lineage and the R12 lineage. In practical terms, CST_RELEASE_GRP acts as the canonical "which release am I running as?" switch for code that must branch between legacy and R12 cost processing logic.

Key Procedures and Functions

  • GET_I_RELEASE_LEVEL — A function that returns the value of the G_I_Release_Level constant (110509). Callers use this to detect that the session is operating under the pre-R12 (11i) release level.
  • GET_J_RELEASE_LEVEL — A function that returns the value of the G_J_Release_Level constant (110510). This value signals the R12 (Release 12) level, and is the value typically used to gate R12-specific processing paths.

Both are zero-argument functions returning NUMBER. No parameter lists are documented, and none should be assumed. Their only role is to expose the two constants defined at lines 5 and 6 of the package specification. The package contains no other documented subprograms beyond these two.

Tables Accessed

The ETRM metadata lists no tables referenced through APPS synonyms. This is consistent with a pure constant/lookup package whose functions perform no SQL. Because the specification holds only constant declarations and two trivial getters, CST_RELEASE_GRP does not read or write any application tables; the release-level values are hard-coded literals. This design avoids a table dependency and lets the package be compiled and resolved without any data access, which is important for a foundational utility consulted early in cost processing runs.

Usage Notes

The package is referenced by three other packages according to the ETRM metadata, indicating it is a lightweight dependency used across the Cost Management codebase. Typical invocation patterns are:

  • Internal PL/SQL branching — R12 cost processors call GET_J_RELEASE_LEVEL or reference the constants to select R12 behaviour, falling back to GET_I_RELEASE_LEVEL for Release 11i compatibility.
  • Custom extensions and CEMLI code — Customer-developed cost routines that must run against both 11i and R12 can compare a release level to these constants instead of embedding numeric literals.
  • Not directly exposed on Forms or concurrent programs — There is no evidence in the metadata of a form or concurrent program entry point; the package is a server-side utility intended for programmatic use only.

The user search term g_j_release_level maps directly to the constant G_J_Release_Level (110510) and its accessor GET_J_RELEASE_LEVEL, confirming that the object of interest is the R12 release-level marker. Because the package is a specification (header) file, its behaviour is deterministic and version-stable between 12.1.1 and 12.2.2, making it a safe constant source for release detection logic.