Results for “usage_duration”

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

Overview

The OKS_K_LINES_V view is a Service Contracts (OKS) reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Service Contracts Line Attributes," reflecting its role as a consolidated, read-only projection of the attribute-level data that characterizes individual service contract lines. In the Service Contracts data model, contract lines represent the priced deliverables — products, services, and subline components — that a customer subscribes to under a contract. The K_LINES naming convention corresponds to the contracts "lines" entity, and the view exposes the full breadth of line-level attributes without requiring callers to join or interpret the underlying base and translation tables manually.

The view is particularly significant because it spans configuration, pricing, billing, tax, and usage-related attributes in a single object. This makes it valuable for reporting, data extraction, and integration scenarios where a functional consumer — an outbound interface, a data warehouse load, or an OAF-based inquiry page — needs line detail in a denormalized, ready-to-query form. Because the object is recorded as VALID, it is a stable, supported access path within the Service Contracts module.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

• OKS_K_LINES_B — the base table holding line-level attributes (the "_B" suffix denotes base, language-independent columns).
• OKS_K_LINES_TL — the translation table holding language-dependent (translatable) line text such as descriptions and names, keyed by language.

The companion metadata in the view text references columns directly from the base table using the alias KLN (e.g., KLN.ID, KLN.CLE_ID), confirming the join between the base and translation tables on the line identifier. The view thus presents the B/TL pair as a single logical entity, surfacing the translated content alongside numeric and coded attributes.

Key Columns

The view exposes a wide set of line attributes. Notable columns include:

• ROW_ID, ID, CLE_ID, DNZ_CHR_ID — identifiers: the row locator, the line ID, the parent contract line entity ID, and the contract header (CHR) identifier linking the line to its contract.
• DISCOUNT_LIST, LOCKED_PRICE_LIST_ID, PRICE_UOM — pricing constructs applied to the line.
• ACCT_RULE_ID, PAYMENT_TYPE, CC_* — accounting rule and payment method details, including credit card number, expiry, bank account, and authorization code.
• TAX_AMOUNT, TAX_INCLUSIVE_YN, TAX_STATUS, TAX_CODE, TAX_EXEMPTION_ID — taxation attributes for the line.
• PROD_PRICE, SERVICE_PRICE, CLVL_* , TOPLVL_* — product and service prices plus component-level (CLVL) and top-level (TOPLVL) pricing, quantity, UOM, and adjustment values.
• USAGE_EST_YN, USAGE_EST_METHOD, USAGE_EST_START_DATE, USAGE_DURATION, AVERAGING_INTERVAL, SETTLEMENT_INTERVAL — usage estimation and billing cycle attributes.
• MINIMUM_QUANTITY, DEFAULT_QUANTITY, FIXED_QUANTITY, AMCV_FLAG — quantity controls, including the annualized minimum contract value flag.
• TERMN_METHOD, UBT_AMOUNT, CREDIT_AMOUNT, SUPPRESSED_CREDIT, OVERRIDE_AMOUNT — termination and credit behaviors.

Common Use Cases and Queries

Typical uses include contract line reporting, pricing auditing, tax reconciliation, and feeds into billing or data warehouse systems. A representative query retrieves core line attributes for a given contract:

• Line detail by contract: SELECT id, cle_id, dnz_chr_id, prod_price, service_price, tax_amount, price_uom FROM oks_k_lines_v WHERE dnz_chr_id = :contract_id;
• Tax reconciliation: SELECT id, dnz_chr_id, tax_amount, tax_inclusive_yn, tax_code FROM oks_k_lines_v WHERE tax_status = :status;
• Usage-billed lines: SELECT id, dnz_chr_id, usage_est_method, averaging_interval, settlement_interval FROM oks_k_lines_v WHERE usage_est_yn = 'Y';

Because the view joins the base and translation tables, results reflect the current language-dependent text for each line. Queries should filter on indexed identifiers such as DNZ_CHR_ID or CLE_ID to avoid full scans across large contract populations.