Results for “oke_k_form_headers_u1”

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

Overview

OKE_K_FORM_HEADERS is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores print form header information associated with Project Contracts output, capturing the header-level attributes required when contract-related forms — such as printed contract documents, order forms, and related attachments — are generated and tracked. The table sits at the intersection of the contract structure (headers and lines), the print form definitions, and the deliverable records that drive contractual obligations.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries its own surrogate primary key (FORM_HEADER_ID) while holding foreign keys to OKE_K_PRINT_FORMS, OKE_K_LINES, and OKE_K_DELIVERABLES_B, indicating that it records descriptive, context-dependent attributes about a print form instance rather than acting as a pure hub or link. Downstream, OKE_K_FORM_LINES references this table, reinforcing its role as a header-level satellite within the contract print hierarchy.

Key Information Stored

The table is physically wide, with 168 documented columns. The most significant columns are:

• FORM_HEADER_ID — surrogate primary key (OKE_K_FORM_HEADERS_PK) and the parent key referenced by OKE_K_FORM_LINES.
• K_HEADER_ID — foreign key to OKE_K_PRINT_FORMS, identifying the print form definition this header belongs to.
• PRINT_FORM_CODE — code identifying the print form; combined with K_HEADER_ID and FORM_HEADER_NUMBER in unique index OKE_K_FORM_HEADERS_U2, which serves as the primary business-key candidate.
• FORM_HEADER_NUMBER — sequential or user-facing number distinguishing multiple headers under the same print form.
• FORM_DATE — the effective date associated with the printed form header.
• STATUS_CODE — lifecycle state of the form header (for example, draft, active, or released).
• K_LINE_ID — foreign key to OKE_K_LINES, tying the header to a specific contract line.
• DELIVERABLE_ID — foreign key to OKE_K_DELIVERABLES_B, linking the header to the deliverable it documents.
• TEXT01–TEXT50, NUMBER01–NUMBER50, DATE01–DATE50 — descriptive flexfield-style attribute columns used to store customer-specific header information without schema changes.
• REFERENCE1–REFERENCE5 — generic reference columns for external identifiers or cross-system pointers.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Note that OKE_K_FORM_HEADERS_U1 on FORM_HEADER_ID duplicates the primary key and is effectively a unique constraint supporting the surrogate key.

Common Use Cases and Queries

Typical use cases include reporting on generated contract forms, reconciling form headers against their lines, and auditing deliverables tied to printed contract documents. A common join pattern retrieves header and line detail:

SELECT h.FORM_HEADER_ID, h.FORM_HEADER_NUMBER, h.STATUS_CODE, l.FORM_LINE_ID
FROM OKE_K_FORM_HEADERS h, OKE_K_FORM_LINES l
WHERE h.FORM_HEADER_ID = l.FORM_HEADER_ID
AND h.PRINT_FORM_CODE = :p_code;

To reconcile headers with their source contract lines and print form definitions:

SELECT h.FORM_HEADER_ID, p.PRINT_FORM_CODE, kl.K_LINE_ID, h.FORM_DATE
FROM OKE_K_FORM_HEADERS h, OKE_K_PRINT_FORMS p, OKE_K_LINES kl
WHERE h.K_HEADER_ID = p.K_HEADER_ID
AND h.K_LINE_ID = kl.K_LINE_ID;

Reporting queries frequently filter on STATUS_CODE and FORM_DATE, and join to OKE_K_DELIVERABLES_B for deliverable-level summaries. Because of the 50 text/number/date placeholder columns, reports should reference only the attributes configured for the specific implementation, since unused columns remain null.

Related Objects

• OKE_K_PRINT_FORMS — joined via OKE_K_FORM_HEADERS.K_HEADER_ID; defines the print form master record.
• OKE_K_LINES — joined via OKE_K_FORM_HEADERS.K_LINE_ID; provides contract line context.
• OKE_K_DELIVERABLES_B — joined via OKE_K_FORM_HEADERS.DELIVERABLE_ID; links headers to contractual deliverables.
• OKE_K_FORM_LINES — references OKE_K_FORM_HEADERS.FORM_HEADER_ID; holds the detail lines belonging to each header.

These four relationships form the core dependency graph for the table, governing both referential integrity and the standard query paths used in Project Contracts print form reporting.