Search Results validate_reporting_level




Overview
Explore in AI Chat

Overview

FND_MO_REPORTING_API is a public PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Multiple Organizations (Multi-Org) reporting architecture. It provides programmatic control over the reporting context — the Reporting Level and Reporting Entity that determine which operating unit, legal entity, or business group data a session is permitted to see. Rather than forcing developers to manipulate Multi-Org profile options or session state directly, the package exposes a controlled interface for initializing, validating, and introspecting the reporting context used by Multi-Org security views and predicates.

The package is classified as an API and is declared with AUTHID CURRENT_USER, meaning execution privileges and name resolution follow the invoking schema rather than the definer. This is significant for Multi-Org enforcement, because the reporting context is inherently session- and user-specific. The package predates the 12.x multi-org data security model (its header dates to 2005), so it is primarily associated with the 11i/12.0/12.1 Multi-Org architecture; in 12.2 it remains available, largely for backward compatibility and for organizations that have not migrated to the newer security model. The searched symbol, Get_Reporting_Level_Name, is the function most frequently referenced by developers investigating how a session's current reporting level is resolved at runtime.

Key Procedures and Functions

  • Initialize — Establishes the reporting context for the session by accepting a reporting level, a reporting entity identifier, and a predicate type that defaults to 'AUTO'. This is the entry point that sets the internal package state subsequently used by the predicate and name-resolution functions.
  • Get_Predicate — Returns a VARCHAR2 SQL fragment suitable for appending to a query's WHERE clause so that the query is automatically restricted to the current reporting context. It accepts an optional table alias, an optional optimizer hint, and a variable override used to bind the reporting entity identifier. This function is the mechanism by which Multi-Org views and custom reports enforce row-level filtering.
  • Get_Reporting_Entity_Name — Returns the descriptive name of the reporting entity currently in effect, allowing a form or report to display the organization or entity against which data is being reported.
  • Get_Reporting_Level_Name — Returns the name of the reporting level currently in effect. This is the function referenced by the search term get_reporting_level_name, and it is typically used to render the active Multi-Org context, for example in a form header or report parameter listing.
  • Validate_Reporting_Entity — Verifies that the supplied reporting entity identifier is valid for the specified reporting level, raising an error when the combination is not permitted for the current user.
  • Validate_Reporting_Level — Verifies that the supplied reporting level itself is a recognized and permitted value.

Tables Accessed

The package reads the following tables through APPS synonyms:

  • FND_PRODUCT_GROUPS — Supplies the product group (application) information associated with the reporting context.
  • FND_PROFILE_OPTION_VALUES — Provides the profile option values, notably the Multi-Org profile settings, that determine which reporting levels and entities are available to the current user.
  • HR_ALL_ORGANIZATION_UNITS — The authoritative source of organization unit definitions, used to resolve reporting entity identifiers into organization names and to validate entity existence.
  • HR_ORGANIZATION_INFORMATION — Holds the descriptive and classification attributes of organizations, used to determine the reporting level (for example business group, legal entity, or operating unit) to which an organization belongs.

The package is documented as reading these tables; the metadata does not indicate any write operations.

Usage Notes

FND_MO_REPORTING_API is invoked from Oracle Forms, concurrent programs, and custom PL/SQL code that must respect Multi-Org security. The standard pattern is to call Initialize to set the reporting context, then call Get_Predicate to obtain a WHERE-clause fragment that is concatenated into the query, thereby restricting results to the permitted organization. Validate_Reporting_Level and Validate_Reporting_Entity are typically called before Initialize to reject invalid input supplied by a user or by a calling program.

The name-resolution functions, Get_Reporting_Level_Name and Get_Reporting_Entity_Name, are commonly used for display purposes — populating a form field or a report heading so the user can confirm which organization context is active. Because the package depends on profile option values, behavior varies by user responsibility and profile configuration, and callers should not assume a fixed reporting level. With fifteen other packages referencing it, the API is well embedded in the Multi-Org infrastructure, and any custom code that reimplements its logic risks diverging from standard security enforcement. Developers should prefer calling the API over direct manipulation of Multi-Org profile options or organization tables.