Search Results ledger_from_p

Overview

APPS.GL_GLRGNJ_XMLP_PKG is the generated PL/SQL package that supports the Oracle General Ledger XML Publisher (BI Publisher) concurrent program associated with the GLRGNJ report — the "Journal" style report used to print journal entries and lines by ledger, period, batch, source, currency, and posting status. In Oracle EBS 12.1.1 and 12.2.2 the APPS schema hosts these XMLP wrapper packages, each of which encapsulates the bind parameters, WHERE-clause fragments, and flexfield concatenation logic required to drive the report's data template and layout. The package is compiled AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user, which allows it to inherit the ledger and data access set security context established by the concurrent request.

The package declares a large set of global variables that mirror the concurrent program's parameters — P_PERIOD_NAME, P_JE_SOURCE_NAME, P_BATCH_NAME, P_POSTING_STATUS, P_CURRENCY_CODE, P_START_DATE, P_END_DATE, P_KIND, P_LEDGER_ID, and P_ACCESS_SET_ID — together with internal control strings such as PERIOD_WHERE, CURRENCY_WHERE, POSTING_STATUS_WHERE, DAS_WHERE, and LEDGER_WHERE. These are assembled at runtime to compose the dynamic SQL predicates that the report's data model consumes.

Key Procedures and Functions

The package exposes roughly 27 program units. BEFOREREPORT and AFTERREPORT are the standard XML Publisher entry points invoked as before- and after-report triggers; BEFOREREPORT initialises parameter values, resolves the ledger and access set, and constructs the dynamic WHERE fragments. G_LINESGROUPFILTER provides the grouping filter applied to journal lines during data retrieval.

The remaining units are accessor functions that return the value of the package-level variables to the report definition. Documented examples include FLEXDATA_P (returns the concatenated accounting flexfield expression FLEXDATA, which stitches segment1 through segment30 with newline separators), POSTING_STATUS_SELECT_P, POSTING_STATUS_WHERE_P, PERIOD_WHERE_P, CURRENCY_WHERE_P, STRUCT_NUM_P, PARAM_LEDGER_NAME_P, INV_FLEX_MSG_P, WIDTH_P, JE_USER_SOURCE_DSP_P, ACCESS_SET_NAME_P, DAS_WHERE_P, LEDGER_FROM_P, LEDGER_WHERE_P, PARAM_LEDGER_TYPE_P, CONSOLIDATION_LEDGER_FLAG_P, and PARAM_CURRENCY_P. The name suffix "_P" denotes a parameter/placeholder accessor pattern that XML Publisher templates bind to. Users searching for "period_where_p" are locating PERIOD_WHERE_P, the accessor that exposes the compiled period predicate (defaulting to "1 = 1") used to constrain GL_PERIOD_STATUSES rows.

Tables Accessed

The package references several GL tables via APPS synonyms. GL_LEDGERS and GL_LEDGER_SET_ASSIGNMENTS resolve the ledger definition and its assignment to the reporting context. GL_ACCESS_SETS and GL_ACCESS_SET_ASSIGNMENTS enforce data access set security so the report returns only ledgers the user is permitted to see. GL_PERIODS and GL_PERIOD_STATUSES supply the accounting calendar and the open/closed status of each period, driving the PERIOD_WHERE logic. GL_JE_SOURCES identifies the journal source names displayed on the report, and GL_SYSTEM_USAGES provides system reference data used during validation and defaulting.

Usage Notes

GL_GLRGNJ_XMLP_PKG is invoked indirectly whenever the associated GLRGNJ XML Publisher concurrent program is submitted from the Submit Request window or scheduled through the concurrent manager. The report engine calls BEFOREREPORT to populate the parameter globals, then evaluates the "_P" accessor functions while rendering the template. The package is also referenced by custom BI Publisher data definitions that reuse its WHERE-clause fragments. Because the ETRM metadata records zero referencing packages, direct calls from other PL/SQL packages are not documented; customisations should treat the package as internal API and avoid modifying it, since Oracle regenerates these wrappers during patching and version upgrades between 12.1.1 and 12.2.2.