Search Results set_factor

Overview

APPS.GLIQAVG_PKG is a small Oracle E-Business Suite PL/SQL package body residing in the General Ledger (GL) schema. Its name and structure indicate that it supports an "average balance inquiry" style utility within the GL module, providing a lightweight session-level state holder for three related values: a code combination identifier, a template identifier, and a numeric factor. Rather than performing complex business logic itself, the package exposes paired setter and getter routines that allow other GL components to store and later retrieve these values within a single database session.

The package body carries the header marker $Header: gliqavgb.pls 120.2 2005/05/05 01:18:54 kvora ship $, confirming it is a shipped Oracle artifact that has remained stable since the 11i-era code line and is carried forward into Oracle EBS 12.1.1 and 12.2.2. In the ETRM classification it is registered as an OTHER API owned by APPS, and it is referenced by three other packages, indicating that its getter functions are consumed by dependent GL logic rather than being invoked directly by end users.

Key Procedures and Functions

The package exposes three setter procedures and three getter functions, each operating on a package-level variable of the same base name.

• SET_CCID — Assigns a code combination identifier to the package's internal code_combination_id variable. This identifies the accounting flexfield combination the calling process is currently working with.
• SET_TEMPLATE_ID — Assigns a template identifier to the internal template_id variable, allowing a caller to tag the current context with a specific allocation or budget template.
• SET_FACTOR — Assigns a numeric factor to the internal factor variable, typically used to carry a multiplier or scaling value associated with the current inquiry or calculation.
• GET_CCID — Returns the currently stored code_combination_id. This is the function most relevant to a search for "get_ccid", since it is the documented accessor for the code combination value and is the routine that dependent packages call.
• GET_TEMPLATE_ID — Returns the currently stored template_id value.
• GET_FACTOR — Returns the currently stored factor value.

The getters take no arguments as documented and simply return the corresponding package state variable. The setters likewise follow a single-value signature; parameter lists are not reproduced here to avoid misstating the documented interface.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms for GLIQAVG_PKG. This is consistent with its design: the package does not read from or write to any GL base tables such as GL_CODE_COMBINATIONS or GL_BALANCES. Instead, it stores all of its state in PL/SQL package-level variables that persist only for the duration of the database session or the calling process. Any persistence of the code combination, template, or factor values is the responsibility of the calling application code, not of this package.

Usage Notes

GLIQAVG_PKG operates as a session-scoped context holder. A typical usage pattern is for a caller to invoke SET_CCID, SET_TEMPLATE_ID, and SET_FACTOR to establish the current working context, and for subsequent or downstream code — including the three packages documented as referencing GLIQAVG_PKG — to call GET_CCID, GET_TEMPLATE_ID, and GET_FACTOR to retrieve those values without re-passing them through every procedure signature.

Because the state is held in package variables, it is valid only within the same session and is not visible across concurrent requests. When invoked from Oracle Forms, a concurrent program, or custom PL/SQL, the setter calls must be executed before the corresponding getter calls in the same session. There are no documented parameters, initialization steps, or table dependencies to configure. The package's simplicity and long-standing "ship" status mean it can be relied upon as a stable accessor; however, customizations should avoid assuming any behavior beyond the documented get/set of the three values.