When the ADFS Token-Signing certificate is updated on the ADFS server, it will have to be imported to Lawson and Infor OS.  The networking team should let the Lawson team know when the certificate is being updated in ADFS.

Someone with admin rights on the ADFS instance will need to export the certificate and provide you with the “.cer” file before these tasks can be completed.

Update the Certificate in Lawson

Log onto the Lawson Server

Start a ssoconfig -c session

Go to “Manage WS Federation Settings” > “Manage Certificates”

Select “Delete WS Federation Certificate”

Select “Create certificate for “WS Federation”

Select “Delete IdP certificate”

Enter the service name of your ADFS service (if you are unsure, export all the services and look for the one that redirects to  your ADFS server).

Select “Import IdP Certificate”

Enter the service name of your ADFS service

Provide the full path where you have the token-signing certificate saved

Reboot the server

Update the Certificate in Infor OS

Log into the Infor OS server as the LAWSON user

Log into the InforOSManager (should be an icon on the desktop)

Go to Identity providers on the left side

Double-click on your IdP

Select “From URL” to import the new certificate and metadata

Provide the URL: https://<your adfs server>/federationmetadata/2007-06/federationmetadata.xml

Click “Load”

Make sure the certificates load (there may only be one, but there should be at least one)

Reboot the server

 

 

To suppress Receiving Delivery and Putaway (PO134) delivery tickets when MSCM Delivery Documents are all that is needed is to disable the Back-Office PO Receiving (PO30) Receiving Delivery and Putaway (PO134) delivery ticket by removing the printer from PO Receiving (PO30) or create a dummy printer to stop the back-office delivery ticket from printing.

Removing the printer from PO Receiving (PO30) only works if the user does not have a default printer assigned to them. After being removed, the default printer will simply populate back in the field upon clicking change.

Additionally, an enhancement to PO Company Setup (PO01) was added which provides a flag called “Delivery and Putaway Ticket Print” which allows disabling the delivery ticket printing at the company level.

In Lawson you may run into the following error when a user is trying to change or run a job:

“Cannot run AP520, entire Company run is in progress”

The error can be found at the bottom of your screen (see below screenshot in red box)

 

To resolve this, open and then log in to Lawson Interface Desktop (LID):

Type the following: lapm <enter_your_productline> qmon and press enter

 

Next. find the AP record and delete it. The error should be fixed and disappear. See if the user can now change/run the job. Refer to the screenshots below for a visual guide.

 

Have you ever wondered how to request a new Lawson software license key?

You will need to request a new software license key from your Infor Representative. Here are the steps to do so:

  1. Log into Infor Concierge
  2. In the Application Switcher select the Infor Support Portal application.
  3. At the top click on the Resources menu
  4. Select Request a Software Key > Key Request
  5. Click the Browse button to search for and locate your company name
  6. Fill/Select required fields
  7. Select Next button
  8. Select the product you need a license key for. If what you need is not on the list, then note it in the ‘Notes’ section at the bottom of the page.
  9. Click the Submit button.

 

That’s all you need to do!

Follow this simple guide below to learn how to free up Lawson Interface Desktop (LID) error about max license usage.

When too many users are using LID (or don’t exit out properly), you can max out license usage.

To resolve this error, on the LSF App server (or server users are connecting to via LID), open task manager and end any LAPM.exe tasks as shown below (the users login name should show below so if this request is for a specific user, you can surgically end these lapm.exe processes):

Once those lapm.exe processes are killed, tell the user to try and login again and it should allow them to do so.

 

The Journal Posting (GL190) program output states the message “Another job currently processing for company (0).”

This error indicates that another updating job is currently processing, in needs recovery, or was deleted from recovery.

Go to Job Scheduler and choose all users and verify that an update job is currently running for this company. If so, you will need to allow this job to complete before you can run GL190.  If no active jobs, check waiting and resolve any jobs in needs recovery.

If there is not another job being processed or needing recovery, you will need to update the record that will allow GL190 to run.  Create a paint a screen to update the GLSYSTEM file in the IF System Code and change the Updating field to 00 or blank out the field entirely.

GL190 may also create a GLMONITOR record that needs to be cleared. To clear this record, go to GL15.1, GLMONITOR Maintenance, and Inquire on the program that is running (in this case, you would Inquire on GL190). If a record appears, but the job is not actually running, delete the record.

There is a simple way to check the WAS Server status. First, open the command (cmd) prompt. The command to check which servers are running in WAS is in WAS_HOME/profiles/<profile>/bin.  To check all the servers, supply the switch “-all”.  Otherwise, provide a server name. See the screenshot below for a visual reference for checking the status of your WAS Server.