Results for “mvt_stat_status”

50+ results




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

Overview

IC_TRAN_PND is the staging table for pending inventory transactions within the Oracle Process Manufacturing (OPM) Inventory module, owned by the GMI schema. In Oracle EBS 12.1.1 and 12.2.2, it functions as the holding area where inventory movements await validation, costing, and final posting to the perpetual inventory ledger. Rows are inserted by material transaction entry forms, open interface programs, and batch processing routines, and are subsequently processed by the Inventory Transaction processor, which validates each line and writes the accepted results into the permanent inventory tables.

The table carries a 45-column physical definition and is classified heuristically as satellite-leaning in Data Vault terms. This classification is a modeling suggestion: the table extends core inventory and item hubs with descriptive, transactional context rather than serving as a pure hub or link. Its primary key, IC_TRAN_PND_PK, is defined on the single column TRANS_ID, a system-generated surrogate identifier.

Key Information Stored

Each record represents one pending inventory transaction line. The most significant columns include:

No additional unique indexes beyond IC_TRAN_PND_PK are documented, so TRANS_ID is the only formal business-key candidate, though combinations of ITEM_ID, WHSE_CODE, LOT_ID, and TRANS_DATE are frequently treated as natural query keys in practice.

Common Use Cases and Queries

The primary operational use case is monitoring and troubleshooting inventory transactions that have not yet posted. A typical query retrieves all pending lines for a given item and warehouse:

  • SELECT TRANS_ID, ITEM_ID, WHSE_CODE, LOT_ID, TRANS_QTY, TRANS_UM, TRANS_STAT FROM IC_TRAN_PND WHERE ITEM_ID = :item AND WHSE_CODE = :whse;

Reconciliation reports join IC_TRAN_PND to IC_ITEM_MST and IC_LOTS_MST to surface item descriptions and lot expiry data. Interfaces that stage transactions before batch validation are validated by counting rows by TRANS_STAT, and lot-status transition audits compare LOT_STATUS values against IC_LOTS_STS. Posting diagnostics commonly filter on GL_POSTED_IND and COMPLETED_IND to isolate rows stuck in the pipeline.

Related Objects

The following related objects are most significant, based on documented foreign key relationships:

  • IC_ITEM_MST / IC_ITEM_MST_B — joined on ITEM_ID for item master validation.
  • IC_LOTS_MST — joined on ITEM_ID and LOT_ID for lot control.
  • IC_LOTS_STS — joined on LOT_STATUS for lot status codes.
  • SY_ORGN_MST / SY_ORGN_MST_B — joined on ORGN_CODE and CO_CODE for company and organization defaults.
  • SY_UOMS_MST — joined on TRANS_UM and TRANS_UM2 for unit-of-measure definitions.
  • MTL_MOVEMENT_STATISTICS — joined on MOVEMENT_ID for movement statistics reporting.
  • IC_STAT_RPT — references IC_TRAN_PND via TRANS_ID as a dependent reporting table.
  • GMD_GRADES_B and QC_GRAD_MST — joined on QC_GRADE for quality grade validation.
  • SY_REAS_CDS / SY_REAS_CDS_B — joined on REASON_CODE for transaction reason codes.