Who's On?

	Membership:
	Latest: John Bonin
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5270

	People Online:
	Visitors: 308
	Members: 0
	Total: 308

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

GL90 Drill to payments

3 Replies

0 Subscribed to this topic

16 Subscribed to this forum

Sort:

Author

Messages

Margie Gyurisin

Veteran Member Send Private Message

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 Send Private Message

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 Send Private Message

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: 3351

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.