The cookie and XML data is stored in the RQC work directory. This directory is defined in the LAWDIR/system/rqc_config.xml file.

To delete the cookie and XML data, follow the steps below:

  1. Change to your rqc_work directory.
  2. Delete all files for the web user(s) (e.g., rm userid*)
  3. Change to your rqc_work/cookies directory.
  4. Delete all files for the web user(s) (e.g., rm userid*)
  5. Change to your rqc_work/xml directory (if it exists).
  6. Delete all files for the web user(s) (e.g., rm userid*)
  7. Run the following URL to perform IOS Cache Refresh: http://hostname/servlet/IOSCacheRefresh
  8. Run the following URL to perform RQC Cache Refresh: https://hostname:port/rqc/html/utility.htm
  9. Have the user delete their browser cache ensuring that ‘All time’ is selected. See linked KB 1188792: “How to clear your browser cache”.
  10. Have the user enter RQC and immediately click on the NEW button.
  1. In LBI, open Reporting Services Report Administration
  2. Under Server Administration click on Email and Printer Settings:
  3. Select All Devices to see current list of devices and note the device type (important for loadfile):
  4. Now lets build the loadfile in CSV format:From left to right, the columns are <ownername>, <username>, <user email>, <Device Type>If it’s a printer, replace username and user email with <printername> and <\\networkprinter>
  5. Now lets import the file with Import Devices:

If there are any errors, it will let you know, if not, you can check All Devices section to see if your device loaded in.

Many organizations opt to engage Lawson consultant teams for managing their Lawson Security and LBI systems. These consultant teams offer managed services at a fixed monthly rate and possess extensive knowledge and expertise. This service is particularly suitable for larger organizations, but smaller organizations that do not require a full-time Lawson employee on-site may also find it beneficial. Nogalis provides this service, and you can contact us via our contact page for further information.

There are times when you may encounter the following error message, “Fld Error: Key Number Does Not Exist”. This can appear when attempting to compile a 4GL program in Lawson, it is possible that the key needs to be added to kndef.

Note that this error message will likely present itself in the XXXX.scr.err file.

To resolve this error, simply follow the steps outlined below:

  1. Login to LID
  2. Run command kndef to define the missing key
  3. cd LAWDIR/(productline)/sdlib
  4. rm *
  5. srgen (productline) (source)
  6. qcompile (productline) (source) (program)
  7. recompile any other invoked programs

Your error message should now disappear and the program should run normal.

Lawson Expense Management can occasionally lead to a duplicate invoice or another issue. If you’re running the EX542 and it goes into status 1 or 2 (in process or error) in EX20.1 and EX20.2 for your expense report.  Then you’ll likely see an error saying “Invoice Already Exists”.


To resolve this, you may need elevated privileges. If you believe you have the access, follow the steps below.

  1. Go to EX20.1, inquire on your ER number.
  2. Change the status to 9 and click Change.
  3. Go to EX20.2, inquire on your ER number (locate the ER with the error field “Invoice Already Exists”
  4. Change the status to 9 and then remove the error field. Click Change.
  5. Re-run EX542 and see if it completes properly.

That it! If you’re still having issues and Infor is not able to assist, it might be worth looking into Lawson Managed Services (MSP). Reach out to a Nogalis representative to see if they can assist and or to provide your organization 24/7 Lawson support from an entire team of consultants at a fixed rate instead of having to hire a full-time position.

tokendef: Using tokendef to add a user menu with a couple of different forms as menu options in Portal.


Trying to use ‘tokendef’ to add a user menu with a couple different forms as menu options, specifically for AP90.1 and AP90.2.  In Portal the menu launches (the menu name appears at the top), but the menu options do not display.  An XML error may also be encountered in Portal when trying this.


To setup this up correctly, menu names that are going to be used in Portal, must be in a XXXX.01 format, where ‘X’ is a letter or number.


After creating a new menu using tokendef you will need to run an IOSCacheRefresh otherwise, you will get an error stating bookmark not found in Portal when trying to access the new menu.

When restoring an existing cloud user in Lawson security (that was previously disabled), you have to match the mingle IFS ID with the SSOP identity.


  1. Go to mingle >> User Management

  1. View a user and under details look for the IFS User GUID
  2. Go to your orgs Infor Security Service webpage and edit the users identity
  3. Under SSOP Identity, (delete existing one) and copy the IFS User GUID in step 2 in the user field.
  4. Type in any password in both fields and click Save



This should resolve the authentication error.


Here is a screenshot of the whole process (ISS on left, Mingle User Management on right):

Good luck!

At times your user may get the error “Requestor does not exist” when logging into Lawson Portal and selects the Shopping link for Requisition Center.


This is because a valid Requestor must exist in Manage Identities in the Lawson Security Administrator (LSA) application.  To verify this, follow these steps:

1)  Login to the LSA Application

2)  Select User Management

3)  Select Manage Identities and verify the correct Requestor is populated

4)  Upon entering RQC/Shopping and the User’s Profile in Shopping where you see the user’s Requester, if it’s not showing the correct Requester, have the user click on the “New” button in the bottom-right-hand corner of the screen.


Note:  After any changes are made in LSA, upon re-entering RQC XML, you need to go into the Utilities link (rqc/html/utility.htm) and click on the RQC IOS Cache Refresh button before accessing the Shopping link again in RQC.