Results for “loct_desc”

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

Overview

GML_GPOAO_DETAIL_ALLOCATIONS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the GML - Process Manufacturing Logistics product family. Its documented purpose is to expose Sales Order Detail Allocations, presenting lot-level allocation detail for pending inventory transactions associated with process manufacturing sales orders. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is available to any reporting, integration, or inquiry component that holds SELECT privileges on the synonym.

Functionally, the view is a denormalized read layer that joins transaction detail to lot master attributes, lot status descriptions, location descriptions, and quality grade descriptions. It removes the need for downstream reports to reconstruct these joins independently, ensuring a consistent interpretation of allocation quantities, units of measure, and lot status text. Because the underlying pending-transaction table IC_TRAN_PND is the staging area for inventory movements before posting, the view reflects allocation activity that is in-flight rather than fully posted, making it useful for operational monitoring rather than purely historical analysis.

The user-requested column STATUS_DESC is the descriptive text of the lot status code. It is sourced from IC_LOTS_STS and is critical for reconciliation and status-driven reporting, since numeric status codes alone are not self-describing.

Underlying Base Objects

The view definition filters the pending transaction table to document type 'OPSO' with a delete mark of zero, then joins to four reference tables. The documented base objects, all exposed through APPS synonyms, are:

• IC_TRAN_PND — Pending inventory transaction table; the driving table supplying LINE_ID, TRANS_ID, LOT_STATUS, LOCATION, TRANS_QTY, and related fields.
• IC_LOTS_MST — Lot master; supplies LOT_NO, VENDOR_LOT_NO, SUBLOT_NO, LOT_DESC, QC_GRADE, LOT_CREATED, and EXPIRE_DATE.
• IC_LOTS_STS — Lot status definition; supplies STATUS_DESC.
• IC_LOCT_MST — Location master; supplies LOCT_DESC and is joined on both LOCATION and WHSE_CODE.
• QC_GRAD_MST — Quality grade master; supplies QC_GRADE_DESC.

Notably, the joins to IC_LOTS_STS and QC_GRAD_MST are outer joins (marked with the (+) operator), so a transaction whose lot status or quality grade has no matching definition row will still appear, with NULL in STATUS_DESC or QC_GRADE_DESC. The joins to IC_LOTS_MST and IC_LOCT_MST are inner joins, so missing lot or location master rows will suppress the record.

Key Columns

The twenty columns of the view fall into four functional groups. The first group identifies the transaction and lot: LINE_ID and TRANS_ID key the pending transaction line, while LOT_NO, VENDOR_LOT_NO, SUBLOT_NO, and LOT_DESCRIPTION describe the allocated lot. The second group covers status and location: LOT_STATUS is the numeric status code, STATUS_DESC is its human-readable description, LOCATION is the location code, and LOCT_DESC is its descriptive name. The third group addresses quality: QC_GRADE and QC_GRADE_DESC. The fourth group carries allocation quantities: QUANTITY1 and UOM1_INT form the primary quantity and its internal unit of measure, with QUANTITY2 and UOM2_INT providing a secondary quantity and unit where dual UOM tracking applies.

Auxiliary date and reason fields complete the model: REASON_CODE, LOT_CREATED, and EXPIRE_DATE. EXPIRE_DATE is particularly relevant for shelf-life-sensitive allocation reporting, while LOT_CREATED supports lot age and traceability analysis.

Common Use Cases and Queries

The view is typically used for pending allocation inquiry, lot status verification before shipment, and integration feeds into warehouse or third-party logistics systems. Because STATUS_DESC is a plain text column, it is well suited to filters that avoid hard-coded status codes.

A representative query retrieving allocated lines by status text, ordered by expiration, would be:

• SELECT LINE_ID, LOT_NO, STATUS_DESC, LOCATION, LOCT_DESC, QUANTITY1, UOM1_INT, EXPIRE_DATE FROM APPS.GML_GPOAO_DETAIL_ALLOCATIONS_V WHERE STATUS_DESC = 'Released' ORDER BY EXPIRE_DATE;
• SELECT LOT_NO, QC_GRADE_DESC, QUANTITY1, QUANTITY2 FROM APPS.GML_GPOAO_DETAIL_ALLOCATIONS_V WHERE QC_GRADE_DESC IS NOT NULL;
• SELECT COUNT(*), LOT_STATUS FROM APPS.GML_GPOAO_DETAIL_ALLOCATIONS_V GROUP BY LOT_STATUS;

The final example is useful for identifying status codes that lack a matching definition, since those records will not resolve to a STATUS_DESC value and may indicate incomplete status setup.