/
Error acs.SegmentThree in Account Inquiry

Error acs.SegmentThree in Account Inquiry


Description of Issue

Error in Account Inquiry after upgrade:

Munis (glactinq)

Prepare statement 1341 failed. -6372 [ISAM -4104]

Additional information concerning a status error of -6372:

[Microsoft ][SQL Server Native Client 11.0] [SQL Server] The multi-part identifier "acs.SegmentThree" could not be bound.

Context

Recent upgrade

Cause

Segment sort order is not unique

Resolution

General Ledger Menu > Inquiries and Reports > Account Inquiry

  1. In Account Inquiry, click Seg Find.
  2. Select Sort by Segment.
  3. From the "Active Sort Set Order Definition" screen, select 3 unique options (example: 09-org, 11-object, 12-project).  Click Accept to save.
  4. Click Back to return to the main Account inquiry screen.
  5. Click Search and enter search criteria and click Accept.  Results should show if GL data access is sufficient.
  6. Please contact Munis Support if error persists.


Additional Information





Related content

Accounts out of order in Account Inquiry after upgrade - Sort by Segment missing segments
Accounts out of order in Account Inquiry after upgrade - Sort by Segment missing segments
More like this
Update Order of Account Entry in General Ledger Settings
Update Order of Account Entry in General Ledger Settings
More like this
Unable to open find cursor 6372 error in Next Year Budget Entry - Active sort order is different than Fund Org Obj or Proj
Unable to open find cursor 6372 error in Next Year Budget Entry - Active sort order is different than Fund Org Obj or Proj
More like this
Error in Account Inquiry - A column has been specified more than once in the order by list
Error in Account Inquiry - A column has been specified more than once in the order by list
More like this
Unable to save active set order in Account Inquiry - 2019.1.16
Unable to save active set order in Account Inquiry - 2019.1.16
More like this
No search results in Account Inquiry for all searches- user has GL data access
No search results in Account Inquiry for all searches- user has GL data access
More like this