Hi,

If the locations is used in other objects you wont be able to delete it. May be you can try to use the hidden check box functionality to hide it.

Correct, -the location is used in other objects, -namely old executed transport tasks, -which we cannot find a way to remove , - 

Hi,

Please make sure you have run the Cleanup of Inventory job to remove the zero records in Inventory Part in Stock before trying to delete the locations. Deletion of Inventory Locations has been allowed even when there are Transport Tasks in Executed status. Refer bug ID 153897.

Ultimately, this is the most likely solution.

Hi, - thank you for respons

Upasari: Please describe how we workt with theCleanup of Iventory  job funktion

Shawn : Please explain what you mean by this, - do I understand you correctly, that you expect the reply will be that deletion of an obsolete location is not an option in IFS?

Hi @Benny Jensen 

Go to Warehouse Management > Quantity in Stock > Cleanup of Inventory

Enter the delete parameters and click OK.

@Benny Jensen 

Shawn : Please explain what you mean by this, - do I understand you correctly, that you expect the reply will be that deletion of an obsolete location is not an option in IFS?

Yes, most certainly.  Depending on the type of transaction, nearly every object in IFS will at some point become locked due to the transaction or history such that it can never be deleted.  There are certain items to be sure that can be deleted only once every other connection is removed, but the general rule is that once an object (part, order, user, project, invoice, location, site, etc) is used in a transaction, that item can’t be deleted.  

Some items can be hidden or inactivated or otherwise blocked so they can’t be seen or used in future transactions, but that is as good as it gets.

Hi @Upasari 

Is this bug available from App10 onwards? No chance to downport into App9 right? When you say “Refer bug ID 153897”, its not actually visible to us, customers right?

Thanks,
Asela

Hi @Asela Munasinghe 

This issue has been fixed in both App9 and App10.