Results for “field_id”

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

Overview

The APPS.WMS_PAGE_CONFIG_UI_V view is a multilingual reporting and integration object within the Warehouse Management (WMS) module of Oracle E-Business Suite. Its purpose is to expose page configuration metadata — the set of fields rendered on WMS mobile and desktop pages together with any configuration templates applied to those fields — in a form suitable for user interface consumption and downstream reporting. The view carries the STATUS of VALID in the APPS schema and is defined as a UNION ALL of two distinct result sets, one describing the base page fields and one describing the same fields as overlaid by a configuration template. This design allows callers to query a single object and obtain both the un-templated field definitions and any template-specific overrides.

Underlying Base Objects

The documented dependency chain for the view comprises three referenced objects:

• WMS_PAGE_FIELDS_VL (VIEW) — the multilingual source of page field definitions, supplying columns such as FIELD_NAME, FIELD_TYPE, FIELD_PROMPT, and FIELD_IS_CONFIGURABLE.
• WMS_PAGE_TEMPLATES_VL (VIEW) — the multilingual source of page configuration templates, supplying TEMPLATE_NAME, USER_TEMPLATE_NAME, TEMPLATE_DESCRIPTION, CREATING_ORGANIZATION_ID, and ENABLED.
• WMS_PAGE_TEMPLATE_FIELDS (SYNONYM) — the association of individual fields to templates, supplying the FIELD_PROPERTY1_VALUE and FIELD_PROPERTY2_VALUE overrides.

The first branch of the UNION derives entirely from WMS_PAGE_FIELDS_VL, with TEMPLATE_* columns hard-coded to -1 or NULL to denote the absence of a template. The second branch joins all three objects and applies outer joins (WPT.PAGE_ID (+) and WTF.FIELD_ID (+)), filtered by WPT.ENABLED = 'Y', so that only enabled templates contribute rows.

Key Columns

• PAGE_ID / FIELD_ID — composite identifiers locating a field on a WMS page.
• FIELD_DISP_SEQUENCE_NUMBER — controls the order in which the field prompt is rendered.
• FIELD_NAME / FIELD_TYPE / FIELD_CONSTRUCTOR_PARAM — logical name, datatype, and constructor argument for the field control.
• FIELD_PROMPT — the translatable label displayed to the user.
• FIELD_IS_CONFIGURABLE / FIELD_IS_VISIBLE / FIELD_CATEGORY — flags and grouping that govern whether a field may be customized and whether it appears.
• FIELD_PROPERTY1_DEFAULT_VALUE / FIELD_PROPERTY2_DEFAULT_VALUE — default values defined at the page-field level.
• TEMPLATE_ID / TEMPLATE_NAME / USER_TEMPLATE_NAME / TEMPLATE_DESCRIPTION — the template identity and its user-facing labels; TEMPLATE_ID = -1 signals a non-templated row.
• CREATING_ORGANIZATION_ID / CREATING_ORGANIZATION_CODE / COMMON_TO_ALL_ORGS / ENABLED — organizational scope and enablement of the template.
• FIELD_PROPERTY1_VALUE / FIELD_PROPERTY2_VALUE — the template-specific override values for the field properties.

Common Use Cases and Queries

Typical usage includes diagnosing why a WMS field renders with a particular prompt, retrieving template descriptions for administrative review, and extracting the field layout for a page for integration or documentation. A query retrieving template descriptions resembles the following:

SELECT page_id, field_id, field_name, template_id, template_name, template_description FROM apps.wms_page_config_ui_v WHERE template_id != -1 ORDER BY page_id, template_id, field_disp_sequence_number;

To list all fields for a specific page regardless of template, the caller omits the template filter. To compare default versus templated property values, the FIELD_PROPERTY1_DEFAULT_VALUE column is compared against FIELD_PROPERTY1_VALUE. Because the view unions base and templated rows, queries that require only base field metadata should filter on TEMPLATE_ID = -1 to avoid duplicate field rows.