Attempting to close year and the batch status report has a number of batches that have a status of 'In error'. These batches are batches from prior to the 9.0 conversion. Answering yes to clear report does not clear this file to allow the year end to be completed.

Hot fix 080704 is installed. Is there a file that can be deleted to get past this situation?

Thanks,
David

Hi David,

Have you run the Data Integrity Check with the HotFix installed?

Andrew that was quick.....

We did a rebuild in data integrety and were able to clear the batch journal. Now we get the message to print and clear 'Prior Year Posting Journal', but can find nothing to print.

Thanks, David

Hi David,

The posting journals in Ledger 90A are tagged with each year as a radio button. When you print the posting journal, find the year at the top and ensure that radio button is selected.

I tried all the radio buttons and get the message nothing to print.

Thanks, David

OK, if you get a 'nothing to print' message for your posting journal, but Year End says that there is, then your data is out of synch. The internal posting sequence range doesn't match the data file GLPJRPYR.dat.

When you select the prior year, do you see a sequence range or is in 'blank to blank'? This is important as it will determine the required steps.

If 'blank to blank', then the above data file has a size greater than zero bytes. Something prevented the data file from being cleared when the report was printed and purged. The solution is to rename this file.

If a sequence shows, then the program is expecting information in the above data file that isn't there. The cause is usually that the data file was manually removed rather than printing/purging the report. The usual solution is to post something (to prior year) to generate a new sequence for the journal report, and print and purge all sequences. This likely won't be available to you, as Post to Prior Year will be disabled. Data would need to be repaired.

The first (easier) scenario is likely the problem, as Year End looks at the posting journal data files, not the internal sequence not yet purged.

Possting sequence is 'blank to blank'. The GLPJRPYR.dat show 0 Kb with a date of 6/6/08.

So I should rename the file?

Thanks, David

If the GLPJRPYR file is zero bytes, then the Year End screen would show the status of 'Print Prior Year Journal' as OK. Are you sure you are looking at the same data set?

It doesn't hurt to try renaming the file, as you can always rename it back if you had to.

Adagio Ledger 90A posting journal files all start with the letters GLPJR. This includes Current Year, Prior Year, Next Year, Provisional, Next Year Provisional, and Unposted. All should have a file size of zero (with the exceptions of Next Year regular and Next Year provisional - GLPJRNYR and GLPJRNPV).

Renaming the file did no good. Files do show zero file size.

Thanks, David

There is something different happening than what is being reported here. If the files are gone, then Year End will not display that there is a posting journal that needs to be printed and purged.

Were any of your error batches (from the original post) those that were posted to the prior year?

Non were batches to post to a prior year. They were all batches that had been deleted.

David

Hi David,

When I have a GL9 data set and posting information to the prior year, the file GLPJRPYR has a size greater than zero bytes, and Year End shows that the Prior Year Posting Journal needs to be printed and cleared. If all I do is rename or remove this file, Year End no longer shows the Prior Year posting journal as a requirement - it gets listed as OK on the Year End list.

This means that either you are renaming a file in a different company data directory, or your data has more problems than are being reported from an integrity check.

To investigate further, we'd need a copy of your GL data that is exhibiting this behaviour.

Hi David,

Thank you for the data.
The Prior Year posting journal file was zero bytes. However the Error Prior Year posting journal file GLPSTPYR.WAP has 220 bytes. This means that indeed attempting to pst to prior year (perhaps in the old version) did have an error.

When this file is removed, Year End is now OK to proceed with. The process completed successfully when I tried it.

I deleted the suggested file and year end close works smoothly.

Thanks for all your help and the fast reponse to my questions today.

David