Results for “csi_ctr_item_associations_u01”

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

Overview

The table CSI.CSI_CTR_ITEM_ASSOCIATIONS is a transactional data store within the Customer Relationship Management (CRM) and Service application family of Oracle E-Business Suite (EBS). It resides in the CSI (Customer Service Intelligence) schema and holds the inventory item information associated with counter templates or counter groups. Counters in EBS represent units of measurement for tracking usage or wear on an asset. When an inventory item—whether designated as 'Trackable' or 'Serviceable'—is associated with a counter template or counter group, and that item is subsequently instantiated in Install Base or Service Contracts, the counters defined in this table are triggered or instantiated against the associated asset.

The Data Vault classification heuristic mined from the foreign key structure identifies this table as standalone. In practical Data Vault modeling terms, the table can be considered a link object. It links or associates an inventory item to a counter and, in some cases, to a counter group, effectively representing a relationship between master data entities. The presence of a surrogate primary key, standard WHO columns, and object version number further supports this classification as a relationship-oriented table rather than a pure hub or satellite.

Key Information Stored

The table contains 35 documented columns. The most operationally significant columns are summarized below.

• CTR_ASSOCIATION_ID — Internally generated surrogate primary key. It is the sole column of the unique index CSI_CTR_ITEM_ASSOCIATIONS_U01, making it the business-key candidate from a database uniqueness perspective. The primary key constraint is CSI_CTR_ITEM_ASSOCIATION_PK.
• GROUP_ID — Identifier of the counter group to which the association belongs.
• INVENTORY_ITEM_ID — Identifier of the inventory item associated with the counter or counter group.
• COUNTER_ID — Identifier of the specific counter with which the association is made.
• USAGE_RATE — Numeric rate that governs how usage is calculated or accrued against the counter.
• USE_PAST_READING — Flag indicating whether a past reading should be considered when evaluating the counter.
• ASSOCIATED_TO_GROUP — Flag indicating whether the record is associated with a counter group as opposed to an individual counter template.
• START_DATE_ACTIVE — Date from which the association becomes active.
• END_DATE_ACTIVE — Date on which the association ceases to be active.
• SECURITY_GROUP_ID — Security group identifier; this column carries a foreign key to FND_SECURITY_GROUPS and enforces data access partitioning.
• OBJECT_VERSION_NUMBER — Used for optimistic locking and concurrent update control.
• MIGRATED_FLAG and MIGRATED-related indicators — Track whether the record was migrated from a prior system.
• MAINT_ORGANIZATION_ID — Identifier of the maintenance organization responsible for the item-counter association.
• PRIMARY_FAILURE_FLAG — Indicates whether the counter is considered the primary failure indicator for the associated item.

The remaining columns consist of standard WHO audit columns, the ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield (DFF) columns, and additional MIGRATED_FLAG related fields. These support auditability, extensibility, and legacy data migration tracking.

Common Use Cases and Queries

EBS developers and functional consultants query CSI_CTR_ITEM_ASSOCIATIONS to determine which counters apply to a given inventory item, to resolve group-level associations, and to drive counter instantiation logic in Install Base and Service Contracts. Typical operational scenarios include:

• Identifying all counters linked to a specific inventory item for usage tracking and preventive maintenance scheduling.
• Distinguishing item-level associations from group-level associations by testing the ASSOCIATED_TO_GROUP flag.
• Determining active associations by filtering records where SYSDATE falls between START_DATE_ACTIVE and END_DATE_ACTIVE.
• Reporting on counters whose usage rate or primary failure flag influences maintenance strategy.

A representative query to retrieve active counters for a given item is:

SELECT ctr_association_id, inventory_item_id, counter_id, usage_rate, start_date_active, end_date_active
FROM csi.csi_ctr_item_associations
WHERE inventory_item_id = :inventory_item_id
AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Because SECURITY_GROUP_ID is mandatory in multi-org security setups, queries are typically joined to FND_SECURITY_GROUPS or filtered by the session's security group context.

Related Objects

• FND_SECURITY_GROUPS — Referenced via the foreign key CSI_CTR_ITEM_ASSOCIATIONS.SECURITY_GROUP_ID. Join on SECURITY_GROUP_ID to enforce security partitioning.
• CSI_COUNTERS / CSI_CTR_TEMPLATES — Master counter and counter template definitions; join via COUNTER_ID.
• CSI_COUNTER_GROUPS — Counter group definitions; join via GROUP_ID.
• MTL_SYSTEM_ITEMS_B — Inventory item master; join via INVENTORY_ITEM_ID to resolve item names, numbers, and trackable/serviceable attributes.
• CS_... (Service Contracts) and CSI_..._INSTANCE tables — Install Base and Service Contracts objects that consume counter associations to instantiate counters at asset creation.
• CSI_CTR_ITEM_ASSOCIATIONS_U01 — Unique index on CTR_ASSOCIATION_ID; used by the optimizer for primary key lookups.
• CSI_CTR_ITEM_ASSOCIATIONS_N01 — Non-unique index on INVENTORY_ITEM_ID, supporting item-driven queries and joins.