Results for “date_completed”

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

Overview

OKS_LEVEL_ELEMENTS is a Service Contracts (OKS) transactional table that stores each individual billing, revenue, or schedule period within a contract level. Where a level defines a logical tier or grouping inside a service contract line, OKS_LEVEL_ELEMENTS decomposes that level into discrete dated elements, each carrying its own amount, start and end dates, and processing milestones. The table therefore acts as the finest-grained record of when money is due, when revenue is recognized, and when downstream actions such as printing, interfacing, or completion occur for a given contract level.

Under the heuristic Data Vault classification derived from its foreign key structure, OKS_LEVEL_ELEMENTS is satellite-leaning. In modeling terms, it behaves as a descriptive satellite attached to a parent level business key, with one row per period, rather than as a pure hub of independent business entities. Its dependency on OKC_RULES_B via RUL_ID and on FND_SECURITY_GROUPS via SECURITY_GROUP_ID reinforces its role as an attribute-bearing detail table.

Key Information Stored

The documented physical schema contains 22 columns. The most operationally significant are:

• ID — the surrogate primary key, enforced by OKS_LEVEL_ELEMENTS_PK. A unique index, OKS_LEVEL_ELEMENTS_U1, also exists on ID, marking it as the sole documented business-key candidate.
• SEQUENCE_NUMBER — ordering of the period within its parent level.
• DATE_START and DATE_END — the effective window covered by the element.
• AMOUNT — the monetary value attributed to the period, central to billing and revenue reporting.
• DATE_RECEIVABLE_GL — the date used when posting the receivable to the general ledger.
• DATE_REVENUE_RULE_START — the anchor date for revenue recognition rules.
• DATE_TRANSACTION, DATE_DUE, DATE_PRINT, DATE_TO_INTERFACE, DATE_COMPLETED — a lifecycle of milestone dates used by concurrent programs and reporting.
• RUL_ID — foreign key to OKC_RULES_B, tying the element to the pricing or rule definition that generated it.
• CLE_ID and PARENT_CLE_ID — self-referencing-style identifiers linking an element to its level and parent element.
• DNZ_CHR_ID — the contract header identifier used to trace the element back to its contract.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org / security partitioning.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard concurrency control and audit columns.

Common Use Cases and Queries

Typical usage centers on billing schedules, revenue recognition schedules, and period-level contract analytics. A common pattern joins the element to the contract header and rule to produce a dated billing register:

• Listing all periods for a contract: SELECT CLE.SEQUENCE_NUMBER, CLE.DATE_START, CLE.DATE_END, CLE.AMOUNT FROM OKS_LEVEL_ELEMENTS CLE WHERE CLE.DNZ_CHR_ID = :contract_id ORDER BY CLE.SEQUENCE_NUMBER;
• Retrieving the governing rule: join CLE.RUL_ID = OKC_RULES_B.ID to surface rule details for each period.
• Revenue reporting: filter on DATE_REVENUE_RULE_START within a fiscal range and aggregate AMOUNT.
• Interface monitoring: query rows where DATE_TO_INTERFACE is populated but DATE_COMPLETED is null to identify elements awaiting downstream processing.
• Security-scoped reporting: restrict by SECURITY_GROUP_ID to honor operating unit or responsibility-level access.

Related Objects

• OKC_RULES_B — referenced through OKS_LEVEL_ELEMENTS.RUL_ID; supplies the rule or pricing definition behind each period.
• FND_SECURITY_GROUPS — referenced through OKS_LEVEL_ELEMENTS.SECURITY_GROUP_ID; enforces data security partitioning.
• OKS_LEVEL_ELEMENTS_PK / OKS_LEVEL_ELEMENTS_U1 — the primary key and unique index on ID.
• OKS_LEVELS (parent level entity) — the logical container that OKS_LEVEL_ELEMENTS periods decompose, referenced indirectly via PARENT_CLE_ID and CLE_ID.
• OKC_CONTRACTS / OKC_HEADERS — traced through DNZ_CHR_ID to associate elements with the originating contract header.
• OKS_BILLING_SCHEDULES and OKS_REVENUE_* — functional consumers that consume element amounts and dates for billing and revenue generation.