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!

 

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.

When you perform a data refresh in your SQL database, such as reloading data into tables, you may need to take steps to ensure dependent objects and overall database performance are optimized. Follow these steps to Update your SQL Tables after a Lawson Data Refresh.

First, open up the properties for the DB that was just refreshed and you can see that the DB tables have the PROD name.

 

Next, run the following SQL query for the TEST DB:

ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_DATA NAME = INFORLAWTEST10_DATA

ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_INDEX NAME = INFORLAWTEST10_INDEX

You’ve now updates your SQL tables post-refresh.

Many of our clients would like to lock down their external websites to EMSS (Employee and Manager Self-Service) only, because it is a security risk to allow super users to access Human Resources (HR) & Financials from the web.  The official word is that this cannot be done in Lawson.  However, Nogalis has devised a method to remove the search box and all but the desired bookmarks from the external Lawson website (See a sample screenshots below).  If you would like to have this done at your organization, Nogalis is happy to help. Please contact us today!

Internal Lawson Site

External Lawson Site

Problem: An XM User Profile is getting overwritten.

 

  1. Login to XM and view the user profile in XM (Admin rights required):
  2. Locate and view your user:
  3. View the Administration Log and figure out who or what process might be changing this:
  4. In this case we see the HRBkg process modifying this user. This can be bringing data in for your organizations HR application (Workday etc.).

 

You can consult Infor further to get more information on the process updating your XM Users (assuming it’s not a completely custom process). Nogalis also offers a team of managed service professionals to help support processes like Expense Management among other applications. We also support custom processes unlike Infor. Visit us at our contact page for more information: https://www.nogalis.com/support/

 

Problem:
An Expense Report needs to be re-routed immediately for someone else to approve ASAP. Follow these steps to quickly solve this issue.

 

Solution:

1. First, log in to Mingle and Open the Infor XM App under the Applications section.

 

2. Go to Admin >> Tools Document Management (note: admin permissions required)

 

3. Next, search your expense report and Edit it:

 

4. At the bottom left, remove any existing users and add the user you want to approve, then click Save at the top right of the screen:

 

The user you add will now see the Expense Report and will be able to process it.

If you are compiling a form that generates an error “Program X Does Not Allow INVOKE”, that means that the invoked program needs to be set to allow invoke.  To do that, from a LID session, go to the form in pgmdef (pgmdef <prodline> <system code>).  Select Define (F6) > Program (A).  Set the property “Can Be Accessed Via INVOKE” to Yes.  Compile the invoked form and then compile the custom form that does the invoking.

 

Define (F6) > Program (A)

 

This is an update to an older version of this article, which can be found here.

If you found this article helpful, Nogalis provides managed services and expert technical resources to assist with Lawson patching and system maintenance. Let us help ensure your patches are applied efficiently and your system is running smoothly. Contact us to learn more about how we can support your Lawson environment.

During patch install, if customizations exist, the activate will fail on ujobload

lawappinstall ACTIVATE installation started at 11/14/2024 15:48:00 for the following deliverables: PATCH121887.57 PATCH121211.58 PATCH126341.59.
command line = ‘E:\lawson\gen/bin/lawappinstall activate test10’.
11/14/2024 15:48:03 Bypassing Database preparation. Already successful.
11/14/2024 15:48:03 Bypassing blddbdict. Already successful.
11/14/2024 15:48:03 Executing dbreorg listing.
11/14/2024 15:48:03 dbreorg listing execution successful.
11/14/2024 15:48:03 Database change confirmation.
11/14/2024 15:48:07 Database change confirmation successful.
11/14/2024 15:48:07 Database reorganization confirmation.
11/14/2024 15:48:09 Database reorganization confirmation successful.
11/14/2024 15:48:09 Executing dbreorg.
11/14/2024 15:48:09 dbreorg execution successful.
11/14/2024 15:48:10 Executing ujobdump for TEST10.
11/14/2024 15:48:10 ujobdump execution successful.
11/14/2024 15:48:10 Executing ujobload for TEST10.
11/14/2024 15:48:10 ERROR – ujobload failed.

 

Resolution:
Review the lawdir/prodline/backup/ACTIVATEstage/JOBconversion.dmp file for user jobs that need to be deleted from jobdef.

  1. open up that dmp file and see what the actual job names are.
    Look for #> NTID JobName
  2. Look up the username for each of the NTID
    In portal, under LSF Administrator Tools, username lookup
  3. Go into jobdef and delete the job that it is failing on for each user.
  4. Once jobs have been deleted, run lawappinstall activate again and it should now complete successfully.