I’m at a loss on how to proceed, so I’m reaching upward for insights on this. I’ve never seen anything like it before, and Jeethendra Mukkera (who has been doing the research) hasn’t either.
- Customer has been using NetSuite with multiple locations without bins being in-use or enabled prior to this add-on WMS implementation in a recently refreshed sandbox.
- We attempted a walkthrough for the usual Inbound/outbound/internal operations using existing stock information (Using the Bin Putaway Worksheet to bin the items, for example) and were continually stopped when transactions would fail to post from WMS to ERP due to inventory mismatches. Inventory mismatches that were not possible until the WMS was installed.
- Because it is an “existing data” issue found during the implementation, it’s outside of our scope to resolve (WMS SOW/PC Hours) and the customer is reliant on basic support (not ACS) to seek redress.
- All we can do is escalate the understanding of the problem.
- We and the customer have been in a cycle of disagreement with NetSuite Support on how to resolve these issues. The implementation is stalled until these issues can be resolved.
- We believe that enabling the features for NS-WMS and installing the bundles for NS-WMS has resulted in an inconsistency between the underlying inventory data layers used by NetSuite, such as:
- Inventory Balance
- Inventory Number
- Inventory Number Map
- Item/Location inventory
- Bin-level inventory, where applicable
- Commitment/allocation data
- WMS Open/Pick Task data
Has anyone heard of this issue, before?
And if so, can you provide any assistance?