Search Results okc_span




Overview
Explore in AI Chat

Overview

The OKC_SPAN table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for releases 12.1.1 and 12.2.2. It serves as a master definition table for modeling the temporal structure of contract cycles. As per its official description, it defines the legs, stages, or intervals that compose a cycle, including their duration in a designated time unit. In practical terms, this table is essential for configuring and managing complex, recurring contractual timelines, such as payment schedules, delivery milestones, or review periods. It provides the foundational building blocks for time-based events and obligations within the Contracts application, enabling systematic tracking and execution of contractual terms over time.

Key Information Stored

The table's primary purpose is to store definitions of time spans. While the specific column list is not fully detailed in the provided metadata, the structure and foreign key relationships indicate critical data points. The primary key column is ID. A central column is SPN_ID, which acts as a unique identifier for a span definition and is referenced in self-referential and child table relationships. The table also links to the OKC_TIMEVALUES table via the TVE_ID foreign key, which associates the span with specific time values or measurements. This connection is crucial for storing the span's duration and its designated time unit (e.g., days, months, years). The self-referential foreign key on SPN_ID suggests the table may support hierarchical or linked span structures, allowing for the creation of complex, multi-level cycles.

Common Use Cases and Queries

A primary use case is the setup and analysis of contract payment terms or renewal schedules. For instance, a three-year contract with annual payments would be modeled using spans defining each yearly leg. Common reporting needs include listing all defined spans within the system or analyzing the duration of spans used in active contracts. Sample SQL patterns would involve joining OKC_SPAN with related tables like OKC_TIMEVALUES to get a complete picture of the cycle definition.

  • Query to retrieve span definitions with their associated time values:
    SELECT s.id, s.spn_id, t.time_value, t.uom_code FROM okc_span s, okc_timevalues t WHERE s.tve_id = t.id;
  • Identifying hierarchical span structures:
    SELECT parent.spn_id AS parent_span, child.spn_id AS child_span FROM okc_span parent, okc_span child WHERE child.spn_id = parent.spn_id AND child.id != parent.id;

Related Objects

The OKC_SPAN table is centrally connected to several other key Contracts Core tables, as evidenced by its foreign key constraints. Its most direct relationship is with the OKC_TIMEVALUES and OKC_TIMEVALUES_B tables, which store the quantitative duration and unit of measure for each span. The self-referential foreign key indicates a relationship within the OKC_SPAN table itself, likely for building parent-child span hierarchies. Furthermore, the metadata shows that OKC_TIMEVALUES also holds a foreign key back to OKC_SPAN.SPN_ID, confirming a bidirectional relationship essential for the time-value data model. These relationships underscore that OKC_SPAN is a master definition table upon which the detailed time valuation and scheduling logic within Oracle Contracts depends.