Search Results tolerance_minus




Overview
Explore in AI Chat

Overview

CS_CTR_COUNTERS_HISTORY_V is a Service (CS) module view that exposes counter readings history information within Oracle E-Business Suite 12.1.1 and 12.2.2. In the Enterprise Asset Management and field service context, counters are used to track cumulative consumption, usage, or operational measurements associated with serviceable items, assets, and equipment. Counters may record values such as meter readings, mileage, copy volumes, or runtime hours. The view consolidates the counter definition attributes held in CS_COUNTERS with the descriptive attributes of the counter group to which each counter belongs, producing a denormalized result set that is convenient for reporting and integration purposes.

Because the object is a view rather than a table, it holds no data of its own. It is a read-only projection designed to simplify access to counter configuration and historical reading boundaries. The ETRM metadata notes that the view is "Not implemented in this database," meaning the object definition may not be instantiated in every environment; availability depends on the specific patch level, module licensing, and applied product code.

Underlying Base Objects

The view text is defined over two base tables:

  • CS_COUNTERS (alias A) — the primary source of counter definitions and attributes. The foreign key COUNTER_GROUP_ID links each counter to its group.
  • CS_COUNTER_GROUPS (alias B) — provides the counter group NAME and DESCRIPTION, joined on COUNTER_GROUP_ID.

The SELECT joins the two tables with the predicate A.COUNTER_GROUP_ID = B.COUNTER_GROUP_ID, and exposes A.ROWID as ROW_ID. All counter-level columns originate from CS_COUNTERS, while the group-level name and description originate from CS_COUNTER_GROUPS. No additional base objects are documented in the ETRM metadata. The documented view exposes 42 columns, including the standard EBS Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and 15 flexfield attribute columns plus CONTEXT.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on counter configuration, verifying rollover settings before reading entry, and integrating counter metadata with external maintenance systems. A common query retrieves rollover boundaries for active counters:

  • SELECT counter_id, counter_name, rollover_first_reading, rollover_last_reading, uom_code FROM cs_ctr_counters_history_v WHERE valid_flag = 'Y';
  • SELECT counter_group_name, counter_name, initial_reading, step_value FROM cs_ctr_counters_history_v WHERE counter_group_id = :group_id;
  • SELECT c.counter_name, c.tolerance_plus, c.tolerance_minus FROM cs_ctr_counters_history_v c WHERE c.uom_code = :uom;

Because the view is read-only and joins only two tables, it is lightweight and suitable for concurrent program extracts and BI Publisher reports, though environments where the view is not implemented will return an invalid object error until the supporting CS objects are created.