Results for “site_ref_code”

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

Overview

AMS_IBA_PL_PAGES_B is a Marketing (AMS) module base table that stores page definitions per site. Within the Oracle EBS 12.1.1 and 12.2.2 architectures, this table functions as a foundational repository for personalized landing pages, campaign microsites, and various interactive marketing components deployed across different application sites. The table is owned by the AMS schema and is identified by the object name AMS_IBA_PL_PAGES_B, with a status of VALID.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. This suggests that AMS_IBA_PL_PAGES_B acts as a central business entity hub, holding distinct and unique page definitions that are referenced by multiple dependent tables. The presence of the primary key PAGE_ID, along with foreign key relationships to SITE_ID and SECURITY_GROUP_ID, reinforces its role as a core anchor point within the Marketing module's data model. The table captures the essential metadata required to render and manage pages within the Oracle iStore and Marketing interface framework, linking page identifiers to specific sites and reference codes for logical retrieval and management.

Key Information Stored

The table consists of 13 documented columns in ETRM 12.2.2. The surrogate primary key is PAGE_ID, which uniquely identifies each page definition record and serves as the primary reference point for dependent tables. Business-key candidates are defined by unique indexes; notably, AMS_IBA_PL_PAGES_B_UK2 establishes a composite uniqueness constraint on SITE_REF_CODE and PAGE_REF_CODE, ensuring that within a given site reference context, no two pages share the same page reference code. An additional unique index, AMS_IBA_PL_PAGES_B_UK1, covers SITE_ID and PAGE_REF_CODE, while the documented physical schema also lists a unique index AMS_IBA_PL_PAGES_B_U1 on PAGE_ID and ZD_EDITION_NAME.

Among the most significant columns are SITE_ID, which links the page to a specific marketing site and references AMS_IBA_PL_SITES_B; SITE_REF_CODE, which provides a human-readable site identifier; and PAGE_REF_CODE, which serves as the logical page identifier used by applications and queries. STATUS_CODE indicates the lifecycle state of the page definition, determining whether it is active, inactive, or otherwise constrained. Standard EBS audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, all of which track the record's creation and modification history. SECURITY_GROUP_ID enforces multi-tenant data isolation, while OBJECT_VERSION_NUMBER supports optimistic locking during concurrent updates. The ZD_EDITION_NAME column is associated with edition-based redefinition strategies in later EBS releases.

Common Use Cases and Queries

The most common use case for this table involves retrieving page definitions for a specific marketing site by referencing the SITE_REF_CODE or SITE_ID. A typical SQL pattern joins AMS_IBA_PL_PAGES_B to AMS_IBA_PL_SITES_B to resolve site context and filter by STATUS_CODE to return only active pages. For example, querying by SITE_REF_CODE and PAGE_REF_CODE is a frequent operational requirement, as these columns form a unique business key that applications use to look up pages without relying on the surrogate PAGE_ID.

Reporting scenarios include auditing page usage across sites, identifying pages that have not been updated within a given timeframe using LAST_UPDATE_DATE, and validating that all pages reference valid security groups via SECURITY_GROUP_ID. Additionally, administrators query this table to manage page metadata before deploying updates to dependent parameters and placements.

Related Objects

AMS_IBA_PL_PAGES_B maintains significant relationships with several objects. The table AMS_IBA_PL_SITES_B is referenced via the SITE_ID foreign key, establishing the parent site context. The translation table AMS_IBA_PL_PAGES_TL references PAGE_ID and stores language-specific page content. AMS_IBA_PL_PG_PARAMS also references PAGE_ID and contains configurable parameters associated with each page. AMS_IBA_PL_PLACEMENTS_B references PAGE_ID and defines the placement of content regions or components within pages. Additionally, the foreign key on SECURITY_GROUP_ID references FND_SECURITY_GROUPS, tying page visibility to Oracle EBS security group definitions. These relationships confirm the table's role as a central hub for page-level configuration within the AMS Marketing module.