Dear Community
i am trying to create a Import project using General Journal Entity. All the fields are mapped I have an issue. How do i avoid duplicate based on Invoice numbers or any other key fields. The current Entity will just keep importing the file without checking the duplication. Is there a way i can reject duplicate journal enteries
I am importing Vendor/Customer Invoice using GLJ.
regards
PS
HI,
have you tried with, General Ledger Parameter-> Check for voucher used= Reject Duplicate
Is should not allow you to post duplicate invoice number.
Dear Ramit
this parameter is already ticked. The issue is that everytime i import the journal it will get a new journal #. So it will not check for duplicate validation on this. i want it to check on Invoice #+cusotmer or Vendor Account.
Hi PS,
If you want to import vendor invoices, why don't use use the AP invoice journals or - better - the pending vendor invoice form in AP?
There you have all checks available that are needed.
Best regards,
Ludwig
Dear Ludwig
thanks for the response. the reason why i want to use the current setup is that it was all working before upgrade to 10.0.12. It suddenly stopped the customised entity which was functional started giving issues. so i tried using the default General Journal Entity to see if it work. the Import works but validations are missing which i guess was part of the customised entity which we were using. With VIJ i can use this but what do i do for Customer Invoices?
Hi,
I don't think the import validation is there in out of box because this duplicate import is a valid scenario for many business, so not a good option to have a validation.
You may think of something customized.
Hi Ramit,
The customized Entity Class is already there for some reason it gives an error after the upgrade to 10.0.12. The error what it says is Journal is locked by system for processing. So not sure if MS can help with this customized Entity. I realized that one of the field is not getting populated with the import and could be the reason that because that field is locked it throws this error.
Regards
If you journal is locked by system, you can fix that by using the Optimization advisor from System admin.
Have you tried already?
Have tried all options. Checked in Optimisation Advisor and also checked 22 entities one by one to see if there is any lock by system. As i doubt the issue is with this one field which is not getting populated on the system. The customised Entity Class used to populate it but with the new upgrade it has stopped and i am not able ot manually put any value in this field. I guess this is where the problem is. this field could be a customised field. Is there any way i can check if this field is locked in AOT?
could you help unselect the Set - based processing in data entity.
how does the status now. seems we need to add customization check the duplicated fields while importing
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 683 Most Valuable Professional
André Arnaud de Cal... 563 Super User 2025 Season 2
Sohaib Cheema 398 User Group Leader
