Results for “comparison_operator_code”

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

Overview

The AMS_FORECAST_DIMENTIONS table belongs to the Oracle Marketing (AMS) application within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its documented purpose is to store all the dimensions defined for an object, meaning it holds the qualifying criteria that describe how a forecast, target, or similar marketing object is segmented and evaluated. Each row identifies an object by type and identifier, and then records one attribute-based dimension — a column, a value, a range, and a comparison operator — that constrains or defines that object.

The table is owned by the AMS schema and contains 18 documented columns in the 12.1.1 physical schema. The ETRM metadata notes that the object is "Not implemented in this database" for the originating environment; this reflects the source database state and should not be read as a functional limitation, since AMS implementations that use forecast dimensions will carry the table in their own instance. The heuristic Data Vault classification mined from the foreign-key structure is standalone — a modeling suggestion that the table is not a classical hub-and-link participant but rather a self-contained attribute-holding structure anchored by a single surrogate key.

Key Information Stored

The primary key is AMS_FORECAST_DIMENTIONS_PK, defined on the single column FORECAST_DIMENTION_ID. This surrogate identifier is the only documented unique key and is the basis for joins; no separate business-key unique index is documented.

• OBJ_TYPE and OBJ_ID — identify the parent object to which the dimension belongs, forming the principal business-key candidate pairing in the absence of a documented unique index.
• PRODUCT_ATTRIBUTE_CONTEXT and PRODUCT_ATTRIBUTE — the descriptive flexfield context and attribute name used on the product side of the dimension.
• PRODUCT_ATTR_VALUE — the value the product attribute is matched against.
• QUALIFIER_GROUPING_NO — groups related qualifier conditions into a logical set, allowing multiple criteria to be combined.
• QUALIFIER_CONTEXT and QUALIFIER_ATTRIBUTE — the flexfield context and attribute name on the qualifier side.
• QUALIFIER_ATTR_VALUE and QUALIFIER_ATTR_VALUE_TO — the lower and upper bound of the qualifier, supporting range-based dimensions when both are populated.
• COMPARISON_OPERATOR_CODE — the operator (for example equals, between, greater than) applied when evaluating the dimension.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing Oracle EBS multi-org and function security partitioning of the record.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit Who columns recording insert and update identity.

Common Use Cases and Queries

Typical usage is resolving the dimensions attached to a marketing or forecast object in order to reproduce its segmentation logic, or auditing which attributes and operators drive a forecast. A representative query retrieves all dimensions for one object and orders them by grouping:

• SELECT forecast_dimention_id, obj_type, obj_id, product_attribute, product_attr_value, qualifier_attribute, comparison_operator_code FROM ams.ams_forecast_dimentions WHERE obj_type = :p_obj_type AND obj_id = :p_obj_id ORDER BY qualifier_grouping_no;
• Reporting by operator to understand distribution of comparison logic: SELECT comparison_operator_code, COUNT(*) FROM ams.ams_forecast_dimentions GROUP BY comparison_operator_code;
• Range analysis: SELECT * FROM ams.ams_forecast_dimentions WHERE qualifier_attr_value_to IS NOT NULL;
• Security-based filtering joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to restrict rows to the current responsibility's permitted security groups.

Related Objects

The following objects are the most significant for joins and dependency analysis:

• FND_SECURITY_GROUPS — referenced through AMS_FORECAST_DIMENTIONS.SECURITY_GROUP_ID, providing the security group definition used to partition dimension rows.
• AMS_FORECAST_DIMENTIONS_PK — the primary-key constraint on FORECAST_DIMENTION_ID, used for direct lookups.
• Parent AMS forecast and marketing objects — referenced indirectly through OBJ_TYPE and OBJ_ID rather than a declared foreign key; joins to forecast header tables must be built on this pair.
• Product and qualifier flexfield definition tables — the contexts and attributes named in PRODUCT_ATTRIBUTE_CONTEXT, PRODUCT_ATTRIBUTE, QUALIFIER_CONTEXT, and QUALIFIER_ATTRIBUTE resolve against the relevant descriptive flexfield metadata.
• AMS API layer — marketing forecast and target APIs read and write dimensions on behalf of the object, and are the supported integration path in place of direct DML.