Results for “ic_item_cdt”

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

Overview

IC_ITEM_CDT is a table in the GMI (Process Manufacturing Inventory) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the GMI schema and carries a VALID status in the ETRM repository. The documented description identifies the object as a "Scheduled count date" table, defining the dates on which physical cycle counts or inventory counts are planned for specific items within specific warehouses.

In the physical inventory and cycle counting process flow, IC_ITEM_CDT acts as the scheduling anchor: it determines which warehouse-item combinations are due for counting, on what date, and under which cycle definition. This allows warehouse managers and inventory planners to generate count requests, monitor count compliance, and reconcile on-hand balances against counted quantities.

From a heuristic Data Vault modeling perspective, mined from the documented foreign key structure, IC_ITEM_CDT is best classified as a link entity. It connects a warehouse-item inventory record (via IC_WHSE_INV) to a text/comment header (via IC_TEXT_HDR) while carrying its own descriptive attributes such as count date and cycle type. This link classification is a modeling suggestion derived from the relationship graph, not a documented Oracle designation.

Key Information Stored

The table is documented with 14 columns. The most significant ones are:

• ITEM_CDT_ID — the surrogate primary key defined by the IC_ITEM_CDT_PK constraint. This is a system-generated identifier unique to each scheduled count record.
• WHSE_CODE — the warehouse code identifying the physical location where the count is scheduled.
• ITEM_ID — the item identifier referencing the inventory record. Together with WHSE_CODE it forms the composite business key linkage to IC_WHSE_INV.
• SCHED_DT — the scheduled count date, the central business attribute of the record. Distinct from COUNT_DATE.
• CYCLE_TYPE — the classification of the cycle count (for example, frequency-driven or ad hoc).
• CYCLE_ID — the identifier of the cycle definition to which this scheduled count belongs.
• COUNT_DATE — the actual count date, which may differ from the scheduled date when counts are performed late or rescheduled.
• TEXT_CODE — a foreign key to IC_TEXT_HDR supplying text or comment information associated with the count record.
• CREATION_DATE / LAST_UPDATE_DATE — audit timestamps for record creation and most recent modification.
• CREATED_BY / LAST_UPDATED_BY — the application user identifiers responsible for creating and updating the record.
• DELETE_MARK — the logical deletion flag; records with a nonzero value should be treated as removed in queries.

The unique index IC_ITEM_CDT_U1 covering WHSE_CODE, ITEM_ID, SCHED_DT, CYCLE_TYPE, and CYCLE_ID is the principal business-key candidate, enforcing that a given item in a given warehouse has at most one scheduled count per date, cycle type, and cycle identifier. The surrogate key ITEM_CDT_ID should be used for joins where referential precision is required; the unique index columns should be used to enforce and query business identity.

Common Use Cases and Queries

The most frequent uses of IC_ITEM_CDT involve generating count worklists, tracking overdue counts, and reporting cycle count coverage. A typical query retrieves all counts scheduled within a date range for a warehouse:

SELECT ITEM_CDT_ID, WHSE_CODE, ITEM_ID, SCHED_DT, CYCLE_TYPE
FROM   GMI.IC_ITEM_CDT
WHERE  WHSE_CODE = :whse_code
AND    SCHED_DT BETWEEN :start_date AND :end_date
AND    NVL(DELETE_MARK, 0) = 0;

Overdue analysis compares SCHED_DT against COUNT_DATE to identify counts not yet executed:

SELECT WHSE_CODE, ITEM_ID, SCHED_DT, COUNT_DATE
FROM   GMI.IC_ITEM_CDT
WHERE  COUNT_DATE IS NULL
AND    SCHED_DT < SYSDATE
AND    NVL(DELETE_MARK, 0) = 0;

Reporting scenarios include cycle count compliance dashboards, count frequency audits by CYCLE_TYPE, and reconciliation of scheduled versus executed counts. Because the table stores scheduling metadata rather than quantities, it is typically joined to inventory and count transaction tables to produce variance reporting.

Related Objects

• IC_WHSE_INV — referenced by IC_ITEM_CDT through ITEM_ID and WHSE_CODE. This is the warehouse inventory master record and the primary parent of the scheduled count.
• IC_TEXT_HDR — referenced through TEXT_CODE, providing text header information linked to the count record.
• IC_ITEM_CDT_PK — the primary key constraint on ITEM_CDT_ID.
• IC_ITEM_CDT_U1 — the unique index on WHSE_CODE, ITEM_ID, SCHED_DT, CYCLE_TYPE, and CYCLE_ID, enforcing business uniqueness.
• Cycle count definition tables — referenced conceptually through CYCLE_ID and CYCLE_TYPE, though not documented as formal foreign keys in the ETRM metadata.
• Physical count transaction tables — downstream objects that consume scheduled count records when counts are executed, joining on warehouse, item, and date.