Search Results product_line_dp

Overview

The EDW_ITEM_PROD_LINE_LCV view is an Oracle E-Business Suite database object owned by the APPS schema and registered to the Engineering (ENG) product module. As its LCV (List of Values / collection view) suffix implies, it is an interface-oriented construct designed to expose product line information in a denormalized, reporting-friendly form. The view conforms product line reference data drawn from interest types into the dimensional structure expected by Oracle's Enterprise Data Warehouse and downstream integration consumers.

This view is documented as VALID in both EBS 12.1.1 and 12.2.2, and the view text carries a WITH READ ONLY clause, confirming it is a query-only object that presents data for extraction, ETL, and analytical reporting rather than transactional maintenance. Within the EBS reporting and integration landscape, such views typically serve as the source for product line dimension loads in the data warehouse, providing a stable, surrogate-keyed representation of product line records.

Underlying Base Objects

The documented metadata lists no referenced base objects, but the embedded view text reveals the actual source objects. The view is defined over two objects joined in the FROM clause:

• AS_INTEREST_TYPES_V (aliased INTYP) — a secured view over interest type setup data, supplying the core product line attributes such as interest type, description, and enablement flags.
• EDW_LOCAL_INSTANCE (aliased INST) — a single-row EDW infrastructure table providing the local instance code used to construct the composite primary key.

The join is effectively a cross join, since EDW_LOCAL_INSTANCE yields one instance code applied uniformly to every qualifying interest type record. The WHERE clause restricts output to interest types flagged with EXPECTED_PURCHASE_FLAG = 'Y', limiting the result set to product lines that participate in expected-purchase activity.

Key Columns

• PRODUCT_LINE_PK — The composite surrogate key, concatenating INTEREST_TYPE_ID, the instance code, and the literal -INTR_TYPE.
• ALL_FK — A constant value of 'ALL', typically used as an "all members" foreign key for dimension aggregation.
• PRODUCT_LINE_DP, NAME — Display name and descriptive label, both sourced from INTYP.INTEREST_TYPE.
• DESCRIPTION — Descriptive text for the product line.
• INTEREST_TYPE_ID — The numeric identifier of the underlying interest type.
• ENABLED_FLAG — Mapped from MASTER_ENABLED_FLAG, indicating whether the product line is active.
• INSTANCE_CODE — The local instance identifier from EDW_LOCAL_INSTANCE.
• CREATION_DATE, LAST_UPDATE_DATE — Standard EBS audit columns.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Descriptive flexfield placeholders, all returned as NULL.
• DELETION_DATE — Explicitly returned as TO_DATE(NULL). This is the column associated with the user's search term: within this view, DELETION_DATE is a placeholder that is always NULL, meaning the view exposes no soft-delete or end-dating information for product lines.

Common Use Cases and Queries

The view is most commonly consumed by ETL processes populating the product line dimension, and by ad-hoc queries listing valid product lines. Because DELETION_DATE is always NULL, queries filtering on deletion status will return all rows.

A representative query for dimensional extraction is:

• SELECT PRODUCT_LINE_PK, PRODUCT_LINE_DP, NAME, DESCRIPTION, INTEREST_TYPE_ID, ENABLED_FLAG FROM EDW_ITEM_PROD_LINE_LCV;

To list only enabled product lines:

• SELECT PRODUCT_LINE_PK, NAME, INSTANCE_CODE FROM EDW_ITEM_PROD_LINE_LCV WHERE ENABLED_FLAG = 'Y' ORDER BY NAME;

Where a query references DELETION_DATE, the NULL result should be understood as a defined behavior of this view rather than missing data. Consumers requiring soft-delete semantics must source them elsewhere.