Search Results oke_terms_b




Overview
Explore in AI Chat

Overview

The OKE_TERMS_B table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as the primary repository for storing master definitions of contract terms and conditions. These terms represent standardized clauses, deliverables, payment schedules, and other contractual stipulations that can be associated with project contracts. The table's role is foundational, enabling the consistent definition, reuse, and enforcement of business rules and legal requirements across all contracts managed within the system. Its existence is critical for maintaining contractual integrity and streamlining the contract authoring process in releases 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the primary key and standard EBS table conventions indicate the core data attributes. The table is uniquely identified by the TERM_CODE column, which is the primary key for the OKE_TERMS_PK constraint. This code acts as a unique identifier for each term definition. Typically, such a table would also store descriptive information like a term name or description, its effective dates (START_DATE_ACTIVE, END_DATE_ACTIVE), and type classifications (e.g., DELIVERABLE, PAYMENT, GENERAL). It likely includes columns for tracking creation and last update information (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and a numeric surrogate key (TERM_ID). The "_B" suffix denotes it as the base table for a key flexfield structure, suggesting it holds the core segments that define the term.

Common Use Cases and Queries

This table is central to operations involving the setup and application of contract terms. A common use case is the generation of a list of all active, standard terms available for assignment to a contract. Administrators may query this table to maintain the term library, while contract managers use it to select appropriate terms during contract creation. For reporting, it is frequently joined to transactional tables like OKE_K_HEADERS_B to analyze which terms are applied across the contract portfolio. A typical query pattern would be:

  • Selecting active terms: SELECT term_code, name FROM oke_terms_b WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Finding terms used on a specific contract: SELECT ot.term_code, ot.name FROM oke_terms_b ot, oke_k_terms ok WHERE ok.term_id = ot.term_id AND ok.k_header_id = &header_id;

Related Objects

As a base table, OKE_TERMS_B has several key dependencies. It is directly referenced by transactional tables that record the instantiation of a master term on a specific contract, such as OKE_K_TERMS. The primary key (TERM_CODE) is likely referenced via foreign key relationships in these child tables. It is also the basis for key flexfield views (e.g., OKE_TERMS_VL) which provide a localized, descriptive view of the data for application forms and reports. Furthermore, it is integral to the Project Contracts' public APIs (e.g., OKC_TERMS_PUB), which provide programmatic control for creating, updating, and assigning terms to contracts, ensuring all data manipulation follows established business logic.