Results for “okc_span”

50+ results




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

Overview

OKC_SPAN is a core configuration table in the Oracle Contracts (OKC) module, part of the Oracle E-Business Suite Contracts Core product. It defines the legs, stages, or intervals that compose a cycle, capturing the duration of each interval in a designated unit of measure. In the contracting model, a "cycle" typically represents a recurring or sequenced business process such as a billing schedule, a fulfillment or service delivery timeline, a milestone progression, or a renewal cadence. Each row in OKC_SPAN represents a single span — one leg or stage — within that cycle, making this table the structural building block from which cycle definitions are assembled.

From a Data Vault modeling perspective, the FK topology mined from the schema classifies OKC_SPAN as hub-leaning. Its self-referencing foreign key (SPN_ID → OKC_SPAN.SPN_ID) suggests a hierarchical parent-child relationship among spans, which is consistent with the idea that a span may be nested within or sequenced against another span. This classification is a heuristic modeling suggestion rather than a mandated design.

Key Information Stored

The table is owned by the OKC schema and contains 30 documented columns in the 12.2.2 physical schema. The most significant columns are:

  • ID — The surrogate primary key, enforced by OKC_SPAN_PK and also backed by the unique index OKC_SPAN_U1. This is the definitive row identifier.
  • SPN_ID — A self-referencing foreign key to OKC_SPAN, establishing parent-child or sequential relationships between spans. This is the column that gives the table its hierarchical character.
  • TVE_ID — A foreign key to OKC_TIMEVALUES, linking the span to a time-value definition that governs how the interval is measured or anchored.
  • NAME — The descriptive label for the span (for example, "Stage 1" or "Billing Interval"), used for identification and reporting.
  • DURATION — The length of the span, the core business attribute describing how long the interval lasts.
  • UOM_CODE — The unit of measure in which DURATION is expressed (for example, days, months), giving the duration its business meaning.
  • ACTIVE_YN — A status flag indicating whether the span is currently active and therefore eligible for use.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by the EBS framework to detect concurrent updates.
  • SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, used for multi-org and data-security filtering.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns for customer-defined extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard who-columns that capture audit and change history.

The surrogate key ID is distinct from any business-key candidate; the only documented unique index is OKC_SPAN_U1 on ID, meaning no alternate natural key is formally enforced in the schema.

Common Use Cases and Queries

Typical uses involve retrieving active spans for a cycle, computing total cycle duration, and reconstructing span hierarchies. A representative query returning active spans with their unit of measure is:

  • SELECT id, spn_id, name, duration, uom_code FROM okc_span WHERE active_yn = 'Y';
  • Joining to the time-values table to resolve timing definitions: SELECT s.id, s.name, s.duration, t.* FROM okc_span s, okc_timevalues t WHERE s.tve_id = t.id;
  • Aggregating total span duration per parent: SELECT spn_id, SUM(duration) FROM okc_span GROUP BY spn_id;
  • Traversing the hierarchy using the self-referencing key to list child spans beneath a parent span.

Reporting scenarios include contract cycle configuration audits, billing or service schedule validation, and identifying stale or inactive span definitions.

Related Objects

The following objects are most significant in relation to OKC_SPAN, based on the documented foreign-key relationships:

  • OKC_TIMEVALUES — Referenced via OKC_SPAN.TVE_ID; supplies the time-value definition associated with the span.
  • OKC_TIMEVALUES_B — The base table variant referenced via OKC_TIMEVALUES_B.SPN_ID, providing the underlying time-value records.
  • OKC_SPAN (self) — Referenced via OKC_SPAN.SPN_ID, modeling parent-child span relationships.
  • FND_SECURITY_GROUPS — Referenced via OKC_SPAN.SECURITY_GROUP_ID, controlling row-level security and multi-org access.
  • OKC_SPAN_PK / OKC_SPAN_U1 — The primary key constraint and unique index that guarantee row uniqueness on ID.

Together these relationships place OKC_SPAN within the Contracts Core cycle-definition subsystem, linking span structure to time-value definitions and to the EBS security framework.