Posts

Lawson Portal: Requestor does not exist error when logging in to Portal and selecting the shopping link for RQC

, ,

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.

How to check if a Lawson portal form is customized

, ,

Login to portal an admin user.

Preferences >> User Options

Set Data Area to LOGAN and APPLY then OK

 

Go to form RD69.1 and click next to cycle through forms and if you see the one you’re looking for, look for the Isdefault flag. If it is set to 0, it means it’s not the default form when users search it.

If the Isdefault is set to 1, when users search PA17.1, they would be brought to the custom form above (but its set to 0 so it wouldn’t apply here).

 

Alternatively, users could still be using a custom form even if Isdefault is 0 if it was setup in a bookmark or favorites tab within portal.

 

Good luck!

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:

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 type of work is typically done by a Lawson functional resource. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page.

 

Scanned Invoices no longer displaying in Lawson Portal for MHC IXDrill

, ,

There are a few common reasons why scanned invoices may stop showing up in Lawson Portal via MHC’s IXDrill.

 

Reason 1 – IXDrill is outdated on the user’s PC and may need a newer version (assuming auto-update is not enabled or working).

Reason 1 resolution: The server’s version of IXDrill may have updated, you’ll need to contact MHC or your organizations Windows IT support to get a newer version installed of MHC IXDrill

 

 

Reason 2 – Error: Cannot connect to ixQueryEngine Server

Reason 2 resolution: The server’s IXQueryEngine process may have crashed and your organizations local IT windows support may need to reboot it. Alternatively, the server may have migrated to a new virtual machine and the URL in your IXDrill settings will need to be updated.

 

 

Reason 3 – Incompatible or Outdated Browser

Reason 3 resolution: Contact MHC to get a compatibility matrix for browser supported with the version if IXDrill you’re currently using or contact your Lawson support team to verify the browser in use is also supported with Lawson Portal.

How to set a distribution group to a Lawson job within Lawson portal

, ,

Before we get started, you’ll need to have distribution groups setup already. See our article on how to do that if you haven’t. You’ll likely need higher privileged access to perform these tasks.

Assuming you already have distribution groups setup, follow the steps below.

  1. Login to Lawson portal.
  2. Go to a Lawson job that you want to set a distribution group for.
  3. Once the job is created, click on the “Reports” button above the Job Name.
  4. In Report Properties, select Distribution Group and then select one of your created distribution groups from the Group Name drop down box and press OK when done.
  5. Click “Change” to save the report properties. Now Inquire on the job and click Reports again to verify the changes were made.

That is, your reports will now show up in the users print manager that are in the selected distribution group. All without having to go to LID.

How to Fix Missing Drill-Around or Drop-Down Boxes on Lawson Portal Forms

, ,

Sometimes after applying a patch, drill-around and drop-down boxes don’t get properly rendered on certain forms. Below are some steps to check which forms may have been affected and how to resolve them.

  1. Assuming you’re logged into LID, change directories to your %LAWDIR%\<productline> directory
  2. Run this command: attrib /s *err
    1. You may see common errors such as: %LAWDIR%\<productline>\XXsrc\PROGRAM.err
      • These can be resolved via running qcompile and then clearing IOS cache (also your browser cache, logging out and back in).
    2. However, a less common error %LAWDIR%\<productline>\XXsrc\PROGRAM.scr.xmlerr cannot be resolved by simple recompiling.
      • This error typically has to do with forms that have drill-around and drop-down boxes.
  3. To resolve PROGRAM.scr.xmlerr errors, we must run srgen and then scrgen
  4. If lawappinstall stage failed to run scrgen and hasn’t been activated you can run the following commands in the below order:
      • srgen -A <productline>
      • scrgen -A <productline> <systemcode> <program> (for the programs with the .scr.xmlerr files in XXsrc directories).
  5. If you’re spotting the .scr.xmlerr files after activating a patch successfully, run the following commands in this order:
      1. srgen <productline>
      2. scrgen <productline>
      3. Check to see if the .scr.xmlerr still exist.
      4. Run qcompile for each program with the .xmlerr manually or run a cobcmp <productline> to compile the entire productline.
        • Run: qcontrol -jlocal,8 (this will increase amount of compile jobs from 2 to 8, change back to 2 after)
        • Run: qstatus | wc -l (this will show you how many compile jobs are remaining, when it hits 4, compiling is done).
  6. If problem persistes, repeat step 5, make sure you’re clearing IOS, server, and browser cache, logging out and back in. Give some time in between testing.

Good luck and happy debugging!

Lawson Portal – Getting Started as a New User

, ,

When first using Lawson portal, it can be a bit overwhelming with all the buttons and unfamiliar UI. The first change I always make is changing the buttons to display text instead of icons.

 

First go to Preferences >> User Options

 

Under “Toolbar Button Display” select Text >> Apply and OK

Once you’ve applied the changes, your icons will change from this:

To this:

This is especially helpful for users with higher tier access as you don’t want to accidentally click delete or change a form when you didn’t mean to!

 

Hope this simple tip was helpful!

Lawson Portal Helpful User Guide

, ,

Over the years I’ve assisted users debug issues in Lawson portal.  Through this time, I’ve noticed a pattern of users not utilizing fundamental functions of portal.  I’ll share to you a few of them today.

 

New Tab Button:

Instead of using up more of your PC’s memory, Lawson has its own tab system that users often miss. This will let you switch between multiple forms faster and easier as shown below:

 

Search box keywords:

 You might be used to typing in form numbers as shown below, but did you know you can type in keywords as well?

Don’t know a form name to General Ledger? Type in the word General Ledger and click search:

This is great for newer and veteran users taking on newer tasks.

 

Form Help:

Finally, if you want to get more information about the form you’re currently using. Go to the form and click Help >> Form Help.

 

Hope these tips helped you in your journey in mastering Lawson Portal.

Resolving “Cannot run this program while GL 190 is running” error when trying to release journal entries in GL40.1

, ,

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

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

In GLMONITOR, type “GL190” and select 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. This should solve the error. Good luck!

Creating a better Employee Self-Service Screen in v10

,

Many v10 Employee Self-Service (ESS) users don’t particularly like the bookmarks bar compared to v9.

A simple fix for this is to make simple modifications to the ESS portal role.

To make this portal role truly a employee self-service screen, limit it further as shown below:

Make sure you also set your product line in options and enable it.  Here are the option settings we use:

Once done, this is what your ESS only users will see:

There is much more to play with here and it is not limited to ESS only, but this is a simple modification.  Enjoy!