Results for “csi_counter_groups_v”

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

Overview

CSI_COUNTER_GROUPS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the CSI (Install Base) product family. Its documented purpose is to expose counter group definitions maintained by the Install Base application. Counter groups are the organising construct through which counters — usage, meter, or measurement definitions attached to installed base instances — are bundled, templated, and reused across parties, items, and instances.

The view is defined as a simple projection over the underlying counter groups table (documented as CS_COUNTER_GROUPS, referenced through the synonym CS_CSI_COUNTER_GROUPS). Rather than applying joins, filters, or aggregations, it presents the columns of that table directly, including descriptive attributes, association metadata, source-object references, and the full set of descriptive flexfield segments (ATTRIBUTE1 through ATTRIBUTE15) and CONTEXT. Because the view preserves the underlying keys without transformation, it is suited to both direct reporting against counter group configuration and integration use cases in which counter groups must be extracted, replicated, or compared across environments.

The columns returned include COUNTER_GROUP_ID, NAME, DESCRIPTION, TEMPLATE_FLAG, CREATED_FROM_CTR_GRP_TMPL_ID, ASSOCIATION_TYPE, SOURCE_OBJECT_CODE, SOURCE_OBJECT_ID, SOURCE_COUNTER_GROUP_ID, plus standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), effective dating columns (START_DATE_ACTIVE, END_DATE_ACTIVE), the attribute flexfield columns, CONTEXT, and OBJECT_VERSION_NUMBER.

Underlying Base Objects

According to the documented metadata, CSI_COUNTER_GROUPS_V is defined over CS_COUNTER_GROUPS, referenced in the ETRM record as the synonym CS_CSI_COUNTER_GROUPS. The view is a one-to-one, non-restrictive projection: every row in the base table is represented, and no column expressions alter datatypes, values, or cardinality. There are no documented joins to lookup tables, parties, or instance tables within the view definition itself.

Because the view is a thin wrapper, its data quality, row counts, and access performance are governed entirely by the base counter groups table. Consumers requiring denormalised descriptions, association-type meanings, or source-object names must join outward to the appropriate CSI or lookup tables; the view does not perform that work on their behalf. The view is valid and is retained primarily to provide a stable name and column list for downstream queries and integrations while the base table remains the system of record.

Key Columns

• COUNTER_GROUP_ID — Primary identifier for the counter group; the join key to counter-to-group assignments and related CSI entities.
• NAME, DESCRIPTION — User-facing identification and free-text description of the group.
• TEMPLATE_FLAG — Indicates whether the record is a template counter group available for reuse rather than an operational group.
• CREATED_FROM_CTR_GRP_TMPL_ID — References the template from which the counter group was instantiated; null for templates themselves.
• ASSOCIATION_TYPE — Classifies how the counter group is associated (for example, with a party, item, or instance context).
• SOURCE_OBJECT_CODE — Code identifying the type of object referenced by SOURCE_OBJECT_ID.
• SOURCE_OBJECT_ID — Identifier of the source object for which the counter group was defined; interpretable only together with SOURCE_OBJECT_CODE.
• SOURCE_COUNTER_GROUP_ID — Self-referencing pointer to a source or originating counter group, used where a group is derived or copied.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating window for the counter group.
• ATTRIBUTE1–15 and CONTEXT — Descriptive flexfield segments supporting installation-specific extensions.
• Audit columns and OBJECT_VERSION_NUMBER — Standard WHO tracking and optimistic-locking version marker.

Common Use Cases and Queries

Typical uses include configuration reporting of counter groups, identifying templates versus instantiated groups, tracing lineage through SOURCE_OBJECT_ID and SOURCE_COUNTER_GROUP_ID, and extracting definitions during migration or reconciliation between environments.

-- Counter groups and their association context
SELECT counter_group_id, name, template_flag,
       association_type, source_object_code, source_object_id
FROM   apps.csi_counter_groups_v
WHERE  NVL(end_date_active, SYSDATE + 1) > SYSDATE
ORDER  BY name;

-- Templates available for instantiation
SELECT counter_group_id, name, description
FROM   apps.csi_counter_groups_v
WHERE  template_flag = 'Y';

Because SOURCE_OBJECT_ID is meaningful only in combination with SOURCE_OBJECT_CODE, queries resolving the referenced object must first determine the code and then join to the corresponding CSI entity table. For flexfield-aware extracts, select CONTEXT and the relevant ATTRIBUTEn columns together, and always constrain by COUNTER_GROUP_ID when joining to child counter assignments to avoid unintended duplication.