on 2025 Apr 14 1:17 PM
Hi,
Is there any limitation on how many storage location could be created for a plant? Would it be possible to create 2.000 storage locations within one plant?
Regards,
Vanessa
Request clarification before answering.
There is no limitation on how many storage locations you can create—a combination can have more than 1M entries. However, as it is a configuration activity, only the system administrator or a qualified person is allowed to create them. Therefore, it should not be a concern for the end client or user how many Storage locations can be created. This activity can impact your security roles if you restrict anything in users' roles. The customer should not think about going creative with it and creating 2000+ storage locations without having a thoughtful conversation and a business reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @VanessaM
Storage location ID is 4 chars long. So you can create 34^4 = 1,336,336 storage locations per plant. I'm not aware of any other limitations.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@jagdeepsingh83 That's right. There are 26 letters in the English alphabet - my bad. That number can go up if you count national characters like Polish Ą, Ę or German Ä, Ö, etc. Any way, the limit is way above 1M, which is more than enough.
Hello @VanessaM
The technical limitation of over 1.6M storage location per plant is inconsequential. No sane design will ever hit this limit. @jagdeepsingh83 is perfectly right - if you worry about the limitation, you need to seriously revisit your design.
I know of a single scenario that would mandate a substantial number of storage locations. That is spare parts management where there is a requirement to manage parts issues to each technician separately. Often, storage locations are used to model technicians here. Still, the number of storage locations will not get anywhere close to the technical limit even in huge organizations.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As mentioned before, this is not our recommendation. We want to convice the customer that this is not a good practice. A technical limitation would have been one argument to put on our list. That is why I posted the question here. My assumption is also that there is no limitation except the one that comes from the lenght of the ID. But it might have been that there is a limit of maybe 999 - because as both of you mentioned, that should by far be sufficient and I don't know if there were ever created more than that.
However, if you have other valid reasons against doing this, it will be highly appreciated if you share them. Telling the customer that he is insane doesn't seem to be good practice as well 🙂
| User | Count |
|---|---|
| 18 | |
| 16 | |
| 5 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.