Results for “ams_web_plce_mp_vl”

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

Overview

AMS_WEB_PLCE_MP_VL is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, classified under the AMS (Marketing) product family. As documented in the ETRM repository, the view "returns the placement and related object detail information" and is registered with a status of VALID across both 12.1.1 and 12.2.2 environments. The "_VL" suffix follows the Oracle Applications convention for a language-sensitive view, meaning that the view resolves translated (TL) columns based on the runtime session language rather than exposing all language rows. Functionally, AMS_WEB_PLCE_MP_VL joins the base placement-media-placement table with its translation table to present a single, language-filtered row per placement, combining operational attributes with the user-facing title.

For reporting and integration, the view serves as the canonical read interface for web placement metadata. Oracle Marketing and its dependent modules (for example, iStore and campaign execution) rely on such views to retrieve placement configuration without querying the underlying base tables directly, preserving the abstraction of the multi-language data model.

Underlying Base Objects

Per the documented view metadata, AMS_WEB_PLCE_MP_VL is defined over two referenced base objects, both exposed to APPS through synonyms:

• AMS_WEB_PLCE_MP_B — the base (non-translated) table holding the physical placement-media-placement records and their attributes.
• AMS_WEB_PLCE_MP_TL — the translation table holding language-specific descriptive columns, notably PLACEMENT_MP_TITLE.

The view text joins these two objects on PLACEMENT_MP_ID and restricts the translation row with the predicate TL.LANGUAGE = USERENV('LANG'). This is the standard Oracle multi-language pattern: the _B table stores language-independent data, the _TL table stores translated text, and the _VL view presents the appropriate translation for the current session language. Because the join is an equi-join on the primary key and translation is filtered to a single language, the view returns exactly one row per placement provided the translation row exists.

Key Columns

The view projects the complete column set of the base table plus the translated title. The most significant columns include:

• ROW_ID — the ROWID of the underlying AMS_WEB_PLCE_MP_B row, useful for direct row addressing.
• PLACEMENT_MP_ID — the primary key of the placement-media-placement record and the join key to the translation table.
• PLACEMENT_ID — foreign key linking the record to its parent placement.
• OBJECT_USED_BY / OBJECT_USED_BY_ID — identifies the object or entity that consumes the placement, supporting the "object_used_by" relationship model.
• CONTENT_ITEM_ID / CITEM_VERSION_ID / CONTENT_TYPE_CODE — identify the content item, its version, and content type associated with the placement.
• DISPLAY_PRIORITY, PUBLISH_FLAG, MAX_RECOMMENDATIONS — behavioral controls governing display ordering, publication state, and recommendation limits.
• PLACEMENT_MP_TITLE — the translated, user-facing title of the placement.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, and the 15 ATTRIBUTE (descriptive flexfield) columns.

Common Use Cases and Queries

Typical use cases include placement inventory reporting, integration extracts feeding web storefronts, and administrative queries identifying which objects consume a given placement. Because the view is language-aware, queries should be issued from a session whose language corresponds to the desired translation. A representative query retrieving active placements for a specific consuming object is shown below:

• SELECT placement_mp_id, placement_id, object_used_by_id, object_used_by, content_item_id, display_priority, publish_flag, placement_mp_title FROM apps.ams_web_plce_mp_vl WHERE object_used_by_id = :object_id AND publish_flag = 'Y' ORDER BY display_priority;
• To list all placements with their translated titles: SELECT placement_mp_id, placement_mp_title, content_type_code FROM apps.ams_web_plce_mp_vl;
• To correlate content versions: SELECT p.placement_mp_id, p.placement_mp_title, p.citem_version_id FROM apps.ams_web_plce_mp_vl p WHERE p.content_item_id = :content_item_id;

Because the view is defined with a USERENV('LANG') predicate, care should be taken in batch or concurrent programs to set the session language explicitly; otherwise the default language of the executing session determines which translation row is returned. Direct DML is not supported against this view, and all maintenance should target the underlying base and translation tables through the supported AMS APIs.