Results for “bt_cle_id”

50+ results




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

Overview

OKS_BILLRATE_SCHEDULES_V is an APPS-owned view within the Oracle E-Business Suite Service Contracts (OKS) module. Its documented purpose is to display the bill rate and the associated schedule definition for a service activity billing type configured in Coverage. In practice, the view surfaces the time-window, day-of-week, and rate-amount attributes that govern how a service line is priced, allowing billing arrangements to be defined with granular precision — for example, a Labor billing type charged at a flat rate of 150 USD per hour on weekdays between 08:00 and 18:00.

The view is read-only by design and functions as a reporting and integration surface rather than a maintenance entity. Because it exposes the full schedule structure — start and end times, weekday flags, holiday indicator, UOM, and both flat-rate and list-price-percentage pricing modes — it is consumed by custom reports, conversions, and integrations that require the pricing rules behind a coverage billing type. The user's "flat_rate" search maps directly to the view's FLAT_RATE column, the monetary amount applied when pricing is expressed as a fixed per-unit charge rather than a percentage over list price.

Underlying Base Objects

The documented implementation exposes OKS_BILLRATE_SCHEDULES as the referenced base object, accessed through a synonym. The view text is a straightforward SELECT of all columns from that base, with no joins, filters, or transformations applied. Consequently, every row and column in OKS_BILLRATE_SCHEDULES_V corresponds one-to-one with the underlying table, and no aggregation or derived business logic is introduced by the view itself.

Because the view is unqualified by additional predicates, row-level security is not enforced within the SQL; access control depends on the APPS schema grants and any Oracle EBS security group conventions (the SECURITY_GROUP_ID column is projected but not filtered). This makes the view suitable as a low-overhead read layer on top of the base table.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing flat-rate pricing across coverage billing types, reconciling rates against list-price-based pricing, and extracting schedule windows for downstream billing or integration processes.

Retrieve all flat-rate schedules for a given billing type:

SELECT id, cle_id, bt_cle_id, bill_rate_code, uom, flat_rate,
       start_hour, end_hour, holiday_yn
  FROM oks_billrate_schedules_v
 WHERE bt_cle_id = :p_bt_cle_id
   AND flat_rate IS NOT NULL;

List schedules active on weekdays only:

SELECT id, flat_rate, uom, start_hour, start_minute,
       end_hour, end_minute
  FROM oks_billrate_schedules_v
 WHERE monday_flag = 'Y'
   AND tuesday_flag = 'Y'
   AND wednesday_flag = 'Y'
   AND thursday_flag = 'Y'
   AND friday_flag = 'Y';

Compare flat-rate versus percentage-over-list-price pricing arrangements:

SELECT id, bill_rate_code, flat_rate, percent_over_list_price
  FROM oks_billrate_schedules_v
 WHERE flat_rate IS NOT NULL
    OR percent_over_list_price IS NOT NULL;

Because the view mirrors the base object without transformation, queries can be tuned directly against OKS_BILLRATE_SCHEDULES, with the view retained for supported, read-only access.