Search Results ledger_id_param




Overview
Explore in AI Chat

Overview

GL_CASH_CLR_ACCT_ANAL_RPT_PKG is a report support package in the Oracle E-Business Suite General Ledger module. Its business purpose is to drive the Cash Clearing Account Analysis report, a reconciliation-oriented report that lists journal activity affecting the cash clearing account so that users can trace uncleared and cleared items, including subledger-sourced transactions such as Payables checks, against the General Ledger balances for a selected ledger and accounting period range.

The package is classified under the API classification OTHER, indicating that it is not a public, supported integration API. It is an internal implementation container for a report, providing the procedural scaffolding that a report definition or a report driver invokes to prepare data, derive security predicates, and resolve descriptive names before the report output is formatted. It is not designed to be called directly by external or customer-written code.

Key Procedures and Functions

  • BEFORE_REPORT — The principal setup routine, executed before the report body runs. It establishes the security context by calling XLA_SECURITY_PKG.SET_SECURITY_CONTEXT with the subledger application identifier, then builds the data access security clause using GL_ACCESS_SET_SECURITY_PKG.get_security_clause, passing the data access set identifier parameter together with the ledger and segment column mappings. Where no restriction is returned, the clause defaults to an unrestricted predicate. The routine also resolves the effective period numbers for the from/to period parameters from GL_PERIOD_STATUSES, and constructs the Payables uncleared detail query, which joins GL journal lines and headers, GL import references, XLA accounting entries and transaction entities, and AP checks to the period status table.
  • ACCESS_SET_NAME — A lookup routine that returns the name of the data access set associated with the report parameters. This is the element most directly relevant to the "data_access_set_name" search term: the Data Access Set name is the user-facing label shown for the security context within which the report was run, complementing the numerically identified data access set used to build the security clause in BEFORE_REPORT.
  • LEDGER_NAME — A lookup routine that returns the ledger name for the ledger identifier supplied to the report, used to print the ledger context on the report output and to disambiguate results when the same report is run across multiple ledgers.

Tables Accessed

  • GL_ACCESS_SETS — Read to resolve the data access set identifier to its descriptive name, supporting the ACCESS_SET_NAME routine and the security-context labelling of the report.
  • GL_LEDGERS — Read to translate the ledger identifier parameter into the ledger name printed on the report, and to validate the ledger against which security is applied.
  • GL_PERIOD_STATUSES — Read to obtain the effective period numbers corresponding to the from and to period parameters for the selected ledger and the subledger application identifier. These effective period numbers bound the journal line selection so that only activity within the requested accounting period window is included.

Usage Notes

This package is invoked as part of the Cash Clearing Account Analysis report flow, typically from the concurrent program or report definition that owns the report's parameter list. Its BEFORE_REPORT routine runs once at report startup to seed the security clause, period boundaries, and query text into package globals that the report's data queries subsequently reference.

Because the report is secured by data access set, execution results depend on the access set assigned to the responsibility or to the user's ledger and data access set configuration; the ACCESS_SET_NAME routine exists precisely so that the report output identifies that security context. In 12.1.1 and 12.2.2 the package resides in the APPS schema and should be treated as an internal, unsupported object for modification purposes. Custom code should not call BEFORE_REPORT, ACCESS_SET_NAME, or LEDGER_NAME directly; report behavior should be influenced through supported parameters and access set configuration.