Search Results source_counter_name

Overview

CSI_CTR_RELATIONSHIPS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. The view exposes the counter relationship data model used by Oracle Install Base to describe how one counter relates to another counter within an asset or item instance. In ETRM terms it is documented as a "Counter relationships view," and its status is VALID across the 12.1.1 and 12.2.2 application releases.

Counters in Install Base represent measurable or tracked attributes of an instance — meter readings, usage accumulators, or derived values. A counter relationship defines how a source counter maps to an object counter, including the relationship type (for example, a rollup, offset, or dependency), an optional bind variable name used in formula evaluation, and a numeric factor applied during computation. The view flattens this configuration data and augments it with the human-readable counter names, making it suitable for reporting, data extraction, and integration without requiring joins to the counter name table. Because it presents denormalized, descriptive data, it is commonly consumed by BI Publisher reports, Oracle Discoverer/OBIEE extracts, and downstream interfaces that need to resolve counter IDs into meaningful labels.

Underlying Base Objects

The view is defined over three documented objects: CSI_COUNTER_RELATIONSHIPS (referenced through a SYNONYM), and two aliased instances of CSI_COUNTERS_VL (a VIEW). The primary driver is CSI_COUNTER_RELATIONSHIPS, aliased CCR, which supplies the relationship definition rows and the audit and descriptive attribute columns.

The join to CSI_COUNTERS_VL is performed twice, using aliases CCV and CCV2, to resolve the counter names. The join predicate is CCR.SOURCE_COUNTER_ID = CCV.COUNTER_ID AND CCR.OBJECT_COUNTER_ID = CCV2.COUNTER_ID. This means both the source counter and the object counter referenced by each relationship must exist in CSI_COUNTERS_VL, which is the translatable (_VL) view presenting counter names in the current language. Note that the view text applies an inner join, so relationships whose source or object counter is not present in the counter master view will be excluded from the result set. The view does not itself store data; it is a read-only projection used for querying and reporting.

Key Columns

• RELATIONSHIP_ID — Primary identifier of the counter relationship definition.
• CTR_ASSOCIATION_ID — Identifier of the associated counter association to which the relationship belongs.
• RELATIONSHIP_TYPE_CODE — Code describing the nature of the relationship between the two counters.
• SOURCE_COUNTER_ID / SOURCE_COUNTER_NAME — The originating counter's identifier and its resolved display name.
• OBJECT_COUNTER_ID / OBJECT_COUNTER_NAME — The target counter's identifier and its resolved display name. This is the column users typically search for when querying "object_counter_id".
• BIND_VARIABLE_NAME — Name of the bind variable used when the relationship participates in a formula or expression.
• FACTOR — Numeric multiplier applied when computing the object counter from the source counter.
• ACTIVE_START_DATE / ACTIVE_END_DATE — Validity window controlling when the relationship is in effect.
• Standard EBS columns: SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15, and MIGRATED_FLAG.

Common Use Cases and Queries

The view is queried to audit counter configuration, validate relationship definitions before migration, and support extracts that must resolve object counter IDs to names. A typical query filters by object counter ID:

SELECT relationship_id, source_counter_id, source_counter_name, object_counter_id, object_counter_name, factor FROM csi_ctr_relationships_v WHERE object_counter_id = :p_object_counter_id;

To list all relationships that are currently active:

SELECT relationship_id, relationship_type_code, source_counter_name, object_counter_name, factor FROM csi_ctr_relationships_v WHERE TRUNC(SYSDATE) BETWEEN active_start_date AND NVL(active_end_date, TO_DATE('4712-12-31','YYYY-MM-DD'));

Because the view already exposes both counter names, reports avoid additional joins, making it the preferred source for counter-relationship reporting in Oracle Install Base.