Search Results flex_code

Overview

PA_UDS_SECTIONS_V is an APPS-owned reporting view in the Oracle Projects (PA) module that exposes all user definable sections configured for the Projects status report layout framework. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the metadata dictionary for Descriptive Flexfield (DFF) based regions that administrators place on configurable project status report pages. Rather than storing section definitions itself, the view joins the page-type region configuration table to the descriptive flexfield context definitions, producing a single denormalized result set describing each user definable section by its flex code, flex name, description, layout style, and page placement attributes.

The view is primarily consumed by the Projects page layout utilities and by any extension or reporting layer that needs to enumerate the sections available for a given page type. Because the flexfield values it exposes are date-effectivity aware, the view is also useful for auditing which sections were active during a given reporting period.

Underlying Base Objects

The documented ETRM metadata identifies the following referenced base objects:

• FND_DESCR_FLEX_CONTEXTS_VL (VIEW) – supplies the descriptive flexfield context name and description, joined on DESCRIPTIVE_FLEX_CONTEXT_CODE with the flexfield restricted to PA_STATUS_REPORT_DESC_FLEX.
• PA_LOOKUPS (VIEW) – supplies the layout meaning through LOOKUP_TYPE PA_USER_REGION_STYLES, joining ATTRIBUTE1 to the view region code.
• PA_PAGE_LAYOUT_UTILS (PACKAGE) – called to compute the DELETABLE_FLAG for each region using the page type, region source type, and region source code.
• PA_PAGE_TYPE_REGIONS (SYNONYM) – the driving table providing region source code, page type, region codes, display order, mandatory flag, and date effectivity.

The view is therefore a pure projection: it performs no DML and cannot be updated through the view layer. All persistence occurs in PA_PAGE_TYPE_REGIONS and the flexfield definition tables.

Key Columns

The view returns the following navigationally relevant columns:

• FLEX_CODE – the region source code, identifying the descriptive flexfield context.
• FLEX_NAME – the descriptive flexfield context name, drawn from FND_DESCR_FLEX_CONTEXTS_VL.
• FLEX_DESCRIPTION / DESCRIPTION – the flex context description, matching the "flex_description" search term users typically query against.
• LAYOUT_MEANING – the human-readable layout style derived from PA_LOOKUPS.
• START_DATE_ACTIVE / END_DATE_ACTIVE – date effectivity of the section.
• PAGE_TYPE_CODE – the status report page type to which the section belongs.
• REGION_SOURCE_TYPE – always 'DFF' for rows returned by this view.
• DELETABLE_FLAG – computed flag indicating whether the region may be removed.
• VIEW_REGION_CODE / EDIT_REGION_CODE – the OAF region codes used for display and maintenance.
• DISPLAY_ORDER, MANDATORY_FLAG, DEFAULT_REGION_POSITION, PLACEHOLDER_REGION_FLAG – placement and behavior attributes.
• ROW_ID – the ROWID of the underlying PA_PAGE_TYPE_REGIONS row.

Common Use Cases and Queries

The view is typically queried to inventory available sections, to validate configuration before deploying a page type, or to troubleshoot missing regions. A representative query filtering by flex description follows:

• SELECT flex_code, flex_name, flex_description, layout_meaning, page_type_code FROM pa_uds_sections_v WHERE upper(flex_description) LIKE upper('%'||:search||'%');
• SELECT * FROM pa_uds_sections_v WHERE page_type_code = :page_type AND deletable_flag = 'Y';
• SELECT flex_code, display_order, mandatory_flag FROM pa_uds_sections_v WHERE sysdate BETWEEN start_date_active AND nvl(end_date_active, sysdate + 1);

Because REGION_SOURCE_TYPE is fixed to 'DFF' in the view text, callers need not filter on it, and the APPLICATIONS_ID predicate (275, Oracle Projects) is applied internally, ensuring only Projects flexfield contexts are returned.