Transferring Supplies Between Asset Locations
Hello,
Currently we have a few asset locations setup in Lawson. Our main asset location is used to transfer inventory to the smaller asset locations through an IC22 transfer. An IC141 is ran, the user prints the order, the supplies are picked, and then transferred. Is anyone utilizing MSCM for this process? The problem with the current process is it is manual and it does not allocate quantity on items. Is anyone using a more efficient process and willing to share their experiences?
Thank You,
Brandon Nolan
Supply Chain System Analyst
Brandon.Nolan@mymlc.com
Comments
-
We have some intransit transfers and some direct transfers. Below is an example using direct transfer.
example: direct transfer from AAA to BBB
req location BBB with from-location AAA and issue type DT
the items in stock location BBB that need to transfer from AAA are set to reorder doc R and IC12.2 from-location AAA
scheduled IC141 for location BBB - this creates an unreleased requisition with req loc BBB, requester IC141BBB and from location AAA
scheduled process flow runs to release the requisition
the req gets picked up by the regular WH130 for location AAA
the shipment/pick goes to MSCM for picking from AAA
after MSCM shipment pick and submit, the DT issue trans is complete for location AAA and the RT receipt trans is complete for BBB0 -
Good Morning Stephanie,
Would you be willing to share a process flow? Is there much build on the backend for this process? The IC screens seems pretty straight forward. I appreciate your quick response!
Brandon0 -
I tried to include all the setups in the example, but this is assuming that you are already using MSCM for picking. When you say share a process flow, do you mean share the process flow that releases the requisition?0
-
Yes we are already using MSCM for requisitions. Okay just looked at the IC12, that makes sense. So for the IC141 requestor it would need to be defined on the IC02 right? The IC141 would run.
This is the part I didn't understand. "scheduled process flow runs to release the requisition" Would there be something prior to the WH jobs?
After picked in MSCM is this released in the handheld correct? I appreciate your help!0 -
The requester should be setup on RQ04 with IC141 + req location. This is also noted in the form help on IC141. The scheduled process flow is not required. There is a parameter on IC141 to Create Unreleased Documents (if you leave this No, then you will only get a report), but then the Unreleased req needs to be released, you could do this manually or setup a process flow to do this automatically. The requisition release would need to be done before the WH130, since the WH130 will not pick it up if it's still unreleased. The picking on the handheld is just like picking any shipment, so yes you would pick and release/submit on the handheld. Hope this helps.0
-
Okay sorry for the delayed response. I really appreciate the information. Is the RQ04 setup for a user or the job itself?
Brandon0 -
Hi,
The requester is needed for the job to create the requisition, so it's not related to a user.0 -
I was able to successfully test this. Any things to look out for with this process? Thanks again for your help!
Brandon0 -
We have been using this for years without any issues, so I can't think of anything, but if you have any specific questions, let me know.0
-
Hello Stephanie, one issue we potentially have with this transfer is the asset locations are 45 miles apart. Have you run into a timing issues or have a work around for this?
Brandon0 -
You could use the intransit option - set transaction type to IT instead of DT in RQ01. Then the receiving location will need to complete a receipt in IC23 for the intransit transfer.0
Categories
- All Categories
- 3 General Posts
- 6 Public Sector
- 5.8K Developer Community
- Migrated Forums
- Cloud Migration
- 5 Community News
- 2 User Groups
- 4 Featured Content
- Featured Developer
- Featured Public Sector
- 4 Featured Forums
- Featured Healthcare
- 2 Announcements
- Customer Bulletins
- In the Birst Space
- Legacy Blog Posts
- 132 RMS News
- Site News