Results for “csi_ctr_item_associations”

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

Overview

The CSI_CTR_ITEM_ASSOCIATIONS table resides in the CSI (Install Base) schema and is a core configuration table within Oracle E-Business Suite's Enterprise Asset Management (EAM) and Install Base counter functionality. Its documented purpose is to hold counter item associations data—specifically, the relationships that define which meters (counters) are associated with which inventory items, and how those counters are consumed for maintenance and usage tracking purposes. This table serves as the bridge between the item master definition and the physical counter/meter readings captured against installed assets, enabling preventive maintenance scheduling, usage-based maintenance triggers, and failure analysis tied to consumption thresholds.

Based on the FK structure mined from the metadata, the heuristic Data Vault classification for this table is standalone. Rather than functioning as a pure hub, link, or satellite, the table holds its own descriptive and association attributes with a direct FK to FND_SECURITY_GROUPS for row-level security. Modelers treating this as a Data Vault artifact would likely position it as a link-style entity joining items to counters, though the presence of several descriptive and control columns (usage rate, flags, active dates) gives it satellite-like characteristics as well.

Key Information Stored

The table contains 35 documented columns. The most significant for functional and reporting purposes are:

• CTR_ASSOCIATION_ID — the surrogate primary key, enforced by CSI_CTR_ITEM_ASSOCIATION_PK, and also the sole unique business-key candidate via index CSI_CTR_ITEM_ASSOCIATIONS_U01.
• INVENTORY_ITEM_ID — the item being tracked.
• COUNTER_ID — the counter/meter associated with that item.
• GROUP_ID and ASSOCIATED_TO_GROUP — group-level scoping and whether the association applies across the group.
• USAGE_RATE — the rate at which the counter is consumed or accumulated over time.
• USE_PAST_READING — a control flag governing whether historical counter readings are honored.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window of the association.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing multi-org/security partitioning.
• MAINT_ORGANIZATION_ID — the maintenance organization that owns the association.
• PRIMARY_FAILURE_FLAG and MIGRATED_FLAG — status indicators for failure attribution and data migration state.
• Standard WHO audit columns (LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER) plus ATTRIBUTE1–ATTRIBUTE15 for customer extensibility.

Common Use Cases and Queries

Typical usage centers on identifying which counters apply to a given item and validating that an association is currently active.

• Retrieve active counters for an item:

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

• Security/partition-scoped reporting joined to FND_SECURITY_GROUPS via security_group_id.
• Maintenance organization roll-ups using maint_organization_id to report counters by servicing org.
• Failure analysis filtering where primary_failure_flag = 'Y'.
• Migration auditing where migrated_flag is populated from legacy systems.

Related Objects

• FND_SECURITY_GROUPS — direct FK from SECURITY_GROUP_ID; used for row-level security joins.
• MTL_SYSTEM_ITEMS_B — join on INVENTORY_ITEM_ID to resolve item descriptions.
• CSI_COUNTERS (and CSI counter value tables) — join on COUNTER_ID to reach meter definitions and readings.
• CSI_ITEM_INSTANCES — installed base instance records that consume these item/counter associations.
• CSI_CTR_READINGS or equivalent counter-reading tables — join back to counter_id for usage history.
• EAM maintenance objects — maint_organization_id links to organization definitions driving preventive maintenance.