Enhance Putaway Preferences

As part of this request, we would like to address 2 issues:

1. Putaway preferences are not assigning putaway locations directly (using include/exclude locations) and we had to implement a workaround using location dedication to a specific inventory status. The API documentation was fixed to reflect this API limitation and remove the include/exclude locations. However, we still see it makes sense to have the include/exclude putaway locations in the putaway preferences to directly configure putaway preferences without relying on a workaround through location dedications.

2. The three types: PO, TRANSFER, RETURN, that drive the putaway preference are too restrictive. Can it be expanded to allow user-defined values? For example, we need to differentiate between replenishment POs and POs tied to a customer order. There is a significant negative impact on productivity if you putaway POs that are chained to a customer order in bulk storage with replenishment POs. It creates extra unneeded steps in the store to putaway those items in regular inventory locations and then pick them again as opposed to have them be putaway to a crossdock location for SFS/delivery or a BOPIS staging location for customer pick up. Using a field like LineType would allow us to configure the value in that field and pass it in the putaway preference. When an order is received, the putaway location can be assigned based on the putaway preference for that LineType value.