We are trying to run the inventory/wip reconciliation report
Getting the transaction date is in a close period.
I tried to change the dates to just today and still get the error message.
Is this just new year user error? what else should I look for.
Thanks,
Ken
The WIP Recon report uses the same engine as the Capture COS/WIP - meaning it has to run every transaction against the posting rules.
Any chance a GL Account has been disabled or had its end date set to 12/31/2019, and there is a transaction that would hit that account?
Try running the Capture COS/WIP process without posting. I bet you get the same error.
How would I find a disabled GL account or one that has an end date?
Use GL Account Maint, and when you search you can say to include Inactive GL accts.
I’d also use the options button and select Returna All rows
Then just click on the Active or To column header to sort, and scrol to the top or bottom, to see if any are inactive or have a to adte.
So if you set it to 1/1/2020 to 1/7/2020 it works?
If that is the case, I’d query the PartTran table for transactions that have a SysDate of 1/8/2020. See if any have a bad tran date (like like a fat-fingered year)
FWIW - I’ve never seen your error.
Typically, if a transaction is in a closed period, (like if someone entered a PO Recipt on 1/5 with a receipt date of 12/31, after FP 12 was closed) the report runs fine.
That tran wouldn’t show on WIP Recon being run for 1/1/20 - 1/31/20. But it would show on it being run for 12/1/19 - 12/31/19 (and it would show as Unposted)
Aslo, have you tried running WIP Recon using the Transaction System Date from 1/8/20 to 1/8/20?
Found the problem.
User changed the Earliest Supply Date to 1/1/20, so she changed it back to 1/1/19. She says the date should be 1/1/20 vs 1/1/19.
Are there transactions that are messing with being able to move the date forward?
The Earliest Apply date limits data entry that would create transactions in a closed period.
I’d guess that someone created a transaction that had an apply date prior to 1/1/20, and then the Earliest Apply date was changed to 1/1/20. When WIP Recon was run it threw an error because of that transaction.
Setting the earliest apply date should be okay, and prevents accidents.
There are some things that can make back dated transactions, that aren’t obvious. For example, if a packer was created and marked shipped on 12/30, it creates trans with an apply date of 12/30. If that packer is then changed from shipped to unshipped, on 1/5, it creates trans (to undo the ones when it was shipped) with an apply date of 12/30 (the same date as the packer originally shipped).
