Search Results sic_code_type




Overview
Explore in AI Chat

Overview

APPS.OKL_INDUSTRY_CODES_UV is a reporting view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 landscape, owned by the APPS schema. It exposes the industry code (SIC) values that Oracle Lease and Finance Management (OKL) uses to classify lessees and contracts by their Standard Industrial Classification. The view is intended for read-only reporting and integration rather than for transactional updates; it flattens the underlying lookup architecture into a single, presentation-friendly projection that joins each industry code to its parent SIC code type.

The view is particularly relevant to users searching on "sic_code_type," because that term is the driving lookup type in the view's WHERE clause. It returns the categorized list of SIC type codes along with the industry codes that belong to each type, together with the meaning and description attributes carried on the underlying lookup rows.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: AR_LOOKUPS, itself delivered as a view over the Receivables lookup tables. The view definition references AR_LOOKUPS twice, using the aliases IDTY and IDTC, producing an internal join of the lookup table against itself.

The filtering condition restricts the driving row to records where IDTY.LOOKUP_TYPE equals the literal value 'SIC_CODE_TYPE'. The join predicate then matches IDTC.LOOKUP_TYPE to IDTY.LOOKUP_CODE, meaning an industry code row (IDTC) is returned only where its lookup_type value equals the lookup_code of a SIC code type row (IDTY). This creates a classification hierarchy in which each lookup_code under SIC_CODE_TYPE acts as the lookup_type namespace for the industry codes beneath it. Because both columns are read from the same base view, no additional tables are required and the result set is bounded by the rows defined in the AR lookup repository.

Key Columns

  • INDUSTRY_CODE — sourced from IDTC.LOOKUP_CODE; the individual industry code value under a given SIC code type.
  • INDUSTRY_CODE_MEANING — sourced from IDTC.MEANING; the user-facing label shown in list of values and reports.
  • INDUSTRY_CODE_DESC — sourced from IDTC.DESCRIPTION; the longer descriptive text for the industry code.
  • INDUSTRY_CODE_TYPE — sourced from IDTY.LOOKUP_CODE; the parent classification, identical to the SIC_CODE_TYPE lookup value used in the filter.

Only rows defined under the SIC_CODE_TYPE lookup type are surfaced, and the type column is repeated across every industry code belonging to that type.

Common Use Cases and Queries

The view is typically used to populate list of values, validate industry code entry, and drive segmentation reporting in leasing and finance. A common query retrieves all industry codes for a specific type:

  • SELECT industry_code, industry_code_meaning, industry_code_desc, industry_code_type FROM apps.okl_industry_codes_uv WHERE industry_code_type = :p_type ORDER BY industry_code;
  • SELECT DISTINCT industry_code_type FROM apps.okl_industry_codes_uv ORDER BY 1; — enumerates the available SIC code types.
  • SELECT industry_code, industry_code_meaning FROM apps.okl_industry_codes_uv WHERE UPPER(industry_code_meaning) LIKE '%BANK%'; — ad hoc searching by description or meaning.

Because the source is a lookup-based view, values are maintained through the Receivables lookup administration rather than by direct DML. Queries should therefore be treated as read-only and joined to contract or party tables on the industry code value when building analytic reports.