OKC Contract Lines Summary – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Summary of okc line style hierarchies, the jtf objects linked to each line level and the active and overall count of contract lines by status for each line type. This is useful for developers to see how the oracle contracts line data is structured and how the link to external objects, e.g. installed base or counters for service contracts works
Report Parameters
Class, Category
Oracle EBS Tables Used
okc_line_styles_v, okc_subclass_top_line, okc_subclasses_v, okc_classes_v, okc_line_style_sources, jtf_objects_vl, okc_k_lines_b, oks_k_lines_b, okc_k_items, okc_k_headers_all_b, okc_statuses_b, okc_statuses_v
Report Categories
Related Reports
OKS Service Contracts Billing Schedule, OKS Service Contracts Billing History, AR Transactions and Lines 11i, GL Account Distribution Analysis, GL Account Analysis (Distributions)
Running This SQL Without Blitz Report
Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | OKC Contract Lines Summary 11-Oct-2020 145318.xlsx |
| Blitz Report™ XML Import | OKC_Contract_Lines_Summary.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/okc-contract-lines-summary/ |
OKC Contract Lines Summary - Case Study & Technical Analysis
Executive Summary
The OKC Contract Lines Summary report provides a structural overview of the Oracle Contracts (OKC) data model. It is primarily a technical or techno-functional report used to understand how contract lines are organized, hierarchically structured, and linked to external objects (like Inventory Items or Service Counters).
Business Challenge
Oracle Contracts is a complex module with a highly normalized data structure.
- Data Visibility: “We have thousands of contracts, but I don’t understand the hierarchy. Which lines are ‘Service Lines’ and which are ‘Usage Lines’?”
- Integration: “We need to build an interface to a third-party billing system. How do we link the contract line to the specific asset being serviced?”
- Customization: “We want to add a custom field to the ‘Covered Product’ line. What is the underlying Line Style ID for that?”
Solution
The OKC Contract Lines Summary report maps the contract structure.
Key Features:
- Hierarchy Visualization: Shows the parent-child relationships between different line styles (e.g., Service Line -> Covered Product -> Pricing Attribute).
- Object Linking: Identifies the “JTF Object” linked to each line (e.g.,
OKX_INSTALL_ITEMfor Installed Base items). - Status Counts: Provides a count of active vs. inactive lines for each style.
Technical Architecture
The report queries the core OKC setup and transaction tables.
Key Tables and Views
OKC_LINE_STYLES_V: Defines the types of lines (Service, Warranty, Subscription) and their hierarchy.OKC_K_LINES_B: The transaction table storing the actual contract lines.JTF_OBJECTS_VL: Defines the external entities (like Inventory Items) that can be attached to a contract line.
Core Logic
- Structure Analysis: Starts with the top-level line styles and recursively finds their children (Sublines).
- Usage Analysis: Counts how many actual contract lines exist for each style to show which features are being used.
- Metadata Exposure: Lists the source tables and views used by each line style.
Business Impact
- Developer Productivity: Serves as a “map” for developers building extensions or reports on the Contracts module.
- System Health: Helps identify unused or obsolete contract types.
- Data Migration: Essential for planning data migration strategies when moving legacy contracts into Oracle.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics