Results for “term_code”

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

Overview

OKE_TERMS_B is a foundational table in the Oracle EBS Project Contracts (OKE) module. It stores the definition and metadata for contract terms used across the Project Contracts application, including the term codes that drive term behavior, term type classification, and lookup validation. In Oracle EBS 12.1.1 and 12.2.2, this table sits at the core of the contract-terms configuration layer, providing the reference definitions that user contracts, templates, and clauses ultimately depend on when terms are authored, defaulted, or validated.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault model. This suggests the table functions as an independent reference entity rather than participating in a parent-child satellite relationship. Its primary key, OKE_TERMS_PK, is defined on TERM_CODE, confirming TERM_CODE as the bearer of business meaning. A unique index, OKE_TERMS_U1 (TERM_CODE, ZD_EDITION_NAME), reinforces the surrogate/business-key distinction by introducing edition-awareness into uniqueness enforcement.

Key Information Stored

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

• TERM_CODE — The primary key and the attribute most frequently searched. It uniquely identifies each contract term definition and is the value users look up when they search for "term_code".
• TERM_TYPE_CODE — Classifies the term (for example, categorizing terms by behavioral or functional type), enabling filtering and grouping in reporting.
• USER_DEFINED_FLAG — Indicates whether the term is seeded system data or user-created, which is essential for upgrade and customization analysis.
• VIEW_APPLICATION_ID — Associates the term with a specific application context, supporting multi-application term registration.
• LOOKUP_TYPE — Links the term to a lookup type used for validation or value-list generation.
• ZD_EDITION_NAME — Supports edition-based redefinition (EBR), allowing multiple editions of the same term code to coexist during online patching.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit and concurrency columns tracking who created and last modified each row.

The primary key (TERM_CODE) is the surrogate identifier documented for joins, while the unique index OKE_TERMS_U1 establishes (TERM_CODE, ZD_EDITION_NAME) as the effective business key under editioning.

Common Use Cases and Queries

Typical use cases include validating that a term code exists before contract authoring, reporting on user-defined versus seeded terms, and resolving a term's type and lookup configuration for downstream processing. A direct lookup by term code is the most common pattern:

• SELECT term_code, term_type_code, user_defined_flag, lookup_type FROM oke.oke_terms_b WHERE term_code = :p_term_code;
• SELECT term_code, term_type_code FROM oke.oke_terms_b WHERE user_defined_flag = 'Y' ORDER BY term_code;
• SELECT term_code, view_application_id, lookup_type FROM oke.oke_terms_b WHERE term_type_code = :p_type;

These queries support configuration audits, migration validation between 12.1.1 and 12.2.2, and reporting extracts of term metadata. Because editioning applies, queries in a 12.2.2 environment should account for ZD_EDITION_NAME when uniqueness or historical comparison matters.

Related Objects

OKE_TERMS_B is referenced by the tables that store contractual term instances and by the messaging layer that maps term codes to interface values. The most significant related objects are:

• OKE_TERMS_TL — Translation table joined on TERM_CODE to retrieve language-specific term names and descriptions.
• OKE_TERMS_VL — The view combining base and translation rows, commonly used for value lists.
• OKE_CONTRACT_TERMS — Contract-level term instances joined on TERM_CODE.
• OKE_TERMS_INTERFACE — Interface staging table referencing TERM_CODE for inbound term loading.
• OKE_TERMS_CLASSES — Classifies terms and joins on TERM_CODE for categorization.
• OKE_TERMS_USAGES — Tracks where terms are used, referencing TERM_CODE.

Collectively, these relationships confirm OKE_TERMS_B as the authoritative reference source for term definitions within Oracle Project Contracts.