Search Results procurement contracts




The OKC.OKC_BUS_DOC_TYPES_B table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a fundamental data structure within the Oracle Contracts Core module. This table serves as the repository for business document type definitions, which are critical for classifying and managing various contract and agreement documents across the Oracle Contracts application. Below is a detailed technical summary of its purpose, structure, and key attributes.

Purpose and Functional Context

The OKC_BUS_DOC_TYPES_B table stores metadata about business document types, enabling Oracle Contracts to differentiate between contracts, amendments, renewals, and other agreement types. These document types drive workflow behavior, validation rules, and reporting categorization. The table is part of the Oracle Contracts Core schema (OKC) and is tightly integrated with other key tables like OKC_BUS_DOC_TYPES_TL (for translated descriptions) and OKC_CONTRACT_DOCS (for document instances).

Key Columns and Structure

The table includes the following critical columns:

  • DOC_TYPE_ID: Primary key, uniquely identifying each document type.
  • DOC_TYPE_CODE: A short, unique identifier (e.g., "STANDARD" for standard contracts).
  • START_DATE and END_DATE: Define the active period for the document type.
  • CATEGORY_CODE: Groups document types into broader categories (e.g., "SALES" or "PURCHASE").
  • ALLOW_AMENDMENTS_FLAG: Controls whether amendments are permitted for this document type.
  • ALLOW_RENEWALS_FLAG: Determines if renewal workflows apply.
  • SECURITY_GROUP_ID: Supports multi-org access control.

Integration with Oracle EBS Modules

The table integrates with:

  • Oracle Workflow: Document types trigger specific approval workflows.
  • Oracle Approval Management (AME): Rules may be conditioned on document types.
  • Oracle Reports: Enables filtering contracts by type in analytics.

Technical Considerations

For implementations, note:

  • The table is seed-data heavy, with Oracle-provided document types that can be extended but not modified.
  • Custom document types require careful alignment with existing CATEGORY_CODE values to ensure UI consistency.
  • In EBS 12.2.2, the table supports Edition-Based Redefinition (EBR), allowing online patching.

Common Use Cases

Typical operations involving this table include:

  • Configuring new contract types for industry-specific requirements.
  • Extending expiration logic via the END_DATE column.
  • Driving conditional clauses in Contract Expert rules.

Performance and Indexing

The table is optimized for frequent reads but minimal writes. Key indexes include:

  • Primary key index on DOC_TYPE_ID.
  • Unique index on DOC_TYPE_CODE.
  • Non-unique indexes on CATEGORY_CODE and date ranges for reporting.

In summary, OKC_BUS_DOC_TYPES_B is a metadata cornerstone for Oracle Contracts, enabling precise document classification and process orchestration. Its design reflects Oracle EBS's emphasis on configurability while maintaining data integrity through strict code-based relationships.