Results for “print_form_type_code”

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

Overview

OKE_PRINT_FORMS_B is a core setup and reference table in the Oracle E-Business Suite Project Contracts (OKE) module. It stores the definitions of print forms used when generating contract documents, such as the layout templates, form types, and validity windows that drive the Contract Terms and print generation process. Each row represents a discrete print form definition that Oracle Projects and Project Contracts can invoke when producing formatted contract output for a given business scenario.

From a Data Vault modeling perspective, this table is heuristically classified as hub-leaning. Its role as the anchor of a business concept — the print form, keyed by the natural business key PRINT_FORM_CODE — resembles a hub. Downstream integrations or data warehouses would typically treat PRINT_FORM_CODE as the enduring business key and attach descriptive satellite content (form type, active dates, attributes) separately.

Key Information Stored

The table is owned by the OKE schema and contains 26 documented columns in the 12.2.2 ETRM metadata. The most significant are:

• PRINT_FORM_CODE — the primary business identifier for the print form; also the single-column primary key component of OKE_PRINT_FORMS_PK.
• PRINT_FORM_TYPE_CODE — classifies the form (for example, which document or contract output category it serves).
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling when the form may be selected or used.
• ZD_EDITION_NAME — an edition-tracking column used in the multi-tenant / editioned data model; it participates in the unique index OKE_PRINT_FORMS_U1 (PRINT_FORM_CODE, ZD_EDITION_NAME).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible, client-configured attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing insert/update provenance.

The surrogate primary key is OKE_PRINT_FORMS_PK on PRINT_FORM_CODE, while OKE_PRINT_FORMS_U1 on (PRINT_FORM_CODE, ZD_EDITION_NAME) serves as the business-key candidate, reflecting the editioning model.

Common Use Cases and Queries

Typical usage centers on setup validation, reporting of available forms, and integration with contract output processes. Example queries include:

• Listing all active print forms for a given date: SELECT print_form_code, print_form_type_code FROM oke_print_forms_b WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1);
• Filtering by form type: SELECT * FROM oke_print_forms_b WHERE print_form_type_code = :type;
• Auditing recent changes via the WHO columns: SELECT print_form_code, last_update_date, last_updated_by FROM oke_print_forms_b WHERE last_update_date > :since;
• Joining to the _K (knowledge/translation) table to resolve the form name for reporting.

Related Objects

The most significant related object documented is OKE_K_PRINT_FORMS, which references OKE_PRINT_FORMS_B via the foreign key OKE_K_PRINT_FORMS.PRINT_FORM_CODE → OKE_PRINT_FORMS_B. This _K table supplies translatable, multilingual descriptive text (the form name/description) keyed to PRINT_FORM_CODE, and the two are almost always queried together to obtain both identity and readable labels. Beyond this direct relationship, the print form definitions integrate logically with contract print generation processes and the OKE contract document setup, though those dependent objects are not explicitly enumerated in the provided metadata.