Movement Requests Are Merged into One Pick Slip Despite Pick Slip Grouping Rule
Summary:
Hi Experts,
I am facing an issue where multiple Movement Requests are being merged into a single Pick Slip, even though I have already created a Pick Slip Grouping Rule and configured it to Group by Order.
My expectation is that each Movement Request should generate a separate Pick Slip, but the system continues to consolidate them.
Does anyone know:
- Why Oracle is merging the Movement Requests into one Pick Slip despite the grouping rule?
- Are there any additional setups, parameters, or rules that could be overriding the Pick Slip Grouping Rule?
- How can I prevent the system from merging multiple Movement Requests into a single Pick Slip?
0