Results for “xla_mo_reporting_entities_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_MO_REPORTING_ENTITIES_V is an APPS-owned view in the Subledger Accounting (XLA) product family. It exposes the set of reporting entities for which subledger accounting and multi-organization reporting can be performed. In Oracle EBS Release 12, XLA uses a "reporting entity" concept to determine the accounting and reporting context — the set of books or ledger — under which subledger transactions are accounted. This view consolidates that list so that concurrent programs, inquiries, and reporting logic can present the user with the valid entities available in the current environment.

The view is multi-org aware. Its definition branches explicitly on FND_PRODUCT_GROUPS.MULTI_ORG_FLAG, allowing it to behave correctly whether the instance is configured with Multi-Org enabled ('Y') or disabled ('N'). It also honors the operating unit context established through USERENV('CLIENT_INFO'), which is the standard mechanism by which EBS establishes session-level operating unit context. This makes the view sensitive to the user's current responsibility and operating unit selection.

Underlying Base Objects

The documented referenced base objects are:

• FND_PRODUCT_GROUPS (synonym) — supplies the MULTI_ORG_FLAG that drives the conditional UNION ALL branches.
• FND_PROFILE (package) — used as FND_PROFILE.VALUE_WNPS to retrieve the session's set of books (GL_SET_OF_BKS_ID) in the non Multi-Org branch.
• GL_SETS_OF_BOOKS (view) — the source of the set-of-books name and SET_OF_BOOKS_ID used for the reporting-level and entity identifiers.
• HR_ALL_ORGANIZATION_UNITS_TL (synonym) — provides organization names in the translation table.
• HR_ORGANIZATION_INFORMATION (synonym) — provides the classifications and flexfield segments: CLASS (HR_LEGAL), LEGAL ENTITY ACCOUNTING (Org Information 1 – Set of Books), and OPERATING UNIT INFORMATION (Org Information 1 – Legal Entity, Org Information 3 – Set of Books).

Because it references these HR and GL objects, any change to organization classifications or to the set-of-books assignment of a legal entity is reflected immediately when the view is queried.

Key Columns

• REPORTING_LEVEL — a literal distinguishing the level of the entity: '1000' for set-of-books/ledger-level rows and '2000' for legal-entity-level rows.
• ENTITY_NAME — the human-readable name of the reporting entity (set of books name or organization name).
• ENTITY_ID — the identifier of the entity; it holds SET_OF_BOOKS_ID at level 1000 and ORGANIZATION_ID at level 2000.
• OPERATING_UNIT_ID — exposed as -9999 in the supplied definition; it is a placeholder that downstream queries can join or filter on. Users searching on operating_unit_id should note that the operating unit restriction is actually applied internally via HR_ORGANIZATION_INFORMATION.ORGANIZATION_ID and USERENV('CLIENT_INFO') rather than through this column's value.
• LEGAL_ENTITY_ID — -9999 at level 1000; the organization ID of the legal entity at level 2000.
• SET_OF_BOOKS_ID / SET_BOOKS_ID — the ledger associated with the entity, derived either from the operating unit information (ORG_INFORMATION3) or from the legal entity accounting segment (ORG_INFORMATION1).

The -9999 sentinel values are deliberate: they signal "not applicable" for the columns that do not apply at a given reporting level, and they protect callers from NULL comparisons in joins.

Common Use Cases and Queries

This view is typically used to build selection lists of available reporting entities for XLA inquiries, subledger reports, and reconciliation routines, and to resolve the ledger assigned to the current operating unit. A representative query is:

SELECT reporting_level,
       entity_name,
       entity_id,
       set_of_books_id
FROM   apps.xla_mo_reporting_entities_v
WHERE  reporting_level = '2000'
ORDER BY entity_name;

To retrieve only entities relevant to the current operating unit session, filter by the entity identifiers returned for level 2000, since the operating unit context is already enforced inside the view through the CLIENT_INFO sub-expression. A typical integration pattern is to join the view back to GL_SETS_OF_BOOKS or HR_ALL_ORGANIZATION_UNITS_TL for additional attributes, using ENTITY_ID as the join key and matching on REPORTING_LEVEL to disambiguate set-of-books rows from legal-entity rows. Because the view is defined in the APPS schema, the calling user must have SELECT privileges on it, normally granted through the standard XLA responsibility setup.