Search Results csi_counter_groups_bcv_v




Overview
Explore in AI Chat

Overview

CSI_COUNTER_GROUPS_BCV_V is a backward compatibility view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. The view is documented in ETRM as a "backward compatible view for CS_COUNTER_GROUPS_V," indicating that it exists to preserve the interface expected by older customizations, integrations, and reports while Oracle's internal model evolved around a differently named base object. In both 12.1.1 and 12.2.2, the object carries a VALID status and a stable column list, making it a reliable access point for counter group data.

The view presents the metadata and configuration attributes of counter groups — reusable definitions used by Oracle Install Base to govern how counters (meter readings) are collected, validated, and associated with installed base instances and items. Because counter groups form the foundation for tracking usage-based service and warranty information, the view is frequently consumed by reporting layers and by custom interfaces that need to read group definitions without depending on the current internal view name.

Underlying Base Objects

Per the ETRM documentation, CSI_COUNTER_GROUPS_BCV_V is defined over exactly one referenced base object: the view CSI_COUNTER_GROUPS_BC_V. The definition is a direct projection — each of the thirty-one columns in the outer view is a straight pass-through of the identically named column in the inner view, with no joins, filters, expressions, or derivations applied. The documented view text confirms this pattern: for every column, the SELECT list maps the source column to a column of the same name, sourced from CSI_COUNTER_GROUPS_BC_V.

The "_BCV_" naming convention (Backward Compatibility View) signals that this object is a compatibility shim rather than a primary data container. It does not itself own or store rows; all data is materialized through the underlying view, which in turn resolves ultimately to the counter group base tables maintained by CSI. Consequently, the view inherits the security, indexing, and performance characteristics of its base object, and the documented dependency chain records only CSI_COUNTER_GROUPS_BC_V as the referenced base object.

Key Columns

  • COUNTER_GROUP_ID — Primary identifier for the counter group; the standard key used when joining to other CSI counter objects.
  • NAME — The user-defined name of the counter group, typically the value displayed in lists of values and reports.
  • DESCRIPTION — Free-text description of the group's purpose.
  • TEMPLATE_FLAG — The column most commonly targeted in searches for this view. It distinguishes groups used as templates (from which other groups are instantiated) from ordinary, operational counter groups.
  • CREATED_FROM_CTR_GRP_TMPL_ID — Identifies the template group from which a given group was created, supporting traceability between templates and their instances.
  • SOURCE_OBJECT_CODE / SOURCE_OBJECT_ID / SOURCE_COUNTER_GROUP_ID — Describe the originating object and source group when a counter group is copied or derived.
  • ASSOCIATION_TYPE — Indicates the nature of the group's association within Install Base.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range governing when the group is active.
  • ATTRIBUTE1–ATTRIBUTE15 and CONTEXT — The standard Oracle descriptive flexfield segment columns and context, allowing extensible customer-defined attributes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard auditing and optimistic-locking columns present on most EBS transactional entities.

Common Use Cases and Queries

The most frequent use case, given the "template_flag" search, is identifying which counter groups serve as templates versus operational groups. The following query retrieves all template-designated groups:

  • SELECT counter_group_id, name, description, template_flag FROM apps.csi_counter_groups_bcv_v WHERE template_flag = 'Y';

A second common scenario is resolving the origin of a group back to its template:

  • SELECT cg.name, cg.template_flag, cg.created_from_ctr_grp_tmpl_id, t.name template_name FROM apps.csi_counter_groups_bcv_v cg, apps.csi_counter_groups_bcv_v t WHERE cg.created_from_ctr_grp_tmpl_id = t.counter_group_id;

Because the view exposes descriptive flexfield columns, a third use case is extracting customer-specific attributes for integration extracts:

  • SELECT counter_group_id, name, template_flag, context, attribute1, attribute2 FROM apps.csi_counter_groups_bcv_v WHERE context IS NOT NULL;

Finally, active-group listings filtered on the effective date range are typical for operational reporting:

  • SELECT counter_group_id, name, start_date_active, end_date_active FROM apps.csi_counter_groups_bcv_v WHERE template_flag = 'N' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

In all cases, queries should be qualified with the APPS schema and observe the standard EBS multi-org and security conventions applicable to the CSI module.