on ‎2019 Mar 14 3:29 AM
Is it possible to allow multiple stock types in one storage type along with functionality of changing the stock types after putaway. We have 3 storage locations in ECC and associated with 3 Availability groups and 3 stock types in EWM.
1. SLoc1 Production Receipts - AG - 001 Stock Type P1
2. SLoc2 Available for Sale - AG - 002 Stock Type F1
3. SLoc3 Expired Product - AG - 003 Stock Type E1
Business process: Production receipts into 001 (P1) and put away to final s.type 002 (F1). When the product is near to expiry or expired move to 003/E1 manually and physically product sits in the same bin more of logical transfer for MRP and ATP purposes, until it is scrapped. Typically scrapped once in a month, business does not want to move out to different bins / s.type. Want to keep 001 (P1), as we don't want to consider the stock that is not put-away for picking.
I have tested the below.
a) With AG 002 and Mandatory check on S.Type,, stock type change from P1 to F1 after put-away and Sloc to Sloc happens. But changing the stock type from F1 to E1 manually not allowed because of the mandatory check.
b) If I remove the mandatory check, during put-away P1 to F1 is not happening, stock is in P1 and excluded from picking. But this allows manually transfer P1/F1 to E1 when product is near expiry
Anybody has come across this situation, appreciate any recommendations without enhancement.
Request clarification before answering.
...if you do not need the stock on F1 in real-time after putaway completion, you could make use of report /SCWM/R_STOCK_TYPE_CHANGE and run as background job e.g. every 10-15 minutes. Create one step to post the non-expired to F1 and one step to post the expired to E1.
...only first idea. Did not think to the end so far but might be worth it to spend some thoughts on this idea...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
I don't think the solution from stock type (posting) / storage type (mandatory) side is feasible. Maybe following options might be worth to consider:
1. Posting the stock in original bin to blocked stock which will not be available. This can be automated with simple enhancement as well otherwise it is a manual process.
2. If product is subject to batch management, suggest to add batch status management and enable batch management in EWM side. Then batch can be restricted without moving from ECC side and can't be picked as per configuration.
Hope this helps. Good luck.
Yp
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 17 | |
| 16 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.