Results for “okc_operations_v”
35 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The OKC_OPERATIONS_V view is a seeded, APPS-owned database object within the OKC – Contracts Core product of Oracle E-Business Suite. It is documented as VALID in both Release 12.1.1 and 12.2.2 and serves as the standard query interface for the OKC_OPERATIONS_B base table. Because Contracts Core stores many of its reference and setup entities using the Oracle Applications multilingual ("TL") pattern, the physical operation definitions reside in a base ("_B") table while translated, language-dependent attributes reside in a corresponding ("_TL") table. The view performs the join between these two objects and presents a single, denormalized result set.
In Oracle EBS reporting and integration, OKC_OPERATIONS_V is the recommended access point for operations data rather than the underlying base table. It automatically restricts returned rows to the session's runtime language through the standard USERENV('LANG') predicate, ensuring that multilingual installations return meaningful, translated descriptions without requiring the calling application to supply language logic. This makes it suitable for concurrent programs, Oracle Reports, BI Publisher data templates, OAF pages, and interface extracts that need operation codes and their translated meanings.
Underlying Base Objects
Per the ETRM 12.2.2 metadata, the view is owned by APPS and is defined over two referenced base objects:
- OKC_OPERATIONS_B (SYNONYM) – the base table holding language-independent operation records, aliased as
OPNB. - OKC_OPERATIONS_TL (SYNONYM) – the translation table holding language-dependent text, aliased as
OPNT.
The two objects are joined on the operation CODE column, with the _TL side additionally filtered by OPNT.LANGUAGE = USERENV('LANG'). The view is therefore an equi-join view; a row is returned only where a matching translation exists for the current session language. The ROW_ID column is populated from OPNB.ROWID, preserving a pseudocolumn reference to the base table row.
Key Columns
- ROW_ID – exposes the ROWID of the underlying OKC_OPERATIONS_B row.
- CODE – the operation code, the logical key shared between the base and translation tables.
- MEANING – the translated display name of the operation.
- DESCRIPTION – the translated long description of the operation.
- SFWT_FLAG – a translation-table flag attribute associated with the operation record.
- OPN_TYPE – classifies the operation type.
- PURPOSE – the business purpose assigned to the operation.
- OBJECT_VERSION_NUMBER – optimistic locking/versioning column carried from the base table.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns.
Common Use Cases and Queries
Typical usages include validating operation codes before contract authoring, populating LOVs, and extracting operation reference data for downstream integrations. A basic lookup by code:
SELECT code, meaning, description, opn_type, purpose FROM apps.okc_operations_v WHERE code = :p_code;
A listing of all operations by type in the session language:
SELECT code, meaning, purpose FROM apps.okc_operations_v WHERE opn_type = :p_opn_type ORDER BY meaning;
For version-aware processing or interface reconciliation, include the audit columns:
SELECT code, meaning, object_version_number, last_update_date FROM apps.okc_operations_v WHERE last_update_date >= :p_since;
Because the view filters on USERENV('LANG'), queries should be run with the intended language context whenever multilingual data is present.
-
View: OKC_OPERATIONS_V 12.1.1
View for table OKC_OPERATIONS_B
APPS.OKC_OPERATIONS_V·↳ OKC_OPERATIONS_B·↳ OKC_OPERATIONS_TL·Explore OKC module →
-
View: OKC_OPERATIONS_V 12.2.2
View for table OKC_OPERATIONS_B
APPS.OKC_OPERATIONS_V·↳ OKC_OPERATIONS_B·↳ OKC_OPERATIONS_TL·Explore OKC module →
-
VIEW: APPS.OKC_OPERATIONS_V 12.1.1
-
VIEW: APPS.OKC_OPERATIONS_V 12.2.2
-
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.
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates
-
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.1.1
Intersection entity between templates and rules.