November 2021 Minimize
Thought-Provoking Commentary for the Lawson Software Community
Welcome to the latest issue of The LawsonGuru Letter, a free newsletter providing provocative commentary on issues important to the Lawson Software community. The LawsonGuru Letter is published by--and is solely the opinion of--John Henley of Decision Analytics.
Quote of the Issue
"I go to the gym religiously. About twice a year around the holidays."
-- Demetri Martin
Trending Topics
Year-End Processes
Our organization implemented cloud-based Financials and Procurement last year (2020). I just joined a few months ago, but from what I hear last year-end didn't go well. I'm researching Lawson year-end to come up with a plan to make this year-end better. Is there a checklist or guide of some sort for year-end close of modules in Procurement and Financials? I'm thinking of something with key jobs to run and the sequence of them, particularly any interdependencies between modules. Read More
InforOS and Employee Number
Is anyone out there using Lawson Employee Number to log in to InforOS? -- We've got it successfully installed and working in our Test environment, but are re-thinking moving forward with it. I know it's not standard, but we've been using it for years... and are debating converting to samAccountName or remain on logging in with our Lawson employee number. Read More
Pick Tickets / Async / Cycle Counts
We have just moved to v11/Cloudsuite and we are beginning our normally scheduled cycle count process. We have found that in this version when our pick ticket job encounters a request for an item that is 'frozen' - it fails the job and our sync process starts stacking up with failed jobs. In v10 - this did not cause the job to fail, the item was just marked as frozen and the job processed to completion. Does anyone know if there is a way in Async to control the severity level of the errors? Meaning treat it as a fill/kill situation and not a job stop error? Read More
Conditional Security Rule - One User
I need to create a conditional rule on the GLJournalEntries security class to allow Inquire only access to the GL40-GL40.9 form for 1 of 6 users that are assigned the two roles that hold this security class. That is to leave 5 of the users with ALL ACCESS to GL40-40.9 and have a rule to only allow 1 specific user to INQUIRE. Our Auditors have requested this. I would think a rule could accomplish this and know where I have to go to do this and how to get to writing the rule, but I am struggling to get the rule set up, as I have only done a rule once and that was several years ago. Read More
Worthwhile Reading
Top 7 business intelligence trends for 2021
BI has undergone significant transformation in recent years, retrenching its importance in the enterprise, thanks to the added benefits of AI, machine learning, NLP, and the cloud.
CIO, August 11, 2021
How to Avoid the Leading Cloud Migration Mistakes
Moving operations into the cloud doesn't have to be a floating nightmare. Avoiding five common migration mistakes will help ensure a smooth and fast transition.
Information Week, June 21, 2021
HRIS Trends for 2021: The Future of HR Management
HR management has grown increasingly complex over the years, especially with growing remote work and globalization trends in the workforce.
CIO Insight, July 1, 2021
Thanks for your continued support of the LawsonGuru Letter and

John Henley
Decision Analytics
© Copyright 2021, Decision Analytics. All rights reserved.

Please share The LawsonGuru Letter in whole or in part as long as copyright and attribution are always included. 

Lawson® is a registered trademark of Lawson Software, Inc.
The LawsonGuru Letter is neither affiliated with nor sponsored by Lawson Software, Inc.  
Lawson Software, Inc. is not responsible for the content of this information.