Results for “oks_coverage_timezones”

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

Overview

The OKS_COVERAGE_TIMEZONES table in the Oracle E-Business Suite Service Contracts (OKS) module stores the time zone definitions associated with coverage schedules for a business process line. As the description states, the object is "suggested to store coverage time zones for a business process line," meaning it holds the time zone configuration used when evaluating service coverage windows, response times, and entitlement boundaries. In Release 12.1.1 and 12.2.2 the table resides in the OKS schema with a VALID status and comprises 19 documented columns.

Under the heuristic Data Vault classification mined from its foreign key structure, OKS_COVERAGE_TIMEZONES is treated as standalone. This modeling suggestion indicates that the table does not participate in a classic hub-and-satellite chain within the documented metadata; rather, it functions as an independent configuration reference whose relationships are expressed through descriptive foreign keys rather than through a shared business key hierarchy.

Key Information Stored

The surrogate primary key is ID, enforced by constraint OKS_CTZ_PK. A separate unique index, OKS_COVERAGE_TIMEZONES_U1, also spans ID and is the documented business-key candidate for this object.

• ID — Surrogate primary key and the value referenced by OKS_CTZ_PK and the unique index OKS_COVERAGE_TIMEZONES_U1.
• CLE_ID — Identifier linking the row to the coverage element or coverage line it qualifies.
• DNZ_CHR_ID — Do-not-zone / coverage header characteristic identifier associating the time zone entry with its parent coverage record.
• TIMEZONE_ID — Foreign key to HZ_TIMEZONES, defining the actual time zone applied to the coverage line.
• DEFAULT_YN — Flag indicating whether this time zone is the default for the associated coverage.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org and data security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework.
• ORIG_SYSTEM_ID1, ORIG_SYSTEM_REFERENCE1, ORIG_SYSTEM_SOURCE_CODE — Origin-tracking columns supporting data migration, denormalization, and interface integrations.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program audit columns recording the process that created or updated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on resolving which time zone governs service coverage windows for a given coverage line. A common query joins the table to HZ_TIMEZONES to retrieve the descriptive time zone name for reporting or diagnostics:

• Locate the default coverage time zone for a business process line by filtering on CLE_ID and DEFAULT_YN.
• Join to HZ_TIMEZONES on TIMEZONE_ID to translate the numeric key into a displayable time zone name for entitlement reports.
• Filter by SECURITY_GROUP_ID to respect multi-org security when exposing coverage configuration to end users.
• Audit configuration drift using CREATION_DATE, LAST_UPDATE_DATE, and PROGRAM_ID to identify who changed coverage time zone settings and when.
• Support data migration or interface validation using ORIG_SYSTEM_REFERENCE1 and ORIG_SYSTEM_SOURCE_CODE.

Related Objects

The following objects are the most significant dependencies based on the documented foreign key relationships:

• HZ_TIMEZONES — Referenced via OKS_COVERAGE_TIMEZONES.TIMEZONE_ID; the authoritative source of time zone definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for application security partitioning.
• OKS_COVERAGE_TIMEZONES_U1 — The unique index enforcing the documented business-key candidate on ID.
• OKS_CTZ_PK — The primary key constraint governing the ID column.
• Parent coverage entities referenced by CLE_ID and DNZ_CHR_ID, which define the coverage line to which each time zone row belongs.