Results for “ic_decm_mst”

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

Overview

IC_DECM_MST is a table owned by the GMI schema and belongs to the Oracle Process Manufacturing (OPM) Inventory module. It is documented as a VALID object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to store information about records in IC_LOCT_INV whose decimal quantities have been reset to tolerance levels. In other words, it acts as a control and audit log for lot/location inventory balances that required correction because their stored decimal quantities exceeded acceptable tolerances.

The ETRM metadata classifies this object heuristically under the Data Vault model as standalone, meaning no foreign key relationships were mined from its structure. As a modeling suggestion, it is best treated as a satellite around the inventory fact records it references logically (through ITEM_ID, WHSE_CODE, LOT_ID, and LOCATION), rather than as a hub or link. This reflects its role as a descriptive audit record rather than an independent business entity.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• LOG_ID — The surrogate primary key, defined by the unique index IC_DECM_MST_PK. This is the column searched via the term "ic_decm_mst_pk".
• ITEM_ID — Identifies the inventory item whose decimal quantity was reset.
• WHSE_CODE — The warehouse in which the affected inventory resides.
• LOT_ID — The lot affected by the tolerance reset.
• LOCATION — The specific storage location within the warehouse.
• LOCT_ONHAND — The on-hand quantity value that was reset to tolerance.
• LOCT_ONHAND2 — A secondary on-hand quantity field, typically used for secondary unit of measure balances.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the log record was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification and the login session responsible.

The only documented unique index is IC_DECM_MST_PK on LOG_ID; no separate business-key unique index is documented, so ITEM_ID/WHSE_CODE/LOT_ID/LOCATION function only as a logical composite reference.

Common Use Cases and Queries

This table is primarily used for reconciliation, audit, and discrepancy investigation. Typical scenarios include:

• Identifying which inventory balances were automatically corrected and why.
• Auditing decimal precision issues in OPM inventory.
• Reporting on tolerance resets by warehouse, item, or date range.

Sample query: SELECT LOG_ID, ITEM_ID, WHSE_CODE, LOT_ID, LOCATION, LOCT_ONHAND, CREATION_DATE FROM GMI.IC_DECM_MST WHERE WHSE_CODE = :whse AND CREATION_DATE >= :from_date ORDER BY CREATION_DATE DESC;

Related Objects

As a standalone object, IC_DECM_MST carries no mined FK relationships. Logically it references:

• IC_LOCT_INV — the primary inventory table on which its records are based, joined via ITEM_ID, WHSE_CODE, LOT_ID, and LOCATION.
• IC_ITEM_MST — joined via ITEM_ID for item detail.
• IC_LOTS_MST — joined via LOT_ID for lot detail.
• IC_WHSE_MST — joined via WHSE_CODE.
• IC_LOCT_MST — joined via LOCATION.

These associations support audit reporting without imposing physical constraints.