njc
Member
We had a strange thing happen while writing an A/P batch.
1. A single batch with 614 entries ran single threaded
2. Batch completed successfully with no errors
3. Started receiving calls today from the bank that we had duplicate check numbers
4. Reviewed batch with following results:
a. First 115 records processed ok
b. Record 116 had same check number as 115
c. Record 117 was ok
d. Record 118 had same check number as 117
e. Above pattern continues for 150 checks and then all is well
At first glance, we would suspect that something else was running at the same time, but we single threaded the job. The other thought is a problem with next numbering - but only for 150 records?? Is there any log in JDE where we can see if another job taking control of the next number was running?
We have a call into JDE but no response as of yet. Has anyone else seen this??
Thanks for any help you can provide.
PS - If you need more info regarding configuration, please let me know what details you need.
Natalie Chlop
Xe, AS/400, Citrix
1. A single batch with 614 entries ran single threaded
2. Batch completed successfully with no errors
3. Started receiving calls today from the bank that we had duplicate check numbers
4. Reviewed batch with following results:
a. First 115 records processed ok
b. Record 116 had same check number as 115
c. Record 117 was ok
d. Record 118 had same check number as 117
e. Above pattern continues for 150 checks and then all is well
At first glance, we would suspect that something else was running at the same time, but we single threaded the job. The other thought is a problem with next numbering - but only for 150 records?? Is there any log in JDE where we can see if another job taking control of the next number was running?
We have a call into JDE but no response as of yet. Has anyone else seen this??
Thanks for any help you can provide.
PS - If you need more info regarding configuration, please let me know what details you need.
Natalie Chlop
Xe, AS/400, Citrix