Fetch lock_jnlnum Failed

Owned by Knowledge Assistant
Last updated: May 08, 2024
Description of Issue
  • Users report error in one or many Munis module programs at moment of output post stopping journal creation
  • Error - Munis (xxxxxxxxx) Fetch lock_jnlnum failed.
Context
  • Fiscal Year Preparation
  • Configuration & Setup
Cause
  • Journal Number Control is not defined for needed fiscal year on the General Ledger and/or Project Ledger
  • Someone has Journal Number Control locked or in update mode making resource unavailable
  • Someone has a program open that is clocking the journal number control process and that lock needs to be released
Resolution
  1. Take note of the Fiscal Year on the transaction that produces error
  2. Review the proof transaction's allocated detail lines to see if they use General Ledger Accounts and/or Project Ledger Expense Strings or Funding Sources
  3. Follow How to set up Journal Number Control for needed Munis Ledger(s)
  4. Verify that GL Journal Source records are created for 2 future years (create if needed)
  5. If using Project Ledger, make sure Project Journal Number Control has been setup as well
    1. How to set up Project Journal Number Control
Additional Information
  • Journal Number Control determines the following
    • What Fiscal Year(s) are in Munis.  Data entry is still limited to 1 year prior, current or next year
    • What next journal number is for that fiscal year's period
    • What effective dates can be used in a period
      • Period 0 and 13 are not limited by effective date as they are not equal to a calendar month