Results for “csi_counter_relationships_u01”

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

Overview

CSI.CSI_COUNTER_RELATIONSHIPS is a transactional table in the Oracle EBS Customer Intelligence (CSI) schema that stores the relationships between counters used within Enterprise Asset Management and related counter-based metering processes. A counter in Oracle EBS represents a measurable device or logical point that accumulates readings, such as an odometer, run-hour meter, or production counter. CSI_COUNTER_RELATIONSHIPS captures how one counter relates to another through either a Formula relationship or a Configuration relationship. A Formula relationship is derived from one or more regular counters and stores formula text that references those counters to compute the resulting reading. A Configuration relationship represents a hierarchical Source-to-Target structure, commonly used for trickle-down meters, where the target is based on a single regular source counter.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is registered with FND Design Data as CSI.CSI_COUNTER_RELATIONSHIPS. The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table is modeled as an independent entity rather than a hub, link, or satellite, though it can be treated as a link during dimensional modeling because it associates source and object counters. Its status is VALID in both 12.1.1 and 12.2.2 releases.

Key Information Stored

The table contains 33 columns. The most significant are:

• RELATIONSHIP_ID — auto-generated internal primary key; the surrogate key of the table, enforced by the unique index CSI_COUNTER_RELATIONSHIPS_U01, which is the documented business-key candidate.
• CTR_ASSOCIATION_ID — identifier of the counter association to which the relationship belongs.
• RELATIONSHIP_TYPE_CODE — indicates whether the row is a Formula or Configuration relationship.
• SOURCE_COUNTER_ID — the source counter in a Source-to-Target configuration.
• OBJECT_COUNTER_ID — the target or object counter produced by the relationship.
• BIND_VARIABLE_NAME — variable name used when the relationship is formula-based.
• FACTOR — numeric multiplier applied when computing the resulting counter reading.
• ACTIVE_START_DATE and ACTIVE_END_DATE — date range during which the relationship is active.
• SECURITY_GROUP_ID — security group identifier; foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — standard descriptive flexfield columns.
• MIGRATED_FLAG — indicator of migration status for the row.

Common Use Cases and Queries

Typical uses include validating counter hierarchies, tracing trickle-down meter configurations, and auditing formula-based derivations of readings. A query to retrieve all relationships for a given object counter:

• SELECT relationship_id, relationship_type_code, source_counter_id, object_counter_id, factor FROM csi.csi_counter_relationships WHERE object_counter_id = :object_counter_id AND SYSDATE BETWEEN NVL(active_start_date, SYSDATE) AND NVL(active_end_date, SYSDATE);

To find all Formula relationships for a source counter, filter on RELATIONSHIP_TYPE_CODE = 'FORMULA'. Reporting use cases include meter reconciliation, derivation of rolled-up readings, and validation of configuration graphs before running counter calculation programs.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce row-level security.
• CSI_COUNTERS — referenced via SOURCE_COUNTER_ID and OBJECT_COUNTER_ID.
• CSI_COUNTER_ASSOCIATIONS — related through CTR_ASSOCIATION_ID.
• CSI_COUNTER_READINGS — consumed during formula and configuration computation.
• CSI_COUNTER_RELATIONSHIPS_U01 — unique index supporting primary-key access.
• CSI_COUNTER_RELATIONSHIPS_N01 / _N02 — nonunique indexes supporting lookups by OBJECT_COUNTER_ID with RELATIONSHIP_TYPE_CODE and by SOURCE_COUNTER_ID respectively.