MS AddIns

Shaun - Most of the clients I've had only extend Add-ins to a subset of the user base. Although you aren't granting them access to anything new by granting add-ins... it does pose the risk of someone compounding a mistake. There is a way to limit what form actions are possible via add-ins. So someone might have ACD in Lawson but can be limited to just A or C etc when the call comes through add-ins. This does require a schema modification in security (supported and documented by Lawson). I don't have the document in front of me but I know the information is on support if you are interested.

At first Addins was relegated to the "super users", the analysts/specialists in Finance, HR and Supply Chain. But over the years in Supply Chain we've been training others to use it when their need arises. One buyer uses it to upload data from lab equipment to create PO lines. We have a specialist that uses Addins to manage IC11, IC12, PO13, PO25.6, and IC81. Our sourcing/contracts team uses the query only to pull agreement data.

We are currently just super user use in SCM, but Finance has all financial analysts using uploads. We will likely roll out some spreadsheet designer workbooks when we get to Cloud Suite as I think the "pre-mapped" aspect will be easier to teach the buyers.

Tech team does not use it. Maybe about 4 of our "superusers" do - fairly often and a regular part of their process I believe.  It's beyond the comprehension of most of our users. 

We have 20k+ employees, around 1,200 app users (those accessing HR11, BN32, AP20, etc.) with 50 add-ins licenses. The bulk are for AP/SCM. But HR, Benefits, Finance, and the tech folks have a handful as well.

It is available to all of our users (roughly 3000) - if they request it - but realistically only used by about a hundred.

In our environment, most of the Finance department use the add-ins.  For Supply Chain, they are only used by the Buyers and System Specialist.  For HR, they are used by Payroll, the System Specialist and a few others, such as benefits staff, who need them for mass uploads.

When Lawson was on-premise, we were limited by the number of licenses that we purchased.  When we migrated to the Cloud, which is subscription-based, we now have the ability to push it to as many users as we want without incurring additional cost.  This is also true with Lawson RQC/RSS users.  Although, we are careful who we give the add-in upload access to, due to inherent risks.

We only allow have a small group of users with access mostly in our central Finance and HR departments.

It is only given to about 10 Supply Chain users, but only used by 2 regularly to upload changes for item management. We have found that it is easier for us to pull an ad hoc report or setup a report to run routinely for the end users. The exception is a PO history report that was created and made into a form for the end users to pull PO Receipt spend. We do not allow anyone outside of Supply Chain to upload information into Lawson.