Results for “ic_cycl_msc”
21 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IC_CYCL_MSC is a table owned by the GMI schema (Process Manufacturing Inventory) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the additional items that have been added to a cycle count. In other words, while a cycle count definition and its header record are driven by the cycle count setup, IC_CYCL_MSC stores the supplemental item entries—the "miscellaneous" additions—that operators or planners attach to a specific cycle count beyond what the base schedule generated. The object carries the status VALID in the ETRM documentation and is listed under the GMI - Process Manufacturing Inventory product module.
From a Data Vault modeling perspective, the mined relationship structure suggests classifying IC_CYCL_MSC as a link. Its foreign keys resolve to multiple parent entities (cycle count header, item master, item master by organization, and text header), which is characteristic of an associative/link table connecting business keys rather than a pure descriptive satellite. This classification is a heuristic suggestion derived from the FK graph, not an Oracle-declared attribute.
Key Information Stored
The table comprises 13 documented columns. The most significant are:
- CYCL_MSC_ID — the surrogate primary key, enforced by the IC_CYCL_MSC_PK index. This is a system-generated identifier and carries no business meaning.
- CYCLE_ID — identifies the cycle count header to which the added item belongs; it is part of the IC_CYCL_MSC_U1 unique index and a foreign key to IC_CYCL_HDR.
- ITEM_ID — the inventory item being added to the count; participates in IC_CYCL_MSC_U1 and references both IC_ITEM_MST_B and IC_ITEM_MST.
- ENTRY_TYPE — denotes the nature/origin of the entry; part of the unique business key.
- ABC_CODE — the ABC classification associated with the added item; completes the IC_CYCL_MSC_U1 business-key candidate.
- TRANS_CNT — a counter related to the transaction/entry activity for the record.
- DELETE_MARK — the standard GMI soft-delete/deactivation flag; records are logically removed rather than physically deleted.
- TEXT_CODE — a foreign key to IC_TEXT_HDR, providing an association to free-form text or notes.
- CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle audit columns recording who created and last modified each row and when.
The surrogate key CYCL_MSC_ID is distinct from the business-key candidate defined by the IC_CYCL_MSC_U1 unique index over CYCLE_ID, ENTRY_TYPE, ITEM_ID, and ABC_CODE, which guarantees that a given item/entry-type/ABC combination is represented only once within a cycle count.
Common Use Cases and Queries
Typical use cases include auditing which items were manually appended to a count, reconciling cycle count scope against the generated schedule, and reporting ABC-coded additions by item. Because the table is a child of IC_CYCL_HDR, join patterns center on CYCLE_ID.
SELECT m.CYCLE_ID, m.ITEM_ID, m.ABC_CODE, m.ENTRY_TYPE, m.TRANS_CNT
FROM GMI.IC_CYCL_MSC m
WHERE m.DELETE_MARK = 0
AND m.CYCLE_ID = :cycle_id;
A reporting query that enriches additions with the item description and header context:
SELECT h.CYCLE_ID, m.ITEM_ID, i.ITEM_DESC, m.ABC_CODE, m.ENTRY_TYPE
FROM GMI.IC_CYCL_MSC m
JOIN GMI.IC_CYCL_HDR h ON h.CYCLE_ID = m.CYCLE_ID
JOIN GMI.IC_ITEM_MST i ON i.ITEM_ID = m.ITEM_ID
WHERE m.DELETE_MARK = 0;
Because of the soft-delete convention, filters on DELETE_MARK are essential in nearly every query against this table.
Related Objects
- IC_CYCL_HDR — parent cycle count header; joined via IC_CYCL_MSC.CYCLE_ID = IC_CYCL_HDR.CYCLE_ID.
- IC_ITEM_MST — item master; joined via IC_CYCL_MSC.ITEM_ID = IC_ITEM_MST.ITEM_ID.
- IC_ITEM_MST_B — item master by organization/business; joined via the same ITEM_ID column.
- IC_TEXT_HDR — text header for associated notes; joined via IC_CYCL_MSC.TEXT_CODE = IC_TEXT_HDR.TEXT_CODE.
These relationships make IC_CYCL_MSC a small but meaningful link between cycle count execution and the item and text reference data in Process Manufacturing Inventory.
-
This table contains the additional items added to a cycle count.
-
This table contains the additional items added to a cycle count.
-
SYNONYM: APPS.IC_CYCL_MSC 12.1.1
-
TABLE: GMI.IC_CYCL_MSC 12.2.2
-
SYNONYM: APPS.IC_CYCL_MSC 12.2.2
-
TABLE: GMI.IC_CYCL_MSC 12.1.1
-
VIEW: GMI.IC_CYCL_MSC# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
VIEW: GMI.IC_CYCL_MSC# 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
Table: IC_ITEM_MST 12.1.1
This is the Item definition table. It contains all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations.
Not implemented in this database·Explore GMI module →
-
Table: IC_ITEM_MST 12.2.2
This is the Item definition table. It contains all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations.
Not implemented in this database·Explore GMI module →
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1