Results for “oke_k_types_b”

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

Overview

OKE_K_TYPES_B is the contract document type definition table within the OKE (Project Contracts) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table stores the master list of contract document types — the configurable categories such as standard contracts, amendments, change orders, or any user-defined classification used to control how contract documents behave throughout their lifecycle. Each row defines a type code, its active date window, the intent or behavioral class it belongs to, and the approval path to be applied. Because contract headers, approval workflows, and numbering rules all resolve against this table, OKE_K_TYPES_B functions as a foundational setup entity for the Project Contracts application.

From a Data Vault modeling perspective, the heuristic classification of OKE_K_TYPES_B is hub-leaning. The table is dominated by a single business key (K_TYPE_CODE) that is referenced by multiple dependent tables, which is characteristic of a hub. The descriptive attributes on the table (intent, type class, active dates, approval path, and the fifteen DFF attribute columns) could be modeled as satellite content attached to that hub in a Data Vault design. Treat this classification as a modeling suggestion rather than a documented Oracle construct; the physical table is a standard EBS setup table with WHO audit columns and a DFF block.

Key Information Stored

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

• K_TYPE_CODE — the primary key of the table (constraint OKE_K_TYPES_PK) and the business key used by all dependent tables. It is also the single-column unique index OKE_K_TYPES_U1, confirming it as the business-key candidate. Values entered here appear as the contract type selected on contract headers.
• TYPE_CLASS_CODE — classifies the document type (for example, contract versus amendment behavior), driving which processing rules apply.
• INTENT — records the business intent of the type, which influences how the contract is classified and reported.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range during which the type is available for selection. Null end dates typically indicate open-ended availability.
• APPROVAL_PATH_ID — foreign key to OKE_APPROVAL_PATHS, identifying the approval workflow assigned to contracts of this type.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield (DFF) columns used to capture client-specific descriptive information for the document type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns available for traceability of setup changes.

Common Use Cases and Queries

Typical uses include validating active document types for a given date, listing types with their assigned approval path, and joining type information to contract header reporting. For example, to list types active today:

• SELECT k_type_code, type_class_code, intent, start_date_active, end_date_active FROM oke.oke_k_types_b WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
• To resolve the approval path for each type: join OKE_APPROVAL_PATHS on APPROVAL_PATH_ID = APPROVAL_PATH_ID.
• To count contracts per type: join OKE_K_HEADERS on K_TYPE_CODE = K_TYPE_CODE, useful for setup-cleanup analysis of unused types.
• To inspect flexfield usage: query ATTRIBUTE_CATEGORY and populated ATTRIBUTE columns to audit client-specific configuration.

Reporting use cases include setup migration validation, active/inactive type listings for user training material, and impact analysis before disabling a type that has historical contracts.

Related Objects

• OKE_APPROVAL_PATHS — referenced by OKE_K_TYPES_B.APPROVAL_PATH_ID; defines the approval workflow assigned to the document type.
• OKE_K_HEADERS — references OKE_K_TYPES_B via K_TYPE_CODE; stores contract headers and is the primary transactional consumer of this setup table.
• OKE_K_HEADERS_H — history/audit table for contract headers, also referencing K_TYPE_CODE, enabling historical reporting of contracts by type.
• OKE_NUMBER_OPTIONS — references OKE_K_TYPES_B via K_TYPE_CODE; holds numbering rules per contract document type.
• OKE_K_TYPES_PK / OKE_K_TYPES_U1 — the primary key constraint and unique index enforcing uniqueness of K_TYPE_CODE.

Together these relationships establish OKE_K_TYPES_B as a controlling setup hub for contract creation, numbering, and approval behavior in the OKE module.