Results for “group_code”

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

Overview

The AMS_ACT_LIST_GROUPS table is a core configuration object within the Oracle E-Business Suite Marketing (AMS) module. Its documented purpose is to store the subdivisions of Target Groups into smaller, more granular units, enabling marketers to segment audiences for finer control over campaign execution. It sits under the AMS schema and is valid in both 12.1.1 and 12.2.2 releases, exposing 24 columns in the documented ETRM 12.2.2 physical schema.

From a Data Vault modeling perspective, the heuristic mined from its foreign key structure classifies this object as a standalone entity rather than a strict hub, link, or satellite. This suggests it behaves primarily as a descriptor/reference table whose relationships are largely internal (driven by CODE and STATUS columns) rather than through heavy parent-child FK chains. The single outgoing foreign key to FND_SECURITY_GROUPS is a security/row-level-access reference rather than a transactional dependency.

Key Information Stored

The table is anchored by its surrogate technical primary key defined in the unique index AMS_ACT_LIST_GROUPS_U1 on ACT_LIST_GROUP_ID. Beyond that identifier, the most operationally significant columns include:

• ACT_LIST_USED_BY_ID and ARC_ACT_LIST_USED_BY — identify the owning Target Group (list) or the context in which the sub-group is consumed.
• GROUP_CODE — the business-meaningful code used by marketers to reference the sub-group.
• GROUP_PRIORITY — controls ordering when multiple sub-groups apply.
• STATUS_CODE and USER_STATUS_ID — lifecycle state of the group.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enabling Multi-Org / row-level security.
• RELEASE_STRATEGY, RELEASE_CONTROL_ALG_ID, and RECYCLING_ALG_ID — govern how contacts are released and recycled out of the group during a dialing or telemarketing campaign.
• CALLING_CALENDAR_ID — restricts calling windows.
• CALL_CENTER_READY_FLAG, DIALING_METHOD, CALLBACK_PRIORITY_FLAG — telephony/CTI execution attributes.
• QUANTUM, QUOTA, and QUOTA_RESET — capacity and quota controls for throughput per sub-group.
• OBJECT_VERSION_NUMBER — optimistic concurrency control used by the OAF framework.

Common Use Cases and Queries

Typical usage centres on reporting which sub-groups exist under a parent Target Group, and on tuning dialing/quota parameters. A common reporting pattern:

SELECT g.act_list_group_id, g.group_code, g.group_priority,
       g.status_code, g.dialing_method, g.quota
FROM   ams.ams_act_list_groups g
WHERE  g.act_list_used_by_id = :list_id
AND    g.security_group_id  = :security_group_id
ORDER BY g.group_priority;

Analysts frequently join to FND_SECURITY_GROUPS to resolve security scope:

SELECT g.group_code, s.security_group_name
FROM   ams.ams_act_list_groups g,
       fnd_security_groups s
WHERE  g.security_group_id = s.security_group_id;

These queries support segmentation audits, capacity planning for outbound campaigns, and validation of release/priority rules before a launch.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce row-level security.
• AMS_ACT_LISTS / AMS_ACT_LIST_ALL — parent Target Group definitions referenced via ACT_LIST_USED_BY_ID.
• AMS_ACT_LIST_MEMBERS — associates individual contacts with sub-groups.
• AMS_ACT_LIST_GROUP_MAPS — linking structures that place members into groups.
• AMS_ACT_CAMPAIGNS / AMS_ACT_CAMPAIGN_LISTS — campaign execution contexts consuming the group.
• AMS_ACT_LIST_GROUP_HIST — history/audit companion to this table.
• FND_CALENDARS — referenced by CALLING_CALENDAR_ID for calling windows.