Search Results pa_role_status_menu_utils




Overview

PA_ROLE_STATUS_MENU_UTILS is an Oracle Applications (APPS) schema PL/SQL package body within the Oracle E-Business Suite Project Accounting (PA) module. It is classified under the ETRM as an "OTHER" API, indicating that it is an internal utility package rather than a formally published public API. The package provides supporting logic that governs the relationship between project role types, project statuses, and the Oracle EBS menu structures that are presented to users. In the Project Accounting security and responsibility model, menus can be conditionally exposed or hidden based on the combination of a user's project role and the current status of a project. This package encapsulates the validation and lookup routines that enforce these mappings so that the correct navigation options are offered, and so that invalid or conflicting role/status configurations are rejected before they can affect user-facing menus.

The object is marked VALID in the ETRM metadata, and the documentation identifies three documented program units. The package depends on standard Oracle technology stack components, including FND_API and STANDARD, as well as Project Accounting foundation objects. Notably, it is reported as not being referenced by any other database object, which is consistent with a leaf-level utility package that is invoked directly from forms or concurrently rather than chained from other PL/SQL dependencies.

Key Procedures and Functions

The ETRM records three documented procedures or functions for this package body:

  • CHECK_DUP_ROLE_STATUS — Performs duplicate-detection validation. It verifies whether a given project role and project status combination already exists in the role/status menu mapping, preventing redundant or conflicting records from being created in the underlying mapping table.
  • CHECK_STATUS_IS_IN_USE — Determines whether a particular project status is currently referenced by existing role/status menu mappings. This supports integrity checks so that a status which is actively driving menu behavior cannot be removed or altered without awareness of its usage.
  • GET_ROLE_STATUS_MENUS — Retrieves the menu definitions associated with a role and status combination. It returns the applicable menu identifiers used to build or filter the navigation available to the user for that role/status context.

The documentation does not enumerate parameter lists for these units; the descriptions above reflect their documented names and evident validation/retrieval purpose only.

Tables Accessed

The ETRM lists three tables referenced by this package through APPS synonyms:

  • PA_ROLE_STATUS_MENU_MAP — The primary mapping table linking project roles and statuses to menu entries. It is the central data store that CHECK_DUP_ROLE_STATUS validates against and that GET_ROLE_STATUS_MENUS reads.
  • PA_PROJECT_ROLE_TYPES_B — The base table of project role types. It supplies the role definitions used when validating or resolving role/status menu combinations.
  • FND_MENUS — The Oracle Application Object Library menus table, providing the menu identifiers and definitions that are returned by GET_ROLE_STATUS_MENUS and validated within the mapping logic.

In addition, the documented dependency list references several Project Accounting PL/SQL collection types, including PA_NUM_TBL_TYPE and PA_VARCHAR2_30_TBL_TYPE, indicating that the package routines exchange data with callers using these standard collection structures. FND_API is referenced, indicating use of the Oracle Application Framework API utilities (commonly for message handling and standardized return status).

Usage Notes

Because PA_ROLE_STATUS_MENU_UTILS is an internal "OTHER" utility and is not referenced by any other database object, it is not intended as an integration point for external systems. It is most commonly invoked from Project Accounting setup forms and related PL/SQL UI logic when administrators define or modify the role/status-to-menu mappings, and when the application resolves which menus should be presented for a given role and project status. The CHECK_ routines are typically called during validation (for example, before insert or update on the mapping records), while GET_ROLE_STATUS_MENUS is called during runtime menu resolution. Custom code should avoid direct dependency on this package, since it is undocumented as a public API and its contract is subject to change across releases; any custom requirement should use supported Project Accounting or FND menu APIs instead.