Search Results ledger_category_code




Overview
Explore in AI Chat

Overview

APPS.FND_MO_REPORTING_ENTITIES_V is a reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the set of ledgers and ledger configurations available for Multi-Organization (MO) reporting and access control. It serves as a security-filtered catalog of reporting entities, joining ledger definitions to their configuration attributes, including the completion_status_code that indicates the state of the ledger configuration setup. The view is referenced primarily by Oracle's Multi-Organization Access Control (MOAC) framework and by reporting components that must determine which ledgers a given responsibility or user may access. It is defined as a UNION ALL of two branches: the primary ledger branch and a branch covering Application Ledger Configurations (ALC) and Secondary Ledgers. Both branches return an identical column signature and are filtered through the MO_GLOBAL package's CHECK_ACCESS function, ensuring that only entities the current operating unit context is authorized to see are surfaced. Because its access filter depends on session-level operating unit context, the view's result set varies by runtime environment, which makes it unsuitable for static extraction without explicitly initializing MOAC context.

Underlying Base Objects

The documented base objects underlying the view are GL_LEDGERS, GL_LEDGERS_PUBLIC_ALL_V, GL_LEDGER_CONFIGURATIONS, GL_LEDGER_RELATIONSHIPS, HR_OPERATING_UNITS, HR_ORGANIZATION_INFORMATION, XLE_ENTITY_PROFILES, and the MO_GLOBAL package. The first branch joins GL_LEDGERS_PUBLIC_ALL_V to GL_LEDGERS on LEDGER_ID and to GL_LEDGER_CONFIGURATIONS on CONFIGURATION_ID, yielding ledger display attributes plus configuration state. The second branch joins GL_LEDGERS_PUBLIC_ALL_V directly to GL_LEDGER_CONFIGURATIONS on CONFIGURATION_ID and restricts the ledger set to TARGET_LEDGER_ID values from GL_LEDGER_RELATIONSHIPS where the target category is ALC or SECONDARY, the relationship is enabled, and the relationship type is SUBLEDGER. Access control in both branches is enforced by a correlated subquery over HR_ORGANIZATION_INFORMATION that calls MO_GLOBAL.CHECK_ACCESS against operating unit organization IDs, with the ledger ID matched to HR_ORGANIZATION_INFORMATION.ORG_INFORMATION3. HR_OPERATING_UNITS and XLE_ENTITY_PROFILES are documented as referenced objects supporting the operating unit and legal entity context used in access evaluation.

Key Columns

  • REPORTING_LEVEL — literal '1000' in both branches, identifying the reporting tier of the returned entity.
  • ENTITY_NAME — the ledger name from GL_LEDGERS.
  • ENTITY_ID — the ledger identifier.
  • OPERATING_UNIT_ID — set to -9999 in both branches, indicating a ledger-level rather than operating-unit-level reporting entity.
  • LEGAL_ENTITY_ID — set to -9999, similarly indicating no legal entity scope at this reporting level.
  • LEDGER_ID — the ledger ID used for downstream correlation.
  • CURRENCY_CODE — ledger currency from GL_LEDGERS.
  • LEDGER_CATEGORY_CODE — the ledger category (for example PRIMARY, ALC, or SECONDARY), which distinguishes the two UNION branches semantically.
  • COMPLETION_STATUS_CODE — sourced from GL_LEDGER_CONFIGURATIONS, this column reports the configuration completion state of the ledger, distinguishing fully configured ledgers from those still in setup. It is frequently used to exclude incomplete ledger configurations from reporting.

Common Use Cases and Queries

The view is most commonly queried to enumerate accessible ledgers for reporting or to filter out ledgers whose configuration is incomplete. A representative query is SELECT ledger_id, entity_name, ledger_category_code, completion_status_code FROM apps.fnd_mo_reporting_entities_v WHERE completion_status_code = 'C';. Another common pattern joins the view to ledger-level reporting tables on LEDGER_ID to constrain results to the current user's authorized ledgers. Because the access predicate relies on MO_GLOBAL.CHECK_ACCESS and operating unit context from HR_ORGANIZATION_INFORMATION, sessions must initialize MOAC context before querying; otherwise results may be empty or restricted unexpectedly. The view is primarily consumed indirectly by EBS reporting infrastructure rather than by ad hoc query, and it should be treated as read-only, session-sensitive metadata exposing ledger configuration status within an organization-access-controlled scope.