Search Results okc_line_style_sources




Overview
Explore in AI Chat

Overview

The OKC_LINE_STYLE_SOURCES table is a core reference table within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a control table that defines the valid data sources from which contract lines can be created for a specific line style. In essence, it enforces business rules by linking a contract line style (a template defining line behavior and attributes) to the specific transactional objects (such as Sales Orders, Purchase Orders, or Assets) that are permitted to be the origin or reference for lines created under that style. This table is fundamental to ensuring data integrity and enforcing the configured sourcing rules during contract authoring and management processes in releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores a simple but critical mapping between a line style and an object code representing a source system entity. Its structure is defined by a composite primary key. The two key columns are LSE_ID, which is a foreign key to the OKC_LINE_STYLES_B table identifying the specific line style, and JTOT_OBJECT_CODE, which is a foreign key to the JTF_OBJECTS_B table identifying the valid source object. The JTF_OBJECTS_B table is a central repository for object definitions across EBS, meaning JTOT_OBJECT_CODE could point to objects like 'OKC_K_HEADERS' for another contract, 'OE_ORDER_HEADERS' for sales orders, or 'PO_HEADERS' for purchase orders. Each record in this table signifies that the given line style is authorized to source lines from the specified object type.

Common Use Cases and Queries

The primary use case is validation during the contract line creation process. When a user attempts to create a contract line from an external source (like a sales order), the application queries this table to verify if the line's style permits sourcing from that object type. It is also critical for generating lists of available source types in UI LOVs (Lists of Values). A common reporting query would involve joining to OKC_LINE_STYLES_B and JTF_OBJECTS_B to produce a human-readable list of all line styles and their permitted sources. For example, a query to find all valid sources for a line style named 'SERVICE' would resemble:
SELECT ols.name AS line_style_name, job.object_name AS source_object
FROM okc_line_style_sources olss,
okc_line_styles_b ols,
jtf_objects_b job
WHERE olss.lse_id = ols.id
AND olss.jtot_object_code = job.object_code
AND ols.name = 'SERVICE';

Related Objects

OKC_LINE_STYLE_SOURCES maintains defined foreign key relationships with two key tables, forming the backbone of its referential integrity.

  • OKC_LINE_STYLES_B: This is the master table for contract line styles. The LSE_ID column in OKC_LINE_STYLE_SOURCES references the ID column in OKC_LINE_STYLES_B. This relationship ensures that every sourcing rule is attached to a valid, existing line style.
  • JTF_OBJECTS_B: This is a central EBS table defining all application objects. The JTOT_OBJECT_CODE column in OKC_LINE_STYLE_SOURCES references the OBJECT_CODE column in JTF_OBJECTS_B. This relationship validates that the specified data source is a registered and known object within the system.
These relationships are critical for any data analysis or integration involving contract line sourcing rules.