November 2016 Minimize

November 2016

The LawsonGuru Letter
Thought-Provoking Commentary for the Lawson Software Community
In This Issue
Pharmacy - NDC# vs. Mfg#
Deleting ACA hours from BN54
IC211 with pricing?
GL20-Accounting Unit/Account Code Combinations
Worthwhile Reading
Quick Links
Subscribe to The LawsonGuru Letter
Quote of the Issue
"Get your facts first, and then you can distort them as much as you please."
-- Mark Twain

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. 
Pharmacy - NDC# vs. Mfg#
Hello - I have built out a few hundred pharmacy items in Lawson & have questions regarding NDC# vs. Mfg#. While I understand that an item can have multiple NDC#'s based on various UOM, our buyer seems to think that NDC# & Mfg#/Vendor# are interchangeable, so we're at a bit of a standstill. Read More...
Deleting ACA hours from BN54
While in the process of adding external ACA hours to an employee's BN54, I did an add over an existing line of data and it also brought in 40 payroll hours in addition to the 466.75 external hours. Of course, when I try to delete the record, I get an error message that you "cannot delete if payroll hours exist". Does anyone have suggestions on how I can correct this epic fail?? :) Read More...
IC211 with pricing?
Is there a report that pulls in a company specific item master but also brings in the cost of the item? IC211 brings in last cost but what if there is no last cost but we have a PO25 for that item, how can that be brought in? What if we want to see the cost at the default buy uom instead of the each? Does Lawson have some kind canned report for this already? Read More...
GL20-Accounting Unit/Account Code Combinations
We have several accounting units that are mapped to various GL Account codes per GL20.2. We have one accounting unit for balance sheet transactions, but we discovered several income statement accounts with exists as "yes" on the GL20.2 for the balance sheet unit. We don't want individuals accidentally coding transactions improperly so we need to turn the exists from "yes" to "no." We have shut off dynamic account generation to prevent the exists from being turned automatically to "yes" if someone keys the wrong GL account code. I also built an upload file to do one mass change for all the bad combinations (we have about 2000). The problem is when I upload, if the bad combination has any ANY activity, even though the balance is now "0," I get the following message. "cannot delete; account has actual activity." Is there any way to turn the exists from "yes" to "no" since we made the adjustment so the combination balance in the ledger is now "0," or are we stuck with these active bad combinations in our ledger that we will have to manually monitor?  Read More...
Thanks for your continued support of the LawsonGuru Letter and




John Henley
Decision Analytics

Worthwhile Reading
Can Hospitals Stay Cyber-Healthy?
Lab tests and diagnostics, medical staff shifts, surgery schedule, patient history - all this data is now hosted, for the most part, in a digital environment. Just imagine what someone could do if he or she had access to all that information.
Information Management, September 29, 2016

9 Ways IT Can Ruin Its Relationship With The Business
Aligning IT and business units sounds fantastic in theory. But when the rubber meets the road, IT leaders face unique challenges as they strive to engage and collaborate with business-side colleagues.
Information Week, September 6, 2016

Get to Know Enterprise Spreadsheets to Improve Business Effectiveness
Enterprise spreadsheets are designed to provide the best of both worlds in that they offer the ease of use and flexibility of desktop spreadsheets while overcoming their defects - chiefly inability to maintain data integrity, lack of referential integrity and dimensionality, absence of workflow and process controls, limited security and access controls as well as poor auditability. All of these issues can cause serious problems for business use.
Information Management, September 30, 2016

 Decision Analytics

© Copyright 2016, 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.