Who's On?

	Membership:
	Latest: Alanna
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5294

	People Online:
	Visitors: 253
	Members: 0
	Total: 253

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

Hide inactive accounts in user drop down lists

5 Replies

0 Subscribed to this topic

43 Subscribed to this forum

Sort:

Author

Messages

Sherry Shimek

Advanced Member Send Private Message

Posts: 43

11/16/2011 3:46 PM

Is there a way to hide inactive accounts in the user drop-down account lists in portal for GL, AP, RQ, and PO, for example?

We changed our supply general ledger accounts and prefer that the users do not see the old inactive accounts in their account drop down lists. We are hoping to prevent time wasted when users choose inactive accounts prior to being stopped by the "inactive account" error.

Because they have been used in the last fiscal year, we cannot delete these accounts. We have tested inactivating accounts at the chart level and also at the accounting unit-account join level and the accounts still show in the drop down list. (The General Ledger at least shows the Inactive Account status, but AP, for example, doesn't.)

We also tried restricting the accounts to a hardly used system, but the accounts still show in the other system's account list.

Thank you for your help easing this transition for our users!

Sincerely,
Sherry Shimek

John Henley

Posts: 3355

11/16/2011 9:12 PM

Hi Sherry, there are two ways I know of that you can accomplish this:
1. LS9 security rules on the GLMASTER table to make the record inaccessible if status = 'I'
2. A very trivial modification to the drillaround rules in GL.sr to add a condition to the select list to only show active accounts.

Sherry Shimek

Advanced Member Send Private Message

Posts: 43

11/16/2011 9:46 PM

Thank you, John. This information will be helpful as we move to LS9 security. One more reason to move quicker to LS Security!!!

Is the second suggestion possible in LAUA? If not, any other options specific to our current security? (Sorry, I should have included that in the original post. We are on Lawson 9.0.1 if that is pertinent.)

Thanks again,
Sherry

Greg Moeller

Veteran Member Send Private Message

Posts: 1498

11/16/2011 9:55 PM

You could possibly do the same thing in LAUA... but I haven't tested it. Go find a security class that has access to GLMASTER, and F6 define on the table. Choose B. Record Security
Type in a condition name --- I used HIDEINACTIVE and tab to the condition ... something like Active Status not equal "I"
Hit enter a bunch of times for it to take, and test.

John Henley

Posts: 3355

11/17/2011 12:57 AM

Thanks for reminding me about that one! It's been a long time since I've done that one. The caveat of doing it with LAUA and/or LS9 security is that it affects all instances of that table for the security class. So if the user also accesses that table for another task, such as GL90, they might not see the accounts in situations where they might be legitimate.

John Henley

Posts: 3355

11/17/2011 12:57 AM

The drill around mod works for both LAUA and LS9.