Search Results table - ce.ce_statement_headers




The OKC_TIME_CODE_UNITS_B table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data structure within the Oracle Contracts Core module. This table stores time-based unit definitions used for contract terms, billing schedules, and other time-dependent contractual obligations. It serves as a reference for standardized time units, enabling consistent time calculations across contract management processes.

Table Purpose and Functional Context

The OKC_TIME_CODE_UNITS_B table functions as a master repository for time measurement units in Oracle Contracts. It supports:

  • Standardization of time periods for contract duration calculations
  • Billing cycle definitions in service contracts
  • Milestone scheduling in project contracts
  • Renewal period definitions
This table integrates with multiple Oracle EBS modules including Service Contracts, Project Contracts, and Lease Management.

Key Columns and Structure

The table contains these critical columns:

  • TIME_CODE_UNIT_ID: Primary key identifier
  • TIME_CODE: Unique code representing the time unit (e.g., 'DAY', 'MONTH', 'YEAR')
  • DESCRIPTION: Human-readable description of the time unit
  • START_DATE_ACTIVE and END_DATE_ACTIVE: Date range during which the time unit is valid
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE: Standard Oracle audit columns
  • LAST_UPDATE_LOGIN: Session information for the last update

Technical Implementation

In Oracle EBS 12.1.1 and 12.2.2:

  • The table follows Oracle's Application Object Library (AOL) standards
  • It's owned by the OKC (Oracle Contracts Core) schema
  • Primary key is enforced through the OKC_TIME_CODE_UNITS_B_PK constraint
  • Table is referenced by multiple views including OKC_TIME_CODE_UNITS_V

Integration Points

OKC_TIME_CODE_UNITS_B integrates with:

  • OKC_CONTRACT_TERMS for duration calculations
  • OKC_BILLING_SCHEDULES for payment timing
  • OKC_K_ARTICLES for contract clause validity periods
  • OKC_K_ITEMS for line item scheduling

Customization Considerations

While the table is seeded with standard time units, organizations can:

  • Add custom time units through the API layer
  • Extend functionality via descriptive flexfields
  • Reference in custom contract calculations
Modifications should preserve referential integrity with dependent contract data.

Performance and Maintenance

As a relatively static reference table:

  • It typically requires minimal maintenance
  • Indexing is optimized for the primary key
  • Table growth is generally linear and predictable
Partitioning is not normally required due to small data volume.

Upgrade Implications

Between 12.1.1 and 12.2.2:

  • Table structure remains largely unchanged
  • Custom time units are preserved during upgrades
  • New time codes may be introduced in newer versions

Security Considerations

Access is controlled through:

  • Oracle Function Security
  • Data security policies in Oracle Contracts
  • Standard Oracle user privileges
Direct table modifications should be avoided in favor of approved APIs.