Search Results amv_c_item_types_u2

Overview

AMV.AMV_C_ITEM_TYPES is a seed configuration table that stores the item types associated with a specific channel in the Oracle E-Business Suite Channel Management and item publishing infrastructure. The table maps item types to channels, and where such a mapping exists, the item type can participate in matching criteria that determine whether information is published to that channel. Its role is therefore provisioning and filtering: it defines which kinds of items belong to a channel and constrains the candidate set used during channel subscription and matching processing.

The table resides in the AMV schema in the APPS_TS_SEED tablespace, with a PCTFREE of 10 and status VALID. Because it holds relatively static reference and matching seed data rather than transactional records, its DML volume is low. The heuristic Data Vault classification for this object is satellite-leaning; from a modeling perspective it is best treated as a satellite describing the channel-to-item-type relationship, with CHANNEL_ITEM_TYPE_ID serving as the surrogate key and (CHANNEL_ID, ITEM_TYPE) acting as the natural business key within the AMV schema.

Key Information Stored

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

• CHANNEL_ITEM_TYPE_ID (NUMBER) — Surrogate primary key, enforced by the unique index AMV_C_ITEM_TYPES_U1 and by AMV_C_ITEM_TYPES_PK. Uniquely identifies each channel/item-type association.
• CHANNEL_ID (NUMBER) — Channel identifier; foreign key to AMV_C_CHANNELS_B. Determines which channel the item type is associated with.
• ITEM_TYPE (VARCHAR2, 30) — The item type value; the second component of the natural business key. Also indexed non-uniquely by AMV_C_ITEM_TYPES_N1.
• SECURITY_GROUP_ID (NUMBER) — Foreign key to FND_SECURITY_GROUPS; used in hosted environments to partition data by security group.
• OBJECT_VERSION_NUMBER (NUMBER) — Used for locking purposes to support optimistic concurrency control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns recording creation and last-update audit information.

The uniqueness of (CHANNEL_ID, ITEM_TYPE) via AMV_C_ITEM_TYPES_U2 guarantees that a given item type can be associated with a channel only once.

Common Use Cases and Queries

Typical uses include listing item types eligible for publication to a channel, validating that a candidate item type is permitted before channel matching, and reporting on channel configuration coverage. A common query retrieves the item types configured for a given channel:

• SELECT CHANNEL_ID, ITEM_TYPE FROM AMV.AMV_C_ITEM_TYPES WHERE CHANNEL_ID = :p_channel_id; — drives matching eligibility lookups.
• SELECT a.CHANNEL_ID, a.ITEM_TYPE FROM AMV.AMV_C_ITEM_TYPES a WHERE a.ITEM_TYPE = :p_item_type; — leverages AMV_C_ITEM_TYPES_N1 for reverse lookup by item type.
• Reporting queries joining to AMV_C_CHANNELS_B for channel names to produce channel configuration reports.
• Union or EXISTS subqueries in publication decision logic to confirm an item type satisfies matching criteria.

Because the data is seed-oriented, queries are generally read-only and perform best using the unique and non-unique indexes described above.

Related Objects

The following objects are most significant in relation to AMV_C_ITEM_TYPES:

• AMV.AMV_C_CHANNELS_B — Referenced by CHANNEL_ID; the parent channel definition table.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; enforces hosted-environment data partitioning.
• AMV.AMV_C_ITEM_TYPES# — The underlying editioning object referenced by this table in an EBS 12.2 online patching context.
• AMV_C_ITEM_TYPES_PK, AMV_C_ITEM_TYPES_U1, AMV_C_ITEM_TYPES_U2, AMV_C_ITEM_TYPES_N1 — Primary key and supporting indexes (business-key and item-type lookups).
• Channel matching and publication routines within the AMV module that consume this table to evaluate whether information should be published to a channel.

The table references only AMV_C_CHANNELS_B and FND_SECURITY_GROUPS; no further outgoing dependencies are documented, which underscores its narrow, configuration-focused role.