End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
"Cannot create a record in Ledger journal table (LedgerJournalTable). Name: Vend_p, Vendor Payments. The record already exists"Getting above error when create payments.
This look like the issue is with the duplicate journal num.
Can you please give any solution to set the journal num?
Check the number sequence for this journal. Is it marked as continuous? It should usually not be necessary to have it continuous, so just remove the Continuous checkbox from the number sequence settings.
If you need to have it continuous (basically if you have requirement that this internal "technical" id sequence has no gaps) you can remove the problematic number from the Status list of the number sequence.
We cannot make it non continuous as it was maintain continuous from very beginning and here, journal number generated was duplicate so we have to change the journal number that is generated at the time of create payment.
Can you please give a way to set the next journal number ? or from where the journal number sequence maintain?
Number sequences are maintained in Organization Administration - Number sequences - Number sequences.
First check if the Next value of the number sequence is ok. If not, change it to some value that is really free (not yet used).
If the Next value is ok, then the problem is that some already used value exists in the Status list of the number sequence. In that case just delete that value from the Status list.
Also please note that continuous number sequences should be used only when it's really required (for example because of legislation) that there are no gaps in the sequence. Journal numbers are just technical sequences inside AX so there should not be any legal requirement for those to be continuous. Continuous number sequences are slower to initialize, and can sometimes have issues like the one you have. So you need to pay some price (slower performance, using time to investigate issues) for the continuous number sequences.
We got the solution for this.
The number sequence having the list generated for specific number sequence and that number sequence is used at the time of create payments.
We have delete the entry from list form
List button open the status of the number sequences and we have cleared that entries.
Now, It works for us.
Thank you for all your replies.
Great to hear that!
Please mark the helpful answer(s) as verified so that others can benefit from them. Thanks!
I am not able to mark answer as verified. Can you help me?
Next to the suggested answers you see text "Was this answer helpful?" or something like that. And you can click Yes.
It is showing only in your responses. There is no link shown in my own response. :)
Yes, that's right. Since I provided the suggested answer. If it was helpful, please mark it as verified.
You're supposed to mark the answer(s) as verified, not your own question. The idea is that others can see which answers / suggestions were helpful.
Also, you are not supposed to mark your own questions / messages as "Make post a suggested answer" when you post them. Since they are not suggested answers to the problem.
Business Applications communities