Search Results get_batch_name




Overview
Explore in AI Chat

Overview

GL_AUTO_ALLOC_VW_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM "OTHER" API category. It supports the Automatic Allocation feature of Oracle General Ledger by supplying display-oriented values for the allocation batch maintenance views used in the AutoAllocation workbench. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references are resolved in the schema of the invoking session rather than in the package owner's schema. This design allows the package to be called safely from within view definitions and other SQL constructs executed as the current user.

The package is a "view package" in the sense that its functions return formatted, human-readable strings used to render information within the AutoAllocation user interface rather than to carry out the allocation calculation logic itself. That core calculation logic resides in separate allocation engine packages; this package's role is limited to presentation-layer derivation.

Key Procedures and Functions

The ETRM registry documents two functions in this package. No parameters beyond those shown in the source header excerpt should be assumed.

  • GET_BATCH_NAME — Returns a VARCHAR2 display name for a batch, defined by a batch type code and batch identifier. It is used to present a meaningful name for allocation and recurring journal batches in allocation-related views and forms, rather than displaying only numeric identifiers.
  • GET_OWNER_DSP — Returns a display form of the OWNER value passed to it, accepting the owner as a VARCHAR2 and returning a VARCHAR2. This function is directly relevant to the user's search term "get_owner_dsp." It resolves or formats the owner attribute associated with allocation rules and batches so that the AutoAllocation interface can present the owning entity in a readable, consistent fashion. Because the package is AUTHID CURRENT_USER, the function executes under the privileges of the calling session, which is important when it is invoked from views accessed by different responsibility holders.

Both functions are declared with PRAGMA RESTRICT_REFERENCES (WNDS, WNPS), indicating that they neither write database state nor write package state. This is a deliberate constraint because such functions are frequently referenced inside SQL statements and view definitions, where side effects would be invalid.

Tables Accessed

The ETRM metadata documents three tables referenced through APPS synonyms: GL_ALLOC_BATCHES, GL_RECURRING_BATCHES, and PA_ALLOC_RULES_ALL. GL_ALLOC_BATCHES stores allocation batch definitions and is the primary source for batch name resolution performed by GET_BATCH_NAME. GL_RECURRING_BATCHES holds recurring journal batch definitions, which use a parallel batch naming convention and are also exposed through the same display function. PA_ALLOC_RULES_ALL holds allocation rule definitions, including the owner information surfaced by GET_OWNER_DSP. All access is read-only, consistent with the WNDS restriction declared on the functions.

Usage Notes

GL_AUTO_ALLOC_VW_PKG is referenced by five other packages in the ETRM registry, indicating that it is a supporting utility consumed by allocation maintenance and inquiry components rather than an entry point invoked directly by end users.

Typical invocation occurs through AutoAllocation view definitions and form-based display logic in Oracle General Ledger and Oracle Projects allocation flows, where the functions supply derived column values at query time. Custom code may call GET_OWNER_DSP or GET_BATCH_NAME from SQL or PL/SQL to reproduce the same display formatting used by the standard product, but should account for the AUTHID CURRENT_USER behavior, which requires the calling schema to have the necessary synonyms and privileges. Because these functions are restricted to read-only operation, they are safe for repeated execution within report queries and concurrent program cursors.