Gl Zone data level security in LAUA

 2 Replies
 1 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Sherry Shimek
Advanced Member
Posts: 43
Advanced Member

    Our health system some needs to restrict some users' data level access to a general ledger zone within one company.  We can restrict the access by using ranges of accounting units, but that is very awkward in our chart of accounts. 

    For example, we use zone 200 specifically for physician medical groups and want to limit their users to data within that zone.  The accounting unit design is that the final three digits are the zone, but the beginning four digits are spread through all zones and thus aren't easy to create valid ranges for data level security.  Some of the valid accounting units are 1000200, 4800200, 4925200, 5625200, 5870200, & 5875200.  1000201 is not to be included.  Currently building valid ranges would have 30 lines of parameters and more importantly require maintenance for any new accounting unit additions.

    Any suggestions?

     

    Sherry Shimek Catholic Health Initiatives Englewood CO
    Sherry Shimek
    Advanced Member
    Posts: 43
    Advanced Member
      I am not sure if the lack of response is that this that the answer is too obvious, is impossible, is outdated as it is the old security model, or if I didn't explain the issue well enough.

      Basically, is there a way to enter secondary data level security parameters for GL that are based on the final three digits of the accounting unit (our zone number) instead of listing every accounting unit in the zone?

      All feedback even uproars of laughter will be appreciated.
      Sherry Shimek Catholic Health Initiatives Englewood CO
      John Henley
      Posts: 3353
        Insert uproar here :)
        Thanks for using the LawsonGuru.com forums!
        John