Results for “op_code”

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

Overview

IC_TRAN_CMP is the completed inventory transaction table within the Oracle Process Manufacturing (OPM) Inventory module, owned by the GMI schema. In Oracle EBS 12.1.1 and 12.2.2, this table stores the permanent record of inventory transactions that have been fully processed and posted — as distinct from pending or staged transaction tables that hold in-flight activity. Once a transaction completes its lifecycle (validation, costing, and general ledger posting), its details are written to IC_TRAN_CMP, making it the authoritative source for historical inventory movement reporting in process manufacturing environments.

From a Data Vault modeling perspective, the metadata's heuristic classification for this table is satellite-leaning. It carries a single-column surrogate primary key (TRANS_ID) plus a wide set of descriptive attributes — dates, quantities, statuses, and flags — that describe the state of a transactional event rather than defining a durable business entity or a many-to-many relationship. This suggests the table functions best as a descriptive satellite attached to a transaction hub or link, rather than as a standalone hub.

Key Information Stored

The table contains 41 documented columns. The most consequential include:

• TRANS_ID — surrogate primary key (IC_TRAN_CMP_PK); the unique identifier for each completed transaction.
• ITEM_ID — the inventory item involved; a heavily referenced foreign key.
• LOT_ID and LOT_STATUS — lot control and its status at transaction time.
• WHSE_CODE — the warehouse where the movement occurred.
• CO_CODE and ORGN_CODE — company and organization context.
• TRANS_DATE and CREATION_DATE — business and system timestamps.
• TRANS_QTY and TRANS_QTY2 — primary and secondary transaction quantities.
• TRANS_UM and TRANS_UM2 — the corresponding units of measure.
• DOC_TYPE, DOC_ID, and DOC_LINE — source document context.
• REASON_CODE — the reason attributed to the movement.
• TRANS_STAT — transaction status.
• GL_POSTED_IND — flag indicating general ledger posting.
• QC_GRADE — quality grade assigned to the item.
• MOVEMENT_ID — link to movement statistics.

No separate unique business-key index is documented beyond the surrogate primary key on TRANS_ID, meaning TRANS_ID is the sole documented unique identifier.

Common Use Cases and Queries

Typical reporting use cases include inventory movement analysis, lot traceability, GL reconciliation, and audit of completed transactions over a period. A representative query retrieves completed movements for an item across a date range:

• SELECT item_id, whse_code, lot_id, trans_qty, trans_date FROM ic_tran_cmp WHERE item_id = :item AND trans_date BETWEEN :from AND :to;
• Lot traceability: filter on LOT_ID and LOT_STATUS to reconstruct a lot's movement history.
• GL reconciliation: use GL_POSTED_IND to identify transactions pending or completed posting.
• Warehouse throughput: aggregate TRANS_QTY grouped by WHSE_CODE and ORGN_CODE.

The IC_STAT_RPT table references TRANS_ID, supporting statistical reporting derived from these completed records.

Related Objects

• IC_ITEM_MST / IC_ITEM_MST_B — item master, joined on ITEM_ID.
• IC_LOTS_MST — lot master, joined on ITEM_ID and LOT_ID.
• IC_LOTS_STS — lot status, joined on LOT_STATUS.
• IC_WHSE_MST — warehouse master, joined on WHSE_CODE.
• SY_ORGN_MST / SY_ORGN_MST_B — organization and company, joined on ORGN_CODE and CO_CODE.
• SY_UOMS_MST — units of measure, joined on TRANS_UM and TRANS_UM2.
• GMD_GRADES_B / QC_GRAD_MST — quality grades, joined on QC_GRADE.
• SY_REAS_CDS / SY_REAS_CDS_B — reason codes, joined on REASON_CODE.
• IC_STAT_RPT — statistical report table referencing this table via TRANS_ID.
• MTL_MOVEMENT_STATISTICS — movement statistics, joined on MOVEMENT_ID.