Results for “okx_billtype”

18 results




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

Overview

The APPS.OKS_ENT_BILL_TYPES_V view is a reporting and integration construct within Oracle E-Business Suite Release 12.1.1 and 12.2.2 that consolidates entitlement-relevant billing type information drawn from Oracle Contracts (OKC) and Oracle Service (OKS) service line data. The view sits at the intersection of the contract billing model and the service entitlement model, exposing billing types that are attached to specific contract lines and service lines. Its primary role is to present a flattened, query-ready result set joining transaction billing type definitions to the contract billing lines and their associated discount/coverage attributes.

The name frequently associated with this object in user searches is okx_billtype, which corresponds to the JTOT object code OKX_BILLTYPE and to the underlying OKX_TXN_BILLING_TYPES_V view. This view is therefore part of the contract-to-service billing type mapping layer used by Oracle Advanced Pricing, Order Management, and Service Contracts reporting.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over the following objects:

  • OKX_TXN_BILLING_TYPES_V — a view providing the transaction billing type definition (aliased as BT), exposing ID1, ID2, NAME, and BILLING_TYPE.
  • OKC_K_LINES_B — the base contract line table (aliased KL), supplying the contract billing type identifier and the transaction group (CLE_ID).
  • OKS_K_LINES_B — the service line table (aliased OKSBTL), which carries the covered amount and covered percent values that link service entitlements to contract lines.
  • OKC_K_ITEMS — the contract line item table (aliased IT), which stores the JTOT relationship mapping between contract items and billing type identifiers.

The joins are driven by shared CLE_ID values across the contract, service, and item tables, and by the JTOT object code 'OKX_BILLTYPE' matching contract items to billing types.

Key Columns

  • BILLING_TYPE_ID (BT.ID1) — the identifier of the transaction billing type.
  • NAME (BT.NAME) — the descriptive name of the billing type.
  • BILLING_TYPE (BT.BILLING_TYPE) — the billing type code or classification value.
  • CONTRACT_BILLING_TYPE_ID (KL.ID) — the contract billing line identifier.
  • TXN_GROUP_ID (KL.CLE_ID) — the transaction group identifier used to link contract, service, and item records.
  • COVERED_AMOUNT (OKSBTL.DISCOUNT_AMOUNT) — the monetary amount covered or discounted against the billing type.
  • COVERED_PERCENT (OKSBTL.DISCOUNT_PERCENT) — the percentage coverage or discount applied.

Common Use Cases and Queries

The view is typically used in entitlement and coverage reporting, contract billing reconciliation, and integration extracts where contract lines must be mapped to their billing types and coverage values. A representative query 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 = :p_billing_type;

Note that the view applies a filter to lease/service line values (KL.LSE_ID IN (5, 23, 59)), restricting output to the specific line categories recognized by the entitlement model. Consumers integrating with OKX billing types should join this view to OKX_TXN_BILLING_TYPES_V when additional billing type attributes are required, and must account for the LSE_ID restriction when reconciling totals against OKC_K_LINES_B directly.