Results for “ams_web_rules_vl”

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

Overview

The AMS_WEB_RULES_VL view is a reporting and integration object within the Oracle E-Business Suite Marketing (AMS) module. It is owned by the APPS schema and holds a status of VALID in both release 12.1.1 and 12.2.2. As its name implies, the "_VL" suffix designates a "view with translation" that joins the base entity table to its translation table so that descriptive text is presented in the run-time session language. The view surfaces configuration data for web rules — the rules that govern how marketing content, offers, or interactions are selected and presented to users in web-based marketing channels. Because it consolidates translated and non-translated attributes into a single queryable structure, the view serves as a convenient reporting and integration surface, allowing concurrent programs, forms, OAF pages, and external interfaces to retrieve web rule definitions without manually joining the base and translation tables.

Underlying Base Objects

The documented metadata identifies two referenced base objects, both accessed through synonyms: AMS_WEB_RULES_B and AMS_WEB_RULES_TL. AMS_WEB_RULES_B is the base (non-translated) table that stores the operational attributes of each web rule, including its identifier, priority, relationship code, and descriptive flexfield context. AMS_WEB_RULES_TL is the translation table that stores the language-dependent rule name. The view definition performs an inner join between these two tables on RULE_ID, filtered by TL.LANGUAGE = USERENV('LANG'). This predicate restricts the translation row to the language of the current user session, ensuring that RULE_NAME is returned in the appropriate language. The join is structured so that one row is returned per web rule per session language, making the view suitable for direct consumption by both user-facing and batch processes.

Key Columns

The view exposes the full column set of the base table plus the translated rule name. Key columns include:

• RULE_ID — Primary identifier of the web rule; the join key between the base and translation tables.
• ACTIVITY_RULE_ID — Reference linking the web rule to its associated marketing activity rule.
• RULE_PRIORITY — Numeric precedence used to sequence rule evaluation when multiple rules apply.
• RELATIONSHIP_CODE — Code describing the relationship or association governing the rule; this is the column most directly relevant to the user's search.
• CONTEXT_TYPE_CODE / CONTEXT_ID — Descriptive flexfield context that further classifies the rule.
• RULE_NAME — Language-specific descriptive name retrieved from AMS_WEB_RULES_TL.
• ORGANIZATION_ID — Multi-org identifier supporting operating unit partitioning.
• SECURITY_GROUP_ID — Security grouping attribute used for data access control.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments available for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ROW_ID — The ROWID of the base table row, exposed for direct row addressing.

Common Use Cases and Queries

Typical usage centers on reporting the active set of web rules, their priorities, and their associated relationship codes. Because the view returns the translated name, it is the preferred source whenever a human-readable output is required. A common scenario is retrieving all rules for a given priority range or filtering by relationship code:

SELECT rule_id, rule_name, rule_priority, relationship_code
FROM apps.ams_web_rules_vl
WHERE relationship_code = :p_relationship_code
ORDER BY rule_priority;

Another frequent pattern joins the view to the activity rule table to report web rules alongside their parent marketing activities, or restricts output by organization for multi-org reporting. The view is also consumed by integration layers that extract web rule configuration for external campaign management platforms. When troubleshooting rule selection behavior, querying this view filtered by RULE_PRIORITY and CONTEXT_TYPE_CODE provides a clear picture of which rule will be evaluated first. Because the view resolves the session language at runtime, reports executed under different language settings automatically return localized RULE_NAME values without additional application logic.