Search Results csi_ctr_estimate_methods_b_pk

Overview

CSI_CTR_ESTIMATION_METHODS_B is a foundational configuration table within the Oracle E-Business Suite Install Base (CSI) module. Its documented purpose is to hold counter estimation data. In EBS, counters are numeric readings captured against an installed base asset—such as meter readings on a machine, odometer values on a vehicle, or page counts on a printer. Counter estimation methods define the rules by which the system projects or estimates a counter value when a direct reading is unavailable, incomplete, or consumed by a service contract. This table therefore governs how estimated usage is derived for billing, preventive maintenance scheduling, and service entitlement calculations.

From a Data Vault modeling perspective, the mined heuristic classification for this table is standalone. In Data Vault terms, a standalone table is typically modeled as a hub when it contains a stable business key with no dependent context, or as a satellite when it carries descriptive attributes attached to a parent hub. Because the documented schema exposes a single primary key (ESTIMATION_ID) with no inbound foreign keys from dependent child tables and only one outbound reference to FND_SECURITY_GROUPS, the table is best treated as a standalone reference or setup entity—functionally akin to a code/seed table that enumerates allowable estimation behaviors. In EBS 12.1.1 and 12.2.2 the table resides in the CSI schema alongside the broader Install Base data model, and its security is scoped through SECURITY_GROUP_ID in multi-organization and multi-tenant deployments.

Key Information Stored

The table carries 32 documented columns. The most significant are:

• ESTIMATION_ID — the surrogate primary key, backed by CSI_CTR_ESTIMATE_METHODS_B_PK and also enforced through the unique index CSI_CTR_ESTIMATE_METHODS_B_U01. It uniquely identifies each estimation method record.
• ESTIMATION_TYPE — the discriminator that categorizes the estimation rule (for example fixed, usage-based, or default-driven).
• FIXED_VALUE — the constant value applied when the estimation method resolves to a fixed result.
• USAGE_MARKUP — a factor or additive amount applied on top of recorded usage to derive the estimate.
• DEFAULT_VALUE — the fallback value used when no other estimation input is available.
• ESTIMATION_AVG_TYPE — specifies the averaging basis used when estimates are computed from historical readings.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range during which the method is valid, enabling date-effective setup control.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security group may access the record.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/ADF framework for concurrent update protection.
• MIGRATED_FLAG — indicates whether the record was introduced through a migration or data conversion rather than native entry.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield (DFF) columns, supporting customer-specific extensions without schema change.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — the standard "Who" columns maintained automatically by EBS.

Note that ESTIMATION_ID serves simultaneously as the surrogate PK and the unique business-key candidate; there is no separate human-readable code column documented.

Common Use Cases and Queries

Typical scenarios include validating which estimation methods are active for a given period, auditing how estimated counters feed contract billing, and identifying migrated versus natively created setups.

• Retrieve currently active estimation methods:
  SELECT estimation_id, estimation_type, fixed_value, usage_markup, default_value
  FROM csi_ctr_estimation_methods_b
  WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• List methods by type for a reporting extract:
  SELECT estimation_type, COUNT(*) FROM csi_ctr_estimation_methods_b GROUP BY estimation_type;
• Identify migrated records for reconciliation:
  SELECT estimation_id FROM csi_ctr_estimation_methods_b WHERE migrated_flag = 'Y';
• Join to security groups to resolve access scope:
  SELECT c.estimation_id, s.security_group_name
  FROM csi_ctr_estimation_methods_b c, fnd_security_groups s
  WHERE c.security_group_id = s.security_group_id;

Because the table is a setup/reference entity, it is generally joined into counter-reading and contract-usage reports rather than transacted against directly.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; the only documented foreign key target, providing row-level security scoping.
• CSI_COUNTERS / CSI_CTR_READINGS — counter and reading tables that consume estimation method logic to project values.
• CSI_ITEM_INSTANCES — the installed base asset records whose counters are estimated.
• CSI_CTR_ESTIMATION_METHODS_TL — the translation table (where present) supplying language-specific descriptions aligned by ESTIMATION_ID.
• CSI_CTR_GROUPS / CSI_CTR_GROUP_MEMBERS — counter grouping structures that reference methods for estimation behavior.
• Service Contracts (OKS) usage tables — downstream consumers of estimated usage for billing and entitlement.

Reviewers of this object should treat it as a low-volume, date-effective configuration table whose correctness directly influences counter estimation downstream.