How to setup a distribution group in Lawson for a jobdef

, ,

Here is a simple step-by-step guide on how to setup a distribution group in Lawson for a jobdef.

  1. Login into Lawson Interface Desktop (LID) and type in: grpdef
  2. Create a group name and add users to group
  3. Create a distribution list using command: dstlstgrpdef
    1. Add your group from step 2 to this new Distribution list
  4. Open jobdef select job you want >> Select step and press F6 >> B. Report Distribution
  5. Now arrow down to Destination and set as Dist Group, under Group/* Print, type your group name or Distribution List. This should populate a list of users on the right side.
  6. So when this job runs, the PRT and Error file will be placed in these users print directories. Press Enter twice to save changes.

If you found this article helpful, Nogalis offers managed services and expert technical resources to assist with Lawson system configurations like setting up distribution groups. Whether you need help managing user groups, optimizing workflows, or maintaining your Lawson environment, our managed services provide the support you need to ensure smooth operations. Contact us to learn more about how we can assist with your Lawson system.

Error Message in Edge when going to LBI from Lawson

, ,

Problem:

When I click on the LBI bookmark in my Lawson screen, I get an error message stating the URL redirected you too many times. This only happens when using the EDGE browser. It did not happen in Chrome.

 

Resolution:

Open settings in EDGE and go to Cookies and site permissions>>Cookies and data stored>>Cookies and site data and make sure the Block Third-party cookies is not off.

Turn on the following:

Now refresh cache and clear your cookies.

Note: adding any exceptions may cause the same issue, so make sure to remove any exceptions under Allow or Clear on Exit.

Tips For Using deljobhst

, ,

Often our Lawson print queues get cluttered and out of hand.  Lawson’s deljobhst command is a really great tool for cleaning up your batch jobs.  It can clear the clutter from your user’s print managers, as well as free up some space on your server.  Run this command in LID.

For each of these commands, you must provide a “ToDate” in MMDDYY format.  So, if you give it an end date of 033119, for instance, you would delete all the selected job history up to March 31, 2019.

You also have the option of providing a user’s account so that you just perform the delete for a specific user.  There is also a from date option that allows you to manage job history for a specific date range.

We recommend setting up some of these commands on a schedule to keep your Lawson server happy & healthy.

Here is a summary of the command:

The -w option will delete all waiting jobs, so jobs in recovery and jobs with Invalid Parameters.  After you run this, there will not be any jobs listed in the waiting queue for the specified user (or all users) up to the specified run date.

The -c option deletes all completed jobs.  This is a great way to clean up user’s job schedule print manager lists.  This action removes the data from the QUEUEDJOB table.  It does not remove print files.

The -r option removes all the print files associated with batch jobs, that were created up to the specified to date.  This will help keep your server from getting too cluttered.  Make sure you back up your print directory, especially if you have a retention policy at your organization.  If you run the command so that it deletes ALL print files (so delete everything up to today), it will delete your entire print directory.  Don’t panic!  It’ll be created the next time a user runs a batch job.

Building a .cbl for Infor

, ,

There are times that Infor support will ask for a .cbl of a program in your Lawson system.

 

When working with Infor Lawson systems, you may encounter situations where Infor support requests a .cbl file for a specific program. This is because .cbl files contain the source code for programs written in COBOL, a language commonly used in business software like Lawson.

Why Infor Support Might Ask for a .cbl file:

  • Troubleshooting Program Errors: If a Lawson program is not functioning correctly, providing the .cbl file allows Infor support to examine the source code to identify and diagnose the issue.
  • Investigating Program Behavior: The .cbl file helps Infor support understand the program’s logic and how it processes data, which can be crucial for resolving unexpected behavior or performance problems.
  • Analyzing Customizations

 

Resolution :

At the command prompt, type bldsh productline system code program

Example: bldsh test IC IC130

This will create a .cbl in your LAWDIR/productline/xxsrc directory.

Lawson Comments & Attachments

, ,

Many Lawson screens have comment buttons that open a drill-around screen with different comment types.  If you have ever wished to query these comments for reporting or other user interfaces, you may have noticed that they are difficult to find.  Infor has “hidden” them in tables with the “L_H” prefix.  This is the “header” for the comment.  If there are any details that spill over the available characters in the commend, there will also be a record in the corresponding L_D table.  The naming convention is “L_HXXX” or “L_DXXX” where “XXX” is the prefix of the table that feeds screen where you add the comments.  For instance, Requisition Header comments can be found in “L_HRQH” and “L_DRQH”.  Join the comments to your main record using the “L_INDEX” column in the parent table.

How to remove the Infor Logo from your Lawson Business Intelligence dashboard

, ,
  1. Login into LBI
  2. Click ‘Display Dashboard’ link under Tools -> Services -> FS Service module.
  3. Click New Property Button and type ‘showBanner’ then click ok.
    1. Important: type showBanner exactly as shown (case sensitive)

  4. Type NO to hide the banner (if showBanner property is not present, default is YES)
  5. Click Update at the top and refresh the page to see changes.

 

Before:

After:

If you found this article helpful, Nogalis offers managed services and technical resources to assist with customizing and maintaining your Lawson Business Intelligence dashboard. Whether it’s tasks like removing logos or other system configurations, our team provides the support you need. Contact us to learn more about our managed service offerings and how we can assist with your Lawson system needs.

Updating GLMonitor

, ,

Sometimes the following error on GL may occur: Resolving “Cannot run this program while GL190 is running” error when trying to release journal entries in GL40.1

You may run into this error at some point in GL40.1 or GL45.1:

Fortunately, there’s an easy fix to this. First login to Lawson portal and search GLMONITOR:

In GLMONITOR, type in GL190 and hit Inquire, if you get results and notice the run time, the process is in fact still running and causing the issue with GL40:

Go to job scheduler by opening LID and typing in jobschd >> F7 + A to select all users >> Then W to go to waiting screen.

Look for any GL190 jobs running and verify the User Name is the same one in GLMONITOR when inquiring on GL190 program. Check the error and if its safe to recover, recover it and let the job complete.

 

Go back to GLMonitor and inquire on GL190 to verify the job is no longer running:

 

Go to GL40.1 and release your Journal Entries.  Good luck!

 

Resolving the “Operator Not Authorized to Change Unit Cost” error

, ,

This is one of those Lawson errors that could waste a morning of work looking through the Infor knowledge base, analyzing/changing security, and or reviewing logs.

 

So, you’re on PO20.1 and want to make a change to a PO entry and get this error:

To resolve this is actually incredibly simple and can be changed on PO04.1 at the bottom of the Buyer Information Tab (your settings may be different based on your needs):

If you happen to get a similar issue for a requisition cost change “Requester not authorized to change unit cost”, simply go to RQ04 and allow unit cost override for the specific requester (your settings may be different based on your needs):

If you found this article helpful, Nogalis offers expert managed services to resolve Lawson errors like this quickly and efficiently. Our offerings include troubleshooting technical issues, streamlining processes, and providing functional finance resource assistance. Whether it’s addressing security settings, resolving errors, or enhancing workflows, our managed services ensure your finance operations run smoothly without the need for a full-time, in-house team. Contact us to learn how we can simplify and optimize your Lawson experience.