Sage 100

2015 Advanced. User accidentally performed a period end and year end processing in Job Cost. They have been in job cost period 1, 2018 for a week or so and all of the period and future period fields have incorrect numbers. How do I recalculate from the detail?

Accidentally??? Did they accidentally leave their brain at home that day?? What period/year should they be on? Sounds like you could dump all detail for 2017 into Excel and run a pivot table to get your bucket numbers...

We should be on period 7 2017. I have no idea how they closed and got on period 1 2018. Isn't there a recalculate transaction detail utility? I hope that exporting to Excel, manipulating the data, and re-importing is the not only way to fix this mess. They have hundreds of jobs.

That is the beauty of pivot tables....... Very easy to do. What are the period buckets - Current and future?? Or they could wait for JC v2.0 to come out and fix it then....

On the phone with Sage. Apparently there is not a recalculate from detail utility. Rut ro.

Did you try just changing the Year and Period in Job Cost Options back?

Yes. Changing it back doesn't help. I did change it back. It isn't quite as bad as I initially thought but still a minor mess. When she closed the year, the YTD and the PTD numbers were set to 0. Then the new PTD and YTD has been accumulating for the last 10 days or so. When they close May in a week the PTD will be reset to 0 and PTD will be OK. The YTD will continue to be screwed up until 2017 is closed unless we fix it either with VI or DFDM. Not even sure VI is an option... still investigating. They have a couple hundred open jobs and each job has 5 - 10 cost codes that need to be changed.

More than likely a restore from backup

You could also try: 1) Backup 2) Set JC Period/year to 1 period prior to the one you want to be in. 3) Do a period end in JC to end up in the JC Period/Year you want to be in. The JC reports use the accounting date of transactions, not physical buckets, to track current/future periodic amounts.

@ChrisStAmand tried that last night in a test company and it doesn't work. The period end doesn't recalc the transaction detail. @RonPeterson Can't restore from backup because the damage has been occuring for 10 days before anyone noticed.

Import reversed entries while in the incorrect year then set things back and import correct entries?

@alanniergarth Great idea. That seems to be the easiest solution to implement. User is trying to decide if they can live with incorrect YTD numbers or hire me for an expensive fix.