Search Results ams_content_rules_vl




Overview

AMS_CONTENT_RULES_VL is a Marketing (AMS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It returns all Content Rules defined in Oracle Marketing. A Content Rule governs how a marketing deliverable — such as an email, campaign message, or collateral distribution — is assembled and dispatched: it determines the sender identity, the reply-to address, the cover letter, whether a table of contents is included, the trigger that activates the rule, and the delivery mode. Because the view resolves multilingual (ML) subject text and joins it to the transactional rule definition, it is the single reporting and integration entry point for content rule configuration.

The _VL suffix denotes a "view with language," combining the base table with its translation table and filtering translated rows to the session language via USERENV('LANG'). This makes the view safe for concurrent multi-language access without exposing language-specific duplicate rows. Users searching for "reply_to" will find that column exposed here, which is the primary reason the view is queried when auditing or migrating outbound marketing message routing.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS through synonyms:

  • AMS_CONTENT_RULES_B — the base (non-translated) table holding language-independent rule attributes, including sender, reply-to, cover letter, trigger, and delivery mode.
  • AMS_CONTENT_RULES_TL — the translation table holding language-dependent text, notably the email subject.

The two are joined on CONTENT_RULE_ID, with ACRT.LANGUAGE = USERENV('LANG') restricting output to the current session language. The view therefore presents one row per content rule per session language, combining the rule's operational configuration with its localized subject line.

Key Columns

Common Use Cases and Queries

Typical applications include auditing reply-to and sender routing, extracting content rule configuration for migration or reconciliation, and joining rules to campaigns. The following queries reflect standard usage patterns:

  • Listing all enabled rules with their reply-to and sender:
    SELECT content_rule_id, sender, reply_to, sender_display_name, delivery_mode
    FROM   ams_content_rules_vl
    WHERE  enabled_flag = 'Y';
  • Isolating rules by reply-to address:
    SELECT content_rule_id, email_subject, reply_to
    FROM   ams_content_rules_vl
    WHERE  reply_to = '[email protected]';
  • Finding the default rule per object type:
    SELECT object_type, object_id, content_rule_id, email_subject
    FROM   ams_content_rules_vl
    WHERE  default_flag = 'Y';

Because the view enforces session-language filtering, reports run under different language settings may return differing EMAIL_SUBJECT values for the same CONTENT_RULE_ID; this behavior should be accounted for in any integration that persists subject text.