Posts

Adding a custom batch command to Lawson Environment Security

  1. If you need to run a batch command in Lawson, first we need to open up Lawson interface desktop (LID).
  2. Type the tokendef
  3. For this example we’ll select Environment Form IDs and then select SECURITY category.
  4. Place your cursor at the top of the Environment Form ID list and press F8 to insert a command
  5. Type in the command you want here, ours is customcomm
  6. In Lawson Security Administrator (LSA), go to ENV profile, open a security class you want to assign customcomm command to. Under Environment Security, you should see your new batch command, select and grant all access.
  7. And we’re done!

Upcoming Events April 2020

Working from home? Check out April’s virtual meetings in the Lawson User Community!

 

Infor Mid-Atlantic User Group Spring Virtual Meeting

Hosted by: Infor Mid-Atlantic User Group
When: Friday April 3rd, 2020 from 9:00 to 3:00 (US/Eastern)

CHANGING PLANS – COME JOIN OUR VIRTUAL MEETING!

In light of all that is currently going on with COVID-19 we are moving to host a Virtual Meeting, delivering the same content we would have provided at the live meeting. We are going to provide a link to a Webinar that will be live that you will be able to join from the saftey of your homes or offices. We hope that you will be able to join us and take advantage of the topics we have lined up.

Date: April 3rd, 2020

9:00am – 9:05am Opening Remarks – Deedre Day, MUG President

9:05am – 10:15am: Infor Update/General Session #1 – Andrew Wolling, Infor

Preparing for your Infor CloudSuite Migration – Mike LaCosse, Infor

This presentation is for Lawson v9 and v10 customers who are wondering what they can do to prepare for the upcoming migration to CloudSuite Financials, Supply Management, and Global Human Resources. Topics include a migration roadmap, preparing existing data, data management in the CloudSuite, and tips/tricks to prepare your team to optimize benefit from Infor CloudSuite. This session will also cover CSF data cleanup, GHR data cleanup, how much data to migrate, how to migrate in phases, as well as training recommendations, partner enablement, and payroll roadmap.

10:30am – 11:30am: General Session #2

Infor Reporting and Analytics Options – Rich Bendickson, Dashboard Gear

Rich Bendickson of Dashboard Gear will go over a variety of reporting and analytics options you can use with your Infor applications. Topics will include connecting to cloud and on-premise data as well as best practices when embarking on a reporting/analytics project. Some examples will be shown in a variety of tools such as Birst, Excel, SSRS, etc. and will cover HR, Finance and Supply Chain examples.

11:45am – 12:45pm: General Session #3

AWS GovCloud and Compliance

An overview of AWS and Cloud Computing, with a focus on compliance and what differentiates AWS GovCloud.

1:00pm – 2:00pm General Session #4

Security Considerations for your Infor Lawson CloudSuite – Vinod Mathur, Appiggenics

Vinod Mathur from Appigenics will discuss key security considerations for your Infor CloudSuite solution. This session will discuss the multiple domains of security applicable to CloudSuites and your responsibilities as a customer in ensuring the secure operations of your new cloud environment. We’ll talk about compliance and governance of your solution.

2:00pm Closing Remarks – Deedre Day, MUG President

View/Register Here

What do I need to know about LDAPS?

Microsoft is hardening their security with LDAP channeling and LDAP signing in an update coming soon. Any applications that rely on LDAP connections to Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS) need to be converted to LDAPS. LDAPS is a secure connection protocol used between applications like Lawson and the Network Directory or Domain Controller. Below are the potential impacted Lawson applications mentioned by Infor in a recent KB Article.

Impacted Lawson applications:

  • Lawson System Foundation (LSF) environments using AD LDS instances for Authentication Data Store (RM Configuration).
  • Lawson System Foundation (LSF) environments using an LDAP Bind to Windows Active Directory for authentication.
  • Landmark Environments using an LDAP Bind to Windows Active Directory for authentication.
  • Infor Federated Services (IFS) synchronization connections to Active Directory.

Infor has recommended that on-premise clients configure the impacted applications and have provided KB Articles on how to perform these tasks.

Some important things to note:

  • This change does affect you, even if you have implemented AD FS
    • If you are using Microsoft Add-ins for LSF and Lawson Process Administrator for Landmark, you will have a Thick Client installed that used LDAP Bind.
  • If your networking team takes the Microsoft LDAPS update and enforces LDAPS connections before these changes have been configured, your Lawson applications will fail in the following ways:
    • The LASE process on LSF will fail to start.
    • Login to services that rely on LDAP bind will be unable to login (Landmark Rich Client, MSCM Handheld Devices, IPA Flows to LSF).
    • IFS will be unable to sync users from Active Directory.
  • This change will NOT impact DSP applications
    • DSP application include Infor Business Intelligence (IBI or LBI), Lawson Smart Office (LSO), Mobile Supply Chain Management (MSCM), etc.
    • These applications use Infor Lawson for authentication. They are not bound to LDAP, nor do they have their own instance of AD LDS.
  • You can update your configuration at any time
    • The changes recommended by Infor can be completed before LDAPS connections are enforced, and there will be no negative impact to your system.

Changing to a new ERP and using Punch Out?

Many ERP systems allow for a much longer location ID than Lawson does.

Many Punch Out vendors have limitations on the size of the location ID.  Make sure to validate with any Punch Out vendors you may have before you come up with a new location naming convention. Otherwise you may have to revisit this item later.

Troubleshoot blddbdict errors

If you are performing a blddbdict as part of database changes, or as part of a product line copy, and you receive the errors “Dictionary Not Built – Fix Errors And Rebuild”, perform the following commands in LID:

setsfl

setnotused <productline>

 

After that, your blddbdict command should be successful.

blddbdict <productline>

Upcoming Events March 2020

Spring is here and there are several Lawson User Group meetings in store!

 

SWUG User Group Mega Meeting

Hosted by: Southwest User Group (SWUG)
When: Tuesday March 10th, 2020 – Wednesday March 11th, 2020 from 8:00 to 5:00 (US/Central)
Where: Grapevine Convention Center 1209 South Main Street Grapevine, TX 76051

User Registration ONLY – The Southwest User Group Mega Meeting

Join Infor employees, certified business partners, vendors and hundreds of your colleagues from companies across the southwest for two days of learning, sharing, networking and fun.

When: March 10th – 11th, 2020

Where: Grapevine Convention Center
1209 South Main Street
Grapevine, TX 76051

AGENDA AS OF FEB. 10, 2020

Thanks, SWUG Board

View/Register Here

 

Georgia Alabama Spring Meeting

Hosted by: Georgia Alabama User Group
When: Friday, March 13th, 2020 from 8:30 to 3:00 (US/Eastern)
Where: Gwinnett Medical Resource Center 665 Duluth Highway Lawrenceville, GA30046

Georgia Alabama Spring Meeting, March 13, 2020

Northside Gwinnett Medical Resource Center

665 Duluth Highway, Lawrenceville, GA 30046

AGENDA AS OF 01-24-2020

The meeting fee is $15.00 for all Infor/Lawson customers attending this meeting.

Vendors: Must contact Kim Walker, kim.walker2@choa.org for sponsorship information and to pay their fee to attend. All vendors must still register for food headcount.

The meeting will begin with registration at 8:30 am and sessions begin at 9 am. The sessions will wrap up around 3 pm. Breakfast and lunch will be provided. Come visit with fellow customers and Infor partners to learn more about what other customers are doing and how partners can assist your organization.

The agenda is being drafted and topics include:

  • The Evolution of Dimensionality: Understanding the Impacts and Benefits of CSF Dimensionality
  • Infor CloudSuite HCM Goals with Performance Management and Lessons Learned
  • Procure to Pay Automation Powered by MHC and Infor
  • Infor Treasury Management for Infor CSF Overview
  • What’s New with Purchasing for Infor CSF & Supply Management
  • Accessing Cloud Data

Near by Hotels, Click Here

We look forward to seeing you at our meeting in March!

The Georgia Alabama User Group Board

View/Register Here

 

IMSUG Spring 2020 Meeting

Hosted by: Infor Mid-South User Group (IMSUG)
When: Friday, March 20th, 2020 from 7:30AM to 4:00PM (US/Central)
Where: Building 4 2555 Park Plaza Nashville, TN 37203

The Spring 2020 meeting of the Infor Mid-South User Group (formerly known as TNLUG) will be held at HCA Healthcare’s corporate headquarters in Nashville, TN.  The meeting will be in our newly remodeled showcase meeting area in building 4. It is a beautiful space and you will NOT want to miss out on this event.  Stay tuned for registration opening and agenda items.

View/Register Here

How to dump RQ02 approval strings out of a Lawson database

Lawson RQ02 approval strings work hand in hand with Landmark and are setup in different ways per organization. Some use general hierarchal titles and some use individual usernames. Regardless of how you implement it, you want to be able to create a report so you can update them as individuals join/leave/move around the organization

To generate a database dump of all approval strings and their levels using my method, you’ll need read access rights to the LSL database and must be using SQL.

  1. Login to your TEST or PROD database application.
  2. Create a new query window and paste the below SQL code in, one is a screenshot to show syntax highlights and the other is the raw code for your convenience.

  3. Run the query, copy and paste with headers into Excel to filter down the data or edit the query.

I’ve renamed various column names to reflect the different levels and dollar amounts more clearly. Feel free to change the query to your liking. This is only the RQ02 strings, to get the filters for users’ setup in Landmark, check out my article titled: “Generating a simple approval level report from the Landmark database”.

How to Restrict a Specific Form Table Field in Lawson Portal

For this tutorial, we will be restricting a table in CU01.1

  1. Login into Lawson Security Administrator
  2. Load up your default security profile typically titled PROD10 or TEST10
  3. Add a new security class

    Ours will be called TestSecClass
  4. Grant token access to CU01.1
  5. Once this is added, we want to restrict a specific table on CU01.1 to find the table name, go to CU01.1 and press CTRL + SHIFT + O when selecting the field
  6. Back in LSA, set CUC-CURRENCY-CODE to Deny Any Access
  7. Add this new class to a role of your choice. Add the role to a user and test CU01.1. To learn more about how Lawson security handles access, check out my other article titled: “Lawson Security – The Theory of Least Privilege Access Explained”

A Brief Overview into the Lawson Requisition and Approval Process

Lawson allows for requester users to submit requisition orders for their organization. To make sure the orders are valid, Lawson also supports approvers to verify and approve/reject the orders.

The core of this is done by setting up Requisition Locations (RQ01) and Requisition Strings (RQ02) and having a workflow process everything in between.

Requisition Strings can be used in many different ways, but in our example it is to have individual approvers approve for a particular location. This can also be general titles like Manager, VP, etc. or however your organization wants to set it up.

As you can see below, these are strings for Company 100, Requesting Location RQ210 with Approvers starting at Level4 and stopping at Level6. The lower limit on the left is the amount that the users approve orders for and depending on the IPA flow logic, could notify or skip them.

When users track requsitions in say RQ10 for example, they can drill around and see history log via the strings themselves:

This is only half the setup for this particular organization.

 

Approvers have to be setup on the Landmark side via Rich Client or Process Server Administrator web application. This is done via “Filters” and these have to be named accordingly to what your IPA Requisition flow will coincide with.

Below is an example of how we would mirror the RQ02 strings in Rich Client (custom report).

The Level 4, 5, and 6 are the “auth id” that our custom flow matches up on. It then grabs the user from Landmark and send notifications based on where the requisition is in the flow.

Some organizations simply don’t use RQ02 strings as they may find it easier to process everything on the Landmark side.  Landmark does have a set of its own reporting tools and filters (See my other article titled “Generating a simple approval level report from the Landmark database“ for a custom database report I created).

The benefits of RQ02 strings in my experience is that the frontend functional users could setup the strings for the developers to mirror in the back end (or by an automated process if done right).

 

Hope this was helpful in giving you a brief overview of requisitions and approvers.

Generating a simple approval level report from the Landmark database

Lawson natively supports requisitions and a hierarchy requisition approval system within organizations. Some use both the approval strings found in RQ02 and setup filters within Lawson Rich Client (An application in Lawson Landmark). More info on this can be found in another one of our articles titled: “A Brief Overview into the Lawson Requisition and Approval Process”

 

To generate a database dump of all approvers and their levels using my method, you’ll need read access rights to the LSL, IPA, and GEN databases and must be using SQL.

 

    1. Login to your TEST or PROD database application.
    2. Create a new query window and paste the below SQL code in, one is a screenshot to show syntax highlights and the other is the raw code for your convenience.


      Run the query and your results should show as so:
    3. Copy and paste with headers into Excel to filter down the data or edit the query.

I’ve included an Active Status to show which locations are active or inactive. This can be changed in RQ01 per company and location.

Feel free to optimize the query to your likings if you see any inefficiencies. Remember, this is only for approval levels on the landmark side, not the RQ02 strings themselves.