Disassociate Bin from a Part

I’m trying to unassociate a BIN from a part. In the Part Maintenance program I list all bins where the part might stored, and then attempt to delete it from that list, but the ‘Delete’ functions is disabled. So where should I go to make the disassociation.


We tried that, but ‘Delete’ (the little red ‘X’) is not an active control on that screen for this part. What settings on a part would make it so?

Hi Tim,

Looks like we’re on close to the same version also, 10.1.600. Could it be because you have QOH in the bin?


1 Like

You can only have one Primary bin per warehouse. So anything listed beyond that is because ther is QOH in the bin (even if it is negative).

Most common source of this when Mtl is received into Bin ‘A’, but Issued from Bin ‘B’.

If QOH of A is 150, and QOH of B is -50. Two bins would show, and their total would be 100.

Do a Mtl trasnfer of Qty 50 from bin A to bin B. You then have just 100 in Bin A (same total qty as before the transfer)

I think I just found the answer: the bin we’re trying to delete (disassociate) from that part is designated as primary for that part.



In our case we have zero quantity of this part in that bin.

So if a bin is designated as Primary … that would be at the warehouse level, and every part stored in that warehouse has that bin as the primary location?

I may have mislead you. I was thinking of the Part Tracker.

You only need to make Warehouse Bins (on the Part -> New menu, not referring to blank bins in a warehouse), if you want to have different Replenishment parameters.

We never setup Part-Warehouse-Bins. For a given part, all bins of a warehouse use the settings on the Part -> Site -> Warehouse -> Detail tab.

@tkueppers If you have done a cost roll up, you can’t delete any bins from that part. I found that out the hard way. It does a cost roll transaction for every bin associated with that part. If you have any transactions for that part in history, you can’t delete the bin from that part.


So if you’ve done a cost roll up, you can’t delete bins from the part, even if there’s no quantity?

Cost rolling does a transaction against the part. It’s one of those things that locks field in place. To check this out, look at a part that hasn’t had a cost roll or any other inventory transaction (check Part Transaction History Tracker for transactions) against it to see if the red X is greyed out. It shouldn’t be for that part.

Just to be sure, we’re talking about the “Warehouse Bin” added to a warehouse in Part Maintenance.

That end up showing as:

Because those are PartBinInfo records. The Data Dictionary says the table is for:

An extention of the PartBin table, hold information specific to KanBan processing.

And I can delete them regardless of whether there is a Qty in them, or there have been PartTrans for this part, with this bin.

I believe Tim mentioned that the bin he was trying to delete was setup as the Primary Bin (one tab over) in addition to the bins on the Bin Information tab.

I know you can’t delete a warehouse either if it has had a cost roll up. I have run into that several times unfortunately.

1 Like

Thanks Beth and Calvin. Very helpful feedback.

1 Like

@Beth do you mean a PartTran Trantype of ADJ-CST?

I’d bet that deletion would be disallowed if the warehouse is referenced by anything. And the one type of records you cant remove would be PartTran.

So if the parttran record specifies the warehouse (or even indirectly, by referencing a PartBin in that warehouse), then deletion would be disallowed.

I hate that a part can’t be deleted if a parttran record exists. Even one that doesn’t do anything. For example, we imported (via DMT) a bunch of parts (we knew some would be removed later). Then DMT’d in a cost for each, we could no longer remove the unwanted part, because a lone ADJ-CST record exited for it.


Yes, if you run a Cost Roll for a part that has that warehouse listed as a valid warehouse for the part at the time the cost roll was done, then you can’t delete the Warehouse because it’s now locked in as having a transaction.

Yep that’s what happened now we have parts in warehouses that will never exist and want to cleanup before stock take. Looks like generating and excluding 0’s is going to have to do.

I’m hoping Epicor have a fix program for this. It’s going to be a pain.

A daring person might find all those lone PartTran entries for the parts in question, and then use SQL to set the P/N to specific P/N, created just for giving those parttrans a valid part table entry to reference.

For example, if my my overzealous DMT’ing created part XYZ-123, and did a cost update - thus creating a PartTran record

TranNum   Company   TranType  PartNum ...
123499    MC        ADJ-CST   XYZ-123

And no other records reference partnum XYZ-123

  1. Create a new Part DMT-Deleted
  2. Use SQL to update parttran 123499, changing partnum from XYZ-123 to DMT-Deleted. Probably not a bad idea to update the Reference field of the PartTran record, to remind you that this is a record you tweaked. Maybe put the original PartNum in the ref field, so you could undo it if you had.
  3. Back in E10, you would be able to delete part XYZ-123

But who would ever manually edit the SQL DB? :wink: