Search Results c_where_flex

Overview

GL_GLXRCTRS_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite concurrent program associated with the GL Account Reconciliation report in General Ledger. The package encapsulates the report-level logic executed by the Oracle Reports XML Publisher runtime, including initialization of session context, derivation of ledger attributes, construction of dynamic WHERE clauses, and calculation of period and date boundaries used by the report query. In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and is classified as OTHER, meaning it is not a published public API but an internal supporting unit whose entry points are invoked by the report definition and the concurrent manager.

The user search term p_ledger_currency corresponds to the ledger functional currency context handled within this package. Although the parameter is not surfaced as a distinct documented procedure, the currency value is derived during BeforeReport execution through a query against GL_LEDGERS that populates the package-level variable C_BASE_CURR (functional currency). This variable is subsequently used to constrain report output to the reporting ledger currency and to feed currency-related WHERE clause generation.

Key Procedures and Functions

• BEFOREREPORT — The principal initialization function. It queries GL_LEDGERS to populate the ledger name, chart of accounts identifier (C_STRUCT_NUM), and functional currency (C_BASE_CURR), and queries GL_ACCESS_SETS to populate the access set name. It also builds the data access security clause (C_WHERE_DAS) via GL_ACCESS_SET_SECURITY_PKG, normalizes optional parameters, and derives period start/end attributes from GL_PERIOD_STATUSES.
• AFTERREPORT — Post-report cleanup/termination logic executed after the report completes.
• P_AMOUNT_TYPEVALIDTRIGGER — Validation trigger logic for the amount type parameter.
• CF_SYSDATE_DATEFORMULA — Formula returning the current system date for report use.
• CP_COUNT_REC_P — Returns the count of records processed by the report.
• C_WHERE_DATE_P — Constructs the date-range WHERE fragment from the start/end date parameters.
• C_WHERE_CURRENCY_P — Constructs the currency WHERE fragment, tied to the ledger functional currency.
• C_WHERE_REF_P — Builds the reference-related WHERE fragment.
• C_RECON_ID_P — Returns the reconciliation identifier used for filtering.
• C_LOGIN_ID_P — Returns the login (FND user) identifier of the current session.
• CP_PERIOD_START_P — Returns the start date of the from-period.
• CP_PERIOD_END_P — Returns the end date of the to-period.
• CP_START_DATE_P — Returns the effective start date for filtering.
• CP_END_DATE_P — Returns the effective end date for filtering.
• CP_EFF_PERIOD_END_P — Returns the effective period number for the end period.
• COUNT_ROWS_P — Returns the total row count for the report dataset.
• C_WHERE_DAS_P — Returns or exposes the data access security WHERE clause.
• C_JGZZ_RECON_FLAG_P — Returns the reconciliation flag used in the JGZZ-related reporting logic.

Tables Accessed

• GL_LEDGERS — Read during BeforeReport to obtain the ledger name, chart of accounts identifier, and functional currency (currency_code). This directly supports the p_ledger_currency context.
• GL_ACCESS_SETS — Read to resolve the access set name associated with the supplied access set identifier, supporting data access security.
• GL_PERIOD_STATUSES — Read to derive period start/end dates and effective period numbers for the from/to periods, filtered by application_id 101 and closing statuses C, O, or P.

Usage Notes

This package is invoked by the GL Account Reconciliation concurrent program/report, not by end-user forms directly. The Oracle Reports runtime calls BeforeReport, AFTERREPORT, and the various group-level and formula functions during execution. The package references APPS synonyms for all tables, requiring the report to run with APPS credentials or an appropriate cross-schema grant. Because it is not a published API, it should not be called from custom code; customizations should instead use supported GL APIs. Parameters such as P_LEDGER_ID, P_ACCESS_SET_ID, P_PERIOD_FROM, P_PERIOD_TO, P_START_DATE, P_END_DATE, P_FLEX_FROM, and P_FLEX_TO are report parameters consumed by the package. The ledger currency filter is implicitly derived from GL_LEDGERS rather than passed explicitly, so callers must ensure the correct ledger context is set before submission.