Results for “okc_k_seq_lines”

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

Overview

OKC_K_SEQ_LINES is a Contracts Core (OKC) transactional configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds the detail records used by the Autonumbering feature for contracts. Where the header-level autonumbering setup defines the overall numbering scheme for a class or subclass of contract, OKC_K_SEQ_LINES stores the individual sequence lines that control how contract numbers are generated — including prefix and suffix text, numeric length, and the starting and ending sequence values. Because autonumbering is evaluated at contract creation time, this table is central to determining the contract number assigned to each new contract document.

Based on the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link. It resolves relationships between contract classification entities and the underlying document sequence generator, rather than acting as a pure hub of a single business concept or a satellite of descriptive attributes.

Key Information Stored

The table contains 20 documented columns in the OKC schema. The most significant are:

• ID — surrogate primary key, enforced by OKC_K_SEQ_LINES_PK. This is the technical identifier and is not a business key candidate for end users.
• LINE_CODE — the line identifier within the autonumbering configuration; a likely candidate for the unique business key when combined with the owning sequence configuration.
• DOC_SEQUENCE_ID — foreign key to FND_DOCUMENT_SEQUENCES, tying the line to the Oracle Applications document sequence that supplies the generated number.
• CLS_CODE and SCS_CODE — the contract class and subclass codes. SCS_CODE carries the documented foreign keys to OKC_CLASSES_B and OKC_SUBCLASSES_B.
• CONTRACT_NUMBER_PREFIX and CONTRACT_NUMBER_SUFFIX — literal text placed before and after the generated number.
• NUMBER_FORMAT_LENGTH — the width to which the sequence number is padded.
• START_SEQ_NO and END_SEQ_NO — the lower and upper bounds of the sequence range.
• MANUAL_OVERRIDE_YN — indicates whether users may override the generated number manually.
• OPERATING_UNIT_ID and BUSINESS_GROUP_ID — multi-org and business group context for the configuration row.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting data security and partitioning.

Common Use Cases and Queries

Typical scenarios include diagnosing why a contract received an unexpected number, reporting on numbering schemes by operating unit, and validating sequence ranges across classes. A representative query joins the lines to the class and subclass reference tables and to the document sequence definition:

• Retrieve active autonumbering lines for a class: SELECT l.id, l.line_code, l.cls_code, l.scs_code, l.contract_number_prefix, l.number_format_length, l.start_seq_no, l.end_seq_no FROM okc.okc_k_seq_lines l WHERE l.cls_code = :class_code;
• Join to document sequences: SELECT l.id, l.line_code, s.name, l.manual_override_yn FROM okc.okc_k_seq_lines l, fnd_document_sequences s WHERE l.doc_sequence_id = s.document_sequence_id;
• Join to class definitions: SELECT l.line_code, c.name AS class_name, l.contract_number_prefix FROM okc.okc_k_seq_lines l, okc.okc_classes_b c WHERE l.scs_code = c.code;

These patterns support contract administration reports, number-gap audits, and post-implementation verification of numbering configuration.

Related Objects

• OKC_CLASSES_B — joined via SCS_CODE; provides the contract class definition.
• OKC_SUBCLASSES_B — joined via SCS_CODE; provides the subclass definition.
• FND_DOCUMENT_SEQUENCES — joined via DOC_SEQUENCE_ID; supplies the underlying sequence generator.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces security grouping.
• OKC_K_SEQ_HEADERS (or equivalent header configuration) — the parent autonumbering setup that these detail lines extend, where used.
• OKC_K_HEADERS / OKC_K_LINES — the contract header and line tables whose numbers are ultimately derived from these lines.