Results for “oks_k_lines_b”

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

Overview

OKS_K_LINES_B is the core Service Contracts line attributes table in the Oracle E-Business Suite (EBS) Service Contracts (OKS) module. Owned by the OKS schema and valid in both 12.1.1 and 12.2.2, it stores the extended attribute set that governs how each service contract line is priced, billed, taxed, and covered. Where the primary contract line tables capture entitlement and coverage structure, OKS_K_LINES_B holds the commercial and behavioral detail — pricing adjustments, usage and quantity rules, billing schedules, tax handling, credit card and commitment references, and coverage terms — associated with a contract line.

The table contains 101 documented columns and exposes two unique indexes: OKS_K_LINES_B_U1 on ID (also the primary key via OKS_K_LINES_B_PK) and OKS_K_LINES_B_U2 on CLE_ID. Under a heuristic Data Vault classification mined from its foreign-key structure, the table is modeled as standalone rather than as a hub, link, or satellite. This reflects that most of its descriptive attributes are populated by the owning OKS service contract processes rather than by dimension-style references; the classification is a modeling suggestion, not a physical constraint.

Key Information Stored

ID is the surrogate primary key, unique and enforced by OKS_K_LINES_B_PK. CLE_ID is the second unique business-key candidate and is the natural join path back to the parent service contract line. The most significant columns fall into distinct attribute groups:

• Identity and linkage: ID, CLE_ID, DNZ_CHR_ID, OBJECT_VERSION_NUMBER.
• Pricing and discounting: DISCOUNT_LIST, DISCOUNT_AMOUNT, DISCOUNT_PERCENT, PRICE_UOM, PROD_PRICE, SERVICE_PRICE, CLVL_LIST_PRICE, CLVL_EXTENDED_AMT, OVERRIDE_AMOUNT, ALLOW_BT_DISCOUNT, LOCKED_PRICE_LIST_ID, LOCKED_PRICE_LIST_LINE_ID.
• Billing and usage: USAGE_EST_YN, USAGE_EST_METHOD, USAGE_EST_START_DATE, USAGE_TYPE, USAGE_DURATION, USAGE_PERIOD, BILLING_SCHEDULE_TYPE, PRORATE, MINIMUM_QUANTITY, DEFAULT_QUANTITY, FIXED_QUANTITY, SETTLEMENT_INTERVAL, AVERAGING_INTERVAL, BASE_READING.
• Tax and credit: TAX_AMOUNT, TAX_INCLUSIVE_YN, TAX_STATUS, TAX_CODE, TAX_EXEMPTION_ID, TAX_CLASSIFICATION_CODE, EXEMPT_CERTIFICATE_NUMBER, EXEMPT_REASON_CODE, FULL_CREDIT, CREDIT_AMOUNT, SUPPRESSED_CREDIT.
• Coverage and payment: COVERAGE_TYPE, COVERAGE_ID, STANDARD_COV_YN, EXCEPTION_COV_ID, PAYMENT_TYPE, CC_NO, CC_BANK_ACCT_ID, COMMITMENT_ID.
• Audit and standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, REQUEST_ID.

Common Use Cases and Queries

Typical reporting centers on line-level pricing, tax exposure, and coverage analysis. A join to the parent contract line via CLE_ID is the standard access path.

• Retrieving pricing and discount detail for a given line: SELECT cle_id, prod_price, service_price, discount_percent, discount_amount FROM oks.oks_k_lines_b WHERE cle_id = :cle_id;
• Identifying lines with tax exemptions: filter on TAX_EXEMPTION_ID IS NOT NULL or TAX_STATUS to audit exempt certificate usage.
• Usage-based billing analysis: aggregate by USAGE_TYPE, USAGE_EST_METHOD, and BILLING_SCHEDULE_TYPE to profile quantity and interval rules.
• Coverage exception reporting: join EXCEPTION_COV_ID and COVERAGE_ID to severity and coverage definitions.
• Audit of changes: constrain on LAST_UPDATE_DATE and LAST_UPDATED_BY to track modifications.

Related Objects

The foreign-key metadata documents the principal reference targets, and the unique index on CLE_ID identifies the parent linkage:

• Service Contract Lines (via CLE_ID): the owning line entity joined through the OKS_K_LINES_B_U2 unique key. This is the primary business relationship.
• PON_OFFER_COMMITMENTS: referenced through COMMITMENT_ID for procurement commitment linkage.
• CS_INCIDENT_SEVERITIES_B: referenced through INCIDENT_SEVERITY_ID to associate service-request severity with the line.
• FND_SECURITY_GROUPS: referenced through SECURITY_GROUP_ID, enforcing multi-org security on the row.
• IBY_FNDCPT_TX_EXTENSIONS: referenced through TRXN_EXTENSION_ID for payment transaction extension detail tied to credit card processing columns.
• OKS_K_LINES_B_PK / OKS_K_LINES_B_U1 (ID) and OKS_K_LINES_B_U2 (CLE_ID): the enforcing constraints that guarantee uniqueness and drive join performance.

These objects together support the full lifecycle of a service contract line from pricing and coverage definition through billing, taxation, and payment execution.