Results for “activity_offer_id”

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

Overview

The AMS.AMS_IBA_CAMPAIGN_RULES table is a core association entity within the Oracle E-Business Suite Marketing module (AMS). Its documented purpose is to associate campaigns with display rules, providing the persistence layer for campaign-driven interactive business application (IBA) behaviour. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the AMS schema and carries a status of VALID in the ETRM repository, indicating that it is a supported, shipped database object rather than a deprecated or custom artefact.

Functionally, the table acts as a junction that binds three distinct marketing concepts: the campaign itself, the display rule that governs how content or offers are presented, and—where applicable—the activity offer that supplies the promotional material. This makes the object central to rule-based campaign execution and to the targeting logic used by Marketing and related user interfaces.

From a dimensional modelling perspective, the heuristic Data Vault classification derived from the foreign-key structure is link. The table primarily resolves many-to-many style relationships between campaigns, display rules, and activity offers, rather than holding a large descriptive payload. It is therefore best treated as a link table in a Data Vault model, with the referenced master tables acting as hubs and any descriptive attributes handled in a satellite.

Key Information Stored

The table contains thirteen documented columns. The most significant are summarised below.

• CAMPAIGN_RULE_ID — the surrogate primary key, enforced by AMS_IBA_CAMPAIGN_RULES_PK and also carried by the unique index AMS_IBA_CAMPAIGN_RULES_U1. It uniquely identifies each campaign-to-rule association.
• CAMPAIGN_ID — foreign key to AMS_CAMPAIGNS_ALL_B, identifying the owning campaign.
• RULE_ID — foreign key to AMS_IBA_DISPLAY_RULES, identifying the display rule applied to the campaign.
• ACTIVITY_OFFER_ID — foreign key to AMS_ACT_OFFERS, linking the rule association to a specific offer.
• QUALIFIER_TYPE — a classifier column that distinguishes the qualifier context in which the rule applies.
• RULESET_ID — identifies the rule set to which the association belongs, supporting grouped rule evaluation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, driving multi-org / security-group access control.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the AMS framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on nearly all EBS transactional and association tables.

The primary key is a system-generated surrogate, while CAMPAIGN_RULE_ID is also the documented business-key candidate through the unique index. The remaining foreign keys are non-unique, confirming the link-table nature of the object.

Common Use Cases and Queries

Typical usage centres on determining which display rules apply to a given campaign, or conversely which campaigns use a particular rule. A common reporting query joins the table to its parents:

• List all rules for a campaign: SELECT r.rule_id, r.campaign_id, r.qualifier_type FROM ams.ams_iba_campaign_rules r WHERE r.campaign_id = :p_campaign_id;
• Identify campaigns affected by a rule change by filtering on RULE_ID against AMS_IBA_DISPLAY_RULES.
• Audit which offers are linked to rule-driven campaigns via ACTIVITY_OFFER_ID and AMS_ACT_OFFERS.
• Security-scoped extraction using SECURITY_GROUP_ID to restrict results to the operating unit or responsibility the user is entitled to.

Because OBJECT_VERSION_NUMBER is present, any integration that writes to this table must supply and increment it correctly, otherwise concurrent updates will fail with an optimistic locking error. Extraction routines for data warehousing should treat the table as a link source and resolve the referenced hubs through their natural keys.

Related Objects

The tbl references and is referenced by the following significant objects, joined on the columns shown:

• AMS_CAMPAIGNS_ALL_B — joined on AMS_IBA_CAMPAIGN_RULES.CAMPAIGN_ID = AMS_CAMPAIGNS_ALL_B.CAMPAIGN_ID; the campaign header.
• AMS_IBA_DISPLAY_RULES — joined on AMS_IBA_CAMPAIGN_RULES.RULE_ID = AMS_IBA_DISPLAY_RULES.RULE_ID; the rule definition.
• AMS_ACT_OFFERS — joined on AMS_IBA_CAMPAIGN_RULES.ACTIVITY_OFFER_ID = AMS_ACT_OFFERS.ACTIVITY_OFFER_ID; the associated offer.
• FND_SECURITY_GROUPS — joined on AMS_IBA_CAMPAIGN_RULES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; access control.

These four relationships constitute the documented dependency footprint and should be considered the primary navigational paths for any query, report, or integration built on this object.