
Hi all,
We currently use the standard Purchase order conformation batch job within our Dynamics AX 2012 solution. But for some reason the date on which the batch job is created originally is the Date posted on all purchase orders generated! I have tried re-creating the job many ways so this issue does not occur but have failed every time. our current setup is as follows.
1. Access Procurement and sourcing\periodic\purchase orders\confirm purchase orders.
2. Selected the "Late selection" option.
3. Clicked the "Select" button and selected the status "Open order .. Received".
4. Clicked the "Batch" button.
5. Checked "batch posting".
6. Configured batch options
7. Label batch name, set recurrence options, identified batch server. (no end date, 5 minuet intervals)
8. Clicked OK to exit the batch processing form.
9. Clicked OK in the "Confirm purchase order" form.
I have noticed there is a document Date field but this is grey'd out and you would hope reverts to today's date but it does not seem to happen? Is this a known issue with CU6 as i cannot find any reference to it.
Once the batch job has been created you can amend the document date field but when you put "today's date" in the field (Ctrl + T) it also seems to stay fixed on this date.
The Report itself seems to pull the date from the confirm purchase order conformation screen as we have updated this through SQL as a test so this is the date the batch job is incorrectly updating.
*This post is locked for comments
I have the same question (0)Hi Kaila,
Thanks for the clear steps to reproduce, it really helps.
If you're using AX 2012 R1 or R2, there is a hotfix for this problem: KB 2867584 - 'Confirmed Purchase Order date is incorrect when running in batch with "Late selection"'
On LCS, it is possible to see the modification made by the hotfix. Although not recommended by Microsoft, I think it would be easy to adjust the code without installing the hotfix if you preferred. However, perhaps best to take the advice of your partner.
The hotfix is included in CU7 for R1. I cannot see which CU it is available in for R2.