Search Results cs_counter_groups_s

Overview

APPS.CSI_GROUPING_PKG is a server-side PL/SQL package body in the Oracle E-Business Suite Applications schema (APPS). It belongs to the CSI (Installed Base / Customer Support Intelligence) product family and manages the persistence and lifecycle of counter group definitions. Counter groups provide the logical grouping construct used to organize meters and counters registered against customer products and instances within Oracle Installed Base.

The package exposes a discrete set of data manipulation routines — INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW — that operate directly against the counter grouping base and translation tables. In this respect it functions as a low-level table handler rather than as a self-contained public API. Its routines are designed to be called by higher-level business logic that has already performed validation, rather than being invoked directly by end users. The ETRM metadata records the package body as VALID in both Oracle EBS 12.1.1 and 12.2.2, and confirms that it references APP_EXCEPTION and FND_API, indicating that it participates in the standard EBS API error-handling and message conventions.

Key Procedures and Functions

The documented program units are four DML handlers. No parameter lists are recorded in the metadata, so only their purposes are described below.

• INSERT_ROW — Creates a new counter group record in the underlying counter group tables. This routine is the primary entry point for defining a new grouping of counters or meters for an item instance.
• UPDATE_ROW — Modifies the attributes of an existing counter group record. It is used when group definitions change, such as renaming a group or altering its descriptive attributes.
• LOCK_ROW — Acquires a row-level lock on an existing counter group record before it is modified. This is used to enforce concurrency control and to prevent simultaneous conflicting updates within a single transaction.
• DELETE_ROW — Removes a counter group record. This is typically the final step in the counter group lifecycle, following the removal or reassignment of any counters associated with the group.

Tables Accessed

The package operates against the following tables, referenced through APPS synonyms:

• CS_COUNTER_GROUPS_S — The counter group base (primary) table. This is the principal target of the INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW operations. The "_S" suffix denotes the base table in the standard EBS multi-table translation pattern, with translated columns held in a companion "_TL" table.
• CS_CSI_COUNTER_GROUPS — A related counter group table that maintains the association between counter groups and CSI (Installed Base) entities such as instances, items, and counters. This table supports the linking logic required when groups are created, modified, or removed.
• DUAL — The standard Oracle single-row utility table, used for lightweight queries such as sequence lookups, existence checks, or surrogate key retrieval.

The metadata also records dependencies on APP_EXCEPTION, FND_MESSAGE, and FND_API, confirming that the package raises and handles errors using the EBS message dictionary rather than raw Oracle error codes.

Usage Notes

CSI_GROUPING_PKG is not exposed as a standalone public interface and, per the ETRM dependency record, is not referenced by any other database object in the APPS schema. It is therefore invoked as a build-block routine by the application components that manage counter groups — most commonly Oracle Installed Base forms, the counter grouping user interface, and any concurrent programs that bulk-create or maintain counter group data.

Customizations and extensions should follow the same pattern: validate business rules at the calling layer, then delegate the physical insert, update, lock, and delete operations to this package so that locking and error-handling behavior remain consistent with the standard product. Because the package is not referenced by other database objects, its signature may change between releases without upstream impact; custom code should therefore call it defensively and avoid assumptions about internal implementation. The cs_counter_groups_s search term maps directly to the base table this package manipulates.