Results for “product_status_code”

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

Overview

OKL_PRODUCTS_UV is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family (Leasing and Finance Management) and serves as the base view for the Products screen within that module. The view consolidates all product information maintained by the leasing application, exposing both operational attributes and descriptive Flexfield context, and functions as a single denormalized read layer over the underlying product definition. Because it also returns descriptive lookups and a self-joined reporting product name, it is well suited to reporting, integration, and data-extraction scenarios where a consumer requires product data without navigating the normalized base structures.

Underlying Base Objects

Per documented ETRM 12.2.2 metadata, OKL_PRODUCTS_UV is defined over OKL_PRODUCTS_V, which is the primary product view. The view self-joins OKL_PRODUCTS_V a second time (aliased PDT_1) using an outer join on the reporting product identifier, such that PKDT.REPORTING_PDT_ID = PDT_1.ID(+). This join resolves the internal reporting product identifier to a human-readable product name, denormalizing the reference within the same result set. The view also references OKL_ACCOUNTING_UTIL, a PL/SQL package, whose GET_LOOKUP_MEANING function is invoked to translate the stored product status code into its display meaning using the OKL_PRODUCT_STATUS lookup. All objects reside in the APPS schema and the view status is VALID. Note that the view does not reference the base product table directly; it is layered entirely on OKL_PRODUCTS_V plus the accounting utility package.

Key Columns

• ID, NAME, VERSION, DESCRIPTION — primary product identity attributes; FROM_DATE and TO_DATE bound the effective period.
• PTL_ID and AES_ID — identifiers linking the product to its price list and accounting association structures.
• PRODUCT_YN — carries the LEGACY_PRODUCT_YN value, indicating whether the record is a legacy product.
• LEGACY_PRODUCT_YN — the legacy product flag, exposed directly and also mapped through PRODUCT_YN.
• REPORTING_PDT_ID and REPORTING_PRODUCT — the reporting product identifier and its resolved name (the latter supplied via the outer self-join).
• PRODUCT_STATUS_CODE and PRODUCT_STATUS_MEANING — the stored status code and its lookup meaning obtained from OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive Flexfield context and segment values.
• OBJECT_VERSION_NUMBER — optimistic locking support; CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view supports product inquiry screens, reporting extracts, and integrations that require product detail with resolved status and reporting product. A typical query filters active products and returns the descriptive meaning:

• List non-legacy active products: SELECT id, name, product_status_meaning FROM okl_products_uv WHERE legacy_product_yn = 'N' AND product_status_code = 'ACTIVE';
• Retrieve product with its reporting product name: SELECT id, name, reporting_product FROM okl_products_uv WHERE reporting_pdt_id IS NOT NULL;
• Audit extract on Flexfield values: SELECT id, name, attribute_category, attribute1, attribute2 FROM okl_products_uv;
• Identify legacy products for migration or cleanup: SELECT id, name, version, from_date, to_date FROM okl_products_uv WHERE nvl(legacy_product_yn,'N') = 'Y';

Because PRODUCT_YN and LEGACY_PRODUCT_YN both derive from the same source column, consumers should avoid treating them as independent flags when building business logic.