Results for “source_object_code”

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

Overview

The OKS_TEMPLATE_COUNTERS_V view is an APPS-owned, VALID database view within the Oracle E-Business Suite Service Contracts (OKS) module. It exposes counter template definitions used to configure and track service counters on contract lines, subscriptions, and covered serviceable items. In Oracle EBS 12.1.1 and 12.2.2, service contracts rely on counter groups and individual counters to capture usage-based readings such as meter quantities for equipment servicing or copy counts on leased devices. This view consolidates counter-group metadata and counter definitions into a single, denormalized reporting surface.

Its role is reporting and integration rather than transactional processing. The view joins configuration-layer records (counter groups and counters) against their associations to source objects, enabling reports, concurrent programs, and external interfaces to resolve which counters apply to which business entities. Because it references other APPS views rather than base tables directly, it inherits the labeling and filtering semantics layered into those views.

Underlying Base Objects

The documented base objects referenced by OKS_TEMPLATE_COUNTERS_V are:

• OKX_COUNTER_GROUPS_V (VIEW) — supplies the counter group, name, and source object code.
• OKX_COUNTERS_V (VIEW) — supplies individual counter attributes including type, UOM, and reading values.
• OKX_CTR_ASSOCIATIONS_V (VIEW) — supplies the link between counter groups and source objects, contributing SOURCE_OBJECT_ID. This is the object that a user searching for "okx_ctr_associations_v" would encounter.
• OKS_AUTH_UTIL_PVT (PACKAGE) — an authorization utility package in the OKS schema; its presence in the dependency chain indicates the view participates in Service Contracts security and access-utility logic.

The view text joins OKX_COUNTER_GROUPS_V to OKX_COUNTERS_V on COUNTER_GROUP_ID, and to OKX_CTR_ASSOCIATIONS_V on the same key, producing one row per counter within an associated counter group.

Key Columns

• COUNTER_GROUP_ID — Identifier for the parent counter group; the join key across all three source views.
• COUNTER_ID — Identifier for the individual counter within the group.
• NAME — Concatenation of counter group name and counter name (CG.NAME || '.' || CT.NAME), giving a fully qualified label suitable for display.
• TYPE — Counter classification (for example, absolute or gauge/consumption style readings).
• UOM_CODE — Unit of measure code applied to the counter reading.
• NET_READING — Current net reading value recorded against the counter.
• VALUE_TIMESTAMP — Timestamp of the reading, useful for recency and period analysis.
• SOURCE_OBJECT_ID — Identifier of the associated source object (such as the covered item or contract object) drawn from the associations view.
• SOURCE_OBJECT_CODE — Code denoting the source object type, enabling classification of the association.

Common Use Cases and Queries

Typical uses include retrieving all counters associated with a given source object for billing, maintenance planning, or usage verification; producing master data extracts of counter templates; and validating that counter groups are properly associated to contracts. A representative query is shown below.

SELECT counter_group_id, counter_id, name, type, uom_code, net_reading, value_timestamp, source_object_id, source_object_code
FROM apps.oks_template_counters_v
WHERE source_object_id = :p_object_id
ORDER BY name;

A second pattern lists counter groups and their association codes for a specific source object type:

SELECT DISTINCT counter_group_id, source_object_code, source_object_id
FROM apps.oks_template_counters_v
WHERE source_object_code = :p_code;

Because the view depends on OKS authorization utilities, queries executed by restricted users may return only counters to which they hold access. For bulk extraction, a reporting schema or APPS responsibility with appropriate service contract privileges is recommended.