Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Lawson S3 Financials
Hide inactive accounts in user drop down lists
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
251
Members:
0
Total:
251
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 Financials
Hide inactive accounts in user drop down lists
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Sherry Shimek
Advanced Member
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
Senior Member
Posts: 3348
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
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
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
Senior Member
Posts: 3348
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
Senior Member
Posts: 3348
11/17/2011 12:57 AM
The drill around mod works for both LAUA and LS9.
You are not authorized to post a reply.