Dynamic issuance locations
- 09 Jul 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Dynamic issuance locations
- Updated on 09 Jul 2024
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
In maintenance dynamic issue locations, different sets of issue location calculations can be created. For example, a distinction can be made between orders placed in the store versus webshop orders. Webshop orders, for example, would always be collected and issued through an order picking warehouse, while store orders would be partially issued from the store and partially from an order picking warehouse, depending on the ordered products. 
For each issue location calculation, the detail rules can be specified. The rules, as shown below, are executed based on the sequence number, with execution working from low to high. If no rule meets the criteria, no issue location will be assigned to the reservation.
By adding a rule to this, the detail screen above will appear.
The following data can be specified in this:
| Rule type | Type of calculation to be performed. The following types of calculations are possible:
| ||||||||||
| Warehouse location level 1 | The ability (or requirement) to provide this field depends on the chosen rule type. | ||||||||||
| Branch | The ability (or requirement) to provide this field depends on the chosen rule type. | ||||||||||
| Issue location | If the ordered products meet the specified rule type, this issue location will be assigned to the reservation. | ||||||||||
| Information | Free text about the calculation rule. | ||||||||||
| Calculation order | Order of execution for issue location calculation, number 1 is executed first. | ||||||||||
| Expired rule | By marking a rule as expired, it will still exist but the calculation for this rule will not be executed. |
Was this article helpful?