Results for “csi_counter_direction_type”

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

Overview

APPS.EAM_CFR_COUNTER_READINGS_V is a reporting and integration view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that presents counter readings captured against enterprise assets and maintainable equipment. It is defined within the Enterprise Asset Management (EAM) and Complex Maintenance, Repair, and Overhaul (CMRO) product family and is layered on top of the CSI counter reading infrastructure, specifically the CSI_COUNTER_READINGS_V view maintained by the Customer Support/Installed Base schema. The view exposes both the raw reading attributes and decoded lookup meanings, allowing consumers to obtain human-readable descriptions for reading types and counter directions without performing their own lookup joins.

The view is not an entity table; it is a query surface. This means it inherits the row-level security, business logic, and access controls implemented in CSI_COUNTER_READINGS_V and should be treated as read-only for reporting purposes. The decoded READING_TYPE and DIRECTION columns are particularly valuable for dashboards, ad hoc reporting, and interface extraction, where downstream systems require semantic values rather than coded lookup identifiers.

Underlying Base Objects

The ETRM metadata documents three referenced objects underpinning this view:

• CSI_COUNTER_READINGS_V (VIEW) — Aliased as CCRV, this is the primary driving object. It supplies every column that originates from the counter records, including counter identifiers, timestamps, readings, reset information, and descriptive flexfield attributes.
• CSI_LOOKUPS (VIEW) — Aliased twice. CLK is joined for the CSI_COUNTER_READING_TYPE lookup type to translate READING_TYPE into a meaning. CLK2 is joined for the CSI_COUNTER_DIRECTION_TYPE lookup type to translate DIRECTION into a meaning.
• CSI_COUNTER_READINGS_PVT (PACKAGE) — The PL/SQL API layer that governs the logic behind the counter reading view, handling validation, rollover behavior, and reading maintenance.

The join predicates are significant. The reading type join converts READING_TYPE to character for comparison against CLK.LOOKUP_CODE. The direction join employs NVL(ccrv.direction,'B'), meaning that counter directions which are null are treated as the default lookup code 'B'. This effectively ensures that every row retains a populated direction meaning even when the stored direction is absent.

Key Columns

• COUNTER_VALUE_ID — Primary identifier for the counter value record.
• COUNTER_ID / COUNTER_NAME / COUNTER_DESCRIPTION — Identifies the parent counter and its descriptive attributes.
• READING_TYPE and READING_TYPE (MEANING) — The coded reading type plus the decoded lookup meaning.
• DIRECTION and DIRECTION (MEANING) — The counter direction code, defaulted to 'B', and its decoded meaning from CSI_COUNTER_DIRECTION_TYPE.
• UOM_CODE — The unit of measure in which the counter is expressed.
• COUNTER_READING, LIFE_TO_DATE_READING, NET_READING — The absolute reading, cumulative life-to-date total, and net value.
• INITIAL_READING, ROLLOVER_LAST_READING, ROLLOVER_FIRST_READING — Setup values defining the counter range and starting point.
• VALUE_TIMESTAMP — The effective date and time the reading was taken.
• RESET_MODE, RESET_REASON, READING_BEFORE_RESET, READING_AFTER_RESET — Describe resets applied to the counter and the values flanking each reset.
• ADJUSTMENT_TYPE, ADJUSTMENT_READING — Manual adjustment details.
• AUTOMATIC_ROLLOVER_FLAG, INCLUDE_TARGET_RESETS, DISABLED_FLAG, MIGRATED_FLAG — Control and status flags.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Audit and concurrency attributes.
• ATTRIBUTE1 through ATTRIBUTE30 and ATTRIBUTE_CATEGORY — Descriptive flexfield storage.

Common Use Cases and Queries

Typical scenarios include counter reading trend analysis, rollover detection, asset health reporting, and extracting readings for integration into condition-monitoring or metering systems. Because the direction meaning is pre-decoded, the view is frequently used where the search term csi_counter_direction_type is relevant, removing the need for consumers to join CSI_LOOKUPS manually.

Sample query retrieving the latest readings per counter with decoded direction and reading type:

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

Sample query filtering to a specific direction meaning, such as ascending counters:

• SELECT counter_value_id, counter_name, direction, counter_reading
• FROM apps.eam_cfr_counter_readings_v
• WHERE reading_type = 'MANUAL' AND direction LIKE 'Ascending%';

Administrators should remember that the view is owned by APPS and should be referenced with the APPS schema prefix or through a synonym, and that all access is subject to the security rules enforced by the underlying CSI objects.