Search Results join_doc_id




Overview
Explore in AI Chat

Overview

APPS.PMITS_INV_LINE_SUMM_V is a Business Intelligence System (BIS) view owned by the APPS schema and registered in Oracle E-Business Suite under the FND Design Data identifier PMI.PMITS_INV_LINE_SUMM_V. It exposes summarized inventory transaction line information drawn from the Process Manufacturing (PMI/OPM) inventory tables, presenting a denormalized, security-filtered projection of inventory movements suitable for reporting and downstream integration. The view is documented as VALID in both the 12.1.1 and 12.2.2 releases, and is not referenced by any other database object, meaning it functions strictly as a read-only consumer of the underlying inventory and lot data.

Because the view surfaces the column TRANSACTION_SECONDARY_UOM alongside TRANSACTION_UOM, it is directly relevant to queries concerning dual-unit-of-measure inventory accounting, including the search term "transaction_secondary_uom". This makes it a convenient access point when reporting on OPM inventory movements captured in both primary and secondary UOMs without navigating the underlying transactional tables directly.

Underlying Base Objects

The view is defined over the following documented dependencies:

The view therefore joins transactional inventory data to item and lot master attributes, while enforcing security through PMI_SECURITY_PKG and formatting dates through FND_DATE. This composition explains why the columns are largely denormalized and include both codes and identifiers.

Key Columns

  • DOC_ID, JOIN_DOC_ID, DOC_TYPE — document identity and type; JOIN_DOC_ID carries the actual document ID for transfer, transfer-in, transfer-out, and inter-org transaction types (XFER, TRNI, TRNR, MTRI).
  • LINE_ID, ITEM_ID — detail line identifier and item identifier.
  • COMPANY_CODE, ORGANIZATION_CODE, WAREHOUSE_CODE, LOCATION — organizational and physical context of the transaction.
  • TRANSACTION_DATE — transaction date, rendered as a string via FND_DATE.
  • LOT_ID, LOT_NUMBER, SUBLOT_NUMBER, LOT_STATUS, QUALITY_CONTROL_GRADE — lot and quality attributes.
  • REASON_CODE — reason for the transaction.
  • TRANSACTION_UOM, TRANSACTION_SECONDARY_UOM — the primary and secondary units of measure for the transaction; the latter is the column targeted by the user's search.
  • TRANSACTION_QTY, TRANSACTION_QTY2 — quantities in the primary and secondary UOMs respectively.
  • TRANS_TYPE — transaction type; documented as used to join subsidiary ledger data with inventory data.

Common Use Cases and Queries

Typical uses include inventory movement reporting, dual-UOM analysis, lot traceability, and reconciling inventory transactions with subsidiary ledger data via TRANS_TYPE. The security package restricts results to the organizations and warehouses the runtime user is authorized to see.

To isolate transactions carrying secondary UOM information:

  • SELECT DOC_ID, ITEM_ID, TRANSACTION_UOM, TRANSACTION_SECONDARY_UOM, TRANSACTION_QTY, TRANSACTION_QTY2 FROM APPS.PMITS_INV_LINE_SUMM_V WHERE TRANSACTION_SECONDARY_UOM IS NOT NULL;

To trace a specific lot across warehouses:

  • SELECT LOT_NUMBER, SUBLOT_NUMBER, ORGANIZATION_CODE, WAREHOUSE_CODE, TRANSACTION_DATE, TRANSACTION_QTY, TRANSACTION_SECONDARY_UOM FROM APPS.PMITS_INV_LINE_SUMM_V WHERE LOT_NUMBER = :lot;

To summarize movement by transaction type:

  • SELECT TRANS_TYPE, COUNT(*), SUM(TRANSACTION_QTY) FROM APPS.PMITS_INV_LINE_SUMM_V GROUP BY TRANS_TYPE;

Because the view is not referenced by other database objects and enforces security at query time, it serves as a stable, read-only reporting surface rather than a transactional interface.