/
General Journal Entry Proof - Invalid Transaction Structure

General Journal Entry Proof - Invalid Transaction Structure



Description of Issue

Received an Invalid Transaction Structure error using General Journal Entry/Proof

Munis (glcjeent)
Invalid Transaction Structure
An invalid structure for database transaction logging has been detected. 
A BEGIN WORK instruction was executed within an open transaction...



Context
  • General Journal Entry/Proof (GEN, GNI, GCR)

  • Error Message



Cause
  • This system thinks user is trying to take action in the incorrect order or server and workstation are not on the same page or step.  

  • This lock error is usually due to having more than one session of the same program open or another user posting a transaction that would hit the same account at the same time.



Resolution
  1. Close out of EERP

  2. Log back in to EERP

  3. Try again

  4. If the error persists and/or is consistent, please contact General Ledger Support for assistance.



Additional Information












Related content

Journal Reversal - Invalid Transaction Structure
Journal Reversal - Invalid Transaction Structure
More like this
Error in Budget Transfers and Amendments - Invalid Transaction Structure
Error in Budget Transfers and Amendments - Invalid Transaction Structure
More like this
General Ledger Journal Lock
General Ledger Journal Lock
More like this
Invalid structure in Invoice Entry and Proof- A COMMIT WORK instruction was executed without an open transaction
Invalid structure in Invoice Entry and Proof- A COMMIT WORK instruction was executed without an open transaction
More like this
Munis glcjeent Could not add new DTDF detail record -6372 When Releasing a Journal Entry
Munis glcjeent Could not add new DTDF detail record -6372 When Releasing a Journal Entry
More like this
Master Article - An invalid structure for database transaction logging has been detected
Master Article - An invalid structure for database transaction logging has been detected
More like this