Results for “line_code”

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

Overview

OKC_K_SEQ_HEADER is a configuration table within the Contracts Core (OKC) product schema of Oracle E-Business Suite. As documented in the ETRM repository, it "holds the configuration rules for Autonumbering setup." In practical terms, the table governs how contract numbers and related document identifiers are generated automatically when users create contracts in the Oracle Contracts module. Rather than storing transactional contract data, OKC_K_SEQ_HEADER defines the header-level parameters of each autonumbering scheme — the controlling record to which sequence lines and process definitions are attached.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This heuristic reflects the table's role as a descriptive, configuration-oriented structure that carries attributes and flags around a defined process context rather than acting as a pure hub of business keys or a link between entities. Modelers designing an enterprise data warehouse over EBS should consider treating OKC_K_SEQ_HEADER as a satellite of the referenced process definition.

Key Information Stored

The table contains 14 documented columns. The most functionally significant are:

• PDF_ID — Foreign key to OKC_PROCESS_DEFS_B. This ties the autonumbering header to a specific process definition, forming the primary logical linkage of the record.
• LINE_CODE — The identifier applied to the sequence lines governed by this header, used when assembling the generated number.
• USER_FUNCTION_YN — Indicates whether a user-defined function participates in generating the number.
• MANUAL_OVERRIDE_YN — Controls whether users may manually override the automatically generated value.
• SITE_YN — Determines whether the setup applies at the site level.
• CLS_SCS_NONE — A class/succession control flag influencing how numbering is resolved.
• BG_OU_NONE — Relates to business group or operating unit scoping of the numbering rule.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF framework.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard WHO-column tracking.

The documented metadata does not explicitly identify a surrogate primary key column; the operative business linkage is through PDF_ID combined with the security grouping.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include auditing which process definitions have autonumbering enabled, verifying manual override policies, and confirming that site-level versus operating-unit-level configuration is applied correctly.

A representative query joins the header to its process definition:

• SELECT h.pdf_id, h.line_code, h.manual_override_yn, h.site_yn, p.process_name FROM okc_k_seq_header h, okc_process_defs_b p WHERE h.pdf_id = p.id;
• Security-aware extracts should include h.security_group_id in the WHERE clause to respect multi-org access.
• Change-tracking reports filter on last_update_date to detect recent configuration modifications.

Related Objects

• OKC_PROCESS_DEFS_B — Referenced via PDF_ID; the parent process definition that the autonumbering header configures.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs data access partitioning.
• OKC_K_SEQ_LINES — Sibling table holding the individual line segments that compose the generated number, tied to this header.
• OKC_K_HEADERS — The transactional contract header where generated numbers are ultimately stored.
• OKC_K_LINES — Contract lines that inherit numbering from the header configuration.
• OKC_AUTO_NUMBERING APIs — PL/SQL packages that read these rules at runtime to produce sequence values.