My employer has been using Lawson for some years, paying for manager self service (MSS) but not successfully able to implement it. I'm new to the organization (working in HR), and have taken responsibility for getting MSS up and running. We keep running into system limitations for basic HR processes, and appear to be faced with the decision to abandon MSS, or use our talented IT folks to make lots of changes, to the extent that we have to expend significant resources to make the system work for us.
For example, some employee data is stored outside of the E1-E8 tables, so they aren't accessible to MSS. We also want some data to be read-only (like upper and lower limits of pay ranges) while allowing managers to enter personnel actions such as a merit increase- but the system seems to only have two conditions in 'plain vanilla'- either you can see it and change it, or you can't see it at all. You wouldn't want a manager to change the pay range, but you'd certainly want a manager to know the pay range when making any pay increase, so they don't go over the top of the range.
I'd really appreciate any opportunities to have a brief phone call (30 minutes or less) with anyone on this list who is in a 1000+ person organization and has managed a rollout out MSS, and is willing to have a brief chat. I'd like to know whether you rolled out MSS 'plain vanilla', and if so, what you see as the major system limitations for how your HR processes operate. For organizations that have implemented MSS but had to make significant changes to get it to work, I'd be interested in learning (at a high level) what types of changes you had to make. For example, if you pushed a lot of data from other tables into the UF table(s) just to be able to access it through MSS.
I'm new to this site/forum (one of our Lawson IT experts just pointed me here) but I'll monitor for responses- If you aren't interested in a brief call but want to post responses, that would be welcome too.
Thank you,
Keith
Currently using 8.1 Apps on 9.0 Foundation
Although we haven't rolled out MSS yet (we're working on it) - I'm sorry that you're finding it so challenging to work with. I'm sure some of it is cultural, since we haven't found that there isn't enough information, we've found that we'd much prefer to keep some employee information more confidential than provided out of the box, and thus it sounds like we're more interested in suppressing information than your organization, so we haven't found it limiting at all.
And I personally disagree with your statement "you can see it and change it, or you can't see it at all". I've worked with Lawson for a long time, however, I've never heard of pushing data from other tables into UF just to be able to access it via MSS? I'm wondering if what you're looking at , at this point has already been modifiefd by your folks? It doesn't sound out of the box at all to me.
I wish you the best in whatever your organization's decision is regarding MSS.
One final thought - are you using ESS? Is that working for your employees?
I was pretty new in the company when we implemented ESS/MSS including the Benefit Open Enrollment, in "plain vanilla flavor". You will need a savvy programmer to do the changes and mostly in javascript, html, xml, ags and dme calls. I made changes to the drill around, personnel action screen, added lookup/list, change and hide verbiages... mostly cosmetics. Our changes is not to make it look professional but functional and acceptable. Hope this helps