Results for “ams_web_recomms_u1”

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

Overview

AMS_WEB_RECOMMS is a transactional table owned by the AMS schema within the Oracle E-Business Suite Marketing (AMS) module. Per the ETRM 12.1.1 / 12.2.2 documentation, it is used to store tracking data for web dynamic schedules — specifically the recommendations rendered to web visitors through Oracle Marketing's dynamic content and recommendation engine. Each row represents a single recommendation event tied to an offer, a web tracking record, and a recommendation rule.

The table is classified as VALID and contains 30 documented columns. The metadata's heuristic Data Vault classification identifies this as a standalone object. In modeling terms, this suggests AMS_WEB_RECOMMS behaves as a satellite-like entity attached to the web tracking hub, carrying descriptive and dimensional attributes about each recommendation rather than serving as a pure hub or link. That classification should be treated as a modeling suggestion rather than a hard architectural constraint.

Key Information Stored

The surrogate primary key is WEB_RECOMM_ID, constrained by the unique index AMS_WEB_RECOMMS_U1 and the primary key constraint AWRC_PK. This column uniquely identifies each recommendation record and is the business-key candidate documented in the ETRM metadata. Other significant columns include:

• WEB_TRACKING_ID — foreign key to AMS_WEB_TRACKING; associates the recommendation with the originating web tracking session or event.
• OFFER_ID — references the marketing offer being recommended, linking to the AMS offer entity.
• OFFER_SRC_CODE — identifies the source system or channel from which the offer was retrieved.
• RECOMM_OBJECT_ID — the identifier of the recommended object (offer, product, or content payload).
• RECOMM_TYPE — classifies the recommendation, distinguishing offer-based, rule-driven, or content recommendations.
• RULE_ID — identifies the recommendation rule that produced the record, enabling effectiveness analysis of specific rules.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / MLS data security.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• Standard who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) segment columns for extensibility.

Common Use Cases and Queries

The primary reporting use case is measuring the effectiveness of web recommendation rules and offers. Analysts join this table to AMS_WEB_TRACKING to correlate impressions and clicks with the specific recommendations served. A typical query pattern follows:

• Recommendation volume by rule: SELECT RULE_ID, COUNT(*) FROM AMS.AMS_WEB_RECOMMS GROUP BY RULE_ID.
• Recommendations joined to tracking sessions on WEB_TRACKING_ID to evaluate conversion behavior.
• Offer-level funnel analysis filtering on OFFER_ID and OFFER_SRC_CODE.
• Recommendation-type segmentation using RECOMM_TYPE for A/B or rule-variant performance reporting.
• Extensibility reporting through the ATTRIBUTE* DFF columns where clients capture custom tracking metadata.

Because the table is append-heavy and tied to web activity, queries should filter on CREATION_DATE or WEB_TRACKING_ID to restrict result sets.

Related Objects

• AMS.AMS_WEB_TRACKING — joined on WEB_TRACKING_ID; the parent tracking record for the recommendation.
• FND.FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; enforces access control.
• AMS offer entities keyed via OFFER_ID (e.g., AMS_OFFERS).
• Recommendation rule definitions referenced through RULE_ID, typically within the AMS rulebase tables.
• Dynamic schedule and web personalization entities in AMS that consume the runtime output.