Mali
Active Member
Hi All,
We have an issue with model Journal entries. This has been happening since last year but this time I monotored it. Got the Model record from F0911 at different stages of the process to see exactly at which point this happens.
1)User creates the Model JEs properly
Say there are 10 lines in the document out of those 4 lines are for Company 003
2)She makes a copy for the model for the 1 st month
3) Posts the copy. No issues with the copy or the Model.
4)Overnight or over the week end, all 4 lines of the company 003 of the model gets a batch # assigned.
*)Batch # is the only field that has changed…
*)Audit fields are not updated.
*)Only company 003 records are updated
*)Those 4 records are the only records with that batch #
*)Batch # is not in the f0011 batch control file.
Any of you have any ideas what it could be?
I suspect some integrity report in update mode just because can't think of any thing else. I am sure that Batch # was issues on a specific date going by that batch # range.
I went thr the submitted jobs for that date by the batch # and couldn't find any report specifying that batch # or the document # or even the Account # on one of those lines.
I am going to ask around from other IT folks in our company whether any NON_JDE processes that would be doing this.
Any ideas...
Thanks a lot in advance!
Mali
We have an issue with model Journal entries. This has been happening since last year but this time I monotored it. Got the Model record from F0911 at different stages of the process to see exactly at which point this happens.
1)User creates the Model JEs properly
Say there are 10 lines in the document out of those 4 lines are for Company 003
2)She makes a copy for the model for the 1 st month
3) Posts the copy. No issues with the copy or the Model.
4)Overnight or over the week end, all 4 lines of the company 003 of the model gets a batch # assigned.
*)Batch # is the only field that has changed…
*)Audit fields are not updated.
*)Only company 003 records are updated
*)Those 4 records are the only records with that batch #
*)Batch # is not in the f0011 batch control file.
Any of you have any ideas what it could be?
I suspect some integrity report in update mode just because can't think of any thing else. I am sure that Batch # was issues on a specific date going by that batch # range.
I went thr the submitted jobs for that date by the batch # and couldn't find any report specifying that batch # or the document # or even the Account # on one of those lines.
I am going to ask around from other IT folks in our company whether any NON_JDE processes that would be doing this.
Any ideas...
Thanks a lot in advance!
Mali
