Results for “oks_level_elements_u1”

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

Overview

The OKS.OKS_LEVEL_ELEMENTS table in Oracle E-Business Suite (Release 12.1.1 and 12.2.2) stores the billing schedule for service contract headers, lines, and sub-lines. Each row in this table represents a "level element," which combines a billing date with its associated billable amount. The data is derived from the billing stream information captured in the OKS_STREAM_LEVELS_B table, with one or more level element records corresponding to each billing stream record. This object resides in the OKS schema, is registered under FND Design Data as OKS.OKS_LEVEL_ELEMENTS, and holds a status of VALID.

The table plays a central role in the service contracts billing cycle. The "Service Contracts Main Billing" concurrent program reads OKS_LEVEL_ELEMENTS to identify which lines must be billed for a given period, filtering records by the DATE_TO_INTERFACE value and updating DATE_COMPLETED once billing finishes. Under the heuristic Data Vault classification mined from its foreign-key structure, this object leans toward a satellite role: it carries descriptive, time-stamped billing attributes attached to the billing stream and contract entities rather than acting as a pure hub or link.

Key Information Stored

The most significant columns documented for OKS_LEVEL_ELEMENTS include:

• ID — Surrogate primary key (NUMBER), enforced by the OKS_LEVEL_ELEMENTS_PK constraint and also the single column of the unique index OKS_LEVEL_ELEMENTS_U1. It is the sole documented business-key candidate on this object.
• SEQUENCE_NUMBER — VARCHAR2(240) chronological sequence generated programmatically to express the level element's order within a billing stream.
• DATE_START and DATE_END — Bounding dates of the billing period, derived from the contract line or sub-line start date.
• AMOUNT — The billable amount associated with the level element.
• DATE_TO_INTERFACE — The interface date used by the billing program to select records for processing; indexed by OKS_LEVEL_ELEMENTS_N3.
• DATE_COMPLETED — Updated after the billing process to mark the element as billed.
• DATE_RECEIVABLE_GL, DATE_REVENUE_RULE_START, DATE_TRANSACTION, DATE_DUE, and DATE_PRINT — Additional accounting, transaction, and output dates relevant to receivables and invoicing.
• RUL_ID — Foreign key to OKC_RULES_B, linking the element to the governing contract rule.
• CLE_ID, PARENT_CLE_ID, and DNZ_CHR_ID — Identifiers relating the element to its parent contract line, parent level element, and contract header respectively.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include identifying unbilled schedule lines, reconciling billing amounts against contract rules, and auditing the chronological schedule of a specific billing stream.

• Listing pending billable elements for a period: SELECT ID, SEQUENCE_NUMBER, AMOUNT, DATE_TO_INTERFACE FROM OKS_LEVEL_ELEMENTS WHERE DATE_COMPLETED IS NULL AND DATE_TO_INTERFACE <= :p_date;
• Reviewing the schedule for a contract line: filter on CLE_ID or DNZ_CHR_ID with ordering by SEQUENCE_NUMBER.
• Reconciling elements to their governing rule via a join on RUL_ID to OKC_RULES_B.
• Auditing the last billing run by inspecting DATE_COMPLETED and DATE_TO_INTERFACE ranges.

Related Objects

• OKS_STREAM_LEVELS_B — Source billing stream records from which level elements are derived.
• OKC_RULES_B — Referenced through RUL_ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID.
• OKS_LEVEL_ELEMENTS self-reference via PARENT_CLE_ID for sub-line hierarchies.
• The Service Contracts Main Billing concurrent program — primary consumer that reads and updates this table.