Results for “user_access_level”

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

Overview

The view APPS.OKC_SEARCH_KHEADERS_V is a Contracts Core (OKC) object that supplies the data set rendered by the Find grid on the Contract Search screen in Oracle E-Business Suite. It is a denormalised, presentation-oriented view rather than a transactional entity: it consolidates contract header attributes from the base and translation tables of OKC_K_HEADERS with status, subclass, lookup, organization, and responsibility-access information so that the search screen and its supporting LOVs can retrieve a fully described contract row in a single query.

Because the view is owned by APPS and exposes standard WHO columns, it is equally usable as a reporting and integration source. Report writers and interfaces that need contract header detail — number, amount, currency, status, dates, operating unit, and the caller's access level — can query it directly without reconstructing the multi-table join themselves. In EBS 12.1.1 and 12.2.2 the object is valid and retains the same definitional shape, with the caveat that 12.2 multi-organization architecture routes the operating unit through ORG_ID and that the HR_ALL_ORGANIZATION_UNITS_TL reference resolves through the APPS synonym set.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_K_HEADERS_B — the contract header base table; supplies identifiers, contract number and modifier, estimated amount, currency, status and subclass codes, template flags, and all key dates.
• OKC_K_HEADERS_TL — the translation table; joined on ID with LANGUAGE = USERENV('LANG') to supply SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, and KNOWN_AS.
• OKC_STATUSES_TL and OKC_SUBCLASSES_TL — lookup translation tables that convert STS_CODE and SCS_CODE into their displayed meanings.
• OKC_APP_FUNCTION_ACCESSES — enforces application function security by matching the current responsibility's application.
• FND_LOOKUPS — joined twice to derive the CUST_PO_NUMBER_REQ_YN and PRE_PAY_REQ_YN meanings.
• HR_ALL_ORGANIZATION_UNITS_TL — resolves AUTHORING_ORG_ID to the operating unit name.
• OKC_UTIL and FND_GLOBAL — packages invoked in the select list for GET_K_ACCESS_LEVEL and for the responsibility application ID used by the function-security predicate.

Key Columns

• CONTRACT_ID (CHRB.ID) and ROW_ID — primary key and row identifier for the contract header.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER — the user-visible contract identifier, including version modifier.
• CONTRACT_AMOUNT — aliased from CHRB.ESTIMATED_AMOUNT; the estimated monetary value of the contract. This is the column returned when a user searches on "contract_amount".
• CURRENCY_CODE — currency of the estimated amount.
• STATUS_CODE/STATUS_MEANING and SUBCLASS_CODE/SUBCLASS_MEANING — coded and translated status and subclass values.
• START_DATE, END_DATE, DATE_SIGNED, DATE_APPROVED, DATE_TERMINATED, DATE_RENEWED, DATETIME_CANCELLED — lifecycle dates.
• AUTHORING_ORG_ID/OPERATING_UNIT and ORG_ID — organization context for multi-org security.
• USER_ACCESS_LEVEL — computed by OKC_UTIL.GET_K_ACCESS_LEVEL for the current user.
• SHORT_DESCRIPTION, DESCRIPTION, COMMENTS, KNOWN_AS — descriptive text in the session language.

Common Use Cases and Queries

The view supports contract search, ad-hoc reporting, and integration extracts. Because it already applies language and function-security predicates, it returns only rows the caller's responsibility may see.

SELECT contract_number,
       contract_number_modifier,
       contract_amount,
       currency_code,
       status_meaning,
       start_date,
       end_date,
       operating_unit
FROM   okc_search_kheaders_v
WHERE  contract_amount >= 100000
ORDER  BY contract_amount DESC;

A second common pattern joins the view to contract parties for a customer-facing extract:

SELECT k.contract_number, k.contract_amount, k.currency_code
FROM   okc_search_kheaders_v k
WHERE  k.status_meaning = 'Active'
AND    k.org_id = :p_org_id;

The view's computed USER_ACCESS_LEVEL column makes it suitable for read-only dashboards where the security check must not be bypassed; direct queries against OKC_K_HEADERS_B would omit this and the translation and lookup meanings. In 12.2.2, ensure the session's ORG_ID and language are initialised so that the multi-org and translation predicates resolve as intended.