Results for “ic_cycl_adt”

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

Overview

GMI.IC_CYCL_ADT (Cycle Audit) is a Process Manufacturing Inventory table in Oracle E-Business Suite, owned by the GMI schema and marked VALID in both 12.1.1 and 12.2.2. It records the outcome of physical cycle counting activity against inventory, capturing counted quantities, on-hand balances, variances, and the subsequent post-count adjustments for each item, lot, and warehouse location combination. The table functions as the audit and reconciliation layer between a cycle count event and the inventory balances ultimately updated by posting.

Within a heuristic Data Vault classification derived from the foreign-key structure, IC_CYCL_ADT is best modeled as a link entity: it resolves relationships among a cycle definition, an inventory item, a warehouse/location, a lot/sublot, and reference data such as document type and units of measure. This is a modeling suggestion rather than a documented Data Vault design.

Key Information Stored

The table comprises 39 documented columns. Its surrogate primary key is IC_CYCL_ADT_PK (CYCLE_ID, SEQ_NO), with SEQ_NO — the column surfaced by the user's search — providing the sequence component that uniquely orders audit rows within a given cycle. A second unique index, IC_CYCL_ADT_U1 (SEQ_NO, CYCLE_ID, ITEM_ID, WHSE_CODE, LOCATION, LOT_NO, SUBLOT_NO), acts as a composite business-key candidate that guarantees a single audit record per item/location/lot context within a cycle.

• CYCLE_ID / SEQ_NO — cycle identifier and sequence number forming the composite primary key.
• CYCL_ADT_ID — surrogate identifier for the audit record.
• ITEM_ID, LOT_ID, LOT_NO, SUBLOT_NO — the item and lot/sublot being counted.
• WHSE_CODE, LOCATION — warehouse and storage location.
• CYCLE_NO, COUNT_NO, ITEM_NO, ITEM_DESC1 — cycle reference, count iteration, and descriptive item data.
• TRANS_QTY1 / TRANS_QTY2, COUNT_QTY1 / COUNT_QTY2 — transaction and counted quantities in the two UOMs (UOM1, UOM2).
• ONHAND, ONHAND2, VAR_QTY1, VAR_QTY2, VAR_PERCENT — system on-hand, absolute variance, and variance percentage.
• POST_ONHAND, POST_ONHAND2 — the adjusted on-hand written after posting.
• DOC_TYPE — document type, and FROZEN_QTY1 / FROZEN_QTY2 — frozen quantities at count time.
• TRANS_DATE, CYCLE_START_DT, ITEM_COUNT_DT — transaction and count dates.

Common Use Cases and Queries

Typical reporting covers cycle count accuracy, variance analysis, and audit trail reconstruction. A variance report retrieves audit rows for a cycle ordered by the sequence key:

SELECT cycle_id, seq_no, item_id, whse_code, location,
       onhand, count_qty1, var_qty1, var_percent
  FROM   gmi.ic_cycl_adt
 WHERE  cycle_id = :cycle_id
   AND  delete_mark = 0
 ORDER BY seq_no;

Lot-level accuracy queries group variances by item and lot using the U1 business-key columns, while period-based audits filter on TRANS_DATE or ITEM_COUNT_DT. Because SELECT access to the GMI schema is restricted in production, these queries are frequently surfaced through inventory cycle count reports or custom extracts rather than run directly by end users.

Related Objects

The documented foreign keys anchor IC_CYCL_ADT to reference master data:

• SY_DOCS_MST — joined on IC_CYCL_ADT.DOC_TYPE to SY_DOCS_MST.DOC_TYPE, supplying document type descriptions.
• SY_UOMS_MST — referenced twice, via IC_CYCL_ADT.UOM1 and IC_CYCL_ADT.UOM2, to resolve unit-of-measure definitions.
• IC_CYCL_HDR and related cycle definition tables — joined on CYCLE_ID to the cycle header.
• IC_ITEM_MST — joined on ITEM_ID for item master attributes.
• IC_LOTS_MST / lot tables — joined on LOT_ID or LOT_NO/SUBLOT_NO to confirm lot context.
• IC_WHSE_MST — joined on WHSE_CODE for warehouse details.

These relationships make IC_CYCL_ADT a central link between cycle-count execution data and the inventory and reference masters that define its context.