Results for “user_access_level”

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

Overview

The OKS_AUTH_HEADERS_HV view is an APPS-owned, VALID database object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the OKS — Service Contracts product family. The object name follows the standard EBS convention of the _HV suffix, denoting a "Header View" — typically a denormalized, human-readable join over the base contract header tables and their translation tables. In the Service Contracts schema, the letters CHR in the underlying columns stand for Contract Header Repository/Contract Header Renewal context, and the view exposes the authoritative, presentation-ready record of a service contract header, including its identifying attributes, status, currency, dates, and renewal/authored relationships.

Because the view is built over OKC_K_HEADERS_BH and OKC_K_HEADERS_TLH, it sits within the OKC (Contracts Core) kernel that the OKS Service Contracts module layers upon. This makes OKS_AUTH_HEADERS_HV a natural integration point for reporting, analytics, and interfaces that need one row per contract header with both base and translated (language) descriptive columns. The view is not a stored table; it is a pure projection whose results always reflect the current state of the underlying header tables.

Underlying Base Objects

The documented base objects and referenced constructs are:

• OKC_K_HEADERS_BH (SYNONYM) — the base header table supplying the bulk of structural and transactional columns (ID, status, dates, amounts, currency).
• OKC_K_HEADERS_TLH (SYNONYM) — the translated header table supplying the language-dependent descriptive columns (SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, NON_RESPONSE_REASON, etc.). The _TLH suffix signals a translation table joined on the header ID and language.
• OKS_K_HEADERS_BH (SYNONYM) — the OKS-specific header extension, carrying Service Contracts attributes queried through the OKC_UTIL package.
• OKC_STATUSES_V (VIEW) — resolves the status code (STS_CODE) to a meaningful status meaning.
• OKC_SUBCLASSES_V (VIEW) — resolves the subclass/class context.
• OKC_UTIL (PACKAGE) — the contractual utility package invoked for value derivation and lookup logic embedded in the view definition.

This aggregation of base, translation, and status/subclass views is what allows a single query against OKS_AUTH_HEADERS_HV to return a fully described contract header without the caller manually joining four or more objects.

Key Columns

• ROW_ID / ID / OBJECT_VERSION_NUMBER — the row identifier, primary contract header ID, and optimistic-locking version.
• MAJOR_VERSION — supports versioned contract headers.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER — the user-facing contract identifier and its modifier.
• STS_CODE, SCS_CODE, QCL_ID — status code, subclass code, and quality/class list reference; STS_CODE is resolved via OKC_STATUSES_V.
• CHR_TYPE, RFP_TYPE, TRN_CODE — contract/authored type, request-for-proposal type, and transaction code.
• CURRENCY_CODE, ESTIMATED_AMOUNT — financial context of the header.
• START_DATE, END_DATE, DATE_SIGNED, DATE_TERMINATED, DATE_RENEWED, DATETIME_CANCELLED — lifecycle dates.
• CHR_ID_RESPONSE, CHR_ID_AWARD, CHR_ID_RENEWED, CHR_ID_RENEWED_TO — the header's relationships to response, award, and renewal contracts.
• SHORT_DESCRIPTION, DESCRIPTION, COMMENTS, COGNOMEN — translated descriptive fields from OKC_K_HEADERS_TLH.
• TEMPLATE_YN, TEMPLATE_USED, ARCHIVED_YN, DELETED_YN — governance flags.
• INV_ORGANIZATION_ID, AUTHORING_ORG_ID, BUY_OR_SELL, ISSUE_OR_RECEIVE — organization and directional context.
• AUTO_RENEW_DAYS, KEEP_ON_MAIL_LIST, SET_ASIDE_REASON, SET_ASIDE_PERCENT, RESPONSE_COPIES_REQ — renewal and solicitation attributes.

The user's search term, class_meaning, is not a direct column of this view; it is a derived descriptive value — the human-readable meaning of the contract classification/subclass. In practice it is obtained by resolving SCS_CODE through the OKC_SUBCLASSES_V view (or the equivalent OKC subclass lookup) rather than being stored on OKC_AUTH_HEADERS_HV itself.

Common Use Cases and Queries

Typical uses include service-contract reporting, renewal tracking, and downstream integration extracts that require one row per contract header with descriptive text and status meaning.

• List active service contracts with their status and class meaning.
• Trace renewal chains via CHR_ID_RENEWED and CHR_ID_RENEWED_TO.
• Extract headers for a specific customer PO or currency.

SELECT v.CONTRACT_NUMBER,
       v.STS_CODE,
       v.CURRENCY_CODE,
       v.START_DATE,
       v.END_DATE,
       v.SHORT_DESCRIPTION
FROM   APPS.OKS_AUTH_HEADERS_HV v
WHERE  v.DELETED_YN = 'N'
AND    v.ARCHIVED_YN = 'N';

SELECT v.CONTRACT_NUMBER,
       v.CHR_TYPE,
       v.DATE_RENEWED,
       v.CHR_ID_RENEWED_TO
FROM   APPS.OKS_AUTH_HEADERS_HV v
WHERE  v.CHR_ID_RENEWED IS NOT NULL;

For class meaning, join to the subclass view: ... JOIN APPS.OKC_SUBCLASSES_V s ON s.CODE = v.SCS_CODE. Because the view depends on translation and status views, always filter on DELETED_YN and ARCHIVED_YN to exclude logically removed headers.