Results for “ams_cells_all_b”

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

Overview

AMS_CELLS_ALL_B is the base table in the AMS (Marketing) schema that stores the definition of marketing cells, which are better known as Segments in Oracle Marketing. A cell represents the atomic building block of a marketing segmentation model and is composed of one or more Discoverer workbooks and worksheets that define the population of customers, prospects, or parties targeted by a campaign. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the master definition repository for every segment created through the Oracle Marketing segmentation UI, and it is the anchor point from which list generation, party assignment, and campaign execution logic flow.

From a Data Vault modeling perspective, the documented FK structure suggests AMS_CELLS_ALL_B behaves as a hub: it holds the durable business key CELL_ID (and its alternate key CELL_CODE) with relatively stable descriptive attributes, while relationship and lifecycle variation is captured in surrounding link and satellite objects such as AMS_PARTY_MARKET_SEGMENTS and AMS_CELLS_ALL_TL. This classification is a heuristic derived from the FK topology rather than a mandated design.

Key Information Stored

The table exposes 20 documented columns, of which the most significant are:

• CELL_ID — surrogate primary key (AMS_CELLS_ALL_B_PK) and unique index AMS_CELLS_ALL_B_U1; the internal identifier referenced by nearly every dependent table.
• CELL_CODE — the user-visible business key, protected by unique index AMS_CELLS_ALL_B_U2.
• PARENT_CELL_ID — self-referencing FK enabling hierarchical segment nesting.
• MARKET_SEGMENT_FLAG — distinguishes a marketing segment from a plain cell.
• SEL_TYPE — indicates the selection type used to build the segment population.
• OWNER_ID — FK to JTF_RS_RESOURCE_EXTNS identifying the owning resource.
• ENABLED_FLAG and STATUS_CODE / STATUS_DATE — control lifecycle and availability of the segment.
• ORIGINAL_SIZE — the count of parties captured when the segment was last evaluated.
• USER_STATUS_ID — references user-defined status values.
• ORG_ID and SECURITY_GROUP_ID — multi-org and security-group context (SECURITY_GROUP_ID FKs to FND_SECURITY_GROUPS).
• COUNTRY — geographic qualifier for the segment definition.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for concurrency control.

Common Use Cases and Queries

Typical usage includes listing active segments for a marketing campaign, inspecting segment hierarchies, validating segment sizes, and joining to translated names. The translated name lives in AMS_CELLS_ALL_TL, so most reports join B and TL on CELL_ID.

• Retrieve active segments: SELECT cell_id, cell_code, market_segment_flag, original_size FROM ams.ams_cells_all_b WHERE enabled_flag = 'Y' AND org_id = :p_org;
• Resolve display names: SELECT b.cell_code, t.cell_name FROM ams_cells_all_b b, ams_cells_all_tl t WHERE b.cell_id = t.cell_id AND t.language = USERENV('LANG');
• Walk the hierarchy with a CONNECT BY on PARENT_CELL_ID.
• Measure segment membership via AMS_PARTY_MARKET_SEGMENTS joined on MARKET_SEGMENT_ID.

Related Objects

• AMS_CELLS_ALL_TL — translated name/description; join on CELL_ID.
• AMS_PARTY_MARKET_SEGMENTS — party-to-segment assignments; join on MARKET_SEGMENT_ID.
• AMS_ACT_MARKET_SEGMENTS — links activities to segments; join on MARKET_SEGMENT_ID.
• AMS_ACT_DISCOVERER_ALL — Discoverer workbook associations; join on ACT_DISCOVERER_USED_BY_ID.
• AMS_LIST_SELECT_ACTIONS — list selection actions; references INCL_OBJECT_ID.
• JTF_RS_RESOURCE_EXTNS — owner resource, via OWNER_ID.
• FND_SECURITY_GROUPS — security context via SECURITY_GROUP_ID.
• AMS_CELLS_ALL_B itself — self-join on PARENT_CELL_ID for hierarchies.