Search Results instance_association_id

Overview

CSI_COUNTER_ASSOCIATIONS_V is an Oracle E-Business Suite view owned by the APPS schema within the CSI (Install Base) product module. It exposes counter instance associations, providing a reporting and integration layer over the counter association data maintained by Install Base. Counters in Oracle EBS represent meters or measurement devices attached to an installed asset, and a counter association links a counter to the object against which its readings are tracked. Because the view carries a ROWID-less, join-free projection of the underlying entity, it is a convenient, read-only access point for extracts, concurrent programs, Oracle Discoverer workbooks, and third-party integrations that must resolve which counter is associated with which source object over a defined validity period.

The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The user search term "migrated_flag" maps directly to the MIGRATED_FLAG column, which is exposed unchanged from the base table and is commonly used to distinguish records that originated from a data migration or upgrade activity from those created natively within the Install Base application.

Underlying Base Objects

The view is defined exclusively over the single base object CSI_COUNTER_ASSOCIATIONS, referenced through a SYNONYM. The definition is a straight column-projection SELECT with no joins, filters, or computed expressions: each column of the view is mapped one-to-one to a column of the base table. As a result, the view adds no transformation logic and no row-level restriction — its cardinality and content mirror the base table exactly.

The documented base object reference is:

• CSI_COUNTER_ASSOCIATIONS (SYNONYM)

Because it is a simple projection, the view cannot be used for DML in the same manner as a key-preserved single-table view accessed directly; the underlying table should be the target of any association maintenance performed by the application or by controlled data-load routines.

Key Columns

• INSTANCE_ASSOCIATION_ID — Primary identifier for the counter instance association record.
• SOURCE_OBJECT_CODE and SOURCE_OBJECT_ID — Identify the business object (and its primary key) to which the counter is associated, such as an instance, item, or party.
• COUNTER_ID — The counter definition associated with the source object.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Define the effective date range during which the association is active; support historical and as-of-date reporting.
• MIGRATED_FLAG — Indicates whether the association was introduced by a migration or conversion process rather than transactionally within Install Base.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who columns for audit and lineage.
• SECURITY_GROUP_ID — Legacy multi-organization security column retained for compatibility.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segments available for customer-specific extensions.

Common Use Cases and Queries

Typical usage includes inventorying counters attached to a given installed base object, validating migration loads, and feeding downstream metering or billing processes. The following query lists active associations for a specific counter:

• SELECT instance_association_id, source_object_code, source_object_id, counter_id, start_date_active, end_date_active, migrated_flag FROM csi_counter_associations_v WHERE counter_id = :p_counter_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

To identify migrated records for reconciliation after an upgrade:

• SELECT instance_association_id, source_object_id, counter_id, creation_date FROM csi_counter_associations_v WHERE migrated_flag = 'Y' ORDER BY creation_date;

Because the view is a direct projection of CSI_COUNTER_ASSOCIATIONS, queries against it should be tuned with the same indexing and filtering strategy applied to the base table, and date-bounded predicates on START_DATE_ACTIVE and END_DATE_ACTIVE are recommended for performance and correctness.