Results for “update_method”

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

Overview

IC_CYCL_HDR is a table in the GMI Process Manufacturing Inventory module of Oracle E-Business Suite, owned by the GMI schema. It stores the header-level information for physical cycle count events, defining the warehouse and organization in which a count is scheduled and executed. In the EBS inventory flow, the cycle count header acts as the controlling parent record: it establishes the counting scope, drives the generation of the detail lines (the items and lots to be counted), and captures lifecycle dates such as scheduled start, actual start, and end. Because it holds descriptive state and business dates that change over time while its relationships to organizational and warehouse masters remain largely stable, the heuristic Data Vault classification is satellite-leaning: a modeling exercise would typically treat it as a satellite attached to an organization/warehouse hub and possibly a cycle-count business-key hub, rather than as a pure hub or link.

Key Information Stored

The table’s surrogate primary key is CYCLE_ID, enforced by the IC_CYCL_HDR_PK index. A second unique index, IC_CYCL_HDR_U1, covers ORGN_CODE, CYCLE_NO, and CYCLE_SOURCE, and is the documented business-key candidate that uniquely identifies a cycle count within an organization.

• CYCLE_ID — surrogate primary key; the join key to all detail records.
• ORGN_CODE — the organization owning the count; a foreign key to SY_ORGN_MST and SY_ORGN_MST_B.
• CYCLE_NO — the user-facing cycle count number.
• CYCLE_SOURCE — the source or origin of the cycle count, part of the business key.
• WHSE_CODE — the warehouse being counted; a foreign key to IC_WHSE_MST.
• CYCLE_DESC — descriptive text for the count event.
• CYCLESTART_DT, CYCLESCHESEND_DT, CYCLEEND_DT — the scheduled start, scheduled end, and actual end dates that define the count window.
• ACTUALSTART_DT — the timestamp at which counting actually commenced.
• UPDATE_METHOD — indicates how count results are applied to inventory balances.
• PRINT_COUNT, PRINT_FORMAT — controls for how count sheets are printed.
• INCLCTL_IND, INCLSUPER_IND, INCLEXCEPT_IND, EXCLZERO_IND, EXCLNEG_IND — inclusion/exclusion indicator flags that filter which items or lots are eligible for the count.
• IN_USE — status flag indicating whether the cycle is actively in progress.
• TEXT_CODE — a foreign key to IC_TEXT_HDR pointing to attached text or notes.
• DELETE_MARK, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY — standard audit and logical-deletion columns.

Common Use Cases and Queries

The primary use cases involve identifying open or in-progress cycle counts, reporting count accuracy, and driving the detail extraction that feeds count sheets. A typical query joins the header to its detail and warehouse master:

• Listing active counts by warehouse: SELECT h.CYCLE_NO, h.WHSE_CODE, h.CYCLESTART_DT FROM IC_CYCL_HDR h WHERE h.IN_USE = 1 AND h.DELETE_MARK = 0.
• Joining details to header: SELECT d.* FROM IC_CYCL_DTL d, IC_CYCL_HDR h WHERE d.CYCLE_ID = h.CYCLE_ID AND h.ORGN_CODE = :org.
• Cycle-duration reporting using CYCLEEND_DT minus ACTUALSTART_DT to measure count turnaround.
• Filtering by ORGN_CODE, CYCLE_NO, and CYCLE_SOURCE (the unique business key) to retrieve a specific cycle event.
• Retrieving supplementary count configuration from IC_CYCL_MSC via CYCLE_ID.

Related Objects

IC_CYCL_HDR sits at the center of a small cluster of process-manufacturing inventory objects, linked primarily through CYCLE_ID:

• IC_CYCL_DTL — child detail table, joined on IC_CYCL_HDR.CYCLE_ID = IC_CYCL_DTL.CYCLE_ID, holding the individual items/lots in the count.
• IC_CYCL_MSC — miscellaneous cycle data, joined on CYCLE_ID.
• IC_WHSE_MST — warehouse master, joined on WHSE_CODE.
• SY_ORGN_MST / SY_ORGN_MST_B — organization masters, joined on ORGN_CODE.
• IC_TEXT_HDR — text/notes header, joined on TEXT_CODE.

These relationships confirm IC_CYCL_HDR as a dependent satellite of organization and warehouse dimensions while serving as the parent hub for cycle count details and miscellaneous attributes.