Search Results oks_billrate_schedules




Overview
Explore in AI Chat

Overview

OKS_BILLRATE_SCHEDULES is a Service Contracts (OKS) module table that stores bill rate information and the associated schedules for a service activity billing type defined in Coverage. In Oracle EBS 12.1.1 and 12.2.2, this table supports the rate-generation logic used when a coverage line or service activity is billed against a rate schedule rather than a simple contract price. Each row captures a rate value together with the time-of-day window and the days of the week during which that rate applies, enabling tiered or time-sensitive billing for labor and services.

The metadata classifies this object heuristically as standalone in a Data Vault model. That is, the mined foreign-key structure does not identify a dominant parent business entity beyond FND_SECURITY_GROUPS, so it should be treated as a self-contained entity rather than a strict hub, link, or satellite. In practice, most of its descriptive attributes (rate code, flat rate, UOM, percentage over list price, day and hour flags) are non-key business attributes, which would typically be modeled as satellite columns if a Data Vault design were applied.

Key Information Stored

The table contains 34 documented columns. The most significant are:

Common Use Cases and Queries

Typical reporting needs include rate cards by coverage line, time-window billing analysis, and holiday/weekend premium validation. A representative query joining to the coverage line and contract header is:

SELECT b.ID, b.DNZ_CHR_ID, b.BILL_RATE_CODE, b.FLAT_RATE,
       b.UOM, b.START_HOUR, b.END_HOUR, b.HOLIDAY_YN
FROM   OKS.OKS_BILLRATE_SCHEDULES b
WHERE  b.CLE_ID = :cle_id
AND    b.SECURITY_GROUP_ID = :security_group_id;

Analysts frequently filter on MONDAY_FLAG ... SUNDAY_FLAG to reconstruct effective weekly schedules, and use START_HOUR/END_HOUR for time-of-day rate comparisons. Because the table is standalone and small relative to transactional OKS tables, it is commonly extracted in full into a reporting schema or data warehouse and joined by CLE_ID or DNZ_CHR_ID to contract and coverage dimensions.

Related Objects

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID to enforce multi-org security filtering.
  • OKS_COVERAGES / OKS_COVERAGE_LINES (and variants) — joined by CLE_ID to resolve the coverage or service activity owning the rate.
  • OKS_BILLING_TYPES / billing type coverage lines — referenced by BT_CLE_ID to identify the billing type definition.
  • OKS_CONTRACTS_ALL — joined by DNZ_CHR_ID to reach the contract header.
  • OKS_BILLRATE_SCHEDULES_PK / OKS_BILLRATE_SCHEDULES_U1 — the primary and unique indexes over ID.
  • OKS Service Contracts APIs — the billing/rate APIs that insert and maintain rows during coverage definition and rate calculation.

Given its limited documented FK surface, joins beyond the objects above should be validated against the actual 12.1.1/12.2.2 implementation before being relied upon in production reporting.