Search Results orderby_acct2

Overview

APPS.GL_GLRJED_XMLP_PKG is the generated PL/SQL package body that supports the Oracle General Ledger standard report commonly identified as the GL Journal Entry Detail (often wired to a BI Publisher / XML Publisher concurrent program template in Release 12.1.1 and 12.2.2). As with all *_XMLP_PKG packages, the body provides the data-access and formula functions invoked by the report's before-report and after-report triggers, plus the derived-column formulas defined in the accompanying report definition. The package does not own business data; instead it orchestrates calls into the GL public APIs and lookups to resolve the values the report layout needs.

The user search term "p_kind" reflects the report's parameter surface: the package exposes IN parameters (for example, P_LEDGER_ID, P_START_PERIOD, P_ACTUAL_FLAG, P_BUD_ENC_TYPE_ID, and the parameter that identifies the report kind or mode) that the concurrent program passes into these formulas. The classification of this package is OTHER, indicating it is not a published API but a report-support artifact.

Key Procedures and Functions

The body documents 44 functions and procedures. The principal ones include:

• AFTERREPORT — the report-level termination routine; it returns control (TRUE) at the end of report execution.
• BEFOREREPORT — the report-level initialization routine invoked before the layout is produced.
• BEGIN_BALFORMULA / END_BALFORMULA — compute opening and closing balances from debit and credit inputs by returning the absolute difference (abs(BEGIN_DR - BEGIN_CR), abs(END_DR - END_CR)).
• BEGIN_BAL_DR_CRFORMULA / END_BAL_DR_CRFORMULA — companion formula functions exposing the beginning and ending debit/credit components.
• BUD_ENC_TYPE_NAMEFORMULA — resolves a budget or encumbrance type identifier into its display name via gl_info.gl_get_bud_or_enc_name, raising -20101 and issuing a message from the GL_PLL_ROUTINE_ERROR message dictionary on error.
• DISP_ACTUAL_FLAGFORMULA — translates the actual flag (e.g. 'A'/'B') into a user-facing value using gl_info.gl_get_lookup_value against the BATCH_TYPE lookup, with the same error-handling pattern.
• START_EFFECTIVE_PERIOD_NUMFORM / END_EFFECTIVE_PERIOD_NUMFORMUL — derive the effective period number for the start and end periods using GL_GET_EFFECTIVE_NUM.
• GL_GET_EFFECTIVE_NUM — a local helper that resolves an effective period number from a ledger and period, returning an error buffer to the caller.
• Parameter-builder functions/procedures — G_MAINGROUPFILTER, STRUCT_NUM_P, ACCESS_SET_NAME_P, SELECT_ALL_P, WHERE_FLEX_P, ORDERBY_BAL_P, ORDERBY_ACCT_P, ORDERBY_ALL_P, and WHERE_ACTUAL_TYPE_P build the WHERE, ORDER BY, and security (access set / structure) clauses that drive the query.

Each formula follows the standard XML Publisher error protocol: capture errbuf from the GL routine, fetch a formatted message from gl_message.get_message('GL_PLL_ROUTINE_ERROR'), and raise_application_error(-20101).

Tables Accessed

Through APPS synonyms, the package reads the following:

• GL_LEDGERS — validates and derives ledger context (chart of accounts, currency, period information).
• GL_LEDGER_SET_ASSIGNMENTS — resolves the ledger set membership used for access-set-based data restriction.
• GL_ACCESS_SETS — supports the access set / data access privilege logic exposed via ACCESS_SET_NAME_P.
• GL_PERIOD_STATUSES — supplies period status and the effective period number used by the effective-period formulas.

These reads underpin the WHERE clause construction and the period-num derivation that the report layout depends on.

Usage Notes

GL_GLRJED_XMLP_PKG is not invoked directly by end users or by custom application code. It is called automatically by the XML Publisher runtime when the associated GL report concurrent program runs, specifically from the report's before-report trigger, after-report trigger, and each data/formula column reference. Because the package is documented as referenced by zero other packages, it sits at the leaf of the dependency chain rather than acting as a reusable API. In 12.1.1 and 12.2.2 the body is delivered under $GL_TOP (GLRJEDB.pls), with the header showing a version of 120.0. Customers customizing the report should avoid modifying the generated package body directly; instead, extend via a custom template or a copy of the concurrent program, since regeneration of the XML Publisher package will overwrite any local changes.