Split Inventory on a Run
Discover the functionality of splitting WIP through an issue ticket. This helps with splitting inventory on a run when an issue with some parts is detected.
Last updated
Discover the functionality of splitting WIP through an issue ticket. This helps with splitting inventory on a run when an issue with some parts is detected.
Last updated
During the receiving process, your looking at 10 parts provided by a supplier. After conducting an inspection, you note that 3 of those 10 parts contain visual defects that deviate from the expected condition.
How do you address the issue with those 3 parts without holding up the progression of the other 7 through your process?
In ION you can create an issue ticket to handle just those three parts, assign a location to them such as an MRB cage, and continue running the remaining seven.
For information specific to issues check out this page with more details.
The video bellow shows you how to execute this functionality in the run execution window.
This is a more complicated case were the parent inventory item has multiple child components required to build it, these are the aBOM build requirements.
Steps followed in the video:
Establish the run to produce those five cheesecakes.
Once the run has been created you will see these in inventory as WIP. They will also be assigned a location of your choosing, in this case the "Great Place".
The build requirements (aBOM) for a singular cheese cake is setup to be 3 Sugar, 2 Cream Cheese, and 1 Egg. This will be important when we create an split WIP issue with partially installed quantities.
Total Build requirements for the five cheesecakes is thus: 10 cream cheese, 15 sugar, 5 eggs.
During the procedure you have installed 2 sugar and 1 cream cheese when you notice there is an issue with two of the cheesecakes. The location of the installed goods at this point is in the "Great Place" where the cheesecakes were originally destined for.
You create an issue ticket to split those two cheesecakes off the run and put them in a location called "Bad Place".
From the inventory page page, you will now see that those two split cheesecakes are available now in the "Bad Place". If "Bad Place" was an "Unavailable" inventory location, users could use it as a way to make split-off inventory "Unavailable" for use elsewhere.
Likewise the current logic is that all components installed into the split-off inventory will also move to the new location "Bad Place".
Looking at the aBOM now for this run you will see a couple additional pieces of information.
For build requirements that had some inventory installed before the split, they will now show a UI indication that they are shared between the two parent part inventories. In the video's example, it shows the build requirement is linked to inventory ID 12 and 15.
The quantity looks like Qty: 1 of 6 (10). Hovering on the tool tip shows you that 1 inventory is still installed on the build requirement, quantity 6 is the current quantity required by the build requirement of the part, and quantity 10 was the original build requirement quantity. Since it's impossible to exactly know whether the qty 1 was a component of the newly-split off inventory or still in inventory attached to the Run, the previously installed inventory will remain visible on the Run's aBOM even after the split.
6 total sugar are needed for the remaining three cheesecakes down from original 10 demanded.
Imagine you’re overseeing a production process where items (like machines or baked goods) are built from several parts or materials. In some cases, problems come up, so you need to separate out certain items from the production line, while still keeping track of what’s been done. These scenarios explain how the system manages and tracks parts, depending on how far along they were in the assembly process.
These diagrams show how inventory will be divided up based on full installs, partial installs, or no aBOM install scenarios. The final locations of children inventory will be reflective of the locations of the child parts (pink boxes) after the split (on the right side of the arrow).
In this scenario, nothing has been added to the items being produced yet—no materials or components are installed. Let’s say you need to separate out a few of these items before any work has begun.
Outcome: When you split off some items, the system divides all the necessary parts and materials between the two groups without confusion. Each split-off group will have its own list of parts to be installed, and since no materials were installed beforehand, each group’s requirements are completely independent.
This scenario is straightforward because there are no partially completed items to complicate things.
Now, let’s say work has already started, and some of the materials or parts have been installed. You then realize there’s an issue with a few items and need to separate them. The problem here is that some materials have already been used, so it’s not clear which parts belong to which group.
Outcome: The system links both sets of items (the ones you’re keeping in production and the ones you’re separating) to the already installed parts. This way, each group will show the installed parts as “shared” between them, meaning the materials could belong to either set.
This approach makes sure no materials go unaccounted for and that both groups have the components they need because it is unclear exactly which group each part should belong to after the split.
In this case, some parts or materials are installed, but others haven’t been added yet. Let’s say half the materials for each item are installed, while the rest are still waiting to be added. You then need to split out a few items due to an issue.
Outcome: The installed materials will be handled as in Scenario 2, linked to both groups, meaning the system shows them as “shared” between the items in production and those being set aside. Meanwhile, the materials that haven’t been installed yet get allocated separately to each group based on the split.
This setup keeps things organized by showing which materials are completely ready and which are still needed. It allows production to continue for the items that aren’t affected while making sure that the separated items are accounted for accurately.
