Results for “cntr_lvlng”

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

Overview

The view APPS.OKL_BPD_CNTR_LVLNG_SUMRY_UV is a reporting and integration construct within the Oracle E-Business Suite (EBS) Lease and Finance Management module, part of the Oracle Enterprise Contracts and ETRM (Enterprise Transactional Reporting Model) family. It is owned by the APPS schema and is defined in both release 12.1.1 and 12.2.2. The view consolidates counter group leveling information against the contracts, assets, and counters to which they relate, producing a flattened summary of counter-level data. Its name reflects its purpose: BPD (business process data), CNTR (counter), and LVLNG (leveling), with the _UV suffix denoting a user view exposed for downstream reporting and integration consumption.

The view is typically used by reporting tools, custom concurrent programs, and integration interfaces requiring a denormalized snapshot of which counters belong to which counter groups, the effective date ranges of those group assignments, and the associated asset and contract context. Because it joins translation, header, line, and asset tables, it abstracts the multi-table structure of the OKC and OKL schemas into a single queryable surface.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms or views:

• CS_COUNTERS (synonym) — supplies counter identifiers and names.
• OKC_K_HEADERS_B (synonym) — contract header records, providing the contract number.
• OKC_K_LINES_B (synonym) — contract lines representing usage, subscription (OKS), and asset line roles.
• OKC_K_ITEMS (synonym) — the item relationships that link lines to underlying objects such as counters and assets.
• OKC_K_LINES_TL (synonym) — translated line names, restricted to the user's language via USERENV('LANG').
• OKL_CNTR_LVLNG_GRPS_V (view) — counter leveling groups, providing the group name and effective date range.
• OKL_CNTR_LVLNG_LNS_V (view) — counter leveling lines linking groups to counters.
• OKX_ASSETS_V (view) — asset master information, including serial number and description.

The join graph is dense: the usage line is tied to the contract header, to the OKS line, and to the asset line, while the counter is resolved through the OKS line's asset item and the leveling line relationship. This structure reflects the hierarchical nature of lease contract assets, counters, and counter-group leveling assignments.

Key Columns

• COUNTER_GROUP — the name of the counter leveling group from OKL_CNTR_LVLNG_GRPS_V.
• COUNTER_NUMBER — the counter identifier from CS_COUNTERS.
• COUNTER_NAME — the descriptive counter name.
• CONTRACT_NUMBER — the contract header number from OKC_K_HEADERS_B.
• ASSET_NUMBER — the asset line name (translated), linking to the asset recorded against the contract.
• ASSET_SERIAL_NUMBER and ASSET_DESCRIPTION — asset master attributes from OKX_ASSETS_V.
• EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO — the validity window of the counter group assignment, used for point-in-time reporting.

Common Use Cases and Queries

Typical uses include auditing which counters are level-assigned to which groups, reconciling asset counters against contract lines, and feeding downstream meter-reading or billing processes. A representative query filters on a contract and a reporting date:

• SELECT counter_group, counter_number, counter_name, contract_number, asset_number, effective_date_from, effective_date_to FROM apps.okl_bpd_cntr_lvlng_sumry_uv WHERE contract_number = :p_contract AND :p_report_date BETWEEN effective_date_from AND NVL(effective_date_to, :p_report_date);
• SELECT counter_group, COUNT(*) FROM apps.okl_bpd_cntr_lvlng_sumry_uv GROUP BY counter_group;
• SELECT asset_number, asset_serial_number, counter_name FROM apps.okl_bpd_cntr_lvlng_sumry_uv WHERE contract_number IN (:contract_list);

Because the view depends on translated line names via USERENV('LANG'), results are language-sensitive and should be executed in a session whose language matches the reporting requirement.