Results for “xla_mo_reporting_api”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XLA_MO_REPORTING_API is a public PL/SQL package in the APPS schema that belongs to the Oracle Subledger Accounting (XLA) product family, reflected by the XLAMORPS.pls source file header. The suffix "MO" denotes "Multiple Organization," and the package supplies the runtime context required to execute XLA reporting queries against a specific reporting level and reporting entity within a multi-org enabled E-Business Suite instance. In Oracle EBS 12.1.1 and 12.2.2, subledger accounting data (journal entries, balances, and account analysis) must be filtered by the ledger or organization the user is authorized to view. Rather than hard-coding that filter, XLA reporting components call this API to first initialize the reporting context and then retrieve a dynamically generated SQL predicate that restricts rows to the appropriate reporting entity.
The package is declared with AUTHID CURRENT_USER, meaning its unqualified database references resolve under the privileges of the calling session rather than the package owner — a deliberate design choice that preserves the row-level security and MOAC (Multi-Org Access Control) semantics established by the calling application. The package is classified as an API in the ETRM 12.2.2 metadata and is referenced by 24 other packages, indicating it is a foundational dependency for XLA reporting rather than an end-user-facing construct.
Key Procedures and Functions
- INITIALIZE — Establishes the reporting context for subsequent calls. It accepts a reporting level (defaulting to '3000'), a reporting entity identifier, and a predicate type (defaulting to 'AUTO'). A second, overloaded INITIALIZE signature exists that adds a use_nvl parameter; the source comments explicitly warn that this overload should not be used unless performance problems are encountered, referencing internal bug 3025408.
- GET_PREDICATE — Returns a VARCHAR2 SQL fragment that callers append to their reporting queries to enforce the active reporting entity filter. The function accepts an optional table alias, an optional optimizer hint, and a variable-override string (defaulting to bind variable
:p_reporting_entity_id). A second overload, shown commented in the source, supports only the alias and hint parameters. - GET_REPORTING_ENTITY_NAME — Returns the display name of the reporting entity currently in context, suitable for report headers and page titles.
- GET_REPORTING_LEVEL_NAME — Returns the display name of the active reporting level, allowing reporting components to label output according to the granularity in use.
- VALIDATE_REPORTING_ENTITY — Confirms that the supplied reporting level and entity identifier form a valid, accessible pair before the context is used, preventing unauthorized or inconsistent reporting scopes.
- VALIDATE_REPORTING_LEVEL — Confirms that a given reporting level value is legitimate and supported by the reporting framework.
Tables Accessed
The documented table references, resolved through APPS synonyms, support both context derivation and security validation:
- FND_PRODUCT_GROUPS — Identifies the installed product group and application configuration, used to confirm that the XLA reporting framework is enabled in the current instance.
- FND_PROFILE_OPTION_VALUES — Supplies profile option settings, principally the MO operating unit and reporting-related profile values that determine the user's authorized reporting scope.
- HR_ALL_ORGANIZATION_UNITS — Provides organization unit definitions that define candidate reporting entities at the organization level.
- HR_ORGANIZATION_INFORMATION — Supplies the descriptive and classification attributes of those organizations, enabling the package to derive and validate reporting entity names and levels.
Usage Notes
XLA_MO_REPORTING_API is invoked programmatically, not directly by end users. Typical callers are XLA report and inquiry packages, concurrent programs that extract subledger accounting data, and Oracle Forms-based inquiry screens within Subledger Accounting and General Ledger. The canonical invocation sequence is: call INITIALIZE with the reporting level and entity, optionally call the VALIDATE routines to confirm the selection, call GET_PREDICATE and concatenate the returned fragment into a dynamic SQL statement, and use GET_REPORTING_ENTITY_NAME or GET_REPORTING_LEVEL_NAME to populate report headings. Because the package is AUTHID CURRENT_USER and relies on profile-driven MOAC values, custom code that invokes it must run within a session that has a valid responsibility, operating unit, and ledger context established. The persistent relevance of this package to the query "Excel reporting app v20" lies in its role as the predicate generator for XLA reporting extracts: any Excel-based or custom reporting tool that queries subledger accounting tables directly should obtain its reporting-entity restriction from GET_PREDICATE to preserve MOAC security rather than reconstructing the filter manually.