Results for “end_month”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_TIME_IG_STARTEND_VAL_V is a read-only database view owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite. Its documented purpose is to serve as the "View for Time – Generic Start End," presenting a denormalized, reporting-friendly representation of time value definitions used by the contract authoring time-validation framework. In Oracle Contracts, time-related clauses and deliverables frequently need to express recurring or bounded windows — for example, an event that starts on the second Tuesday of a month and ends on the last Friday of a quarter. The underlying TIMEVALUES storage model normalizes these definitions into parent/child rows keyed by a type indicator (TVE_TYPE). This view collapses that structure by self-joining the OKC_TIMEVALUES table so that a single row surfaces both the start and end components of an "IGS" (generic start/end) time definition alongside the descriptive attributes of the parent record.
Because the view is a standard ETRM-documented data definition rather than a private API, it is a legitimate integration and reporting surface. It exposes translated descriptive columns, an OBJECT_VERSION_NUMBER for optimistic locking visibility, and the full WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), making it suitable for audit and extract pipelines.
Underlying Base Objects
The documented referenced base object is OKC_TIMEVALUES, accessed through a synonym. The view text performs three references to this same table, aliased as TGD1, TGD2, and IGS:
- IGS — the parent row filtered by
TVE_TYPE = 'IGS', representing the generic start/end time definition itself. - TGD1 — joined on
TGD1.ID = IGS.TVE_ID_STARTEDandTGD1.TVE_TYPE = 'TGD', supplying the start-side time granularity fields. - TGD2 — joined on
TGD2.ID = IGS.TVE_ID_ENDEDandTGD2.TVE_TYPE = 'TGD', supplying the end-side time granularity fields.
The constant literal 'N' is projected as SFWT_FLAG. Foreign keys such as TVE_ID_LIMITED, DNZ_CHR_ID (the owning contract/document identifier), and TZE_ID (time zone) are carried through from the IGS parent row.
Key Columns
- ID — primary identifier of the IGS time value record.
- DNZ_CHR_ID — the contract/document identifier that owns this time definition.
- TVE_ID_STARTED / TVE_ID_ENDED / TVE_ID_LIMITED — references to the start, end, and limited-time child definitions.
- START_MONTH, START_NTH, START_DAY_OF_WEEK, START_DAY, START_HOUR, START_MINUTE, START_SECOND — the start-side recurrence specification sourced from TGD1.
- END_MONTH, END_NTH, END_DAY_OF_WEEK, END_DAY, END_HOUR, END_MINUTE, END_SECOND — the mirroring end-side specification from TGD2.
- DESCRIPTION, SHORT_DESCRIPTION, COMMENTS — user-facing descriptive text.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for extensibility.
- OBJECT_VERSION_NUMBER and the WHO audit columns — concurrency and audit metadata.
Notably, DAY_OF_WEEK appears twice — as START_DAY_OF_WEEK and END_DAY_OF_WEEK — which is directly relevant to searches involving "day_of_week"; consumers must disambiguate which boundary they intend.
Common Use Cases and Queries
Typical scenarios include contract time-window reporting, data migration validation, and integration extracts that need a flat start/end representation. A representative query retrieving all start/end definitions referencing a particular weekday is:
SELECT id, dnz_chr_id, start_day_of_week, start_nth, end_day_of_week, end_nth, tze_id
FROM apps.okc_time_ig_startend_val_v
WHERE start_day_of_week IS NOT NULL OR end_day_of_week IS NOT NULL;
To restrict to definitions for a specific contract document:
SELECT id, description, start_month, start_day, start_hour, end_month, end_day, end_hour
FROM apps.okc_time_ig_startend_val_v
WHERE dnz_chr_id = :p_chr_id;
Because DAY_OF_WEEK values follow Oracle's conventional numeric encoding (and, in date-format contexts, the NLS day-of-week naming), analysts should confirm the domain values against OKC_TIMEVALUES lookups before filtering. The view should be treated as read-only; inserts and updates must target the base OKC_TIMEVALUES rows via the supported Contracts APIs.
-
View for Time - Generic Start End
APPS.OKC_TIME_IG_STARTEND_VAL_V·↳ OKC_TIMEVALUES·Explore OKC module →
-
View for Time - Generic Start End
APPS.OKC_TIME_IG_STARTEND_VAL_V·↳ OKC_TIMEVALUES·Explore OKC module →
-
PACKAGE: APPS.PAY_MX_DIM_MAG 12.1.1
-
PACKAGE: APPS.PAY_MX_DIM_MAG 12.2.2
-
PACKAGE: APPS.OKC_TIME_PVT 12.1.1
-
PACKAGE: APPS.OKC_TIME_PVT 12.2.2