Results for “object_used_by”

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

Overview

AMS_WEB_PLCE_MP_B is a Marketing (AMS) module table in Oracle E-Business Suite that stores the placements associated with a marketing object. It resides in the AMS schema and is a core transaction-staging object within the Oracle Marketing placement framework, which governs how content, offers, and campaign assets are positioned against definable marketing entities. The table carries a status of VALID in both 12.1.1 and 12.2.2.

The table is uniquely identified by the primary key constraint AWPMB_PK on the PLACEMENT_MP_ID column. The column OBJECT_USED_BY and OBJECT_USED_BY_ID allow the same placement record to be associated with different classes of marketing objects, making the table a polymorphic association store.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a satellite — it holds descriptive, placement-specific attributes that surround a central placement business key rather than defining a hub of independent business entities. This classification is offered as a heuristic modeling suggestion, not an official Data Vault designation.

Key Information Stored

The table contains 33 documented columns. The most functionally significant include the following.

• PLACEMENT_MP_ID — surrogate primary key defined by the unique index AMS_WEB_PLCE_MP_B_U1 and constraint AWPMB_PK; the business-key candidate for this table.
• PLACEMENT_ID — foreign key to AMS_WEB_PLACEMENTS_B, linking the multi-purpose record to its underlying placement definition.
• OBJECT_USED_BY_ID and OBJECT_USED_BY — identify the marketing object that consumes the placement, supporting polymorphic association.
• CONTENT_ITEM_ID — foreign key to IBC_CONTENT_ITEMS, identifying the content item shown at this placement.
• CITEM_VERSION_ID — foreign key to IBC_CITEM_VERSIONS_B, pinning the specific content version displayed.
• CONTENT_TYPE_CODE — discriminates the content type associated with the placement.
• DISPLAY_PRIORITY — controls ordering when multiple placements compete for the same slot.
• PUBLISH_FLAG and MAX_RECOMMENDATIONS — govern publication eligibility and recommendation limits.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org style data security.
• OBJECT_VERSION_NUMBER, CREATED_BY, LAST_UPDATED_BY, and the associated date columns provide standard audit and optimistic-locking support.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.

The surrogate key (PLACEMENT_MP_ID) should be distinguished from the business-key candidate established by the unique index, which is likewise PLACEMENT_MP_ID here; foreign-key columns such as PLACEMENT_ID and CONTENT_ITEM_ID carry the cross-table business meaning.

Common Use Cases and Queries

Typical usage centers on resolving which content appears at a placement for a given marketing object, and in what order. A representative join retrieves placement definitions alongside their content:

• Reporting placements with their content item: SELECT p.PLACEMENT_MP_ID, p.OBJECT_USED_BY, p.DISPLAY_PRIORITY, c.CONTENT_ITEM_NAME FROM AMS_WEB_PLCE_MP_B p, IBC_CONTENT_ITEMS c WHERE p.CONTENT_ITEM_ID = c.CONTENT_ITEM_ID;
• Filtering published placements: restrict on PUBLISH_FLAG = 'Y' and order by DISPLAY_PRIORITY.
• Tracing content versions: join CITEM_VERSION_ID to IBC_CITEM_VERSIONS_B to audit which version was live.
• Security-scoped extracts: constrain by SECURITY_GROUP_ID when generating user-specific reports.

Related Objects

• AMS_WEB_PLACEMENTS_B — referenced via AMS_WEB_PLCE_MP_B.PLACEMENT_ID; the parent placement definition.
• AMS_WEB_PLCE_CITEM_ASSOC — references this table through PLACEMENT_MP_ID, holding content-item associations.
• IBC_CONTENT_ITEMS — referenced via CONTENT_ITEM_ID.
• IBC_CITEM_VERSIONS_B — referenced via CITEM_VERSION_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.