Search Results pa_role_status_menu_map_u1

Overview

PA.PA_ROLE_STATUS_MENU_MAP is an Oracle Projects (PA) transactional table that underpins status-based security for roles within Oracle E-Business Suite 12.1.1 and 12.2.2. The table allows an administrator to constrain the set of menu functions and actions available to a given role according to the current status of a project. In practical terms, when a project is in a particular lifecycle status — such as Draft, Submitted, or Approved — the menu options presented to a user acting under a specific role can be narrowed to those the role is permitted to execute at that status.

The object is stored in the APPS_TS_TX_DATA tablespace with PCT Free of 10 and carries the standard Oracle EBS audit columns. The documented ETRM metadata classifies this object heuristically as a link table in a Data Vault modeling sense. This classification is appropriate because the table resolves relationships between a role and a menu, qualified by a project status code — it is association/relationship data rather than a pure hub (no natural business key of its own) or a descriptive satellite. Practitioners designing an analytical vault over EBS data may therefore treat PA_ROLE_STATUS_MENU_MAP as a link bridging role, project status, and menu entities.

Key Information Stored

The table contains eleven documented columns. The most significant include:

• ROLE_STATUS_MENU_ID — Number(15), the surrogate primary key populated from a sequence. This is the single-column unique index PA_ROLE_STATUS_MENU_MAP_U1 and forms the row's identity.
• ROLE_ID — Number(15), the role for which the status-level menu mapping applies. Indexed non-uniquely via PA_ROLE_STATUS_MENU_MAP_N1, making it the principal retrieval path.
• STATUS_TYPE — Varchar2(30), the status category drawn from PA_PROJECT_STATUSES. Per the documentation, only the value PROJECT is currently supported.
• STATUS_CODE — Varchar2(30), the specific status code from PA_PROJECT_STATUSES to which the menu is linked.
• MENU_ID — Number(15), the identifier of the menu being granted or restricted for that role/status combination.
• OBJECT_VERSION_NUMBER — Number(15), the standard EBS optimistic locking column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns capturing audit and concurrency metadata.

Note that while ROLE_STATUS_MENU_ID is the technical primary key, there is no separate composite business-key unique index documented; the business identity is effectively the combination of ROLE_ID, STATUS_TYPE, STATUS_CODE, and MENU_ID.

Common Use Cases and Queries

Typical scenarios include auditing which menus a given role can access at a given project status, confirming configuration after a security change, and reporting on role-to-menu coverage across status codes.

A straightforward lookup of all mappings for a role might read:

• SELECT role_status_menu_id, status_type, status_code, menu_id FROM pa.pa_role_status_menu_map WHERE role_id = :role_id;

To determine which menus apply to a specific project status:

• SELECT menu_id FROM pa.pa_role_status_menu_map WHERE status_type = 'PROJECT' AND status_code = :status_code;

Reporting frequently joins to PA_PROJECT_STATUSES to retrieve status descriptions and to FND_MENUS for menu naming, and joins against FND responsibility/role tables to resolve the role identity. These queries are normally executed with the APPS schema context to respect security and synonym visibility.

Related Objects

The documented foreign keys and dependencies establish the following significant relationships:

• PA.PA_PROJECT_STATUSES — referenced via STATUS_CODE; the authoritative source of valid project status codes and types.
• FND_MENUS — referenced via MENU_ID; defines the menu structure whose entries are mapped to the role/status combination.
• PA_ROLE_STATUS_MENU_MAP# — the associated database object listed as referencing this table (typically a synonym or related construct in the PA schema).
• FND_ROLES / role definitions — logically related through ROLE_ID, though resolved outside the documented FK set.

Because the table does not reference any other database objects beyond these documented relationships, its dependency footprint is compact and centered on project status definitions and menu metadata.