Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Security
GL90 Drill to payments
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Saef
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5226
People Online:
Visitors:
171
Members:
0
Total:
171
Online Now:
New Topics
User Group Announcements
Carolina User Group Meeting
12/20/2024 3:15 PM
Date & Time: February 6, 2025, 8:30am - 4:00pm
S3 Systems Administration
ADFS certificate - new cert
12/3/2024 9:38 PM
The certificates on the windows boxes expired and
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Lawson S3 Procurement
ED501 Error: Map 850 not supported by /law/c15vda/lawson/test10/edi/bin/laws_out_91
11/12/2024 3:47 PM
Tried runnning ED501 and getting the atathced erro
Lawson S3 HR/Payroll/Benefits
Error
11/6/2024 9:54 PM
When I try to enroll a retiree in 72.1 health plan
Infor ERP (Syteline)
Syteline: New Data Maintenance Wizard (Error) Need help
11/1/2024 4:24 PM
Hi, I need help with an error on syteline while us
Dealing with Lawson / Infor
Implementing Lawson v10 with Cerner Surginet, Case Cart Picking, and Quick Adds for the OR
10/29/2024 4:20 PM
Hi Everyone, I am wondering if there is any org
Lawson S3 HR/Payroll/Benefits
Canada Tax Calculation (Federal and Provincial) Issue
10/23/2024 5:00 AM
Initially, we had problem with CPP2 calculation is
Lawson S3 HR/Payroll/Benefits
CA Section 125 401k Plan
10/22/2024 10:13 PM
Does anyone have any recommendations on how to fac
S3 Systems Administration
Running AC120 deleted records from ACMASTER table
10/22/2024 3:40 PM
We recently ran the AC120 as normal and somehow it
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1372
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Infor / Lawson Platforms
S3 Security
GL90 Drill to payments
Please
login
to post a reply.
3 Replies
0
Subscribed to this topic
15 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Margie Gyurisin
Veteran Member
Posts: 538
8/27/2010 8:00 PM
We are creating a new role for someone to be able to drill back to payment information from the GL90. We have been able to get the payments to appear, but they can not see employee names. We have given them PR51 form access and they can see names on that form but they can not select an employee from the search box???
We have given them acces to all the tables that the PR51 references - EMPLOYEE, PRSYSTEM, PAYMASTR, PRTIME etc.
Do we need to add some invoked program? If so, which one(s)?
I have attached a screen shot to show you an example.
Any help would be most appreciated.
Thanks.
Attachments
Screen_shot_with_name_blank_on_GL90_drill.doc
Arvin Ojales
Advanced Member
Posts: 24
9/1/2010 7:29 PM
That feld is coming from FULL-NAME from the EMPLOYEE file. Are you using LAUA or LS? If using LAUA and the 'Access' field in RM is set to 'N' this will prevent them to see other employee information except their own employee and direct report's (if manager) record. If you're using Lawson Security check all the security class rules (for EMPLOYEE table) that are attached to the user roles.
Arvin Ojales
Margie Gyurisin
Veteran Member
Posts: 538
9/2/2010 11:35 AM
We are using LS9. We have granted access to all the "name" fields we can find in the EMPLOYEE table. We can not find the field name called FULL NAME in the employee table. My security admin is now going to grant full access to the table and then write rules on every field either granting or denying them to see if that helps. We are open to other ideas.
Thank you for responding.
John Henley
Posts: 3353
9/2/2010 2:26 PM
It's a derived field in the EMPLOYEE table. Couple of things you can look at: 1) Make sure the user has access to all the fields that make up the derived field (last name, first name, middle name, middle initial, prefixes, suffixes, etc.). 2) Look at the ELEMENTS used to define the FULL-NAME (an interesting topic in and of itself)...you'll have to dive into dbdef to see which ones are used: FULL-NAME, LAST-SUF, LAST-PRE-SUF, etc.
Please
login
to post a reply.