Results for “wms_page_fields_vl”

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

Overview

WMS_PAGE_FIELDS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, defined within the Warehouse Management (WMS) product. It exposes the configurable field definitions that drive the layout, behavior, and presentation of Warehouse Management pages used within the mobile and desktop user interfaces of Oracle WMS. Because WMS provides a flexible, setup-driven framework for handheld and browser-based transactions, the fields displayed to a user on a given page are not hard-coded; instead they are stored as data and surfaced through this view. WMS_PAGE_FIELDS_VL is therefore the reporting and integration gateway to the page-field configuration metadata, presenting the descriptive, translatable attributes of each field alongside its physical and behavioral properties.

The view is read-only by design. Its purpose is to join the translatable field text to its base definition and restrict the result to the language of the current session, so that reports and external integrations can retrieve a single, language-appropriate row per page and field combination.

Underlying Base Objects

WMS_PAGE_FIELDS_VL is defined over two documented base objects, both referenced through APPS synonyms:

• WMS_PAGE_FIELDS_B — the base table holding the language-independent definition of each configurable page field, including identifiers, sequencing, type, and default values.
• WMS_PAGE_FIELDS_TL — the translation table holding the language-dependent field prompt and user-facing name, keyed by PAGE_ID and FIELD_ID with a LANGUAGE column.

The view joins these two tables on PAGE_ID and FIELD_ID and filters the translation side with T.LANGUAGE = USERENV('LANG'), so only the row matching the session language is returned. The _B suffix denotes the base table and the _TL suffix denotes the translation table; the _VL view name indicates a "view language" construct that flattens the pair into a single-language result set.

Key Columns

The view exposes the full attribute set of a configurable WMS page field. The most significant columns include:

• ROW_ID — the base table row identifier, derived from B.ROWID.
• PAGE_ID — identifies the WMS page to which the field belongs.
• FIELD_ID — the field identifier within the page; together with PAGE_ID it forms the join key.
• FIELD_NAME — the internal field name used by the application.
• FIELD_DISP_SEQUENCE_NUMBER — controls the display order of the field on the page.
• FIELD_PROMPT — the prompt or label displayed to the user.
• FIELD_TYPE — the field data or UI type (for example, text entry, list of values, or check box).
• FIELD_CONSTRUCTOR_PARAM — constructor parameters that drive field instantiation behavior.
• FIELD_CATEGORY — the functional grouping or category of the field.
• FIELD_IS_CONFIGURABLE and FIELD_IS_VISIBLE — flags controlling whether the field may be configured and whether it is currently visible.
• FIELD_PROPERTY1_DEFAULT_VALUE and FIELD_PROPERTY2_DEFAULT_VALUE — default values applied to the field's configurable properties.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• FIELD_USER_NAME — the language-specific user-facing name drawn from the translation table; this is the column whose value changes with the session language.

Common Use Cases and Queries

Typical uses include auditing page-field configuration, documenting which fields are visible or configurable on a given page, and extracting field labels for integration or localization review.

To list all fields for a specific page in the session's language:

• SELECT page_id, field_id, field_name, field_prompt, field_disp_sequence_number, field_is_visible FROM apps.wms_page_fields_vl WHERE page_id = :p_page_id ORDER BY field_disp_sequence_number;

To identify configurable and visible fields:

• SELECT page_id, field_id, field_name, field_user_name, field_type FROM apps.wms_page_fields_vl WHERE field_is_configurable = 'Y' AND field_is_visible = 'Y';

Because the view already applies the USERENV('LANG') filter, queries return only the row set appropriate to the connecting user's language, making it suitable for direct use in concurrent programs, BI Publisher reports, and outbound integration extracts without additional language handling.