Can't find what you're looking for? Still have questions? Contact customer support (smile)

Duplicate Transaction already exists in the General Ledger (SPROC Error)

Owned by Amina Emam
Last updated: 16 Mar 2023 by Kai Andras
2 min read

A SPROC error occurs when there is a problem saving the data to the database. Refer to the below for the most likely issues.

JOURNAL ENTRY

The most common cause for a SPROC error in Journal Entry is a duplicate transaction number.

This means the transaction number already exists in your general ledger. As the transaction number is a unique identifier in Eclipse, you cannot have duplicate transaction numbers.

  • Make sure to check the transactions have not already been posted under the same transaction number. To do this, search the Ledger Inquiry for the records already using the transaction number.

    • This is the most likely culprit in that either you or another user has already posted the data already, and the system is preventing you from duplicating the data.

       

  • If the transactions you are trying to post is not duplicated data then you will need to change the transaction numbers of your journals so you can post them.

    • Highlight the transactions in Journal Entry and right-click. Select Excel to export these lines to a spreadsheet.

    • In the Excel spreadsheet, remove the Tran and Line values from each record.

    • Delete all the records existing in your batch in Eclipse or create a new batch.

    • Highlight all of the records in the Excel spreadsheet from the first column to the last column (Do not include any blank spaces or headers) and Copy these lines.

    • Go back into your batch in Eclipse, right-click in the Journal Entry window and select Paste.

INVOICE and PETTY CASH ENTRY


1. A SPROC error means a field has been entered with too many characters.

  • This is most often either the Invoice Number / Envelope Number or a Description field for one of the Lines.

    • Trim the Invoice Number to 30 characters at most.

    • Trim the Line Description fields to 210 characters at most. Try to trim under 210 characters.

2. A SPROC error can also appear in if the Control Account has an Invalid Chart Code.

  • To check this, open  Control Table → Control Accounts.

  • Open the Control Account that you have selected for the Invoice.

  • Click the Control Accounts tab and compare the codes to the Chart of Accounts module.

    • You can click the button to the right of each code to use the Chart Lookup.

  • Make sure each field in the Control Account is pointing to the correct code, and that code is postable.

    • If the code is not postable, make sure to change it to postable in the Chart of Accounts module.