Search Results oke_k_types_b




Overview

The OKE_K_TYPES_B table is a core master data table within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as the definitive repository for contract document types, which are fundamental to classifying and governing the lifecycle of all contractual agreements within the system. Each record defines a unique type of contract document, such as a standard contract, amendment, or change order. This table is central to the application's configuration, as the contract type dictates critical behaviors including approval workflows, numbering sequences, and the set of rules and validations applied to contract headers and lines. Its role is to provide a controlled, referential foundation upon which all transactional contract data is built and managed.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign keys indicate the essential data relationships. The primary key is the K_TYPE_CODE, a unique identifier for each contract document type. A critical foreign key column is APPROVAL_PATH_ID, which links the contract type to a specific approval workflow defined in the OKE_APPROVAL_PATHS table. Other columns typically found in this table, based on its function, include a name and description for the type, indicators for enabling specific features (like funding or deliverables), and references to default numbering schemes. The '_B' suffix denotes it as the base table for a translatable entity, implying the existence of a corresponding _TL (translation) table for multilingual support.

Common Use Cases and Queries

This table is primarily referenced for setup validation, operational reporting, and data integrity checks. Common scenarios include generating a list of all active contract types for a setup review, identifying which contract types use a specific approval path, or troubleshooting issues where a contract fails to pick up the correct numbering sequence. A typical query would join OKE_K_TYPES_B with its related transactional and setup tables.

  • List all contract types with their approval paths:
    SELECT kt.k_type_code, kt.name, ap.name AS approval_path_name FROM oke.oke_k_types_b kt, oke.oke_approval_paths ap WHERE kt.approval_path_id = ap.approval_path_id(+);
  • Find contracts of a specific type:
    SELECT kh.contract_number, kh.title FROM oke.oke_k_headers kh WHERE kh.k_type_code = 'STANDARD';

Related Objects

The OKE_K_TYPES_B table has defined relationships with several key transactional and setup tables, as per the provided metadata. The primary foreign key relationship is with OKE_APPROVAL_PATHS via the APPROVAL_PATH_ID column. It is the parent table for the main contract header entities: OKE_K_HEADERS and its history table OKE_K_HEADERS_H, both linked via the K_TYPE_CODE column. This relationship ensures every contract is associated with a valid, configured type. Furthermore, it is referenced by OKE_NUMBER_OPTIONS (also via K_TYPE_CODE), which stores the numbering rules specific to each contract document type. These relationships underscore its role as a cornerstone of the Project Contracts data model.