Versions Compared

Old Version 1

changes.mady.by.user Knowledge Assistant

Saved on

compared with

New Version Current

changes.mady.by.user Knowledge Assistant

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleDescription of Issue

User gets stuck during Invoice Entry and Proof Header Entry when trying to tab past the Cash Account field with a message stating GL stating GL Account Restrictions Exist

Invoice Entry and Proof module freezes on the Proof Header screen for a user or users

Unrecoverable Error Detected


Munis
Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleContext
  • General Billing
  • General Ledger
  • Account/Segment Group Access

...

Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleCause

This scenario will come up when a userUser/role has what looks to be sufficient General Billing Permissions but are getting a GL Account Restrictions Exist message at the bottom of Invoice Entry and Proof Header Entry window, not letting the user get past AR Code entry. This issue can be related to users whose roles have Limited Access in limited Data Access granted for General Ledger - Account/Segment Group Access got the General Billing or gbinvent is not listed as an Applicable program on the data access record. 

There are also instances of users Proof Header screen freezing or spinning after clicking Accept or Enter when looking to advance to the Proof Detail section of Invoice Entry and Proof program. 


Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleResolution

Have an Admin or Supervisor review the General Ledger - Account/Segment Group Access. More than likely the Org or Obj for the AR Code is outside of any Account Segment Ranges that are defined for Invoice Entry and Proof as an Applicable Program. One of those will need to be updated or a new Account Segment will need to be added to account for the AR Code Accounts. 

  1. Navigate to to the User Attributes program either by searching or via the following path: System Administration > Security > User Attributes
  2. Click Search.
  3. Enter the User ID, Name, or E-mail address for the affected user.
  4. Click Accept. 
  5. View the Roles tab and determine which role(s) grant the GL Account Access and which should be updated.
  6. Navigate to the Roles program either by searching or via the following path: System Administration > Security > Roles 
  7. Click Search.
  8. Enter the Role determine in step 5.
  9. Click Accept.
  10. Click the General Ledger folder.
  11. Click into Account/Segment group access folder.
  12. The accounts attempting to be used must exist in a range here for the Applicable Program.
  13. Confirm folder in the Data Access section. 
  14. Any one segment of the full account that is being accessed must exist here. 
    1. If a segment does not exist, click Add. 
    2. Choose the Type. 
    3. Enter the From and To range. 
    4. Click Accept. 
  15. If Account Access is more strictly limited, then make sure that the ranges do not exclude any piece of the account that is being accessed. For example, if the role grants access to the Org, make sure it does not exclude the Fund, Object, or Project.
  16. Check the Applicable programs hyperlink and make sure that gbinvmnt is listed. 
    1. If the program
    the user received the error in is listed here.
    1. is not listed, click Update under the Applicable programs. 
    2. Click Select Programs. 
    3. Check the desired programs or choose Clear All or Select All. 
    4. When the selections are correct, click OK. 
    5. Click Accept. 


Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleAdditional Information

In Accounts Receivable Charge Codes > Accounts tab, review the listed accounts the user needs access to.