Search Results nettable_flag




Overview

The EDW_OPI_LOTD_LOT_LCV view is a source extraction view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OPI (Operations Intelligence) product family and serves as the primary source of lot-level data for the Lot Dimension within the Oracle Business Intelligence / Enterprise Data Warehouse (EDW) data model. The view consolidates lot master records originating from both process manufacturing (OPM) and discrete inventory (INV) sources into a single, unified result set that conforms to the EDW lot dimension load interface.

The view is a UNION ALL construct: the upper branch reads from OPM process manufacturing tables (IC_LOTS_MST, IC_ITEM_MST) and the lower branch reads from the discrete inventory lot table (MTL_LOT_NUMBERS). Each branch joins to EDW_LOCAL_INSTANCE to derive an instance code, which is concatenated into the surrogate primary key EDW_LOT_PK so that lot records remain unique across multiple EBS instances staged into the same warehouse. The EDW_LOT_DP column is hard-coded to 'LOTD', identifying the record type as a lot dimension row during ETL processing.

The user's search term "nettable_flag" maps to the NETTABLE_FLAG column, which the view materialises as a literal NULL for both branches. This is significant: the EBS lot number tables do not carry a nettable attribute at the lot level, so the warehouse load interface explicitly nulls the column to satisfy the target dimension's column contract without asserting a value that cannot be sourced.

Underlying Base Objects

The view is defined over three documented base objects per branch, unified through UNION ALL:

The documented ETRM metadata lists no additional referenced base objects, and the view text confirms the four source tables above.

Key Columns

  • EDW_LOT_PK — Composite surrogate key. For OPM lots it is LOT_ID-ITEM_ID-OPM-INSTANCE_CODE; for INV lots it is INVENTORY_ITEM_ID-ORGANIZATION_ID-LOT_NUMBER-INSTANCE_CODE.
  • EDW_LOT_DP — Dimension discriminator, always 'LOTD'.
  • NETTABLE_FLAG — Explicitly NULL in both branches; no nettable value is derivable at lot level from the source tables.
  • ORGANIZATION_ID / INVENTORY_ITEM_ID — Populated only for INV (discrete) lots; NULL for OPM lots, which are not organisation-scoped in the same manner.
  • NAME and LOT_NAME — Concatenated display names; for OPM, LOT_NO[-SUBLOT_NO](ITEM_NO); for INV, LOT_NUMBER(INVENTORY_ITEM_ID-ORGANIZATION_ID).
  • EXPIRATION_DATE, DESCRIPTION, LOT, PARENT_LOT — Shelf-life, descriptive, and hierarchy attributes.
  • LAST_UPDATE_DATE / CREATION_DATE — Audit columns used for incremental extraction.

Common Use Cases and Queries

This view is consumed by OPI Lot Dimension ETL programs rather than by end-user forms. Typical reporting and diagnostic queries include:

  • Extracting all lots for a dimension load: SELECT * FROM APPS.EDW_OPI_LOTD_LOT_LCV;
  • Identifying discrete lots only: SELECT * FROM APPS.EDW_OPI_LOTD_LOT_LCV WHERE ORGANIZATION_ID IS NOT NULL;
  • Confirming the nettable attribute convention: SELECT EDW_LOT_PK, NETTABLE_FLAG FROM APPS.EDW_OPI_LOTD_LOT_LCV WHERE NETTABLE_FLAG IS NOT NULL; — which returns no rows by design.
  • Incremental staging by audit date: SELECT EDW_LOT_PK, NAME, EXPIRATION_DATE FROM APPS.EDW_OPI_LOTD_LOT_LCV WHERE LAST_UPDATE_DATE >= :last_run_date;

Because NETTABLE_FLAG is hard-coded NULL, consumers should not rely on this view to drive nettable/MRP-sensitive lot logic; that attribute must be sourced elsewhere, typically at the item-organization level.