|
Thought-Provoking Commentary for the Lawson Software Community
|
|
 |
| Quote of the Issue |
"The future is much like the present, only longer."
-- Dan Quisenberry |
|
|
Dear John,
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.
|
|
Item Adds/Changes Best Practice |
Who out there is in charge of maintaining their company's item master, or is familiar with their company's process? We're always looking at ways to streamline our methods, and it would be nice to know any tips or tricks we can use. If you respond, please answer the following questions:
- What is your process for adding new items?
- What is your process for item revisions/changes?
- How much time do you spend doing both in a typical day--not that we usually have those!?!
Read More... |
|
Examiner for Lawson S3
|
 Preparing for your Infor Lawson License Audit?
- Don't overpay for licenses you no longer need
- Combines Lawson 9 Security/RM Users, LAUA, LOGAN, GEN metadata into a single comprehensive, understandable solution
- Export directly to Microsoft Excel® and Adobe Acrobat/PDF®
New Release available, now incorporating Lawson ProcessFlow and supporting IBM iSeries
Read More... |
|
Arrears Re-Order |
| Has anyone reversed the order that payment arrears deductions are taken? Currently, if an employee has multiple common deductions (i.e. 4 health deductions because they were on LOA), the application takes the newest one first. Because we are a monthly payroll this often crosses years and as a result, different premium amounts, our users want the oldest dated arrears to come out first. Just wondering what sort of level of effort this may be? Read More... |
|
Section 132 working condition fringe benefit |
| Does anyone know the remuneration code in Lawson that I can attach to a pay summary group for an OJT program we have that is considered Section 132 working condition fringe benefit? Read More... |
|
AccountingUnitControl |
| We are in the planning stage to transition from LAUA to LSF 9 security. There are users who will be accessing LBI for financial reports only. Is it possible to set up a single security class for these report users (say for the AP275 bursted report) using the AccountingUnitControl to limit their drill around to their respective departments? I've seen in KB where you have to use the IsAttributeInRange to evaluate ranges of values in the AccountingUnitControl. What do you do if you have both single values and ranges? Is there a limit as to how many values are entered into the AccountingUnitControl? Or is it possible to write a script in the security class to evaluate the bursting rights already set up in LBI? Read More... |
|
|
Thanks for your continued support of the LawsonGuru Letter and LawsonGuru.com.
Sincerely,
John Henley
Decision Analyticsbr />
|
|
|
|
Worthwhile Reading |
3 Ways That IT Still Fails Itself
Sometimes we in IT act as our own worst enemy. IT leaders must study these mistakes with brutal honesty.
Information Week, February 11, 2013
BI Still Regularly Fails Business. Here's Why.
Business intelligence software is supposed to help businesses access and analyze data and communicate analytics and metrics.
Information Management, February 20, 2013
IT workers to management: NOW can we telecommute?
IT helps others to work remotely but rarely gets to join in. Is that fair?
ComputerWorld, February 14, 2013
|
|
|
© Copyright 2013, 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. |
|
|