Results for “recurring_flag”

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

Overview

OKC_DEL_MESSAGES is a Contracts Core (OKC) reference and configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the metadata used to construct due date messages for contract deliverables, providing the rule definitions from which the application composes the text and timing of reminders such as upcoming, overdue, or recurring due date notifications. Rather than holding the notification text itself, the table preserves the parameters — relative offsets, before/after indicators, fixed or recurring behaviour, and frequency units — that drive message generation at runtime.

Heuristically, the table exhibits hub-leaning characteristics when classified against Data Vault modeling conventions. Its primary key is a single business-meaningful attribute, MESSAGE_NAME, and it is referenced by an informational foreign key from OKC_DELIVERABLES, meaning the table functions as an authoritative set of named message definitions to which deliverable records subscribe. The presence of descriptive and rule-bearing columns alongside that key suggests it could be modelled as a hub with associated satellite attributes, although the classification is a heuristic suggestion rather than a normative Oracle design.

Key Information Stored

The table contains fifteen documented columns in release 12.2.2. The most significant are:

• MESSAGE_NAME — the primary key column and business identifier, defined by the OKC_DEL_MESSAGES_PK constraint. It is also the first column of the unique index OKC_DEL_MESSAGES_U1 (MESSAGE_NAME, ZD_EDITION_NAME), confirming it as the business-key candidate under editioning.
• REPEATING_FREQUENCY_UOM — the unit of measure governing how often a recurring due date message repeats.
• RECURRING_FLAG — indicates whether the message definition recurs rather than firing once.
• RELATIVE_ST_DATE_UOM and RELATIVE_END_DATE_UOM — the units applied to the relative start and end date offsets for the message window.
• START_EVT_BEFORE_AFTER and END_EVT_BEFORE_AFTER — indicators controlling whether the message is presented before or after the associated start and end events.
• START_FIXED_FLAG and END_FIXED_FLAG — flags distinguishing fixed dates from dates derived relative to the deliverable event.
• ZD_EDITION_NAME — the editioning column, part of both unique indexes and present throughout the OKC schema in 12.2.2 to support online patching and edition-based redefinition.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO-column traceability.

A second unique index, OKC_DEL_MESSAGES_U2, spans START_EVT_BEFORE_AFTER, REPEATING_FREQUENCY_UOM, END_EVT_BEFORE_AFTER, RELATIVE_ST_DATE_UOM, RELATIVE_END_DATE_UOM, MESSAGE_NAME, and ZD_EDITION_NAME, enforcing that each unique combination of rule attributes maps to a distinct message definition.

Common Use Cases and Queries

Typical usage centres on inspecting which message definitions exist, validating the rule combination behind a message, and tracing deliverable-to-message assignments. A representative query lists active definitions for the current edition:

SELECT message_name, repeating_frequency_uom, recurring_flag, start_evt_before_after, end_evt_before_after, start_fixed_flag, end_fixed_flag FROM okc.okc_del_messages WHERE zd_edition_name = 'SET1';

To find which deliverables print a given due date message, join against OKC_DELIVERABLES on the informational foreign key:

SELECT d.deliverable_id, d.print_due_date_msg_name FROM okc.okc_deliverables d, okc.okc_del_messages m WHERE d.print_due_date_msg_name = m.message_name;

Reporting scenarios include auditing recurring versus one-time message configuration, reconciling fixed and relative date rules before a contract template rollout, and verifying that no orphaned message names remain after a configuration change. Because the table is reference data, queries are generally low-volume and read-only, and they benefit from the MESSAGE_NAME and editioning indexes.

Related Objects

• OKC_DELIVERABLES — the principal dependent table. Its column PRINT_DUE_DATE_MSG_NAME references OKC_DEL_MESSAGES, so every deliverable can resolve the message definition that governs its printed due date notification.
• OKC_DEL_MESSAGES_PK — the primary key constraint on MESSAGE_NAME, used by all lookups and enforcing uniqueness of the business identifier.
• OKC_DEL_MESSAGES_U1 and OKC_DEL_MESSAGES_U2 — unique indexes that act as business-key candidates and constrain editioning and rule combinations respectively.
• Contracts Core deliverable APIs and concurrent programs that emit due date notifications consume these definitions when rendering messages at runtime, making the table an indirect dependency of the OKC Contracts authoring and notification flows.