Search Results instance_forecast_id




Overview
Explore in AI Chat

Overview

The CSI_COUNTER_USAGE_FORECAST table resides in the CSI schema, which underpins the Install Base module of Oracle E-Business Suite. It stores counter usage forecasting data captured against customer assets and their associated counters. Within the ETRM 12.2.2 documented schema, the table is classified as VALID and comprises twelve columns. From a data modeling perspective, the heuristic Data Vault classification places this object as a satellite, since it records descriptive forecasting attributes (usage rate, reading basis, effective date ranges) rather than serving as a pure hub of business keys or a link resolving many-to-many relationships. This classification is offered as a modeling suggestion derived from the foreign-key structure and should be validated against the actual implementation in each environment.

Key Information Stored

The documented primary key is CSI_COUNTER_USAGE_FORECAST_PK, defined on the INSTANCE_FORECAST_ID column. A unique index, CSI_COUNTER_USAGE_FORECAST_U01, is also defined on INSTANCE_FORECAST_ID, making it the sole business-key candidate documented in the ETRM metadata. The most significant columns include:

Common Use Cases and Queries

Typical usage involves predicting counter consumption for service contracts, maintenance planning, and meter-based billing. A reporting query joining forecasts to counters might appear as:

SELECT f.INSTANCE_FORECAST_ID, f.COUNTER_ID, f.USAGE_RATE, f.ACTIVE_START_DATE, f.ACTIVE_END_DATE
FROM CSI.CSI_COUNTER_USAGE_FORECAST f
WHERE f.ACTIVE_END_DATE >= SYSDATE
ORDER BY f.COUNTER_ID;

Analysts frequently filter on active date windows to isolate current forecasts, or aggregate USAGE_RATE by COUNTER_ID to project cumulative consumption. The USE_PAST_READING flag supports trend-based versus static forecasting comparisons. Audit-oriented queries filter on LAST_UPDATE_DATE to track recent changes.

Related Objects

Given the standalone Data Vault classification in the ETRM metadata, the table has few documented hard foreign-key dependencies, but logical relationships to core Install Base objects remain significant:

  • CSI_COUNTERS — joined via COUNTER_ID to resolve counter definitions.
  • CSI_ITEM_INSTANCES — links forecasts to the underlying asset instance.
  • CSI_COUNTER_READINGS — provides historical consumption data used when USE_PAST_READING is enabled.
  • CSI_COUNTER_GROUPS — groups counters for aggregated forecasting.
  • CSI_II_RELATIONSHIPS — associates instances with related assets.
  • Install Base public APIs that surface forecasting data for external consumption.

Because the documented foreign-key structure is limited, DBAs should confirm actual referential constraints before relying on implicit joins in production queries.