Results for “arc_act_market_segment_used_by”

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

Overview

The AMS_EVENT_MARKET_SEGMENTS_V view is a reporting and integration object within the Oracle E-Business Suite AMS – Marketing module. It is owned by the APPS schema and holds VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view returns general information about the market segments that are associated with marketing events, joining the event-to-segment association data held in the transactional tables to the descriptive segment (cell) definitions. It therefore serves as the presentation layer that converts stored identifiers into human-readable market segment names, descriptions, and size attributes suitable for concurrent programs, OBIEE extracts, Forms LOVs, and custom reporting.

The view is read-only by definition and carries no DML of its own; consumers treat it purely as a query surface over the underlying marketing event segment associations.

Underlying Base Objects

Per the ETRM metadata, AMS_EVENT_MARKET_SEGMENTS_V is defined over two referenced base objects:

• AMS_ACT_MARKET_SEGMENTS (exposed through a synonym) — the association table that links an activity (event) to a market segment, and which physically stores the ACTIVITY_MARKET_SEGMENT_ID, ACT_MARKET_SEGMENT_USED_BY_ID, ARC_ACT_MARKET_SEGMENT_USED_BY, and MARKET_SEGMENT_ID columns.
• AMS_CELLS_VL (a view) — the multi-language cell/segment definition view, supplying the descriptive attributes CELL_NAME, DESCRIPTION, MARKET_SEGMENT_FLAG, and ORIGINAL_SIZE.

The two sources are combined with an inner join on AAMS.MARKET_SEGMENT_ID = AC.CELL_ID, so a row is returned only where an event-segment association resolves to a valid cell definition. Because AMS_CELLS_VL is itself a translated (_VL) view, the segment name and description returned are language-sensitive and will surface values appropriate to the session or reporting language.

Key Columns

• ACTIVITY_MARKET_SEGMENT_ID — Primary identifier for the event-to-market-segment association row; the natural key for retrieving a single association record.
• ACT_MARKET_SEGMENT_USED_BY_ID — The identifier of the entity that "uses" the market segment within the activity context. This is the column referenced by the search term act_market_segment_used_by_id, and it links the association back to the owning/using activity record.
• ARC_ACT_MARKET_SEGMENT_USED_BY — The archive/context discriminator indicating the source ("used by") type for the association, distinguishing how the segment is attached to the activity.
• MARKET_SEGMENT_ID — Foreign key to the underlying market segment (cell) definition; joined to CELL_ID in AMS_CELLS_VL.
• MARKET_SEGMENT_NAME — The cell name (CELL_NAME) of the segment, the primary display value in reports and LOVs.
• MARKET_SEGMENT_DESCRIPTION — The descriptive text for the segment (DESCRIPTION).
• MARKET_SEGMENT_FLAG — Indicator flag from the cell definition.
• ORIGINAL_SIZE — The original size of the market segment/cell, useful for segment-volume analysis.

Common Use Cases and Queries

Typical scenarios include listing all market segments attached to an event, resolving a MARKET_SEGMENT_ID to its name and description, and joining the association back to the activity by ACT_MARKET_SEGMENT_USED_BY_ID.

SELECT activity_market_segment_id,
       act_market_segment_used_by_id,
       arc_act_market_segment_used_by,
       market_segment_id,
       market_segment_name,
       market_segment_description,
       market_segment_flag,
       original_size
FROM   apps.ams_event_market_segments_v
WHERE  act_market_segment_used_by_id = :p_used_by_id;

To enumerate every segment for a given event association identifier:

SELECT v.market_segment_name,
       v.market_segment_description,
       v.original_size
FROM   apps.ams_event_market_segments_v v
WHERE  v.activity_market_segment_id = :p_assoc_id
ORDER  BY v.market_segment_name;

Because the view hides the join between the association table and the translated cell view, it is the preferred source for BIPublisher reports, OAF/Forms LOVs, and integration extracts that require segment names rather than raw IDs.