In lawson requisition center, you may encounter this issue where you’re not able to change the company when create a new requisition.

In order to fix this, go into your %LAWDIR%\system directory and find the rqc_config.xml

 

Find this setting and set it to true:

<setting id=”allow_company_select” value=”true”/>

Save your rqc_config.xml file

 

Login to Lawson portal and go to Bookmarks >> Requisition Center >> Select Utilities

Click the Reload Configuration file

Click the RQC IOS Cache Refresh

Logout, clear your browser and depending on your server, the cache may take up to 15 minutes to clear.

Now you should see a drillable company box:

When running a report, you may intermittently get this error: “Max processing time or Max records limit reached… Error code 0”

Screenshot of error:

This one is an easy fix. Go to your LBI server, open Central Configuration Manager.

Highlight and stop all SAP Crystal Reports Server processes as shown below:

After waiting for the processes to stop, double click on each one, go to Parameters Tab, under Max Number of Records, select Unlimited (NOTE: in my screenshot below, I could not turn off process for this demonstration so it’s greyed out).

Once you update each of these processes (you may only have one or two), start the SAP Crystal Reports server processes again, then test the LBI report once more and make sure you’re generating enough report data that surpasses the previous record limit (usually greater than 10k records).

 

Good luck and hopefully this helped resolve your issue!

Ensuring your browser is correctly set up for compatibility with Infor OS Portal (or Infor Ming.le) is essential for a smooth user experience. Here’s a step-by-step guide to help you modify the browser compatibility view setting.

Step 1: Launch and Log In

First, open your web browser and navigate to the Infor OS Portal (or Infor Ming.le) website. Enter your credentials and log in to access your dashboard.

Step 2: Access My Settings

Once logged in, look at the toolbar on the top of the page. Click on your username, which should be located towards the top-right corner, and select “My Settings” from the dropdown menu. This will open the Personal Settings window.

Step 3: Edit Personal Settings

In the Personal Settings window, find and click on the “Edit Item” button. This action will open the Edit Personal Settings dialog window.

Step 4: Adjust Browser Compatibility Mode

Within the Edit Personal Settings dialog, locate the “Browser Compatibility Mode to Use” setting. Here, you will see a dropdown menu where you can select the value that matches the browser version you are using. Choose the appropriate option and click “Save” to apply the changes.

Step 5: Save and Close

After saving the changes, you will be returned to the Personal Settings page. To complete the process, click the “Close” button to exit the settings.

By following these steps, you can ensure that your browser is correctly configured for optimal performance with Infor OS Portal (or Infor Ming.le). This simple adjustment can help prevent compatibility issues and improve your overall user experience.

 

A user can on behalf of another user use a proxy to assign a task that the user would typically perform to another user so that the other user can take action for them. For example, Mary is going on vacation and will need someone to take actions in her absence. You can assign a proxy for that task. You could also assign a proxy permanently to one of a user’s tasks.

Proxied work items are routed to the Personal Task of the user who has been assigned as a proxy. A Personal Task is the task that all users have which is named with their username. User Josh Denver may have task named, depending on your site’s naming conventions, “jdenver”.

Users who had been given the required access rights can assign proxies for themselves. Infor Process Automation administrators can also assign proxies for users.

When on LBI (Lawson Business Intelligence), sometimes your users may receive the following error: “The viewer is unable to open an advanced prompt dialog” when they are trying to adjust the parameters on a crystal report running through LBI (see screenshot). To resolve this error, follow the steps below.

First, navigate to the ERS install validator at https://<lbi-server>:<lbi-port>/ers/installvalidator.jsp?

Next, log in as an administrator.  On the System Settings, set “Crystalviewer Ajax” to “Enabled”.

Finally, save the install validator configuration.  The changes are instantaneous, and do not require a restart. You should no longer receive the error!

 

Identifying performance issues and improving performance for Lawson applications in a Windows Environment can sometimes be tricky.

This article provides some ways to improve performance specifically when batch jobs are running more slowly than expected.

  1. Update bpm.properties to assist the performance batch jobs that call services in IPA
    1. On the Lawson server, navigate to LAWDIR/system/bpm.properties
    2. Remove the lines lpxMaxHeap=XXXXX and lpsMinHeap=XXXXX
    3. Add a line “useLPSBridgeSocket=true” (check if the line exists already)
    4. Restart Lawson services
  2. Set Windows page file to 32Gb
    1. On the LSF server, search for “Advanced System Settings”
    2. Go to the Advanced tab
    3. Under “Performance”, select “Settings…”
    4. Select the Advanced tab
    5. Under Virtual memory, select “Change…”
    6. Unchecked “Automatically manage…”
    7. Select the drive where Lawson is installed
    8. Select “Custom size” and set the max to 32000
    9. Click “Set” then “OK”
    10. Reboot the server

 

Error occurring: Batch Job failed: execjob(laStartProcess): Unable to log in Domain\user

 

What’s happening before this error:

When logged in as the lawson user and running a user defined batch job (defined within tokendef) which calls the importdb command. In our example, we run importdb as the command but this can happen for any user defined token that either runs a command or a script such as a perl script or bat file, etc.

 

This is an example of an log text (joblog) with this error in it:

User: domain\UserName Job: JobNameHere Queue:

BEGIN: Job Submitted: Tue Jan 13 15:51:36 2020

 

Step 1: importdb Started . . . .: Tue Jan 13 15:51:36 2020

Token Command. . . . . .: CommandNameHere

execjob(laStartProcess): Unable to log in domain\UserName

StartStep failed: The operation completed successfully.

 

Elapsed Time: 00:00:01

 

END: Job Ended: Tue Jan 13 15:51:37 2020

 

How can this issue be resolved?

These steps are for experienced “Lawson” security admins  (Nogalis provides Managed Service support if needed):

INFOR Single Tenant CLOUDSUITE CUSTOMERS ONLY: 

If you are an Infor Single Tenant CloudSuite customer running the Infor Lawson products, if you do not know the user’s INFORBC account password, you need to do the following:

  1. Go to the CloudSuite Self Service Portal:

https://concierge.infor.com/ then find and select the cloudsuite app (open an infor ticket if you don’t have it)

  1. You will go under service requests, choose the password change option. Change the password for this user that is having the issue.
  2. After that is done, have the user test running the script again.

 

For all On-Premises customers or CloudSuite customers that do know their INFORBC account password:

IMPORTANT As of Oct of 2020, Infor found a bug in the ISS User interface (/scwebadminapp) that when changing just the password, the UID value for the user would be changed and cause the user to no longer see their jobs and reports. JT-1492340. The fix for that requires a combination of ISS version 11.0.9.1627 and then the LSF version needs to be one of the following:

– 10.0.9.2 or higher

– 10.0.10.3 or higher

– 10.0.11.5 or higher

 

If you are on the proper versions, you can use ISS to make the change to the password, if you are not on the proper versions, you should only do the update via the LSA tool in the steps below.

Use the Infor Security Service (ISS) web page (context root is usually /scwebadminapp) if your Lawson System Foundation (LSF) environment is federated with Landmark. Alternately, if you are not federated (uncommon) then log into the Lawson Security Administrator (LSA). If you’re not sure if you are federated with Landmark you should review your LAWDIR/system/lsservice.properties file to check for fed. lines as well as this line; isprimary=true . If these are present, then you are federated.

  1. Search for the user for whom the batch job failed.
  2. Navigate to Manage Identities
  3. Click on the environment identity from the list of Services on the left of the ISS web page or the screen in LSA
  4. That password must be the actual user’s domain (Windows customers) or (Unix, IBM i – OS user) password in order to use user tokens/scripts. Double click within the ‘password and ‘password confirm’ attributes to type (DO NOT USE COPY and PASTE) in the correct domain password for this user. Save the change in ISS by clicking on the “Diskette”/save icon or, if you are in the LSA tool, choose Edit then Change.

 

IMPORTANT: DO NOT DELETE AND RE-ADD THE USER’S ENVIRONMENT IDENTITY OR THEY WILL NO LONGER BE ABLE TO SEE THEIR JOBS AND REPORTS IN THIS ENVIRONMENT.

 

Good luck and again, if you need experienced Lawson Security Admins to complete this task, reach out to us at https://www.nogalis.com/