Search Results default_yn

Overview

OKS_COVERAGE_TIMEZONES_V is a view owned by the APPS schema within the Oracle E-Business Suite Service Contracts (OKS) module. It presents coverage time zone information associated with service contracts, exposing the time zones that apply to specific coverage records. The view is documented in the ETRM reference for both Oracle EBS 12.1.1 and 12.2.2 and is listed with a status of VALID.

Because the OKS schema is the foundation for entitlement, warranty, and service contract processing, time zone data plays a critical role in defining when coverage begins and ends, and how response and resolution commitments are measured across geographies. The view offers a stable, read-only interface to this information, which makes it suitable for reporting, integration, and extension development where directly querying the base table is undesirable. Oracle frequently exposes such _V views to decouple downstream consumers from the physical table model and to ensure that only validated, application-consistent columns are surfaced.

The view returns the full set of identifying, defaulting, and audit columns of the underlying storage, preserving the record integrity expected by concurrent programs, APIs, and reporting tools operating against the Service Contracts module.

Underlying Base Objects

The view is defined over a single documented base object: the OKS_COVERAGE_TIMEZONES table, referenced through its APPS synonym. The view text is a straight, unfiltered projection of all columns from that table:

• No joins, aggregations, or filter predicates are applied.
• No column expressions or renames alter the underlying data.
• The view therefore functions as a direct, read-only alias of the base table for the columns it exposes (it does not add or hide any columns relative to the view text provided).

This one-to-one relationship means row counts, cardinality, and data types in the view mirror OKS_COVERAGE_TIMEZONES exactly. Each row represents one coverage-to-time-zone association, and a given coverage element may therefore appear in multiple rows when more than one time zone is attached. The DEFAULT_YN flag allows one such association to be designated as the primary or default.

Key Columns

• ID — Primary identifier for the coverage time zone record.
• CLE_ID — Reference to the coverage element to which this time zone association applies.
• DEFAULT_YN — Indicates whether this time zone is the default for the associated coverage element (typically Y/N).
• TIMEZONE_ID — Foreign key to the time zone definition (for example, from FND_TIMEZONES) used for coverage scheduling and response commitments.
• DNZ_CHR_ID — Identifier linking the row to the relevant contract or coverage header context.
• SECURITY_GROUP_ID — Multi-tenant / security group discriminator; historically significant for access control in EBS.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Standard concurrent program audit columns identifying the process that created or last updated the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "Who" columns maintained by the EBS framework.
• OBJECT_VERSION_NUMBER — Optimistic locking counter used to detect concurrent updates.

Common Use Cases and Queries

Typical scenarios include reporting the time zones assigned to a coverage element, identifying the default time zone for scheduling service commitments, and feeding integrations that must interpret coverage timing across multiple regions.

List all time zones for a given coverage element:

SELECT v.id, v.cle_id, v.timezone_id, v.default_yn
FROM   apps.oks_coverage_timezones_v v
WHERE  v.cle_id = :p_cle_id;

Retrieve only the default time zone for a coverage element:

SELECT v.cle_id, v.timezone_id
FROM   apps.oks_coverage_timezones_v v
WHERE  v.cle_id = :p_cle_id
AND    v.default_yn = 'Y';

Audit recently created or updated records:

SELECT v.id, v.cle_id, v.timezone_id,
       v.created_by, v.creation_date,
       v.last_updated_by, v.last_update_date
FROM   apps.oks_coverage_timezones_v v
WHERE  v.last_update_date >= SYSDATE - 7
ORDER BY v.last_update_date DESC;

Queries should always be issued against the APPS synonym and, where large volumes are involved, filtered by CLE_ID or DNZ_CHR_ID to leverage indexed access paths on the base table. Because the view adds no predicates, standard Service Contracts access and security rules continue to apply.