Results for “pdt_1”

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

Overview

APPS.OKL_PRODUCTS_UV is a user-facing database view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It presents a consolidated, reporting-friendly projection of lease product definitions by joining the base product view OKL_PRODUCTS_V to itself in a self-join on the REPORTING_PDT_ID column, allowing each product row to carry the descriptive name of its associated reporting product. This self-referential join enriches the product record with both the operational product identity and the reporting hierarchy relationship in a single result set.

The view is defined with a single outer join (pdt.reporting_pdt_id = pdt_1.id(+)), ensuring that products without an assigned reporting product are still returned, with the reporting product name appearing as NULL. Because it exposes descriptive attributes, status meanings, and the full ATTRIBUTE1 through ATTRIBUTE15 flexfield range, OKL_PRODUCTS_UV serves as a convenient integration and reporting source for downstream applications, concurrent programs, and custom reports that need flattened access to lease product metadata for Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented view metadata, OKL_PRODUCTS_UV is defined over two referenced base objects:

• OKL_PRODUCTS_V (VIEW) — the primary source, aliased twice as PDT and PDT_1. PDT supplies the main product row; PDT_1 is the self-join partner that resolves to the reporting product, supplying only its NAME as REPORTING_PRODUCT.
• OKL_ACCOUNTING_UTIL (PACKAGE) — invoked in the SELECT list through OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING, used to translate the PRODUCT_STATUS_CODE into a human-readable status meaning based on the OKL_PRODUCT_STATUS lookup.

The view therefore does not directly reference a base table; it layers its logic on top of the pre-existing OKL_PRODUCTS_V view, inheriting that view's filtering and column derivation, and adds the reporting-product join and status translation on top.

Key Columns

• ID, NAME, VERSION — unique identifier, product name, and version of the lease product.
• PTL_ID, AES_ID — identifiers linking the product to its product template line and accounting/attribute setup context.
• FROM_DATE, TO_DATE — effective date range during which the product definition is active.
• LEGACY_PRODUCT_YN / PRODUCT_YN — flag indicating whether the product originates from a legacy source.
• REPORTING_PDT_ID and REPORTING_PRODUCT — the identifier of the parent reporting product and, via the self-join, its name; REPORTING_PRODUCT is NULL when no reporting product is assigned.
• PRODUCT_STATUS_CODE and PRODUCT_STATUS_MEANING — the coded status and its translated meaning derived through OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING against the OKL_PRODUCT_STATUS lookup.
• DESCRIPTION (aliased DESCTIPTION), OBJECT_VERSION_NUMBER — descriptive text and optimistic-locking version indicator.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the product's descriptive flexfield context and segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit who-columns.

Common Use Cases and Queries

The view is typically used in reporting and integration queries requiring product status meanings and reporting-product resolution without manually joining the self-referencing structure. A typical query retrieves active, non-legacy products with their reporting parent:

• SELECT id, name, reporting_product, product_status_meaning FROM apps.okl_products_uv WHERE product_yn = 'N' AND SYSDATE BETWEEN from_date AND NVL(to_date, SYSDATE);
• SELECT name, reporting_product FROM apps.okl_products_uv WHERE reporting_pdt_id IS NOT NULL ORDER BY reporting_product, name;

These patterns support product catalog listings, reporting-hierarchy analysis, and downstream integrations that need a flat, human-readable lease product feed in Oracle EBS 12.1.1 and 12.2.2.