Results for “amv_d_entities_b”

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

Overview

AMV_D_ENTITIES_B is the base table of the Marketing Encyclopedia System (AMV) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all database tables that may participate in a rule condition or search engine evaluation within the AMV framework, effectively functioning as a registry of "entities" (source tables) that the rules and search infrastructure is permitted to interrogate. Each row describes one such entity together with its owning application, its physical table name, and its operational status.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. The single-column primary key AMV_D_ENTITIES_B_PK on ENTITY_ID behaves as a durable business key that anchors a distinct entity concept, while descriptive and contextual attributes such as STATUS and USAGE_INDICATOR act like satellite-style metadata. Downstream tables (AMV_D_ENTITIES_TL and AMV_D_ENT_ATTRIBUTES_B) reference this hub to record translated names and attribute definitions respectively.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• ENTITY_ID — surrogate primary key, uniquely identifying each registered entity.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• APPLICATION_ID — foreign key to FND_APPLICATION, indicating which EBS application owns the entity.
• TABLE_NAME — the physical base table that the entity represents and that rules or the search engine will query.
• STATUS — lifecycle state of the entity record (e.g., active/inactive).
• USAGE_INDICATOR — flag controlling whether the entity is eligible for rule conditions and search.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, partitioning data for multi-org / security access.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ZD_EDITION_NAME — editioning column supporting the online patching / edition-based redefinition model introduced in 12.2.

The unique index AMV_D_ENTITIES_B_U1 on (ENTITY_ID, ZD_EDITION_NAME) is the main business-key candidate, combining the surrogate identifier with the edition marker.

Common Use Cases and Queries

Typical usage spans rules configuration, search engine setup, and reporting on available entities. To retrieve all active entities owned by a particular application:

• Entity listing: SELECT ENTITY_ID, TABLE_NAME, APPLICATION_ID FROM AMV_D_ENTITIES_B WHERE STATUS = 'A';
• Security-scoped lookup: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to filter by operating unit.
• Translation join: join AMV_D_ENTITIES_TL on ENTITY_ID to obtain language-specific display names.
• Attribute expansion: join AMV_D_ENT_ATTRIBUTES_B on ENTITY_ID to enumerate the columns available for rule construction.

Reporting use cases include auditing which tables the AMV rule engine can reference, verifying USAGE_INDICATOR coverage, and troubleshooting missing entities in the search index.

Related Objects

The following objects are the most significant dependencies, sourced from documented foreign-key relationships:

• FND_APPLICATION — referenced via APPLICATION_ID; identifies the owning application.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data security partitioning.
• AMV_D_ENTITIES_TL — references AMV_D_ENTITIES_B.ENTITY_ID; holds translated entity names.
• AMV_D_ENT_ATTRIBUTES_B — references AMV_D_ENTITIES_B.ENTITY_ID; stores attributes of each entity.
• AMV_D_ENTITIES_B_PK — primary key constraint on ENTITY_ID.
• AMV_D_ENTITIES_B_U1 — unique index on (ENTITY_ID, ZD_EDITION_NAME).

Together these objects form the metadata backbone that supports AMV rule conditions and the Marketing Encyclopedia System search engine across both 12.1.1 and 12.2.2.