Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a situation in the GL and Inventory Journal. we use a new sequence every year i.e DJ19 to year 2019 and DJ18 for 2018. The GL and Inventory of the sequence number is shared. Until now we did not face any issue of duplicate journal batch.
We were running AX2012Fp and Early 2019 we upgraded to AX2012R3. I am a bit amused how can AX2012 allow to save duplicate journal batch numbers while it should be unique.
any suggestions to avoid in the future and also shed some light as why it was duplicated.
Thanks & Regards
Why don't you simply use separate number sequences?
GL and inventory journal transactions are very much different and I would not use the same number sequence for both of them.
Not only to make identification easier but also to make reconciliation much easier.
thanks Ludwig for your immediate response. will follow that. But waht is the solution now. Do i reverse it or some thing else ?
Hello sayyed ar,
If the transactions have been posted then there is no 'solution' or fix required.
As I understood you only the journal batch numbers are affected, which are not critical for accounting because for accounting the voucher numbers count.
Also, after some time (years) those batch numbers should be cleansed / deleted anyway to ensure that you system is performing well.
So, at the moment, I don't see anything that you urgently need to correct.
Are you using the same number sequence code or the same pattern for two number sequences? There is a setting in the Ledger parameters to allow duplicate vouchers or not. You can check this parameter to prevent new postings with a duplicate number.
Thanks for your reply. I am using the same number sequence for GL and Inventory. as suggested by Ludwig I will try to change the sequence number for Inventory. yes, I saw the setting in GL Parameters, this setting is for the voucher not for the Journal Batch Number. Teh voucher is set to "Reject duplicate". The voucher series has no issue but the journal batch number has issue as this is duplicated since its being shared between GL and Inventory module.
Thanks for your reply . in my company here the journal batch number is important and the Auditor says that it cannot be duplicate.so as a solution. I have asked them to reverse the entry and reenter the data.
I was not paying too much attention on the batch numbers. Was thinking of the vouchers. If you have issues with duplicate batch numbers, check if the continuous option on the number sequence. If it is enabled, you can indeed have some issues. In that case try to disable the continuous option.
Thanks for your reply. yes the continuos option is cliked.i need to click it as i need the system to generate the next journal batch number automatically, instead of manually entering it.
The continuous option is not required for generating a next number. This setting ensures that all numbers will be used. When you delete a record, the used number will be put in a list which will be reused again at another moment. This continuous setting is mostly required for vouchers and invoice numbers. For the journal batch numbers it is mostly not required and can cause the issue you are facing.
Thanks Andre for the prompt reply
You mean to say that if i remove the continuous option i will still be able to get the next number.? this is what i understood. Secondly what if the user deletes the journal. will i get back the deleted serial number. coz in my company both are important. The voucher is the foremost as this affects and updates the accounts. What are the other options which will give me the ability to keep both the journal numberas well as the voucher series in line and not losing any number nor duplicating it. as of now i am not facign any issue on the voucher series in any module but facing the issue in GL and Inventory.
Thank in adavcne
For sure, continuous should remain enabled on the voucher numbers. In my experience, there was never a requirement to have the journal batch numbers to be continuous. If this is important for you, then indeed, you should not disable it, but then can have now and then the issue described.
For which country/region is this the continuous batch number for journals required?
I have not heard this so far and I am curious.
Note: Over time you might have to delete old batch numbers; otherwise your system performance might suffer. Is this something that is possible according to your local accounting/audit rules and regulations or will this be an issue?
Business Applications communities