Results for “okc_ebiz_kheaders_v”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_EBIZ_KHEADERS_V is a reporting and integration 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 "Find grid for eBusiness Integration," meaning it supplies the flattened, language-resolved contract header data that integration and inquiry screens consume when presenting a searchable list of contracts to end users or external systems. The view consolidates header-level contract attributes with their translated lookup meanings, textual descriptions, and operating unit names so that a single query returns a fully human-readable result set without requiring the caller to perform additional joins.
The object is defined as a VIEW with VALID status in both Oracle EBS 12.1.1 and 12.2.2. The column list is identical across releases, and the referenced base objects are consistently listed as synonyms over the underlying OKC and HR tables. Because it is a view rather than a table, it holds no data of its own and imposes no storage or index maintenance overhead; its cost is the join and function-call work required at query time.
Underlying Base Objects
The view is defined over the following documented base objects:
- OKC_K_HEADERS_ALL_B (synonym) — the primary contract header table, supplying the transactional columns such as CONTRACT_NUMBER, STATUS_CODE, SUBCLASS_CODE, dates, amounts, and the ORG_ID.
- OKC_K_HEADERS_TL (synonym) — the translation table for contract headers, supplying SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, and COGNOMEN (exposed as KNOWN_AS), filtered by USERENV('LANG').
- OKC_STATUSES_TL (synonym) — the translated status codes, joined on STS.CODE = CHRB.STS_CODE to provide STATUS_MEANING.
- OKC_SUBCLASSES_TL (synonym) — the translated subclass codes, joined on SC.CODE = CHRB.SCS_CODE to provide SUBCLASS_MEANING.
- HR_ALL_ORGANIZATION_UNITS_TL (synonym) — the translated organization units, joined on HR.ORGANIZATION_ID = CHRB.ORG_ID to resolve the OPERATING_UNIT name.
- OKC_UTIL (package) — invoked inline as OKC_UTIL.GET_K_ACCESS_LEVEL(CHRB.ID, CHRB.SCS_CODE) to compute the USER_ACCESS_LEVEL column.
Every translated join carries a LANGUAGE = USERENV('LANG') predicate, so the view automatically returns descriptions, meanings, and organization names in the session's current language.
Key Columns
The view exposes the contract header identity and lifecycle in a single row per contract:
- ROW_ID — the ROWID of the base header row, available for row-level addressing.
- CONTRACT_ID — the surrogate primary key of the contract header.
- CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER — the user-visible contract identifier.
- STATUS_CODE, STATUS_MEANING, SUBCLASS_CODE, SUBCLASS_MEANING — coded and translated classification values.
- DATE_SIGNED — the date the contract was signed; this is the column associated with the search term date_signed. It is exposed directly from OKC_K_HEADERS_ALL_B and is frequently used to filter and report on executed agreements.
- DATE_APPROVED, DATETIME_CANCELLED, DATE_TERMINATED, DATE_RENEWED, START_DATE, END_DATE — the remaining lifecycle dates.
- CONTRACT_AMOUNT and CURRENCY_CODE — estimated value and its currency.
- USER_ACCESS_LEVEL — the caller's access level, derived at query time by OKC_UTIL.GET_K_ACCESS_LEVEL.
- AUTHORING_ORG_ID, ORG_ID, OPERATING_UNIT — organizational context.
- OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — concurrency control, audit, and row-level security columns.
Common Use Cases and Queries
Typical usage includes building contract search grids, feeding integration extracts, and producing signed-contract reports. A representative query filtering on the searched column follows:
- Contracts signed within a period:
SELECT contract_number, date_signed, status_meaning, operating_unit FROM okc_ebiz_kheaders_v WHERE date_signed BETWEEN :p_from AND :p_to ORDER BY date_signed DESC; - Listing active contracts for an operating unit:
SELECT contract_number, short_description, contract_amount, currency_code FROM okc_ebiz_kheaders_v WHERE operating_unit = :p_ou AND status_meaning = 'Active'; - Verifying a user's access:
SELECT contract_number, user_access_level FROM okc_ebiz_kheaders_v WHERE contract_id = :p_id;
Because USER_ACCESS_LEVEL is computed per row by OKC_UTIL, queries should be filtered as narrowly as possible to avoid excessive function invocations. All joins in the view are equijoins on the respective ID/CODE columns with language predicates, so results are deterministic for the session language. The view is read-only in practice and should be used for inquiry rather than DML.
-
View: OKC_EBIZ_KHEADERS_V 12.2.2
Find grid for eBusiness Integration
APPS.OKC_EBIZ_KHEADERS_V·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·Explore OKC module →
-
View: OKC_EBIZ_KHEADERS_V 12.1.1
Find grid for eBusiness Integration
APPS.OKC_EBIZ_KHEADERS_V·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·Explore OKC module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.