Search Results date_to_interface




Overview
Explore in AI Chat

Overview

OKS_LEVEL_ELEMENTS_V is a VALID view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the OKS - Service Contracts product family and, per the ETRM metadata, is documented as a mechanism used to store billing schedule information for lines. The view presents a row-per-billing-element projection of the underlying level element records, exposing the schedule identifiers, financial dates, amounts, and audit columns that drive contract line billing and revenue processing. Because it is a view rather than a table, it introduces no independent storage; it is a read-oriented interface over the level element entity, which makes it a convenient and stable source for reporting, concurrent processing, and integration extracts that need billing schedule detail without joining to the base synonym directly.

Underlying Base Objects

The documented view definition is a straightforward projection over a single referenced base object, listed in the ETRM metadata as the synonym OKS_LEVEL_ELEMENTS. The view text selects all exposed columns from that base with the alias LET:

  • OKS_LEVEL_ELEMENTS (SYNONYM) — the sole documented referenced object; the view is defined as a SELECT over this synonym, with no joins, unions, or aggregations in the documented text.

Because the definition is a one-to-one projection, every row in OKS_LEVEL_ELEMENTS_V corresponds to exactly one row in OKS_LEVEL_ELEMENTS, and the view carries the base object's ROWID forward as ROW_ID. This makes the view update-friendly in structure even though it is typically consumed read-only.

Key Columns

Common Use Cases and Queries

The view is principally used to report billing schedules for contract lines, to verify date milestone progression, and to supply extract routines that interface billing data to downstream financial systems. The presence of DATE_COMPLETED — the column most commonly searched alongside this view — supports reconciliation of completed billing elements against expected schedules.

Typical query patterns include filtering by contract and inspecting completed elements:

  • Retrieve all billing elements for a contract: SELECT cle_id, dnz_chr_id, sequence_number, date_start, date_end, amount FROM oks_level_elements_v WHERE dnz_chr_id = :contract_id ORDER BY sequence_number;
  • Identify completed elements for a period: SELECT id, cle_id, date_due, date_completed, amount FROM oks_level_elements_v WHERE date_completed BETWEEN :from_date AND :to_date;
  • Reconcile revenue and receivables dates: SELECT cle_id, date_revenue_rule_start, date_receivable_gl, rul_id FROM oks_level_elements_v WHERE cle_id = :cle_id;

Because the view mirrors its base object directly, query performance is governed entirely by OKS_LEVEL_ELEMENTS and its indexes, and standard audit columns permit straightforward change tracking in integration extracts.