Results for “oke_k_print_forms”

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

Overview

OKE_K_PRINT_FORMS is a table in the OKE (Project Contracts) product module of Oracle E-Business Suite, maintained under the OKE schema. It stores the association between a project contract header and line and the specific print form used to render that contract for output. In contract authoring and printing workflows, this table acts as the junction that determines which contract document template applies to a given header or line combination.

From a Data Vault modeling perspective (heuristic, mined from the foreign key structure), this table is classified as satellite-leaning. Its composite uniqueness is anchored on the business keys K_HEADER_ID, K_LINE_ID, and PRINT_FORM_CODE rather than on a single surrogate identifier, which is characteristic of a dependent, descriptive relationship table rather than an independent hub.

Key Information Stored

The table contains 27 documented columns. The most significant columns include:

• K_HEADER_ID – References the contract header in OKE_K_HEADERS; identifies the parent contract.
• K_LINE_ID – References the contract line in OKE_K_LINES; scopes the form to a specific line.
• PRINT_FORM_CODE – References OKE_PRINT_FORMS_B; identifies the print form (template) associated with the contract.
• REQUIRED_FLAG – Indicates whether the print form is mandatory for the contract.
• CUSTOMER_FURNISHED_FLAG – Indicates whether the form content is customer-supplied.
• COMPLETED_FLAG – Tracks whether the associated form has been completed.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – The standard EBS descriptive flexfield (DFF) columns for extensible attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit (WHO) columns.

The documented unique index is OKE_K_PRINT_FORMS_U1 on (K_HEADER_ID, PRINT_FORM_CODE, K_LINE_ID), which represents the business-key candidate. The primary key is documented as OKE_K_PRINT_FORMS_UK01 on (K_HEADER_ID, K_LINE_ID, PRINT_FORM_CODE). No single-column surrogate key is present; uniqueness is composite and business-derived.

Common Use Cases and Queries

Typical scenarios include determining which print forms are attached to a contract, auditing mandatory or customer-furnished forms, and driving contract output generation. A representative query joining to the header and line tables:

• SELECT pf.K_HEADER_ID, pf.K_LINE_ID, pf.PRINT_FORM_CODE, pf.REQUIRED_FLAG, pf.CUSTOMER_FURNISHED_FLAG, pf.COMPLETED_FLAG FROM OKE.OKE_K_PRINT_FORMS pf WHERE pf.K_HEADER_ID = :header_id;
• Join to OKE_PRINT_FORMS_B to retrieve form descriptions: SELECT pf.PRINT_FORM_CODE, fb.NAME FROM OKE.OKE_K_PRINT_FORMS pf, OKE.OKE_PRINT_FORMS_B fb WHERE pf.PRINT_FORM_CODE = fb.PRINT_FORM_CODE;
• Find contracts with incomplete required forms: SELECT K_HEADER_ID, K_LINE_ID FROM OKE.OKE_K_PRINT_FORMS WHERE REQUIRED_FLAG = 'Y' AND COMPLETED_FLAG = 'N';

These patterns support reporting on print form assignments, compliance checks, and downstream document generation processes.

Related Objects

• OKE_K_HEADERS – Parent contract header; joined via K_HEADER_ID.
• OKE_K_LINES – Parent contract line; joined via K_LINE_ID.
• OKE_PRINT_FORMS_B – Print form definition; joined via PRINT_FORM_CODE.
• OKE_K_FORM_HEADERS – References this table via (K_HEADER_ID, K_LINE_ID, PRINT_FORM_CODE), representing derived form header output.

Together these relationships position OKE_K_PRINT_FORMS as the linking structure that binds contract headers, lines, and print form definitions within the Project Contracts printing framework.