MSCM - How items move to a hand held

 6 Replies
 2 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member

After orders are built in our Par Ex system, files are generated and ftp'd to our HHT folder on the Lawson server.

We then run and RQ500. After that, users are able to see the items on the hand held, so they can scan and issue out.

What piece of this process sees the items to move them to the hand held?

 

Anyone? Bueller? Bueller? Bueller?

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Your RQ500 creates a demand on the inventory but you still have to run WH130 to create the shipments; the pick ticket is what shows on the handheld.
David Williams
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Who is it? Oh, I'm sorry. I can't come to the door right now. I'm afraid that in my weakened condition, I could take a nasty spill down the stairs and subject myself to further school absences. You can reach my parents at their places of business. Thank you for stopping by. I appreciate your concern for my well-being. Have a nice day!
David Williams
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member

HAHAHAHAHAHAH!!

Too funny!

Thanks for the chuckle and for the clarity on the RQ500/WH130!

You're working late too. Bummer.

Take care David!!

Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member

I know I'm getting granular by asking this, but here goes. What does MSCM look for to push the items to the hand held? Is it some type of listener program??

I'm trying to write clear documentation so that there is a very clear understanding of how their process works from the time an order is built in Par Excellence to the time the see the items on the hand held.

 

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
The MSCM administration software is the go between and within its properties you set the syncing timers.
David Williams
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
There's a "gotcha" in the listener/sync/program update between MSCM and Lawson - the MSCM server is replicating ITEMLOC and will sometimes cache it and not recognize changes in Lawson to the handheld par locations. IT has a clear cache command for this here, but I do not know what it entails.