Results for “okl_industry_code_types_uv”

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

Overview

OKL_INDUSTRY_CODE_TYPES_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL — Lease and Finance Management product. As the name and ETRM description indicate, it presents industry type codes, specifically the classification values used to categorize lessees and other parties by industry (Standard Industrial Classification, or SIC, code types). The suffix "UV" denotes that this is a UI-support view, intended to feed LOVs (Lists of Values), descriptive flexfields, and inquiry screens within the Lease Management application rather than to serve as a transactional table.

In EBS 12.1.1 and 12.2.2 the object is registered as VALID and is defined entirely over Oracle Receivables' lookup infrastructure. Its role in reporting and integration is to expose a clean, denormalized slice of the SIC code type lookups so that Lease Management screens and dependent reports show only the code types that are genuinely meaningful — that is, those that themselves have associated lookup entries. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of AR_LOOKUPS at query time.

Underlying Base Objects

The view is defined over a single documented base object: AR_LOOKUPS, itself a view in the Oracle Receivables schema. AR_LOOKUPS is the standard, long-standing lookup repository in EBS; it stores lookup types, lookup codes, meanings, descriptions, enabled flags, and date ranges that drive virtually every coded value in the Receivables and related product families.

The view text applies a self-referential filter. It selects rows from AR_LOOKUPS where LOOKUP_TYPE equals 'SIC_CODE_TYPE' — the lookup type that designates a record as an industry code type — and then applies an EXISTS subquery that requires a second AR_LOOKUPS row whose LOOKUP_TYPE equals the first row's LOOKUP_CODE. This correlated EXISTS clause effectively restricts the output to code types that have actually been populated with subordinate lookup values, filtering out orphaned or unused code type definitions. The construction means the view inherits the security, enablement, and translation behavior of AR_LOOKUPS but adds a structural completeness check specific to the Lease Management (OKL) UI requirement.

Key Columns

• INDUSTRY_CODE_TYPE — mapped from IDTY.LOOKUP_CODE. The short code identifying the industry classification type (for example, the SIC code type used by the lessee). This is the primary value surfaced to LOVs and inquiry screens.
• INDUSTRY_CODE_TYPE_MEANING — mapped from IDTY.MEANING. The user-facing, translatable label shown in the interface; this is the descriptive text presented to end users when selecting an industry code type.
• INDUSTRY_CODE_TYPE_DESC — mapped from IDTY.DESCRIPTION. The longer free-form description providing additional context about the code type, used for informational display and reporting.

All three columns are derived characteristics of the AR_LOOKUPS row rather than independent attributes, which keeps the view consistent with standard EBS lookup semantics.

Common Use Cases and Queries

Typical uses include populating an industry code type LOV on Lease Management setup and party-entry forms, validating imported or interfaced lessee data, and driving reports that summarize leases by industry classification. Because the view is already filtered to populated SIC code types, consumers can query it directly without re-implementing the EXISTS logic.

A representative query retrieving all available industry code types, ordered for display, is:

• SELECT industry_code_type, industry_code_type_meaning, industry_code_type_desc FROM apps.okl_industry_code_types_uv ORDER BY industry_code_type_meaning;

To resolve a single code type for a specific record, a query filtered on the code would be used:

• SELECT industry_code_type_meaning FROM apps.okl_industry_code_types_uv WHERE industry_code_type = :p_code_type;

For validation or integration checks, the view can be joined to Lease Management party or lease tables on the code type column to confirm that only active, populated code types are referenced. As with any APPS-owned object, access should be granted through the standard OKL responsibilities rather than by direct grants. Because the content is sourced from AR_LOOKUPS, any addition, disabling, or translation of SIC code type lookups is reflected immediately in the view's output, making it the preferred, low-maintenance access point for industry code type reporting in Oracle Lease and Finance Management.