Results for “eam_cfr_counter_readings_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The EAM_CFR_COUNTER_READINGS_V view (owner: APPS, status: VALID) belongs to the Oracle Enterprise Asset Management (EAM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose Work Order Completion Counter readings. In an EAM context, counters are maintained on assets and rebuildable/rotable items to track cumulative usage quantities such as operating hours, mileage, cycles, or production counts. When a work order is completed, the counter values recorded against the asset are captured and exposed through this view so that downstream reporting, maintenance strategy evaluation, and preventive maintenance scheduling can consume the latest readings.

The view is a reporting and integration artifact rather than a transactional base object. It projects the columns of the underlying CSI_COUNTER_READINGS_V view and decorates them with descriptive lookup meanings, allowing Reports, OAF pages, concurrent programs, and external integration layers to retrieve counter data without re-joining the lookup tables themselves.

Underlying Base Objects

The documented referenced base objects for this view are:

• CSI_COUNTER_READINGS_PVT (PACKAGE) — the EAM/CSI counter readings private API package that encapsulates the business logic for counter value creation, maintenance, and retrieval. The view derives its core columns from the counter reading structures maintained by this package.
• CSI_COUNTER_READINGS_V (VIEW) — the principal source object in the FROM clause (aliased CCRV). It supplies all the counter value columns, including identifying keys, reading values, timestamps, and descriptive flexfield attributes.
• CSI_LOOKUPS (VIEW) — referenced twice in the view text, as aliases CLK and CLK2.

Two inner joins to CSI_LOOKUPS enrich the base readings. CLK resolves READING_TYPE against LOOKUP_TYPE = 'CSI_COUNTER_READING_TYPE', and CLK2 resolves DIRECTION against LOOKUP_TYPE = 'CSI_COUNTER_DIRECTION_TYPE', with a NVL(CCRV.DIRECTION, 'B') default of B applied so that rows without a stored direction still match a valid lookup entry. This design explains the search term "csi_lookups" associated with this object: the view cannot return readings correctly unless the relevant CSI lookup codes are seeded in CSI_LOOKUPS.

Key Columns

• COUNTER_VALUE_ID — primary identifier of the counter reading record.
• COUNTER_ID / COUNTER_NAME / COUNTER_DESCRIPTION — identity and description of the counter to which the reading belongs.
• COUNTER_READING / INITIAL_READING / NET_READING / LIFE_TO_DATE_READING — the measured values: the current reading, the starting reading, the net reading since last reset, and cumulative life-to-date usage.
• READING_TYPE / READING_TYPE (MEANING) — the lookup code and its decoded meaning from CSI_LOOKUPS (lookup type CSI_COUNTER_READING_TYPE).
• DIRECTION / DIRECTION (MEANING) — whether the counter increments or decrements, decoded via lookup type CSI_COUNTER_DIRECTION_TYPE.
• VALUE_TIMESTAMP — the effective date/time the reading was taken.
• UOM_CODE / COUNTER_TYPE / RESET_MODE / RESET_REASON — unit of measure, classification of the counter, and reset semantics.
• ROLLOVER_LAST_READING / ROLLOVER_FIRST_READING / AUTOMATIC_ROLLOVER_FLAG — rollover behavior for counters that wrap around.
• READING_BEFORE_RESET / READING_AFTER_RESET — the values bracketing a reset event.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — descriptive flexfield columns for extensibility.
• DISABLED_FLAG / MIGRATED_FLAG / OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard EBS audit and concurrency control attributes.

Common Use Cases and Queries

Typical scenarios include reviewing the latest counter readings for an asset at work order completion, auditing resets, and feeding lifecycle or preventive maintenance programs.

• Retrieve decoded readings for a specific counter:

SELECT counter_value_id, counter_name, counter_reading,
       reading_type, direction, value_timestamp
FROM   apps.eam_cfr_counter_readings_v
WHERE  counter_id = :p_counter_id
ORDER  BY value_timestamp DESC;

• List readings by reading type meaning (requires CSI_LOOKUPS seed data):

SELECT counter_id, counter_name, counter_reading, reading_type
FROM   apps.eam_cfr_counter_readings_v
WHERE  reading_type = 'MANUAL';

• Identify counters that have undergone resets or rollovers:

SELECT counter_id, reading_before_reset, reading_after_reset,
       reset_mode, reset_reason
FROM   apps.eam_cfr_counter_readings_v
WHERE  reading_before_reset IS NOT NULL;

Because the view relies on inner joins to CSI_LOOKUPS, missing or disabled lookup codes for CSI_COUNTER_READING_TYPE or CSI_COUNTER_DIRECTION_TYPE will silently exclude rows. This is the most common data-visibility issue encountered when troubleshooting this view.