Results for “pre_pay_req_yn”

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

Overview

OKC_K_HDR_AGREED_S_V is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. Its documented purpose is to expose contract header information sourced primarily from the OKC_CONTRACT_HEADERS_B base table. Rather than requiring callers to reconstruct multi-table joins between the header base table and its translation table, the view presents a convenient, denormalized projection of contract header attributes together with descriptive text fields.

In the context of EBS 12.1.1 and 12.2.2, this view functions as a read layer used by reporting tools (BI Publisher, Oracle Reports, Discoverer, custom SQL), integrations, and extension development where contract-level details are needed without touching base tables directly. Because it consolidates header attributes and translated descriptive columns, it is well suited to queries that must return contract number, status, dates, and textual descriptions in a single pass.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

• OKC_K_HEADERS_B (SYNONYM) — the contract header base table holding the operational, non-translated columns.
• OKC_K_HEADERS_TL (SYNONYM) — the translation table holding language-dependent descriptive text.

In the view definition, these correspond to the aliases CHRB (OKC_K_HEADERS_B) and CHRT (OKC_K_HEADERS_TL). The join binds translation rows to the correct header, typically on the header ID with language, allowing the descriptive columns (SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN) to be returned in the session's language. The view also projects the ROWID of the base header row as ROW_ID, which supports tools and frameworks that rely on row identifiers for update or navigation logic.

Key Columns

• ID / ROW_ID / OBJECT_VERSION_NUMBER — surrogate identifier, row identity, and optimistic locking token for the header.
• CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — the contract's unique number and any modifier suffix.
• STS_CODE / SCS_CODE / QCL_ID — status, status class, and quality/classification references.
• DATE_APPROVED, DATE_SIGNED, DATE_TERMINATED, DATE_RENEWED — the lifecycle date columns, including DATE_RENEWED, the field most directly relevant to renewal tracking.
• AUTO_RENEW_DAYS, START_DATE, END_DATE — renewal interval and contract validity window.
• SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN — language-dependent descriptive text from OKC_K_HEADERS_TL.
• Attribute1–Attribute15, ATTRIBUTE_CATEGORY — the DFF (descriptive flexfield) columns for client-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• AUTHORING_ORG_ID, BUY_OR_SELL, ISSUE_OR_RECEIVE, CURRENCY_CODE, TEMPLATE_YN, ARCHIVED_YN, DELETED_YN — organizational and classification attributes.

Common Use Cases and Queries

The view is frequently used to report on contracts, identify those due for renewal, and drive integrations needing header-level data. A typical query returning renewal information is:

• SELECT contract_number, date_renewed, start_date, end_date, sts_code FROM okc_k_hdr_agreeds_v WHERE date_renewed IS NOT NULL;

To find contracts approaching expiry where renewal has not yet occurred:

• SELECT contract_number, end_date, auto_renew_days, date_renewed FROM okc_k_hdr_agreeds_v WHERE end_date BETWEEN SYSDATE AND SYSDATE + 90 AND date_renewed IS NULL;

Because the search term "date_renewed" maps directly to the DATE_RENEWED column exposed here, this view is the appropriate access point for renewal-date analysis. Note that in 12.2.x multi-tenant or language-sensitive environments, callers should be mindful of the translation join and the session operating language when relying on the descriptive columns.