Results for “covered_amount”

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

Overview

OKS_ENT_BILL_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Service Contracts (OKS) module. Its documented purpose is to present billing type information for service contracts, consolidating entitlement billing attributes that are otherwise distributed across contract line, item, and billing type entities. Because the view resolves these relationships into a single, query-friendly result set, it is used in reporting, integration, and extension work where a denormalized view of contract billing types is required.

The view is particularly relevant to the commonly searched column BILLING_TYPE_ID, which the view exposes as its first column, aliased from the base billing type identifier (ID1). This makes OKS_ENT_BILL_TYPES_V a natural entry point for lookups keyed on billing type, and for joining billing type definitions back to contract billing lines.

Status is documented as VALID, and the object is present in both Oracle EBS 12.1.1 and 12.2.2 environments, where the underlying OKS and OKC schema objects follow the same logical structure.

Underlying Base Objects

The documented view text joins four base objects, all referenced through APPS synonyms:

• OKC_K_LINES_B — the contract line base table, aliased KL. It supplies the contract billing type identifier (KL.ID) and the line set identifier (KL.LSE_ID).
• OKS_K_LINES_B — the Service Contracts line base table, aliased OKSBTL. It contributes the covered amount and covered percent attributes (OKSBTL.DISCOUNT_AMOUNT and OKSBTL.DISCOUNT_PERCENT).
• OKC_K_ITEMS — the contract items table, aliased IT. It links contract lines to their referenced objects through OBJECT1_ID1, OBJECT1_ID2, and JTOT_OBJECT1_CODE.
• OKX_TXN_BILLING_TYPES_V — the transaction billing types view, aliased BT. It provides the billing type identifier (BT.ID1), name (BT.NAME), and billing type classification (BT.BILLING_TYPE).

The join conditions tie these objects together: OKC_K_LINES_B.ID equals both OKS_K_LINES_B.CLE_ID and OKC_K_ITEMS.CLE_ID, while OKC_K_ITEMS.OBJECT1_ID1 and OBJECT1_ID2 map to the billing type view, filtered on JTOT_OBJECT1_CODE = 'OKX_BILLTYPE'. An additional restriction limits OKC_K_LINES_B.LSE_ID to the values 5, 23, and 59.

Key Columns

• BILLING_TYPE_ID — the billing type identifier (BT.ID1), the primary key value most users query against.
• NAME — the descriptive name of the billing type (BT.NAME).
• BILLING_TYPE — the billing type classification (BT.BILLING_TYPE).
• CONTRACT_BILLING_TYPE_ID — the contract billing line identifier (KL.ID), linking back to the contract line record.
• TXN_GROUP_ID — the transaction group reference, mapped from KL.CLE_ID.
• COVERED_AMOUNT — the covered discount amount (OKSBTL.DISCOUNT_AMOUNT).
• COVERED_PERCENT — the covered discount percent (OKSBTL.DISCOUNT_PERCENT).

Common Use Cases and Queries

Typical usage includes resolving a billing type name from an identifier, reporting covered amounts and percentages by contract, and joining billing type definitions to service contract lines. A representative query by identifier is:

• SELECT billing_type_id, name, billing_type, contract_billing_type_id, txn_group_id, covered_amount, covered_percent FROM apps.oks_ent_bill_types_v WHERE billing_type_id = :p_id;

For reporting covered values per contract billing type, join the view to OKC_K_LINES_B on contract_billing_type_id to retrieve line-level context. Because the view already applies the LSE_ID restriction and the OKX_BILLTYPE item filter, results are limited to the relevant service contract billing lines, sparing callers from reconstructing the multi-table join manually.