Search Results okc_k_seq_lines




Overview
Explore in AI Chat

Overview

The table OKC_K_SEQ_LINES is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the detailed configuration repository for the contract document autonumbering feature. This table defines the specific rules and segments that govern how the system automatically generates unique, sequential numbers for contract documents. Its role is critical for ensuring standardized, consistent, and meaningful numbering across different contract classes and subclasses, which is a fundamental requirement for contract lifecycle management and reporting.

Key Information Stored

The table stores the granular definitions for each segment of an autonumbering format. While the full column list is not detailed in the provided metadata, the structure typically includes a primary key column (ID) and a foreign key column (SCS_CODE) linking to the configuration header. Based on its described purpose, the table would hold columns defining segment types (e.g., constant text, sequential number, date element), segment values, sequencing parameters (start number, increment), and the order of segments within the overall numbering format. The SCS_CODE column is explicitly noted as a foreign key, connecting each detail line to a specific contract class or subclass in the OKC_CLASSES_B and OKC_SUBCLASSES_B tables, thereby scoping the numbering rule.

Common Use Cases and Queries

The primary use case is the administration and troubleshooting of contract document numbering schemes. Functional consultants use this data, often via the application's user interface, to set up or modify numbering formats. Common technical queries involve analyzing the configured rules for a given contract type. A sample SQL pattern to retrieve the autonumbering configuration for a specific class might be:

  • SELECT seq_line.* FROM okc_k_seq_lines seq_line, okc_classes_b cla WHERE seq_line.scs_code = cla.scs_code AND cla.class_code = 'SERVICE_CONTRACT';

Reporting use cases include auditing numbering configurations across the implementation or diagnosing issues where contracts are not generating numbers as expected, which would involve joining this table to the master configuration and contract header tables.

Related Objects

OKC_K_SEQ_LINES has direct relationships with several key Contracts Core tables, as indicated by the foreign key metadata. Its primary foreign key relationship is with the OKC_CLASSES_B table, which stores contract class definitions, and the OKC_SUBCLASSES_B table. This establishes that autonumbering rules are defined at the class or subclass level. The table is protected by the primary key constraint OKC_K_SEQ_LINES_PK on the ID column. It is a child table within the autonumbering configuration setup, and it is logically associated with the contract headers table (OKC_K_HEADERS_B), whose document numbers are generated based on the rules stored in OKC_K_SEQ_LINES.