Results for “instance_number”

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

Overview

OKS_USAGE_ITEM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKS Service Contracts product family and is documented in the ETRM repository with the description "View for Usage LOV." The view exists primarily to drive the List of Values (LOV) that surfaces usage counters and usage items during contract authoring, usage capture, and counter-based billing. It presents a denormalized, presentation-ready projection of counter definitions joined to the items and instances they measure, so that Oracle Forms and OAF pages can populate a usage-item selector with a single query rather than assembling multiple base tables.

Because the view encodes the source relationship between a counter and its origin (a customer product instance or a contract line), it also serves integration and reporting consumers who need to resolve what a given usage counter applies to without navigating the counter association hierarchy directly. The starting point for the user search term "cs_counters" is the CS_COUNTERS table, which is the central driving table of the view.

Underlying Base Objects

The documented view metadata for 12.2.2 lists the following referenced objects: CSI_COUNTERS_B and CSI_COUNTERS_TL (both synonyms), 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 embedded view text exposes the operative joins: CS_COUNTERS (CT) is joined to CS_COUNTER_GROUPS (CG) on COUNTER_GROUP_ID, and the group's SOURCE_OBJECT_CODE governs which branch of the UNION ALL is returned.

In the product-instance branch, CS_COUNTER_GROUPS is joined to CSI_ITEM_INSTANCES (CP) on SOURCE_OBJECT_ID, and the instance's INVENTORY_ITEM_ID is joined to MTL_SYSTEM_ITEMS_KFV (IT) filtered by the ORGANIZATION_ID held in the OKC_CONTEXT session context. In the contract-line branch, the counter group is joined to OKC_K_LINES_B and OKC_K_ITEMS to reach the contract header (OKC_K_HEADERS_B) and party roles (OKC_K_PARTY_ROLES_B), again resolving the inventory item through MTL_SYSTEM_ITEMS_KFV. The presence of CS_CSI_COUNTER_GROUPS, CSI_COUNTERS_B, CSI_COUNTERS_TL, and CSI_COUNTER_ASSOCIATIONS in the documented base list reflects the CSI-processed counter architecture in 12.2.2, where the service contract counter tables are the functional interface over the CSI counter model.

Key Columns

• NAME — the CONCATENATED_SEGMENTS of the inventory item, used as the LOV display value.
• DESCRIPTION — item description carried from MTL_SYSTEM_ITEMS_KFV.
• SOURCE_DETAILS — a composite key of source object code plus serial number and instance number, or contract number and modifier.
• UOM_CODE — unit of measure of the counter.
• ID1 / ID2 — the counter ID (CT.COUNTER_ID) and a constant placeholder '#', forming the LOV identifier pair.
• OBJECT_CODE — literal 'OKX_COUNTER', identifying the LOV entity type.
• SOURCE_ID — instance ID or contract-line ID depending on branch.
• COUNTER_GROUP_ID, TEMPLATE_COUNTER_GROUP_ID — the associated counter group and its originating template.
• COUNTER, USAGE_ITEM_ID — counter name and the usage item identifier.
• OWNER_PARTY_ID / PARTY_ID, REC_TYPE — 'CP' or 'PARTY' discriminator with the owning party.
• START_DATE_ACTIVE, END_DATE_ACTIVE — counter active date range.

Common Use Cases and Queries

Typical consumers restrict the view by organization context and by source object. Because the view relies on SYS_CONTEXT('OKC_CONTEXT','ORGANIZATION_ID'), queries executed outside the OKC Forms session may need to initialize that context or expect the item join to return no rows.

• Populating a usage-counter LOV by item: SELECT name, counter, usage_item_id FROM oks_usage_item_v WHERE usage_item_id = :p_item ORDER BY counter;
• Listing counters tied to a specific contract line: SELECT counter, uom_code, source_details FROM oks_usage_item_v WHERE rec_type = 'PARTY' AND source_id = :line_id;
• Reporting active counters by owning party: SELECT counter, source_details, start_date_active FROM oks_usage_item_v WHERE rec_type = 'CP' AND owner_party_id = :party_id;
• Validating counter-group template propagation via TEMPLATE_COUNTER_GROUP_ID for upgrade and reconciliation analysis.

Queries should treat the view as read-only, filter on REC_TYPE to choose a single UNION ALL branch for performance, and avoid selecting without an item or party predicate given the breadth of the underlying counter population.