Results for “common_to_all_orgs”

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

Overview

WMS_PAGE_TEMPLATES_VL is a multilingual (ML) validation view owned by the APPS schema in Oracle E-Business Suite, belonging to the Warehouse Management (WMS) product family. It exposes page template definitions used by the Warehouse Management mobile and web-based user interface framework, allowing pages presented to warehouse operators to be configured and reused. The "_VL" suffix indicates that the view joins a transactional base table to its translation table and filters the translation row by the session language using USERENV('LANG'). This design lets reports, concurrent programs, forms, and integration interfaces retrieve page template information already resolved to the appropriate language, without the calling application having to join the _B and _TL tables itself. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is treated as a read-only reporting and lookup construct rather than a base entity for DML.

Underlying Base Objects

The view is defined over two documented synonyms: WMS_PAGE_TEMPLATES_B, the base (non-translated) table holding the physical attributes of each page template, and WMS_PAGE_TEMPLATES_TL, the translation table holding language-specific descriptive text. The join is performed on the composite key of PAGE_ID and TEMPLATE_ID, and the TL row is further restricted by T.LANGUAGE = USERENV('LANG') so that only the translation matching the current runtime language is returned. Because the view text selects B.ROWID AS ROW_ID, a unique row identifier from the base table is preserved for each returned row. The relationship is therefore one base row to one translation row per language, with the view presenting the merged, language-resolved record.

Key Columns

• ROW_ID — the rowid of the underlying WMS_PAGE_TEMPLATES_B row, useful as a stable identifier in update-capable blocks.
• PAGE_ID / TEMPLATE_ID — the composite primary key linking a template to a specific page.
• TEMPLATE_NAME — the internal, non-translated name of the template from the base table.
• USER_TEMPLATE_NAME / TEMPLATE_DESCRIPTION — the translated, user-facing name and description sourced from WMS_PAGE_TEMPLATES_TL.
• CREATING_ORGANIZATION_ID / CREATING_ORGANIZATION_CODE — the organization that owns the template definition.
• COMMON_TO_ALL_ORGS — flag indicating whether the template is shared across all organizations rather than restricted to the creating organization.
• ENABLED / DEFAULT_FLAG — status indicators for whether the template is active and whether it is the default for its page.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, enabling customer-defined extensions.

Common Use Cases and Queries

Typical use cases include validating page template configuration before enabling a warehouse mobile page, extracting template definitions for migration or setup comparison between environments, and joining template data to organizational or page metadata. Because the view returns translated names automatically, it is convenient for user-facing LOVs and reports.

List all enabled templates for the session language:

• SELECT page_id, template_id, user_template_name, template_description, default_flag FROM apps.wms_page_templates_vl WHERE enabled = 'Y' ORDER BY template_name;

Identify templates shared across organizations:

• SELECT template_name, user_template_name, creating_organization_code FROM apps.wms_page_templates_vl WHERE common_to_all_orgs = 'Y';

Retrieve the default template for a given page:

• SELECT template_id, user_template_name FROM apps.wms_page_templates_vl WHERE page_id = :page_id AND default_flag = 'Y' AND enabled = 'Y';

All queries should reference the view as APPS.WMS_PAGE_TEMPLATES_VL, relying on the caller's language environment to return the correct translation.