We are currently using the Handheld Integrator v. 8.0.2 for par location replenishment. We're at the very beginning of the process of upgrading from 8.0.3 Apps and Env to LSF9. I understand that the Handheld Integrator is not supported with LSF9. But will it even function with 9.0? :nix: We plan to upgrade to MSCM but not necessarily at the same time as our upgrade to LSF9. The budget for MSCM was planned for Fiscal Year 08. Are we going to be unable to use our current par replenisment process when we upgrade to 9.0? :wwf:

I will reply to my own post just in case anyone was wondering.

The old handheld integrator will NOT work with Lawson 9.0 and LSF9!

Jon

Jon
We are in a similar situation.
We are awaiting the supply chain software and I hope we can install and work the bugs out prior to our scheduled upgrade to 9x
Prior to the go live with MSCM ,
I plan to use the hand-helds to collect data “saving mountains of 281’s; one step to the integrator and process a report
from the DB to be hand keyed or directly uploaded. “not holding my breath on the uploading part”

We out source our host data ,so we are on a mandated time schedule for upgrades.

Good luck
Michael Fiorentino
Materials Management
Wyoming Valley Health Care System
(570) 552-2333 Fax (570) 552-2331
mfiorentino@wvhcs.org

We're in the middle of implementing LSF9, 9.0 Apps, LBI and MSCM... getting ready to run our second pass. We'll probably be testing MSCM in about 3 weeks. My office looks like a warehouse with all the handheld equipment and barcode printers.

Jon

My understanding is different than what I believe I have read above. We are also going through the LSF9 and Apps 9 upgrade process. (We are currently stalled for a whole host of reasons.) Here is how I understand it:

8.0 environment/8.0.3 apps--> Hanhdeld Integrator and MSCM 4.1 will work
LSF9 environment/8.0.3 apps--> Hanhdeld Integrator and MSCM 9.0 will work
LSF9 environment/Apps 9--> Only MSCM 9.0 will work.

I have not mentioned 8.1 apps because I have never asked explicitly about this. What I can say is this. We have the Explore 9 training product line installed with LSF9. The IC520 exists in Apps 9, which would seem to suggest that the Handheld Integrator would continue to work (even if not actually supported). And I can say that I was able to download the par profile to a PDT6100. What I was NOT able to do is upload my counts back to the server...and here is why.

I had my local technical guru-type dude (Thanks, Ron) look at the workfile characteristics of both the 8.0 and 9.0 versions of the RQ500. In version 8, the RQ500 expects 788 characters per line...version 9 looks for something line 830 or 840 characters. I am sure they had a reason to make the change, but I do not know what it is.

In any case, it looks like one of two things could work:
1 - Create a macro of some sort to add the necessary number of characters to the lawmed.txt file before running the "handheld to host" option. Upside-probably pretty easy to create. Downside -You would have to put that on every desktop where the integrator is installed.
2 - Modify the RQ500 in Apps9 to essentially be the exact same as version 8. Upside - One fix takes care of all handhelds. Downside - Now you are working with a modified screen, and we all NEVER EVER use modifed screens, now do we? I also believe that this option would necessitate a modification to the IC588.

More fodder for thought,
rw

We upgraded to LSF9 environment and went live Aug 20, 2007. We are slated to upgrade the applications from 8.0.3 to 9.x next year.

I can say for sure, that the old handhelds will (and do) work with LSF9 environment.

I believe that it is our upgrade of the applications that is going to cause them to not work.

We will be going to MSCM soon too, with new handhelds, so that isn't a real concern.

One thing you will want to make sure of re: MSCM is that your loading docs have wireless access - otherwise it won't work quite correctly!!

Cheers,
-Greg

We actually just went live on Monday (12/10) with LSF9 and 9.0 Apps and MSCM. We have only implemented the Par and Cycle counting part of MSCM though. Waiting for some issues to be resolved with RAD (waiting also for the wireless access points to be installed on the dock). Par counting works great with the Dolphin 9550's. Couple things we've run into:

We use ProcessFlow for req approval. Approvals are based on the requesting location and we've set the par locations as disabled in the Service Criteria Level Definition (formerly WF07). RQ01 and RQ04 have new fields to define how approvals are handled. We had to set up these Requesters and Pars to bypass approvals or we get the error "Process Flow Header Level Approval not Enabled". :banghead:

When an item counted errors out due to no cost or invalid Purch Class for requester or item inactive at location, all of the items except the one that had the error will upload and a req will be created but the req will be unreleased. This used to occur with the old par counting in RQ500 but an MSP fixed that some time ago. There may be a patch out there for 9.0. :nix:

We also have single sign on enabled so our Lawson ID's and passwords are linked to our network ID's an passwords. If a user is logged onto the handheld and then changes their network password all subsequent par count uploads with fail with the message "User [name] Not a Lawson User". They have to log off the handheld device and log back in. No brainer. :beat:

On Tuesday a few of the 9550's locked up on us. Not sure why. I've go all set up in kiosk mode. Had to perform a warm boot (CTRL-SFT for 5 secs) to get back in action. :angry: