Hello again everyone,
To start with some context, my company is using Dynamic Attribute Classes + Dynamic Attribute Values underneath the classes to lock down part color groups and color options within those groups. In testing, we’ve run into a… medium problem.
It appears that the DynAttrValueSet table does not actually generate a row unless an attribute value has had demand attached to it.
Here’s a scenario:
- Order 123 comes in with parts 001, 002, 003.
- 001 has a Dynamic Attribute Class at the part level of “Accessory” and Accessory is set up with an attribute value set of “GREEN, ORANGE, BLUE, PURPLE”.
- The order calls for 2 GREEN 001
- All transactions are A-ok for 001 GREEN
- The next day material handlers need to stock 5 PURPLE 001 in the racking using EKW
- Inventory adjustment fails, no ID/short description exists for purple in the DynAttrValueSet table yet.
Maybe we’re using Attributes in a new and exciting way or something but it seems very odd to me that DynAttrValueSet would not just generate a row for every possible combo when the Dynamic Attribute is set up, so the ID would be ready to roll for any reference needed. Anyone have any insight into this, or should it go straight into an idea?
Wow I read this over and realized I probably sounded a little crazy. Management has tinkered with our implementation order and we’re implementing and deploying Warehouse Management before full implementation, so production is not generating anything. We basically have a part master with set up parts, and mat handlers are checking things in while the warehouse checks things out to simplify it.