Search Results okc_timevalues_bh




Overview
Explore in AI Chat

Overview

The OKC_TIMEVALUES_BH table is a history (audit) table owned by the OKC schema in Oracle E-Business Suite, delivered under the OKC – Contracts Core product. Its documented purpose is to retain historical versions of records from the base table OKC_TIMEVALUES_B. In Oracle EBS Contracts, time values define the temporal attributes attached to contract terms—durations, offsets, and date/time components used when computing effective dates, milestones, and term scheduling. The _BH suffix is the standard Oracle EBS convention for a "before image" history table, capturing rows as they existed prior to an update or delete.

From a data-modeling perspective, the supplied relationship data classifies this object as standalone using the heuristic Data Vault classification. Under Data Vault modeling conventions this would suggest treatment as a satellite, since the table stores descriptive, versioned attributes keyed to the parent entity's identifier and major version rather than capturing a many-to-many relationship (link) or forming an independent business hub. This classification should be regarded as a modeling suggestion rather than a documented Oracle designation.

Key Information Stored

The table contains 48 documented columns, mirroring the column set of OKC_TIMEVALUES_B with the addition of history-version tracking. The most significant columns include:

  • ID and MAJOR_VERSION — together forming the composite primary key OKC_TIMEVALUES_BH_PK. The ID is the surrogate key referencing the base entity; MAJOR_VERSION distinguishes historical revisions of the same row.
  • OKC_TIMEVALUES_BH_U1 (ID, MAJOR_VERSION) — documented as a unique index and therefore the business-key candidate for the history record.
  • OBJECT_VERSION_NUMBER — supports optimistic locking, ensuring concurrent updates are detected.
  • TVE_TYPE — identifies the type of the time value entity, which drives interpretation of the scheduling attributes.
  • TVE_ID_OFFSET, UOM_CODE, DURATION, OPERATOR, BEFORE_AFTER — the core schedule definition fields, expressing an offset with a unit of measure, a duration, and a relational operator applied before or after the anchor point.
  • CNH_ID, DNZ_CHR_ID, TZE_ID, SPN_ID — foreign references to the contract header, contract, time zone, and sponsoring entities with which the time value is associated.
  • TVE_ID_GENERATED_BY, TVE_ID_STARTED, TVE_ID_ENDED, TVE_ID_LIMITED — govern how the time value is generated and its validity window.
  • DATETIME, MONTH, DAY, HOUR, MINUTE, SECOND, INTERVAL_YN, NTH, DAY_OF_WEEK — the concrete temporal components used to compute the effective date.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS used for multi-org security.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — standard Oracle EBS descriptive flexfield columns.

Common Use Cases and Queries

Because OKC_TIMEVALUES_BH preserves prior versions of time value definitions, the primary reporting use case is audit reconstruction: determining what a contract term's time value looked like at a point in time or which user changed it. A typical pattern joins the history key back to the base table or uses it standalone:

  • Retrieve prior versions of a specific time value: SELECT * FROM OKC.OKC_TIMEVALUES_BH WHERE ID = :tv_id ORDER BY MAJOR_VERSION DESC;
  • Identify the latest historical revision before a date: SELECT * FROM OKC.OKC_TIMEVALUES_BH WHERE ID = :tv_id AND LAST_UPDATE_DATE < :eff_date ORDER BY MAJOR_VERSION DESC;
  • Audit trail by user: SELECT ID, MAJOR_VERSION, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKC.OKC_TIMEVALUES_BH WHERE ID IN (:tv_ids);
  • Security-scoped reporting joining SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.

These queries support regulatory audit reports, change-history dashboards, and troubleshooting contract date-calculation discrepancies where the historical definition must be compared against the current one.

Related Objects

  • OKC_TIMEVALUES_B — the primary (current) table for which this is the documented history counterpart; the ID and MAJOR_VERSION columns align.
  • FND_SECURITY_GROUPS — referenced via OKC_TIMEVALUES_BH.SECURITY_GROUP_ID.
  • OKC_TERMS_B / OKC_TERMS_TL — contract terms that consume time values for scheduling.
  • OKC_CONTRACT_HEADERS (CNH_ID) and OKC_CONTRACTS (DNZ_CHR_ID) — header and contract entities referenced by the time value's parent keys.
  • OKC_TIMEVALUES_V and related time-value APIs in the OKC Contracts Core package — the programmatic interfaces that read and write these records and, consequently, drive the history capture.

Where the supplied metadata is limited, cross-referencing the base table's documentation is recommended, as the history table is structurally a superset iteration of OKC_TIMEVALUES_B.