Search Results range_low_value




Overview
Explore in AI Chat

Overview

AMV_D_ENT_ATTRIBUTES_B is the base table within the AMV (Marketing Encyclopedia System) product schema that stores every attribute belonging to an entity in the Marketing Encyclopedia data model. In Oracle EBS 12.1.1 and 12.2.2, AMV supports the definition, cataloging, and retrieval of marketing content and structured product information. An "attribute" here represents a discrete, addressable property of an entity — a field or characteristic that can be referenced by rule conditions or by the search engine. The table therefore functions as the metadata registry that tells the AMV engine which properties exist for each entity and how each property may be used, validated, and searched.

From a heuristic Data Vault modeling perspective, the table leans toward a satellite classification. Its primary key, ATTRIBUTE_ID, is a surrogate identifier, and the table carries a foreign key to AMV_D_ENTITIES_B through ENTITY_ID, which supplies the parent entity context. Descriptive and behavioral properties of the attribute (data type, status, usage, validation rules) are stored alongside that key, which is characteristic of satellite-style descriptive storage rather than a pure hub or link.

Key Information Stored

The documented physical schema contains 18 columns. The most operationally significant are:

A unique index, AMV_D_ENT_ATTRIBUTES_B_U1, is defined over (ATTRIBUTE_ID, ZD_EDITION_NAME). Because it leads with the surrogate ATTRIBUTE_ID rather than distinctive business columns, it functions primarily as a uniqueness constraint supporting the editioning model rather than a true business-key candidate; the surrogate key remains the authoritative identifier.

Common Use Cases and Queries

Typical use cases include enumerating all attributes for an entity prior to building rule conditions, verifying which attributes are search-enabled, auditing validation configuration, and reconciling base records with their translated counterparts.

  • Attributes for a given entity: SELECT ATTRIBUTE_ID, COLUMN_NAME, DATA_TYPE, STATUS, USAGE_INDICATOR FROM AMV.AMV_D_ENT_ATTRIBUTES_B WHERE ENTITY_ID = :entity_id ORDER BY ATTRIBUTE_ID;
  • Search-enabled attributes only: filter on USAGE_INDICATOR to isolate attributes exposed to the search engine.
  • Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to produce attribute inventories per security group.
  • Validation audit: select VALIDATION_TYPE, RANGE_LOW_VALUE, RANGE_HIGH_VALUE, and FUNCTION_CALL for attributes using custom or range validation.

Reporting most often joins this base table to the translated table and to the entity table to resolve a human-readable entity name and attribute label.

Related Objects

  • AMV_D_ENTITIES_B — parent entity table, joined via AMV_D_ENT_ATTRIBUTES_B.ENTITY_ID → AMV_D_ENTITIES_B.
  • AMV_D_ENT_ATTRIBUTES_TL — translation table holding language-specific attribute text, joined via ATTRIBUTE_ID.
  • FND_SECURITY_GROUPS — security group reference for SECURITY_GROUP_ID.
  • AMV_D_ENT_ATTRIBUTES_B_PK — primary key constraint/index on ATTRIBUTE_ID.
  • AMV_D_ENT_ATTRIBUTES_B_U1 — unique index on (ATTRIBUTE_ID, ZD_EDITION_NAME).

These relationships establish AMV_D_ENT_ATTRIBUTES_B as the central attribute registry that rule, search, and validated-content processing within AMV depend upon.