Results for “ams_content_rules_b”

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

Overview

AMS_CONTENT_RULES_B is the base table in the Oracle E-Business Suite Marketing (AMS) module that stores the master definitions of content rules applied to marketing objects. Content rules govern how marketing deliverables—such as email campaigns, direct mail pieces, and cover letters—are assembled, personalized, and dispatched. The table resides in the AMS schema and is documented as VALID in both the 12.1.1 and 12.2.2 releases, with a documented physical schema of 19 columns under ETRM 12.2.2.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests the table behaves primarily as a descriptive attribute store attached to a parent business entity, rather than as an independent hub or a pure link. Its relationships to IBC_CONTENT_ITEMS and FND_SECURITY_GROUPS, combined with its child translation table, are consistent with a satellite that carries configuration attributes for marketing content delivery.

Key Information Stored

The table is anchored by the surrogate primary key CONTENT_RULE_ID, enforced through the unique index AMS_CONTENT_RULES_B_U1. This identifier is the single documented business-key candidate and is referenced by the translation table AMS_CONTENT_RULES_TL.

• CONTENT_RULE_ID – Surrogate primary key uniquely identifying each content rule.
• OBJECT_TYPE / OBJECT_ID – Polymorphic references identifying the marketing object to which the rule applies.
• SENDER / SENDER_DISPLAY_NAME – The originating sender address and the display name presented to recipients.
• REPLY_TO – The reply-to address used for responses generated by the marketing communication.
• COVER_LETTER_ID – Foreign key to IBC_CONTENT_ITEMS identifying the associated cover letter content item.
• TABLE_OF_CONTENT_FLAG – Indicates whether a table of contents is included in the generated content.
• TRIGGER_CODE – Code determining the event or condition that triggers the content rule.
• ENABLED_FLAG – Controls whether the rule is active or inactive.
• DEFAULT_FLAG – Marks the rule as the default for its object context.
• DELIVERY_MODE – Specifies the delivery channel or method for the rule.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS enforcing row-level access control.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

Content rules are queried during campaign execution to resolve sender identity, cover letter content, and delivery behavior. A typical pattern joins the base table to its translation table to retrieve language-specific text:

• Listing active rules: SELECT content_rule_id, object_type, object_id, delivery_mode FROM ams_content_rules_b WHERE enabled_flag = 'Y';
• Joining translations: SELECT b.content_rule_id, t.name FROM ams_content_rules_b b, ams_content_rules_tl t WHERE b.content_rule_id = t.content_rule_id AND t.language = USERENV('LANG');
• Resolving the cover letter: join COVER_LETTER_ID to IBC_CONTENT_ITEMS to obtain the content item description.
• Security-filtered reporting: constrain SECURITY_GROUP_ID against FND_SECURITY_GROUPS to honor row-level access for the reporting responsibility.

Common reporting scenarios include auditing which rules are enabled versus defined, identifying default rules per object type, and tracing the cover letters bound to each rule for compliance review.

Related Objects

• AMS_CONTENT_RULES_TL – Child translation table joined on CONTENT_RULE_ID, holding language-specific rule text.
• IBC_CONTENT_ITEMS – Referenced through COVER_LETTER_ID, supplying the cover letter content item.
• FND_SECURITY_GROUPS – Referenced through SECURITY_GROUP_ID for access control.
• AMS_COTNENT_RULES_B_PK – The documented primary key constraint on CONTENT_RULE_ID.
• Marketing content delivery and campaign execution APIs consume these rules at runtime to personalize and dispatch marketing objects.