Results for “okl_cp_status_code_uv”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_CP_STATUS_CODE_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Leasing and Finance Management) product family. The suffix "UV" denotes a user-facing validation view, a naming convention Oracle applies to lightweight lookup views that expose a filtered set of values for use in forms, concurrent programs, and integration logic. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is documented under the ETRM (E-Business Suite Technical Reference Manual) for the OKL module.
The view presents a curated subset of Oracle Application Object Library lookup values drawn from the CP_STATUS_CODE lookup type. Specifically, it filters the underlying lookup table so that the codes 'I', 'R', and 'Z' are excluded from the result set. This view therefore acts as the authoritative list of permitted counterparty or contract party status codes available to the application at runtime and to any custom reporting or integration layer that consumes EBS data.
Underlying Base Objects
The view is defined over two documented objects:
- FND_LOOKUPS — the Oracle Application Object Library view that stores lookup types, lookup codes, meanings, descriptions, and related attributes used throughout EBS. OKL_CP_STATUS_CODE_UV selects the LOOKUP_TYPE, LOOKUP_CODE, and MEANING columns from this source.
- FND_GLOBAL — the standard EBS package referenced for session context (such as user, responsibility, or application identifiers). Although the view text presented in the metadata does not explicitly join FND_GLOBAL, its inclusion reflects the dependency typically required for row-level security or environment resolution performed through the foundation layer.
Because the view is built on FND_LOOKUPS, any change made to the CP_STATUS_CODE lookup type — such as adding a new lookup code or altering a meaning — is immediately reflected, except for the three codes explicitly excluded by the WHERE clause.
Key Columns
The view exposes three columns, each inherited directly from FND_LOOKUPS:
- LOOKUP_TYPE — the lookup category identifier. For every row returned by this view the value is 'CP_STATUS_CODE', making the column useful primarily for join consistency or for downstream queries that must match the source lookup type explicitly.
- LOOKUP_CODE — the short internal identifier for each status value. This is the code stored in business tables and used in programmatic comparisons. The values 'I', 'R', and 'Z' are deliberately suppressed.
- MEANING — the user-facing, translatable description associated with the lookup code. It is the value normally displayed in LOVs, reports, and user interfaces.
Common Use Cases and Queries
The principal use case is populating list-of-values controls and report parameters in OKL-related extensions and interfaces, ensuring that only valid, non-suppressed status codes are offered to users. A typical query retrieving all available statuses is:
SELECT lookup_code, meaning FROM apps.okl_cp_status_code_uv ORDER BY meaning;
When joining business data to the view, the lookup code serves as the join key:
SELECT t.party_id, t.status_code, v.meaning FROM apps.okl_parties t, apps.okl_cp_status_code_uv v WHERE t.status_code = v.lookup_code;
A third common pattern validates an incoming integration value before insertion, for example by selecting the meaning for a supplied code and rejecting the transaction if no row is returned. Because the view already excludes the 'I', 'R', and 'Z' codes, integration logic benefits from built-in data integrity enforcement without replicating the exclusion filter in custom code. This makes OKL_CP_STATUS_CODE_UV a stable and dependable reference object across both EBS 12.1.1 and 12.2.2.
-
View: OKL_CP_STATUS_CODE_UV 12.1.1
APPS.OKL_CP_STATUS_CODE_UV·↳ FND_GLOBAL·↳ FND_LOOKUPS·Explore OKL module →
-
View: OKL_CP_STATUS_CODE_UV 12.2.2
APPS.OKL_CP_STATUS_CODE_UV·↳ FND_GLOBAL·↳ FND_LOOKUPS·Explore OKL module →
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.FND_LOOKUPS 12.1.1
-
VIEW: APPS.FND_LOOKUPS 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards