AccountingUnitControl

 2 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Georgette
Veteran Member
Posts: 52
Veteran Member

    We are in the planning stage to transition from laua to LSF 9 security.

     

    There are users who will be accessing LBI for financial reports only.  Is it possible to set up a single security class for these report users (say for the AP275 bursted report) using the AccountingUnitControl to limit their drill around to their respective departments?

     

    I’ve seen in KB where you have to use the IsAttributeInRange to evaluate ranges of values in the AccountingUnitControl.  What do you do if you have both single values and ranges?

     

    Is there a limit as to how many values are entered into the AccountingUnitControl?

     

    Or is it possible to write a script in the security class to evaluate the bursting rights already set up in LBI?

    Dave Amen
    Veteran Member
    Posts: 75
    Veteran Member
      Hi Georgette,
      I may be able to answer one of your questions (hopefully). I've successfully loaded 124 5-character attribute values into ProcessLevelControl, and I'm sure AccountingUnitControl can hold the same.

      Is that enough for your purposes?

      Best regards,
      Dave
      (303) 773-3535
      Georgette
      Veteran Member
      Posts: 52
      Veteran Member
        Thanks Dave for your quick response, that will definitely meet our needs.