Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from sigurd_christensen on Oct 22 at 2:09 AM Hi,
Using Storage sections would have been the easy way to achieve differentiated putaway behavior. That existing development (e.g. MDE/RF setup) does not allow this, is very surprising to me. Yet another example that own developments can cause problems for standard functionality.
However, the only other option meeting the putaway principles described by You, would be full-scale Capacity check (probably option 4) and this demands a lot of masterdata regarding capacity + high discipline in master data creation/maintenance. And Cap.chk. can also put a high load on system performance.
Good luck - BR Sigurd
| | | ---------------Original Message---------------
From: tags123
Sent: Monday, October 20, 2014 10:32 PM
Subject: SUT Check Active
Hi,
How does 'SUT Check Active' work in SAP WM storage type? Does Storage unit management should be activated 'SUT check active' option to be used? Please let me know.
We do not want to use storage units functionality.
We have a requirement to do putaway based on quantity (number of pieces) in storage bin. Each material should have fixed bin assigned with LE quantity specified. Putaway process should fill the fixed bin up to maximum quantity (LE quantity). Please note there will not be a scenario where transfer order needs to be split. If fixed bin is full, then putaway strategy should assign another empty bin which can only hold certain capacity (capacity ie number of pieces). If fixed bin becomes empty, no other material should occupy this bin except the material assigned to this bin.
What would be the solution? What is the required configuration?
Hope someone can help.
Thanks in advance. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
