Cannot create a record in Ledger Journal table (The record already exists)

(0) Share

Report

Posted on by Community Member

Good Afternoon,
I am receiving the following error when trying to post a statement.

2335.error.PNG

After doing some reading on my own I found out that this might be caused to a Number Sequence limit. How can I proceed to increase this number? Would it be in the SQL table it's self or within AX?

Thank you for any help provided!

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Mahmoud Hakim 17,887 on at

Like (1)

Report

this is a common issue, you can check this link

stoneridgesoftware.com/microsoft-dynamics-ax-error-the-record-already-exists

Was this reply helpful? Yes No
oldman.logan 565 on at

Like (1)

Report

Depending on if it is a journal entry in GL, AP or AR, the following are the locations for number sequences:

GL -> Setup -> Parameters - Tab name: Number Sequences

AP -> Setup -> Parameters - Tab name: Number Sequences

AR -> Setup -> Parameters - Tab name: Number Sequences

Was this reply helpful? Yes No
Verified answer

AXSHAH 528 on at

Like (1)

Report

We had same issue, change the Number sequence for General ledger with max length including constants to 10 only.

In your case: AEV-000000334 must be AEV-000334.

Also if you have multiple legal entities then make sure each legal entity General ledger number sequence have unique format.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

We were getting the same error while users were trying to Create and Post journal entries in AP, AR and GL modules. I was able to resolve this by Compiling and Synchronizing the following tables and form.

Compiled and Synchronized the tables

LedgerJournalTable
LedgerJournalTrans

Compiled the form
Ledgerjournaltable

Everyone was able to create and post journals after this. For one person I had to RESET the Usage Data and Clear CACHE by deleting the *.AUC files in \APPDATA folder.

Was this reply helpful? Yes No