Results for “shortcut_menu_id”

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

Overview

PA_TM_PAGE_LAYOUTS_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. Its documented purpose is to serve as the database_object_name referenced in the FND_OBJECTS table when Oracle seeds a function or object of type TEAM_MEMBER_HOME. In this capacity, the view acts as the dictionary-level anchor that allows the Team Member Home page layout definitions to be registered as an application object within the Oracle EBS security and menu framework.

Functionally, the view exposes the subset of records in PA_PAGE_LAYOUTS whose PAGE_TYPE_CODE equals 'TM' (Team Member). It therefore presents only those page layout definitions that are relevant to the Team Member Home experience, hiding layouts belonging to other page types. Because it is a simple, non-joining view over a single base object, it can be queried in reporting and integration scenarios as a read-only source of Team Member page layout configuration without risk of exposing unrelated layout categories.

Underlying Base Objects

The view is defined over a single documented base object: PA_PAGE_LAYOUTS (SYNONYM). The ETRM metadata lists PA_PAGE_LAYOUTS as the only referenced base object, and the view text confirms this by selecting directly from PA_PAGE_LAYOUTS with a single WHERE predicate on PAGE_TYPE_CODE. No joins, aggregations, or subqueries are involved, so the relationship between the view and the base table is one-to-one at the row level: every row returned by the view corresponds to exactly one row in PA_PAGE_LAYOUTS having PAGE_TYPE_CODE = 'TM'.

Because all columns of the base table are projected, the view is structurally identical to PA_PAGE_LAYOUTS apart from the filtering. This design supports the FND_OBJECTS seeding requirement while keeping the underlying table as the single system of record for layout definitions.

Key Columns

• PAGE_ID — Unique identifier of the page layout record; primary key of PA_PAGE_LAYOUTS.
• PAGE_NAME — User-facing name of the page layout.
• PAGE_TYPE_CODE — Layout category; always 'TM' in this view by construction.
• DESCRIPTION — Descriptive text for the layout.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating that controls when the layout is active.
• RECORD_VERSION_NUMBER — Optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and user context.
• SHORTCUT_MENU_ID — Reference to an associated shortcut menu definition.
• PERS_FUNCTION_NAME — Personalization function name associated with the layout.

Common Use Cases and Queries

The primary use case is resolving the seeded TEAM_MEMBER_HOME object in FND_OBJECTS back to its layout definitions. Administrators and developers also query the view to audit which Team Member Home layouts exist and whether they are currently active.

SELECT page_id, page_name, description,
       start_date_active, end_date_active
FROM   apps.pa_tm_page_layouts_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
                          AND NVL(end_date_active, TRUNC(SYSDATE));

Because PAGE_TYPE_CODE is pre-filtered to 'TM', queries against the view do not need to repeat that predicate, although including it is harmless. A typical integration use validates the seeded object name in FND_OBJECTS against the view to confirm that the object points to a valid base object definition.