Results for “oke_k_print_forms_v”

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

Overview

OKE_K_PRINT_FORMS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Project Contracts (OKE) module. Its documented description is "Print Forms View", and it serves as a denormalized, read-only presentation layer that joins a transactional print forms record table to its multilingual, translated definition. The view exposes the association between a contract header or line and the print forms configured for it, enriched with descriptive and translation-aware attributes. In Oracle EBS 12.1.1 and 12.2.2 the object is registered as a VALID view, confirming it is a supported dictionary component rather than a custom artifact. Because it consolidates coded foreign keys with human-readable names and date-range information into a single result set, it is a convenient source for reporting, concurrent program extracts, and integration interfaces that need contract print form data without performing their own joins or resolving translated lookup values.

Underlying Base Objects

The ETRM metadata documents two referenced base objects. The first is OKE_K_PRINT_FORMS, exposed as a synonym, which is the primary driving table. It is keyed by K_HEADER_ID and K_LINE_ID and stores the contract-level print form assignment, including the PRINT_FORM_CODE foreign key and the operational flags (REQUIRED_FLAG, COMPLETED_FLAG, CUSTOMER_FURNISHED_FLAG). The second is OKE_PRINT_FORMS_VL, itself a view and the "MLS" (multi-lingual support) form of the print forms definition. The VL object typically resolves to underlying _TL (translations) and _B (base) tables and provides the print form name and description in the session's language. The view joins these two objects on the equality condition K.PRINT_FORM_CODE = V.PRINT_FORM_CODE, so each row pairs one contract print form assignment with its single translated definition record.

Key Columns

The view exposes a broad combination of identifiers, descriptive attributes, flags, and standard audit columns. The K.ROWID column is carried through from the base table and permits direct row addressing. K_HEADER_ID and K_LINE_ID identify the owning contract header and line respectively. PRINT_FORM_CODE is the decoded foreign key, while PRINT_FORM_NAME and DESCRIPTION are supplied from the VL object in the current language. START_DATE_ACTIVE and END_DATE_ACTIVE establish the effective period of the print form definition. PRINT_FORM_TYPE_CODE and PRINT_FORM_TYPE_NAME classify the form. The flags REQUIRED_FLAG, COMPLETED_FLAG, and CUSTOMER_FURNISHED_FLAG indicate whether a form is mandatory, whether it has been completed, and whether it is customer-supplied. The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) support auditing. The ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns provide the flexible descriptive flexfield (DFF) segment values captured on the assignment.

Common Use Cases and Queries

Typical uses include reporting outstanding contract print forms, driving checklist extracts, and feeding downstream document-management integrations. Because the view already joins the translated definition, queries avoid a separate lookup against the VL object.

• List all required, incomplete print forms for a contract header:
  SELECT k_header_id, k_line_id, print_form_name, required_flag, completed_flag FROM apps.oke_k_print_forms_v WHERE k_header_id = :p_header_id AND required_flag = 'Y' AND completed_flag = 'N';
• Retrieve the print form name and effective dates for an assignment:
  SELECT k_line_id, print_form_code, print_form_name, start_date_active, end_date_active FROM apps.oke_k_print_forms_v WHERE k_line_id = :p_line_id;
• Filter by form type and customer-furnished status for reconciliation:
  SELECT k_header_id, print_form_type_name, customer_furnished_flag FROM apps.oke_k_print_forms_v WHERE print_form_type_code = :p_type AND customer_furnished_flag = 'Y';

Consumers should note that the view is descriptive and non-key-preserving across the join; it should be treated as read-only and never used as a DML target. The carried ROWID refers to OKE_K_PRINT_FORMS, so updates must be directed to that base table rather than to the view.