Search Results c_where_ref

Overview

APPS.GL_GLXRCTRS_XMLP_PKG is a report logic package that supports the Oracle General Ledger account reconciliation reporting program, internally associated with the GLXRCTRS concurrent program and its XML Publisher (BI Publisher) template. The package encapsulates the PL/SQL constructs that a report definition requires: global package variables that hold runtime bind and lexical parameters, data-retrieval helper functions, and before/after report triggers. Its primary business purpose is to produce reconciliation reports that compare General Ledger account activity against selected criteria — amount type, currency, reference, period range, and reconciliation status — for a specified ledger and access set. The package declares a large set of package-level variables, including C_BASE_CURR, C_STRUCT_NUM, C_WHERE_FLEX, C_WHERE_ACCT, C_ACC_FLEX, C_LEDGER_NAME, C_ACCESS_SET_NAME, P_LEDGER_ID, P_ACCESS_SET_ID, P_PERIOD_FROM, P_PERIOD_TO, P_START_DATE, P_END_DATE, P_AMOUNT_TYPE, P_LEDGER_CURRENCY, and P_REC_UNREC. These variables are populated at runtime and then referenced by the report query and layout, so that the generated output reflects the user's chosen ledger, accounting flexfield range, and reconciliation filters. The package is classified as a report-support object (API classification OTHER) rather than a public application programming interface.

Key Procedures and Functions

The metadata documents eighteen procedures and functions. BEFOREREPORT and AFTERREPORT are the standard report triggers executed before data retrieval and after report completion respectively; BEFOREREPORT initializes the package state and derives selection criteria, while AFTERREPORT performs final cleanup. P_AMOUNT_TYPEVALIDTRIGGER validates the amount-type parameter. CF_SYSDATE_DATEFORMULA supplies a system-date-derived value used as a report formula column.

The remaining entries are accessor functions for package globals: CP_COUNT_REC_P, C_WHERE_DATE_P, C_WHERE_CURRENCY_P, C_WHERE_REF_P, C_RECON_ID_P, C_LOGIN_ID_P, CP_PERIOD_START_P, CP_PERIOD_END_P, CP_START_DATE_P, CP_END_DATE_P, CP_EFF_PERIOD_END_P, COUNT_ROWS_P, C_WHERE_DAS_P, and C_JGZZ_RECON_FLAG_P. Each exposes the corresponding package variable or computed value to the report's data model, for example the reconciliation identifier (C_RECON_ID), the login identifier (C_LOGIN_ID), the effective period boundaries (CP_EFF_PERIOD_START and CP_EFF_PERIOD_END), the count of processed rows (COUNT_ROWS), and the reconstructed WHERE fragments (C_WHERE_DATE, C_WHERE_CURRENCY, C_WHERE_REF, C_WHERE_DAS). These functions allow XML Publisher templates to embed dynamically derived filter text and totals in the report output.

Tables Accessed

The package reads three documented tables, all referenced through APPS synonyms. GL_LEDGERS is queried to resolve ledger attributes such as the ledger name and functional (ledger) currency corresponding to P_LEDGER_ID; the resolved value is exposed through C_LEDGER_NAME. GL_ACCESS_SETS is accessed to resolve the access set identifier P_ACCESS_SET_ID and its description, populating C_ACCESS_SET_NAME for use in security-scoped reporting. GL_PERIOD_STATUSES is used to determine valid accounting period boundaries and statuses, supporting the effective period start and end computations (CP_EFF_PERIOD_START, CP_EFF_PERIOD_END) and the period range entered by the user. No write operations are performed; the package is strictly read-oriented, consistent with its reporting role.

Usage Notes

This package is invoked when the associated General Ledger reconciliation report concurrent program is executed from the standard request submission flow or from a report-selection form. It is not referenced by any other documented package, so it operates as a leaf report-support module rather than a shared utility. Users searching for C_ACCESS_SET_NAME will find it declared as a package global at line 26, populated during report initialization from the GL_ACCESS_SETS table and surfaced to the report layout through the package's accessor functions. Customizations should treat the package as internal to the seeded report and avoid direct invocation, since parameter population and the BEFOREREPORT/AFTERREPORT sequence are managed by Oracle's report framework. The package is present in both Oracle EBS 12.1.1 and 12.2.2, with the header indicating a 2007 revision.