Results for “security_function_name”

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

Overview

PA_PAGE_TYPE_REGIONS is a Projects (PA) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the regions exposed on Project Management page types. Each row associates a region source (a view, edit, or placeholder region) with a page type, and optionally binds that region to Oracle Forms functions for page-level and security-level access control. The table therefore acts as the join between the user-interface layout of Projects pages and the function-security layer implemented in FND_FORM_FUNCTIONS.

From a dimensional-modeling perspective, the mined metadata suggests a link classification. The table carries no descriptive attributes of its own beyond ordering, flags, and styling; it exists to resolve the many-to-many relationships between page types, region sources, and Forms functions. It should be treated as an associative entity rather than a hub or satellite.

Key Information Stored

The primary key, PA_PAGE_TYPE_REGIONS_PK, is a composite surrogate key over REGION_SOURCE_CODE, PAGE_TYPE_CODE, and REGION_SOURCE_TYPE. A separate unique index, PA_PAGE_TYPE_REGIONS_U1, covers PAGE_TYPE_CODE, REGION_SOURCE_TYPE, REGION_SOURCE_CODE, and ZD_EDITION_NAME, which serves as the business-key candidate and enforces uniqueness within an edition.

• PAGE_TYPE_CODE — identifies the page type to which the region belongs.
• REGION_SOURCE_CODE and REGION_SOURCE_TYPE — identify the region and its category (for example, view, edit, or placeholder source).
• VIEW_REGION_CODE and EDIT_REGION_CODE — the region codes used in view and edit modes respectively.
• DISPLAY_ORDER and DEFAULT_REGION_POSITION — control sequencing and default placement of the region on the page.
• MANDATORY_FLAG and PLACEHOLDER_REGION_FLAG — indicate whether the region must be present and whether it is a placeholder.
• REGION_STYLE — presentation attribute applied to the region.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-range columns governing when the mapping is active.
• PAGE_FUNCTION_NAME and SECURITY_FUNCTION_NAME — foreign keys to FND_FORM_FUNCTIONS controlling page and security function access.
• DOCUMENT_SOURCE and ZD_EDITION_NAME — identify the document source and the edition, supporting multi-edition deployments.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on diagnosing region rendering and function-security behavior on Projects pages. Administrators query this table to confirm which functions are attached to a region, or to identify all regions bound to a given function.

• List all regions and their security functions for a page type:

  SELECT page_type_code, region_source_code, page_function_name, security_function_name
  FROM   pa_page_type_regions
  WHERE  page_type_code = :page_type_code
  ORDER  BY display_order;

• Find every region attached to a specific Forms function:

  SELECT page_type_code, region_source_code, region_source_type
  FROM   pa_page_type_regions
  WHERE  page_function_name = :function_name OR security_function_name = :function_name;

• Validate active, non-expired mappings using START_DATE_ACTIVE and END_DATE_ACTIVE before deployment.
• Report mandatory and placeholder regions per page type to audit layout completeness.

Related Objects

• FND_FORM_FUNCTIONS — referenced twice, via PAGE_FUNCTION_NAME and SECURITY_FUNCTION_NAME, forming the core security linkage.
• FND_FORM_FUNCTIONS_VL — the translatable view joining on FUNCTION_NAME for descriptive reporting.
• FND_COMPILED_MENU_FUNCTIONS — used to trace function assignment to menus.
• FND_RESPONSIBILITY and FND_USER_RESP_GROUPS — used to trace which responsibilities grant access to the functions referenced here.
• PA_PAGE_TYPES (page-type definition) — the parent concept joined on PAGE_TYPE_CODE.