Results for “ams_web_placements_b”

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

Overview

AMS_WEB_PLACEMENTS_B is the base (language-independent) table that stores web placement definitions in the Oracle Marketing (AMS) module of Oracle E-Business Suite. A placement represents a user-defined area on a web page — for example, a banner slot, a promotional region, or a content block — into which marketing content items can be served. The table resides in the AMS schema and is valid in both EBS 12.1.1 and 12.2.2. It is the header entity in a small cluster of dependent objects that hold placement-to-content-type associations, mapping relationships, and translated (multi-language) attributes. Based on the foreign key topology documented in ETRM, the object exhibits a hub-leaning Data Vault classification: PLACEMENT_ID acts as the durable business key, while descriptive and audit attributes sit directly on the same row. In a formal Data Vault model, this would suggest a hub for the placement identity, with satellites for the descriptive/audit columns and links to the associated mapping tables.

Key Information Stored

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

• PLACEMENT_ID — the surrogate primary key, enforced by index AMS_WEB_PLACEMENTS_B_U1 and constraint AWPB_PK. This is also the documented unique business-key candidate.
• PLACEMENT_CATEGORY — classifies the type or nature of the placement.
• SITE_ID, SITE_REF_CODE — identify the hosting web site to which the placement belongs.
• PAGE_ID, PAGE_REF_CODE — identify the specific page on which the placement is rendered.
• LOCATION_CODE — the positional code indicating where on the page the placement appears.
• SITE_PARAM1 through SITE_PARAM5 — flexible parameters used to carry site-specific rendering context.
• DEFAULT_CONTENT_ITEM_ID, DEFAULT_CITEM_VER_ID — the default content item and version served in the placement when no other selection applies.
• STATUS_CODE, AUTO_PUBLISH_FLAG, DISPLAY_SELECTION_CODE — control the lifecycle state, whether content publishes automatically, and how content is selected for display.
• DEFAULT_STYLESHEET_ID, DEFAULT_STYLESHEET_VER_ID — reference the default stylesheet used for presentation.
• SECURITY_GROUP_ID — the multi-tenant security partition, referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking control for concurrent updates.
• Standard WHO/audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, plus the 15 ATTRIBUTE (flexfield) columns.

Common Use Cases and Queries

Typical reporting scenarios include listing active placements for a given site or page, auditing placements that lack a default content item, and joining to the translated table for display names.

• Active placements by site:
  SELECT p.placement_id, p.placement_category, p.page_ref_code, p.location_code FROM ams.ams_web_placements_b p WHERE p.site_id = :site_id AND p.status_code = 'ACTIVE';
• Placements with a default content item:
  SELECT placement_id, default_content_item_id, default_citem_ver_id FROM ams.ams_web_placements_b WHERE default_content_item_id IS NOT NULL;
• Placements missing defaults (data-quality check):
  SELECT placement_id FROM ams.ams_web_placements_b WHERE default_content_item_id IS NULL;
• Translated listing: join AMS_WEB_PLACEMENTS_TL on PLACEMENT_ID and filter by LANGUAGE to obtain the user-facing placement name and description.

Related Objects

• AMS_WEB_PLACEMENTS_TL — translated table joined on PLACEMENT_ID; provides language-specific names and descriptions.
• AMS_WEB_PLCE_CTYPE_ASSOC — associates placements with content types via PLACEMENT_ID.
• AMS_WEB_PLCE_MP_B — mapping/base table linking placements to related content, joined on PLACEMENT_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for multi-org security partitioning.
• FND_APPLICATION / FND_LANGUAGES — supporting reference objects for module and translation context.

Because the table is owned by AMS and accessed primarily through Marketing application APIs and concurrent programs, direct DML should be avoided; reporting should rely on the documented joins above.