ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page
  • How does it work?
  • Initiating an inventory split
  • Automated splitting
  • Carrying information across split inventories
  • What happens to installed inventory and build requirements?

Was this helpful?

  1. Features
  2. Parts Library
  3. Inventory

Inventory splitting

Understand and initiate inventory splitting

PreviousInventory statusNextInventory merging

Last updated 8 months ago

Was this helpful?

How does it work?

When splitting an inventory, the original inventory has its quantity decreased. A new inventory is then created for the quantity difference. This new inventory copies over nearly all of the properties from the original inventory. It also maintains a link to original inventory that is called originPartInventoryId in the API.

Initiating an inventory split

You can manually split an inventory via the inventory or receipts views.

When splitting, you have 2 options:

  1. Split - Splits a single item into 2 items by specifying a quantity. Example: Inventory is quantity 10 and you want to split off one for qty 3.

  2. Split Many - Splits a single item into multiple items by specifying the number of items desired. Example: Inventory is quantity 10 and you want to create 10 inventories of quantity 1.

Automated splitting

ION will automatically split inventory when partially installing, kitting, or scrapping a quantity. This occurs to keep the location/status of inventory items correct. For instance, if you have an inventory for quantity 2 and you kit 1 item, the inventory will split. Now the item that has been kitted will properly show a "Kitted" status and its location can be updated from the original.

For the purpose of barcodes, it is good to know how the new inventory is created. This table below shows how the inventory is created:

Action
How should the inventory split take place

partial kit

New inventory for the kitted item

partial unkit

New inventory for the unkitted item

partial install

New inventory for the installed item

partial uninstall

New inventory for the uninstalled item

partial scrap

New inventory for the scrapped item

partial unscrap

New inventory for the un-scrapped item

direct inventory split

Qty to split becomes new inventory item

partial receive

New inventory for received item

partial unreceive

New inventory for unreceived item

Carrying information across split inventories

Inventory relates to a lot of different objects in ION: runs, kits, issues, purchase lines, etc. Runs and issues only allow 1 inventory item to be related to them. When an inventory that is tied to a run (or issue) is split, it will use the origin part inventory information to maintain a reference to the run/issue.

For the inventory items shown below, the inventory was added to a run and then there was an issue tied to it. When that inventory was split, the new inventory created maintains a reference to both the run and the issue (see "Appears on" and "Issues" columns).

This is also reflected on the aBOM within the trace view:

What happens to installed inventory and build requirements?

Please review Split Inventory on a Run for more information on splitting an inventory item with installed inventory on the aBOM.