Results for “ams_web_rules_b”

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

Overview

AMS_WEB_RULES_B is a table in the AMS (Oracle Marketing) schema that stores rule definitions used for web management within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The object carries a status of VALID and is documented as part of the Marketing product family, where it supports the configuration of rules that govern web-based marketing activities and their interaction with customers, organizations, and security contexts.

From a heuristic Data Vault modeling perspective, the mined relationship structure classifies AMS_WEB_RULES_B as standalone. This classification is a modeling suggestion only; it indicates that the table is not strongly integrated into the surrounding FK network as a link entity, but instead functions primarily as a self-contained definition or reference table. Its relationships are limited to a small number of inbound references, reinforcing its role as a configuration anchor rather than a transaction hub.

Key Information Stored

The table contains 30 documented columns, with the primary key defined by the constraint AWB_PK1 on RULE_ID. A unique index, AMS_WEB_RULES_B_U1, also covers RULE_ID, confirming it as the single business-key candidate in the documented schema. Principal columns include:

• RULE_ID — the surrogate primary key uniquely identifying each web rule.
• ACTIVITY_RULE_ID — foreign key to AMS_ACT_WEB_RULE_TYPES, classifying the rule by activity type.
• RULE_PRIORITY — determines evaluation order when multiple rules apply.
• RELATIONSHIP_CODE — describes the relationship context in which the rule operates.
• CONTEXT_TYPE_CODE and CONTEXT_ID — identify the context and its specific instance for rule application.
• ORGANIZATION_ID — the operating unit or organization scope for the rule.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing data security.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for extensible rule metadata.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on retrieving active rule definitions, ordering them by priority, and joining them to activity rule type classifications. A representative query pattern is:

• List all rules for a given activity type: SELECT r.RULE_ID, r.RULE_PRIORITY, r.RELATIONSHIP_CODE FROM AMS.AMS_WEB_RULES_B r WHERE r.ACTIVITY_RULE_ID = :activity_rule_id ORDER BY r.RULE_PRIORITY.
• Security-scoped extraction: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the caller's permitted security groups.
• Organization-scoped reporting: filter on ORGANIZATION_ID to isolate rules belonging to a specific operating unit.
• Flexfield reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 to surface customer-defined rule attributes.

These patterns support audit reporting, rule migration between environments, and troubleshooting of web management behavior.

Related Objects

Based on documented foreign key and dependency metadata, the most significant related objects are:

• AMS_ACT_WEB_RULE_TYPES — referenced through ACTIVITY_RULE_ID; classifies each web rule by activity type.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; enforces security group access control.
• AMS_WEB_RULES_TL — the translation table (by convention) holding language-specific rule names and descriptions keyed to RULE_ID.
• AMS_WEB_RULES_B_U1 — the unique index on RULE_ID, serving as the documented business-key candidate.
• AWB_PK1 — the primary key constraint on RULE_ID.