Hello all,
I have encountered the following issue:
We have legal entity with several Warehouses. Two of the warehouses are with Warehouse Management processes. There are two particular Product Masters with Size and Colour for wich after “release to warehouse” the wave can`t be processed and no Work can be created. In the “Wave processing history log” there is the following error message: “Object reference not set to an instance of an object.” See also the screenshot attached.
I have compared all the warehouse setups for both warehouses, and they are identical. Same Wave templates, same work templates, same location directives etc. In the BRL1 warehouse the wave gets processes and work is created and in the NRL1 Warehouse no.
Has someone faced this issue before?
Any help and suggestions will be much appreciated.
Thank you in advance.
2 Likes
Hi Nayden! How do you solve this one? I have the same issue/problem. Any workaround? Thank you very much!
Hi @Nayden_Valchev @Matt_de_Castro
You’re definitely not the first to see this type of “Object reference not set…” error. Even when two warehouses look identical, a very small setup difference can stop the wave from creating work.
A few quick checks that often solve this:
1. Item/variant setup per warehouse
Make sure the size–colour variants are fully enabled for the NRL1 warehouse. Missing storage or warehouse dimensions often trigger this error.
2. Location directives
Templates may match, but a tiny filter mismatch or sequence issue can block work creation. Try removing filters temporarily to see if it processes.
3. Reservation hierarchy / unit sequence group
If NRL1 uses a slightly different hierarchy, it can break the wave for specific variants.
4. Locations in NRL1
Ensure the required locations are active, not blocked, and part of the correct zone/layout. Missing valid locations often leads to this error.
Most of the time, it ends up being one small configuration gap between the warehouses.
If you need, happy to help walk through it, always glad to support someone in the community.
Hi @Hardik_Gupta. Thanks for this. I think i’ve solved this issue, by enabling a Location Directive Actions to batch enabled.
however, another error appeared.
”Shipment was not fully allocated”
” Sales order does not allow work creation without location” but i think ill ask my business analysts about this as they only reach out for me to debug what they have with the setup. but if you can provide such insight about this, please do. Thank you very much!!
1 Like
Hi @Matt_de_Castro
Great to hear you sorted the first issue, those small Location Directive switches can really change the behavior.
For the new errors:
“Shipment was not fully allocated”
This usually means the system couldn’t find enough available inventory in the locations your directive is pointing to. Even if stock exists, it might be in a different bin/zone or already reserved. Try checking the available quantity in the bins your directive is targeting.
“Sales order does not allow work creation without location”
This often happens when the line is missing a proper location code or when the item isn’t fully enabled for warehouse processes in that location. A small mismatch in the location setup, reservation hierarchy, or item WH settings can trigger it.
These issues are usually setup-related, not system bugs, so your business analysts checking it makes sense.
If you need, feel free to share more details, happy to help anytime.
