Follow us on Facebook Follow us on Twitter Get the latest job postings quicker!
Follow us on Facebook and Twitter!
Sponsors

PkMS WMS, WMOS, WMi Manhattan Associates Consultants and Support

Like this Page? Share it!
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralLM Messaging for drop locationsLM Messaging for drop locations
Previous
 
Next
New Post
2/22/2017 5:48 PM
 

Hello again,

 

We've uncovered another issue with the messaging between WM and LM, this time relating to travel from a sort location in receiving to a drop location. E.g. say there are several pallets sitting in sort locations on the receiving floor, and the putaway task path has a drop location between the receiving floor and the pallet's final location. In one of our buildings, one of the roles we have may end up taking a pallet from the sort location to the drop location, then returning to the receiving floor and picking up another pallet and taking that to a drop location, and so on. The first task of the day will have correct messaging - say he picks up a pallet from SORT-ACT21 and delivers it to DROP-ACT21. Those are the two locations that will come through on the message. But, then he'll return to the receiving floor, and maybe pick up a pallet from SORT-ACT83 and deliver it to DROP-ACT83. The message for this second task will have these 3 locations:

 

DROP-ACT21 (user's previous location)

DROP-ACT83 (here, it SHOULD be SORT-ACT83)

DROP-ACT83 (destination location)

 

So, the location in the second detail line of the message is incorrect, which causes errors in travel time. So far, I haven't been able to figure out why it works on the first task, but not for any subsequent task.

 

Any thoughts?

 

Thanks.

 
New Post
6/1/2017 8:57 AM
 

Hi again,

 

We haven't discovered a fix for the above scenario yet (aside from writing a script that would look for these transactions and cross-reference with the prod_trkg_tran table to find the sort location and insert it into the appropriate place in the detail message). But, we do have a slightly related issue.

 

It seems that if we turn on the travel activity in the warehouse master, anything sent by the Inventory Movement transaction will have that activity. But how can we specify different activities depending on what the user is doing? E.g. if he's doing a Putaway, that particular travel needs to get grouped into the Putaway job function. If he's doing a Replen, then it needs to get grouped into the Replen job function. This seems like such a basic requirement, but I can't seem to find a way to have the system do it. It looks like the Inventory Movement transaction is hard-coded in the system, and I can't find any sort of configuration for it. It doesn't even exist in the tran_master. I'm getting tired of writing scripts to correct Manhattan's bugs and design flaws. :)

 
Previous
 
Next
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralLM Messaging for drop locationsLM Messaging for drop locations


Copyright 2010-2019 by WMS Support Forum   |  Privacy Statement  |  Terms Of Use