Search Results check_cols_in_proj_header




Overview
Explore in AI Chat

Overview

PA_PAGE_LAYOUT_UTILS is an Oracle Projects utility package in the APPS schema that supports the Project Management page layout framework. Its primary responsibility is to resolve and validate the region-level metadata that drives configurable project page layouts, where a "page layout" consists of pages, regions, and region sources assembled from Oracle Forms, OAF regions, and descriptive flexfields. The package centralizes lookups and integrity checks that other Projects components rely upon, so that page layout configuration screens, project copy routines, and deletion rules behave consistently across releases 12.1.1 and 12.2.2. Because the package is classified as OTHER in ETRM rather than as a public API, it is intended primarily for internal consumption by Oracle Projects forms, concurrent programs, and related PL/SQL packages rather than as a supported extension point.

Key Procedures and Functions

  • GET_REGION_SOURCE_CODE — Given a region source name, source type, application identifier, and flexfield name, returns the corresponding region source code. It is the lookup used to translate a human-readable or partially qualified region definition into the internal code stored on page layout region rows.
  • GET_AK_REGION_CODE — Resolves a region name and application identifier to the Oracle AK (Applications Framework) region code used by the layout engine.
  • COPY_OBJECT_PAGE_LAYOUTS — Copies page layouts from one object instance to another, identified by object type and source/target object identifiers, with standard FND API return status, message count, and message data outputs.
  • CHECK_COLS_IN_PROJ_HEADER — Determines whether customer and project value columns exist at the project header for a given object, returning separate flags for customer existence and project value existence.
  • IS_PAGE_TYPE_REGION_DELETABLE — Evaluates whether a region associated with a page type and region source may be deleted, returning a YES/NO style result.
  • CHECK_PAGE_LAYOUT_DELETABLE — Determines whether a page layout may be deleted, based on the page identifier.
  • CHECK_PAGELAYOUT_NAME_OR_ID — Validates or resolves a page layout name or identifier against a page type code, returning the resolved page layout identifier along with status and error message code outputs.
  • GET_CONTEXT_NAME — Returns the context name corresponding to a context code.
  • GET_PAGE_ID_FROM_FUNCTION — Derives the page identifier for a given page type code and personalization context.
  • POPULATE_PERS_FUNCTIONS — Populates personalization function data used in conjunction with the page layout definitions.

Tables Accessed

The package operates against the Projects page layout schema, including PA_PAGE_LAYOUTS, PA_PAGE_LAYOUT_REGIONS, PA_PAGE_LAYOUTS_TMP, PA_OBJECT_PAGE_LAYOUTS, PA_OBJECT_REGIONS, and PA_REPORT_TYPES. It also reads PA_PROJECTS_ALL to verify project header attributes for the column-checking routine, and accesses PLITBLM, the standard Oracle Forms LOV/query table, for lookup support.

Usage Notes

Invocations typically originate from Oracle Projects setup and configuration forms that manage page layouts, from the object copy routines that duplicate layouts between projects or templates, and from validation logic that decides whether a region or layout is safely deletable. Custom code should treat these routines as internal: parameter lists and behavior are not guaranteed across patches, and callers must honor the FND_API-style X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA conventions where provided. Five other packages reference PA_PAGE_LAYOUT_UTILS, confirming its role as a shared utility layer within Oracle Projects.