Results for “form_header_id”

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

Overview

OKE_K_FORM_LINES is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores line-level information used when the application prints contract-related forms, such as printed contract documents, terms deliverables, and formatted output generated from Project Contracts data. Each row represents a single printable line within a form identified by its parent header record, carrying the resolved display values that the forms engine renders onto the page.

In Data Vault modeling terms, the FK structure mined from this table suggests a satellite-leaning classification. The table is anchored to a parent header (OKE_K_FORM_HEADERS) rather than introducing new business entities of its own, which is characteristic of satellite behavior. It should nonetheless be treated as a modeling suggestion rather than a definitive architectural directive.

Key Information Stored

The table contains 165 documented columns, of which the most significant are the key columns and the generic attribute columns that hold rendered print values. The surrogate/primary key, OKE_K_FORM_LINES_PK, is composed of FORM_HEADER_ID and FORM_LINE_NUMBER. A parallel unique index, OKE_K_FORM_LINES_U1 (FORM_HEADER_ID, FORM_LINE_NUMBER), serves as the business-key candidate and enforces uniqueness of the line sequence within a header.

• FORM_HEADER_ID — foreign key to the parent print form header; determines which form the line belongs to.
• FORM_LINE_NUMBER — sequential line number within the header; the user search term ("form_line_number") maps directly to this column. Together with FORM_HEADER_ID it forms the primary key.
• K_HEADER_ID — reference to the OKE_K_HEADERS contract header that sourced the line.
• K_LINE_ID — reference to the OKE_K_LINES contract line that sourced the line.
• DELIVERABLE_ID — optional link to the deliverable associated with the printed line.
• REFERENCE1 through REFERENCE5 — user-extensible reference attributes used to carry contextual values onto the printed form.
• TEXT01–TEXT50, NUMBER01–NUMBER50, DATE01–DATE50 — generic typed attribute columns holding formatted print values.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include custom print forms, deliverable reporting, contract output reconciliation, and debugging missing or misordered printed lines. A basic query retrieves all lines for a given header in sequence:

• SELECT FORM_LINE_NUMBER, TEXT01, TEXT02, NUMBER01
FROM OKE.OKE_K_FORM_LINES
WHERE FORM_HEADER_ID = :p_header_id
ORDER BY FORM_LINE_NUMBER;

To trace a print line back to its source contract, join on the mined foreign keys:

• SELECT fl.FORM_LINE_NUMBER, kh.CONTRACT_NUMBER, kl.LINE_NUMBER
FROM OKE.OKE_K_FORM_LINES fl
JOIN OKE.OKE_K_HEADERS kh ON fl.K_HEADER_ID = kh.K_HEADER_ID
JOIN OKE.OKE_K_LINES kl ON fl.K_LINE_ID = kl.K_LINE_ID
WHERE fl.FORM_HEADER_ID = :p_header_id;

Reporting scenarios frequently aggregate the generic attribute columns to validate printed content or map form output against contract terms for auditing.

Related Objects

The following related objects are the most significant for dependent logic, joins, or integration:

• OKE_K_FORM_HEADERS — parent header; joined on FORM_HEADER_ID. Defines the form instance owning these lines.
• OKE_K_HEADERS — source contract header; joined on K_HEADER_ID.
• OKE_K_LINES — source contract line; joined on K_LINE_ID.
• OKE_K_FORM_LINES_PK / _U1 — indexes enforcing primary and unique key integrity.
• Deliverable master data — reached through DELIVERABLE_ID for reporting on printed deliverable lines.