Results for “amv_d_attrib_operators”

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

Overview

AMV_D_ATTRIB_OPERATORS is a table within the AMV schema, belonging to the Marketing Encyclopedia System (also referenced as Oracle Marketing) product family in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table stores the relationship between a specific attribute defined within an entity and the operators that may legitimately be applied to that attribute. In effect, it is the metadata registry that drives rule condition authoring: before a rule condition can compare an attribute against a value, the combination of attribute and operator must exist as a valid row in this table. This design lets the application constrain, validate, and expose only meaningful operators (for example, equals, greater than, contains, or between) for a given attribute, depending on the attribute's data type and behavioral semantics.

ETRM's heuristic Data Vault classification identifies this object as satellite-leaning. Read as a modeling suggestion rather than a physical fact, this implies the table is best understood as a descriptive, attribute-bearing structure that qualifies a parent business key (ATTRIBUTE_ID) with contextual detail (permitted operator types), rather than acting as a pure hub of independent identities or a link between two hubs. The surrogate key ATTRIBUTE_OPERATOR_ID anchors each row, while the pairing of ATTRIBUTE_ID and OPERATOR_TYPE carries the business meaning.

Key Information Stored

The table comprises fourteen documented columns. The most significant are:

• ATTRIBUTE_OPERATOR_ID — the surrogate primary key, enforced by AMV_D_ATTRIB_OPERATORS_PK and also supported by the unique index AMV_D_ATTRIB_OPERATORS_U1. This is the identifier most users search for when cross-referencing rule condition definitions.
• ATTRIBUTE_ID — foreign key to the parent attribute definition; identifies which attribute the operator applies to.
• OPERATOR_TYPE — the operator code made available for the attribute, forming the second component of the business-key unique index AMV_D_ATTRIB_OPERATORS_U2.
• STATUS — the record's lifecycle state, controlling whether the attribute/operator pairing is active.
• USAGE_INDICATOR — a flag indicating whether the pairing is intended for use, typically governing presentation in rule-builder interfaces.
• SIMPLE_COUNT and COMPLEX_COUNT — counters reflecting the number of simple versus complex usages of the pairing.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization and access-control partitioning.
• Standard WHO/audit columns — OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — which provide concurrency control and auditability.

The distinction between the surrogate primary key and the business keys is important: ATTRIBUTE_OPERATOR_ID is the technical handle, while the unique combination of ATTRIBUTE_ID and OPERATOR_TYPE is the natural key that prevents duplicate operator definitions for the same attribute.

Common Use Cases and Queries

Typical uses include validating whether a rule condition references a legal attribute/operator pairing, reporting on operator coverage per attribute, and diagnosing rule-builder behavior where operators fail to appear. A representative query to enumerate valid operators for an attribute is:

• SELECT attribute_operator_id, operator_type, status, usage_indicator FROM amv.amv_d_attrib_operators WHERE attribute_id = :attribute_id AND status = 'A';

A second common pattern joins back to rule conditions to confirm that conditions reference documented pairings:

• SELECT rc.attribute_id, rc.operator_type, ao.attribute_operator_id FROM amv.amv_d_rule_conditions rc, amv.amv_d_attrib_operators ao WHERE rc.attribute_id = ao.attribute_id AND rc.operator_type = ao.operator_type;

Reporting scenarios frequently aggregate usage, for example listing attributes by their permitted operator count using SIMPLE_COUNT and COMPLEX_COUNT to gauge configuration complexity.

Related Objects

The most significant related objects and their join columns are:

• AMV_D_RULE_CONDITIONS — the dependent table; joins on ATTRIBUTE_ID and OPERATOR_TYPE. This is the primary consumer of the operator registry, as conditions can only use operators defined here.
• AMV_D_ATTRIB_OPERATORS and AMV_D_RULE_CONDITIONS shared FK — documented as the FOREIGN KEY linking AMV_D_ATTRIB_OPERATORS.ATTRIBUTE_ID to AMV_D_RULE_CONDITIONS.ATTRIBUTE_ID and .OPERATOR_TYPE.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for access partitioning.
• The parent attribute definition referenced by ATTRIBUTE_ID (shown as “%” in the mined relationship data, indicating an unresolved or generic parent reference), which supplies the attribute's own metadata.

Together these objects form the metadata backbone that lets Oracle Marketing rule definitions be validated, constrained, and audited consistently across EBS releases.