Results for “page_location_code”

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

Overview

AMS_IBA_PAGE_LOCATION is a reference table in the AMS (Marketing) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines the posting locations available on a rendered HTML page within the Oracle Marketing iStore and Interactive Blog/Page (IBA) framework. In practical terms, each row represents a named slot or region on an HTML page to which marketing content — such as a marketing message, offer, or campaign asset — can be assigned and displayed to end users.

The table is owned by the AMS schema and is a small, controlled vocabulary object rather than a high-volume transactional entity. It stores the enumerable set of page locations that the application references when a marketer configures where content should appear. Because it serves primarily as a lookup and configuration list, it participates in relatively few joins and is referenced as a lightweight dimension in reporting.

Mined from the foreign key structure, the heuristic Data Vault classification for this object is standalone. This is a modeling suggestion only: the table does not appear as a dependent link or satellite within the documented FK topology, and it can be treated as an independent reference entity. A single foreign key to FND_SECURITY_GROUPS provides the only documented referential outbound path.

Key Information Stored

The documented physical schema for 12.2.2 contains 10 columns. The most significant are:

• PAGE_LOCATION_ID — The surrogate primary key, enforced by AMS_IBA_PAGE_LOCATION_PK. It is also the single business-key candidate, as captured by the unique index AMS_IBA_PAGE_LOCATION_U1. All downstream references resolve through this identifier.
• PAGE_LOCATION_CODE — The user-facing or programmatic identifier for the location, used by the application to look up the correct slot on a page.
• DESCRIPTION — The translatable or descriptive label that explains the purpose of the posting location to administrators and marketers.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, which scopes visibility of the location record by operating unit or security context.
• OBJECT_VERSION_NUMBER — The optimistic-locking column used by the Oracle Applications framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO (audit) columns recording row creation and modification metadata.

No additional descriptive attributes such as width, height, or page template binding are documented in the ETRM extract, indicating that the table is deliberately kept lean.

Common Use Cases and Queries

The most frequent operational need is to resolve the set of active page locations for configuration or validation. A simple listing query is typical:

SELECT PAGE_LOCATION_ID, PAGE_LOCATION_CODE, DESCRIPTION
FROM AMS.AMS_IBA_PAGE_LOCATION
ORDER BY PAGE_LOCATION_CODE;

A security-scoped variant filters by the owning security group:

SELECT p.PAGE_LOCATION_CODE, p.DESCRIPTION
FROM AMS.AMS_IBA_PAGE_LOCATION p
WHERE p.SECURITY_GROUP_ID = :security_group_id;

Reporting use cases include auditing which page locations exist per security group, validating that marketing content has been assigned to a defined location, and reconciling configuration migrations between environments. Because the table is small and changes infrequently, it is well suited to being cached by integration or BI extracts.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID = SECURITY_GROUP_ID; the only documented foreign key relationship.
• AMS_IBA_PAGE_LOCATION_PK — the primary key constraint on PAGE_LOCATION_ID.
• AMS_IBA_PAGE_LOCATION_U1 — the unique index that establishes PAGE_LOCATION_ID as the business-key candidate.
• AMS_IBA_PAGES / AMS_IBA_PAGE_CONTENT — companion AMS objects that bind page definitions and content to posting locations through PAGE_LOCATION_ID.
• AMS_IBA_* configuration tables — the wider IBA family that consumes this lookup when rendering HTML marketing pages.
• FND_STANDARD_DATE / WHO columns — inherited audit conventions applied through the CREATED_BY and LAST_UPDATED_BY columns.

These objects, together with AMS_IBA_PAGE_LOCATION, form the configuration backbone for page-level marketing content placement.