Search Results ledger_category_code




Overview
Explore in AI Chat

Overview

The APPS.GL_LEDGERS_PUBLIC_ALL_V view is a public, security-aware reporting object in the Oracle General Ledger (GL) module. It exposes ledger definition attributes for the ledgers to which the current Oracle E-Business Suite user has access. In Release 12.1.1 and 12.2.2, the Ledger concept consolidated the former Set of Books architecture, and this view functions as the supported public interface through which the accounting setup of a ledger is queried by concurrent programs, forms, and external integrations without requiring direct reads of the underlying GL_LEDGERS table.

Because the view is defined in the APPS schema and is marked VALID, it is safe to consume from custom code, BI Publisher reports, and OAF pages within supported boundaries. Its principal role is to supply ledger metadata — chart of accounts, functional currency, period type, and the code combination identifiers used for system-defined accounts — to any process that must resolve how a given ledger is configured before posting, translating, or reporting.

Underlying Base Objects

The documented referenced base object is GL_LEDGERS (exposed within the APPS schema as a synonym). The view is a direct column projection over that table: each attribute listed in the view text is selected one-for-one from the corresponding GL_LEDGERS column, with no joins in the documented definition. The one transformation present is on the ledger type, where ALC_LEDGER_TYPE_CODE is decoded into the legacy multi-reporting-currency (MRC) convention: 'SOURCE' is returned as 'P', 'TARGET' as 'R', and all other values as 'N', exposed under the alias MRC_LEDGER_TYPE_CODE. The "PUBLIC" designation in the view name indicates that row-level security is applied through the standard ledger security mechanism, so results are automatically filtered to the ledgers the requesting user is authorized to see.

Key Columns

Common Use Cases and Queries

The most frequent requirement is resolving the rounding account for a ledger, which the search term "rounding_ccid" reflects. A typical query joins the view to GL_CODE_COMBINATIONS to return the fully qualified rounding account:

SELECT l.ledger_id, l.name, l.rounding_ccid, gcc.concatenated_segments
FROM gl_ledgers_public_all_v l, gl_code_combinations_kfv gcc
WHERE l.rounding_ccid = gcc.code_combination_id;

Additional scenarios include retrieving a ledger's functional currency and calendar for report parameters, validating whether budgetary control or journal approval is enabled before submitting interfaces, and enumerating accessible ledgers for a multi-org reporting LOV. When querying, note that ROUNDING_CCID may be null if rounding imbalance tracking is not enabled, and that the view returns only ledgers permitted by the user's ledger security profile — a behavior that must be accounted for when the same query is executed by different users or by SYSADMIN-owned concurrent programs.