Search Results tolerance_plus




Overview
Explore in AI Chat

Overview

APPS.CSI_COUNTERS_BC_V is a Business Components (BC) compatibility view in Oracle E-Business Suite, exposed under the APPS schema and defined in the Enterprise Territory and Resource Management (ETRM) foundation layer of the CSI (Customer Service Intelligence / Install Base) product family. Its principal role is to present a unified, flattened projection of counter definitions originating from two distinct source views — CSI_COUNTERS_VL and CSI_COUNTER_TEMPLATE_VL — through a UNION ALL construct, so that application-tier Business Components and dependent reporting or integration routines can query counter metadata, tolerances, and derivation rules from a single relational surface.

The view straddles 12.1.1 and 12.2.2; the underlying column list and the documented metadata are consistent across both releases, with OBJECT_VERSION_NUMBER and column aliases such as CONTEXT, FORMULA_INCOMPL_FLAG, and TYPE reflecting the OAF-style naming conventions used in the later release. Because it is a union view rather than a physical table, it is read-only and intended for query and display purposes.

Underlying Base Objects

ETRM metadata records exactly two referenced base objects for this view: CSI_COUNTERS_VL and CSI_COUNTER_TEMPLATE_VL, both themselves views. CSI_COUNTERS_VL supplies the concrete counter instances (counters attached to an install base item or party), while CSI_COUNTER_TEMPLATE_VL supplies counter templates from which counters can be instantiated. The two branches of the UNION ALL align column-for-column, and the second branch deliberately nulls CREATED_FROM_COUNTER_TMPL_ID and SOURCE_COUNTER_ID to preserve datatype and position compatibility with the first branch. The defaulted group identifier is renamed to COUNTER_GROUP_ID, and COUNTER_TYPE is aliased to TYPE, so any consumer expecting the Business Components contract can read a stable set of column names regardless of the originating branch.

Key Columns

Common Use Cases and Queries

Typical usage includes retrieving tolerance thresholds for a counter, populating LOVs and counter definitions in OAF pages, and feeding extracts that reconcile counter templates against instantiated counters. A representative query filtering on tolerance follows:

SELECT counter_id, name, uom_code,
       tolerance_plus, tolerance_minus,
       step_value, counter_group_id
  FROM apps.csi_counters_bc_v
 WHERE UPPER(name) LIKE UPPER('%:keyword%')
   AND valid_flag = 'Y';

For formula-derivation analysis, querying FORMULA_INCOMPL_FLAG and FORMULA_TEXT exposes counters whose derivation is incomplete. Because the view unions counters and templates, callers should filter on TYPE or COUNTER_GROUP_ID when only one population is required. All queries should be issued against the APPS synonym, and results should respect START_DATE_ACTIVE/END_DATE_ACTIVE and SECURITY_GROUP_ID for a correct, effective-dated, access-controlled result set.