Search Results oke_number_options




Overview
Explore in AI Chat

Overview

The OKE_NUMBER_OPTIONS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. Its primary function is to store and manage the numbering configuration rules for contract document types. This table is essential for defining the automatic numbering sequences applied to key contract documents, such as sales or purchase agreements, ensuring consistent and controlled document identification across the enterprise. It operates as a child table to the contract document type master (OKE_K_TYPES_B), linking specific numbering options to each defined contract type and its transaction direction (buy or sell).

Key Information Stored

The table's structure is defined by its composite primary key and the associated attributes that govern numbering behavior. The key columns include:

  • K_TYPE_CODE: The unique identifier for a contract document type, linking directly to the OKE_K_TYPES_B table. This is part of the primary key.
  • BUY_OR_SELL: A flag indicating the transaction direction (e.g., 'B' for Buy/Purchase contracts, 'S' for Sell/Sales contracts). This completes the primary key, allowing distinct numbering rules for purchase and sales contracts within the same document type.
  • Additional columns (implied by the table's purpose) typically store configuration details such as the numbering method (automatic or manual), the prefix, the starting number, and the last used number for the sequence. These specific column names are not detailed in the provided metadata but are standard for such a numbering control table.

Common Use Cases and Queries

This table is central to setup and configuration tasks within Project Contracts. A primary use case is during the implementation phase, where administrators define how contract numbers are generated for each document type. It is also critical for troubleshooting numbering issues, such as gaps in sequences or incorrect prefixes appearing on contracts. Common queries involve joining with the document type table to review the complete setup.

Sample SQL to list all numbering options for sales contracts:

SELECT kt.name TYPE_NAME,
       no.k_type_code,
       no.buy_or_sell
FROM   oke_number_options no,
       oke_k_types_b kt
WHERE  no.k_type_code = kt.k_type_code
AND    no.buy_or_sell = 'S'
ORDER BY kt.name;

Reporting use cases include auditing numbering configurations and generating documentation for the contract numbering scheme used across business units.

Related Objects

The OKE_NUMBER_OPTIONS table has a direct and documented dependency on the contract document type master table. The key relationships are:

  • Primary Key: OKE_NUMBER_OPTIONS_PK on (K_TYPE_CODE, BUY_OR_SELL).
  • Foreign Key (References): The K_TYPE_CODE column is a foreign key that references the OKE_K_TYPES_B table. This enforces referential integrity, ensuring that a numbering option cannot exist without a valid, predefined contract document type.

This table is a foundational component for the contract creation process, and its data is likely accessed by core Project Contracts APIs and forms responsible for generating new contract document numbers.