You may come across an issue in LSA such as the following, “Selected Dist. List Does Not Match To User Group.” This issue occurs when you don’t have your user assigned to the proper group (and also trying to assign dist. list group via LSA vs ISS). Here is how to fix it:
- Confirm the user is assigned to the group in grpdef:
- Add the group you created with users in dstlstgrpdef
- Lawson Security Administrator (LSA) may have an issue adding this user in their environment info
- Login to Infor Security Service (ISS) and assign the distribution group their to the user.
That’s it!
If a user is having issues seeing a bookmark in Lawson, it may be because the bookmark is a parent of itself which can cause the bookmark to not appear for users even though they have access to it.
This issue can also create an infinite child bug in the Bookmark Manager as seen below:
In the database under the table “LOBKMARK”, we see that this BOOK_MARK 272 is the parent of itself (PARENT_BKMARK is also 272).
IMPORTANT: Always be cautious when making updates to the database.
To fix BOOK_MARK 272, we need to update its PARENT_BKMARK and set it to 0.
Here is the code to do this:
UPDATE LOBKMARK SET PARENT_BKMARK = 0 where BOOK_MARK = 272 and OBJ_ID = 285
We add the OBJ_ID in there as an extra check. It’s always recommended to build and update query with a select query first so you don’t change more than what you need.
The “Lawson RQC Requisition user not able to see Service Tab” issue can crop up from time to time for select users, but it is a simple fix (see below).
After verifying the user has adequate access for requisitions and the RQ04 record is created.
Have the user clear browser cache go to Requisition Center >> Shopping >> and Press NEW.
Have the user logout and back in, check to see if the Service Tab is now there.
Also, in RQ04, you can set a value for Special/Service Items in one of the tab options to see if that resolves the issue as well.
Good luck!
Problem:
When I try to access or add a rule to a security class in the Lawson Security Administrator (LSA), I get the error message, “Data area has been suspended”. How do I resolve this issue?
Resolution:
This error usually occurs after running dbreorg without stopping your LSF WebSphere Application Server prior to the execution of dbreorg. This is a simple fix.
Basic steps to resolve this issue:
- First, we need to stop WebSphere
- Next, stop LSF
- From here, you must make sure that there are no java processes running. This is important so you won’t get the same error message again.
- After confirming, then you can re-start LSF
- Finally, start WebSphere again. You shouldn’t get the error message anymore.
In Lawson, to restore a user’s print files, copy them to their original locations so that they will be visible in the print manager.
The standard locations for print files are:
Example (UNIX):
$LAWDIR/print/UserName/cu201b/1
Example (IBM i)
$LAWDIR/print/UserName/cu201b/1/xxxxxxx
Example (Windows):
%LAWDIR%\print\MYDOMAIN_UserName\cu201b\1
Once the files are copied to the correct directories, load them using loadrpts.
Running the command as follows will load all print files into the print manager for files existing in the standard print directories for all users where the file name in the directory ends with .prt:
loadrpts -s -p productline
To load reports for just one user from the standard print directory for files ending in .prt, use this syntax:
loadrpts -s -u username -p productline
Good luck!
You might be used to copying all Lawson jobs from one user to another when provisioning new users because jobdump and jobload flags can be very confusing in Lawson.
Something like this:
jobdump -d -o Job -v UserName joesmoe jobdump.txt
then
jobload -c -o Job -v UserName <copy userid1> <to userid2> jobdump.txt
What if you only needed specific jobs from a user to copy over?
Lets say we only need to transfer a MA126 job called MA126M:
jobdump -d -o Job -v JobName MA126M -v UserName joesmoe jobdump.txt
Here is a AP155 Job named AP155_P1:
jobdump -d -o Job -v JobName AP155_P1 -v UserName joesmoe jobdump.txt
Remember the dump file will be in the path you’re currently in LID. Good luck!
