Results for “okc_line_style_sources”

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

Overview

OKC_LINE_STYLE_SOURCES is a configuration table in the Oracle Contracts Core (OKC) module of Oracle E-Business Suite. It defines which data sources are valid for a given contract line style. In the Oracle Contracts architecture, a "line style" characterizes how a contract line behaves (for example, whether it is a quantity-based, amount-based, or service-oriented line), while the data source governs where the line's underlying data originates — such as a project, an order, an inventory item, or another originating entity. OKC_LINE_STYLE_SOURCES binds these two concepts together, establishing an allowed pairing that the application enforces when contract lines are created or validated.

The ETRM relationship metadata classifies this object heuristically as a link table in a Data Vault sense. This is a modeling suggestion rather than a declarative property: the table primarily holds associations between two independent business entities (line styles and JTOT object codes) rather than carrying descriptive attributes of its own. Its role is therefore referential and validating, keeping contract line configuration internally consistent.

Key Information Stored

The table's documented physical schema in ETRM 12.2.2 contains thirteen columns. The most significant are summarized below.

• LSE_ID — A foreign key to OKC_LINE_STYLES_B, identifying the applicable contract line style. This column participates in the composite primary key.
• JTOT_OBJECT_CODE — A foreign key to JTF_OBJECTS_B, identifying the permitted data source object (for example, a project or order object registered in the JTF object registry). This column also participates in the composite primary key.
• START_DATE and END_DATE — Define the effective dating window during which the line style-to-source association is active.
• ZD_EDITION_NAME — The edition name used by the E-Business Suite Online Patching (Edition-Based Redefinition) framework; it appears in the unique index OKC_LINE_STYLE_SOURCES_U1.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, supporting multi-organization or security-group data segregation.
• ACCESS_LEVEL — Controls row-level access restrictions on the association record.
• OBJECT_VERSION_NUMBER — Used for optimistic locking to detect concurrent updates.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns capturing record authorship and update history.

The primary key is defined by OKC_LINE_STYLE_SOURCES_PK on (LSE_ID, JTOT_OBJECT_CODE). A separate unique index, OKC_LINE_STYLE_SOURCES_U1 on (LSE_ID, JTOT_OBJECT_CODE, ZD_EDITION_NAME), serves as the business-key candidate and reflects the combination enforced as unique per edition.

Common Use Cases and Queries

Business and technical users typically query this table to determine which data sources are authorized for a particular line style, often while troubleshooting why a contract line cannot be created or why a source is not offered in a selection list. A typical diagnostic query joins to OKC_LINE_STYLES_B to resolve the line style name and to JTF_OBJECTS_B to resolve the object label.

• Filtering by LSE_ID to list every permitted source for a given line style.
• Filtering by JTOT_OBJECT_CODE to find which line styles accept a given data source object.
• Applying START_DATE and END_DATE to restrict results to currently effective associations.
• Applying ZD_EDITION_NAME when analyzing patched versus base editions.

A representative pattern is:

SELECT lss.lse_id, ls.name, lss.jtot_object_code, jo.object_code
FROM okc_line_style_sources lss,
okc_line_styles_b ls,
jtf_objects_b jo
WHERE lss.lse_id = ls.lse_id
AND lss.jtot_object_code = jo.object_code;

Reporting use cases include configuration audits that verify every line style has at least one valid source, and impact analyses preceding updates to line style definitions.

Related Objects

The following objects are most directly related through the documented key structure.

• OKC_LINE_STYLES_B — Joined on LSE_ID; the parent definition of contract line styles.
• JTF_OBJECTS_B — Joined on JTOT_OBJECT_CODE; the registry of permissible data source objects.
• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; supports security-group segregation.
• OKC_LINE_STYLE_SOURCES_PK and OKC_LINE_STYLE_SOURCES_U1 — The primary and unique indexes enforcing the documented key combinations.