Results for “okx_counter”

50+ results




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

Overview

APPS.OKS_USAGE_ITEM_V is a service-contracts reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, delivered as part of the Service Contracts (OKS/OKC) and Enterprise Installation/CSI foundation. The view presents a unified, reporting-friendly projection of counter-based usage items so that they can be consumed by the usage and billing engines as well as by external integrations. Its central purpose is to expose the relationship between a counter (a metered asset attribute such as copies, cycles, or hours), the counter group it belongs to, and the source object that the counter measures. The column OBJECT_CODE is hard-coded to the literal 'OKX_COUNTER', which identifies the row type for downstream consumers such as the usage capture and pricing processes. The user search term "okx_counter" corresponds directly to this object code value, indicating that the search is tied to the counter-based usage item mechanism rather than to the base CSI tables themselves.

Underlying Base Objects

The view is defined as a UNION ALL of two branches, each joining a different family of source objects to the same counter metadata. The documented underlying objects are CSI_COUNTERS_B, CSI_COUNTERS_TL, CSI_COUNTER_ASSOCIATIONS, CSI_ITEM_INSTANCES, CS_CSI_COUNTER_GROUPS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, OKC_K_HEADERS_B, OKC_K_ITEMS, and OKC_K_LINES_V.

  • The first branch joins CSI_COUNTERS_B (CCB) to CSI_COUNTERS_TL (CCT) for the translated counter name, CS_CSI_COUNTER_GROUPS (CG) for the counter group, CSI_COUNTER_ASSOCIATIONS (CCA) filtered to SOURCE_OBJECT_CODE = 'CP', CSI_ITEM_INSTANCES (CP) for the installed item instance, and MTL_SYSTEM_ITEMS_KFV (IT) for the item description and concatenated segments. MTL_PARAMETERS is used to constrain the item to the master organization derived from the OKC_CONTEXT organization.
  • The second branch reads the contract side, incorporating OKC_K_HEADERS_B, OKC_K_ITEMS, and OKC_K_LINES_V so that counters associated with contract lines can be represented as party-level records (REC_TYPE = 'PARTY') rather than instance-level records (REC_TYPE = 'CP').

Key Columns

  • NAME — the item concatenated segments from MTL_SYSTEM_ITEMS_KFV, identifying the installed or contracted item.
  • OBJECT_CODE — always 'OKX_COUNTER', the discriminator tying rows to the counter usage object.
  • ID1 / ID2 — ID1 carries the counter_id, ID2 is the literal '#', used as a composite addressing convention.
  • COUNTER — the translated counter name from CSI_COUNTERS_TL.
  • COUNTER_GROUP_ID / TEMPLATE_COUNTER_GROUP_ID — the counter group and, where applicable, the template group from which it was created.
  • USAGE_ITEM_ID — the usage item identifier from CSI_COUNTERS_B used for billing linkage.
  • REC_TYPE — 'CP' for instance-based counters, 'PARTY' for contract-line-based counters.
  • SOURCE_ID / SOURCE_DETAILS / SOURCE_OBJECT_CODE — identify the measured source; for CP rows this is the instance (SERIAL_NUMBER and INSTANCE_NUMBER), for party rows this is the contract line identifier and contract/line concatenation.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the counter validity window.

Common Use Cases and Queries

Typical uses include reporting all active counters for an installed base, resolving usage items for billing, and reconciling contract-line counters with their instance counterparts.

SELECT name, counter, usage_item_id, rec_type, source_details
FROM   apps.oks_usage_item_v
WHERE  object_code = 'OKX_COUNTER'
AND    TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

A second common pattern filters by counter group to audit associated usage items:

SELECT counter, counter_group_id, usage_item_id, source_id
FROM   apps.oks_usage_item_v
WHERE  counter_group_id = :p_group_id
AND    rec_type = 'CP';

Because the view applies USERENV('LANG') and the OKC_CONTEXT ORGANIZATION_ID, callers must initialize the OKC context before querying to obtain correctly scoped and translated results.