Search Results okl_industry_codes_uv




Overview
Explore in AI Chat

Overview

OKL_INDUSTRY_CODES_UV is a user interface (UI) view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the OKL product family, Oracle Leasing and Finance Management, an application that supports the full lease lifecycle including origination, contract management, asset servicing, and termination. The view exists to provide a denormalized, presentation-friendly source of data for the industry codes List of Values (LOV) used by the OKL user interface.

The "code" in OKL industry codes refers to Standard Industrial Classification (SIC) codes, which classify businesses by the type of economic activity they perform. Within Leasing and Finance Management, these codes are attached to customers, lessees, and prospects to support credit analysis, risk segmentation, and reporting. Rather than exposing the raw ingestion structure of Oracle's generic lookup infrastructure, the view assembles the industry code value, its human-readable meaning, its supplementary description, and the code's classification type into a single flat record set. This makes the view suitable for LOV queries, descriptive flexfield defaulting, and lightweight integration extraction, and it shields consuming forms and reports from the need to understand the lookup typing conventions used in the underlying data.

Underlying Base Objects

The documented definition of OKL_INDUSTRY_CODES_UV references a single base object: AR_LOOKUPS, itself surfaced in the EBS data dictionary as a view over the core lookup table FND_LOOKUPS. The view is a self-join of AR_LOOKUPS. The first alias, IDTC, supplies the actual industry code rows, while the second alias, IDTY, supplies the classification rows that define the available industry code types.

The join condition links the two instances by matching the industry code's LOOKUP_TYPE to the classification's LOOKUP_CODE. The classification side is constrained so that only rows whose LOOKUP_TYPE equals the literal value 'SIC_CODE_TYPE' qualify. In practical terms, this means the set of SIC code types registered under the SIC_CODE_TYPE lookup type defines the parent categories, and every industry code whose LOOKUP_TYPE equals one of those type codes becomes a child row in the view. The result is a two-level hierarchy flattened into a single row per industry code.

Key Columns

  • INDUSTRY_CODE — Sourced from IDTC.LOOKUP_CODE. The stored code value that uniquely identifies an industry classification and the value typically saved on the transaction or customer record.
  • INDUSTRY_CODE_MEANING — Sourced from IDTC.MEANING. The display name or meaning of the industry code, and the value typically presented to the user in the LOV.
  • INDUSTRY_CODE_DESC — Sourced from IDTC.DESCRIPTION. A longer descriptive text associated with the industry code, useful where the meaning alone is insufficiently specific.
  • INDUSTRY_CODE_TYPE — Sourced from IDTY.LOOKUP_CODE. The parent classification, or type, under which the industry code is organized, derived from the 'SIC_CODE_TYPE' lookup set.

Common Use Cases and Queries

The primary use case is driving the industry code LOV on OKL forms, where the view supplies the code and meaning pairs in a compact, already-filtered result set. The view also supports ad hoc reporting on customer or lease population by industry, and can be joined to base tables such as OKL_CUSTOMERS or OKL_TRX_CONTRACTS to resolve stored code values into readable descriptions. Because it reads from lookup tables, results respect whatever SIC code set has been enabled in the instance, so reports remain aligned with configuration rather than hard-coded lists.

A representative query retrieves every industry code with its type:

SELECT industry_code,
       industry_code_meaning,
       industry_code_desc,
       industry_code_type
  FROM apps.okl_industry_codes_uv
 ORDER BY industry_code_type, industry_code;

To limit results to a single classification, add a predicate on INDUSTRY_CODE_TYPE. To resolve codes already recorded on another entity, join on INDUSTRY_CODE to the stored code column and select INDUSTRY_CODE_MEANING for display. When the view is queried from a reporting schema rather than APPS, the standard EBS grants and synonyms for the OKL objects apply.