Results for “creating_organization_id”

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

Overview

WMS_PAGE_TEMPLATES_B is a Warehouse Management (WMS) base table in Oracle EBS that stores page template definitions used by the warehouse management mobile and browser-based user interface. A page template specifies a reusable layout that governs how a transactional page—such as a receiving, put-away, picking, or counting screen—is rendered to the operator. In Oracle EBS 12.1.1 and 12.2.2, this table exists in the WMS schema and is classified as VALID. Its purpose is to centralize the definition of a page, allowing the same template to be deployed across multiple organizations without duplicating configuration.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification: TEMPLATE_ID serves as the durable business key that links the base template definition to its descriptive and child objects. This classification is a heuristic modeling suggestion rather than a declared Oracle construct, but it accurately reflects the table's role as the anchor of a small template cluster.

Key Information Stored

The table contains 30 documented columns. The most significant are:

• TEMPLATE_ID — The surrogate primary key defined by WMS_PAGE_TEMPLATES_B_PK. It uniquely identifies a page template and is the column referenced by all foreign keys.
• TEMPLATE_NAME — The user-facing name of the template, forming part of a business-key candidate in unique index WMS_PAGE_TEMPLATES_B_U2.
• PAGE_ID — Identifies the functional page that the template drives; also part of U2.
• CREATING_ORGANIZATION_ID and CREATING_ORGANIZATION_CODE — The inventory organization that authored the template, establishing ownership for multisite deployments.
• COMMON_TO_ALL_ORGS — A flag indicating whether the template is available to every organization or restricted to the creating organization.
• ENABLED — Controls whether the template is active and selectable at runtime.
• DEFAULT_FLAG — Marks the template as the default for its page.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle descriptive flexfield columns reserved for customer extensions.
• ZD_EDITION_NAME — The editioning column introduced by Oracle's Edition-Based Redefinition (EBR) support, present in both unique indexes U1 and U2.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard WHO audit columns that track template lifecycle activity.

The business-key candidates are WMS_PAGE_TEMPLATES_B_U1 (TEMPLATE_ID, ZD_EDITION_NAME) and WMS_PAGE_TEMPLATES_B_U2 (PAGE_ID, TEMPLATE_NAME, CREATING_ORGANIZATION_ID, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical uses include identifying all active templates for a specific page or organization, auditing which templates are shared across organizations, and reporting the default template assigned to each page. A representative query joins the base table to its translation table for language-specific names:

• SELECT b.template_id, t.template_name, b.enabled, b.default_flag FROM wms_page_templates_b b, wms_page_templates_tl t WHERE b.template_id = t.template_id AND t.language = USERENV('LANG') AND b.enabled = 'Y';
• SELECT page_id, template_name, creating_organization_id, common_to_all_orgs FROM wms_page_templates_b WHERE creating_organization_id = :org_id;
• SELECT b.template_id, f.field_name FROM wms_page_templates_b b, wms_page_template_fields f WHERE b.template_id = f.template_id ORDER BY f.display_sequence;

These patterns support configuration audits, clone and migration scripts between environments, and troubleshooting of missing or incorrect mobile screens. Because the table is edition-enabled, queries should be aware of the ZD_EDITION_NAME column when running under EBR.

Related Objects

The following objects are the most significant dependents or references, based on the documented foreign-key relationships:

• WMS_PAGE_TEMPLATES_TL — The translation table, joined on TEMPLATE_ID, holding language-specific template names and descriptions.
• WMS_PAGE_TEMPLATE_FIELDS — Child table, joined on TEMPLATE_ID, defining the individual fields displayed within each template and their layout attributes.
• WMS_PAGE_TEMPLATES_B_PK — The primary key constraint on TEMPLATE_ID that enforces uniqueness.
• WMS_PAGE_TEMPLATES_B_U1 and WMS_PAGE_TEMPLATES_B_U2 — Unique indexes supporting edition-aware business-key integrity.

Together these objects form a compact but essential configuration cluster for WMS page rendering. Database administrators should treat WMS_PAGE_TEMPLATES_B as the parent of the cluster, since deleting or renumbering TEMPLATE_ID values will cascade logically to translations and field definitions.