Goodafternoon,

We are currently performing our year-end. In A/P, attempting to Year-end, I receive the following:

Period End Clearing Journal - Should print & clear first
with the Proceed button grayed out.

When I attempt to print and clear, a msgbox pops up saying "No clearing posting journal to print".

We are sufficiently quagmired right now. Any insights?

GL 8.0A (yeah, I know)
AP 8.1A

Thanks for your help.

Make sure you have the latest service pack installed for AP = 080821. YOu can find out which service pack in installed by looking at Help/About.

Backup your data.

Run data integrity check. If any errors are found run the Rebuild function. Repeat until no errors are found.

Still can't run the Year End then;

Run a period end. If you have auto print posting journals turned on then do not print and clear the report.

Now go to the Print Clearing Posting Journal/ Print this report for the entire range of posting sequence numbers indicated and clear it when prompted.

You should be able to run the Year End now.

It is possible that your APPOSTP.dat data file (that contains the period end clearing posting journal information) is out of synch with your company profile - which contains the range of posting sequences that should exist. This could have happened because you chose to purge the report but APPOSTP did not purge to zero bytes, or because the file was manually removed or lost instead of printing the report to purge.

If the file has non-zero size and you are sure that the report has been printed, rename the extension of this file to something like 'old' to make it invisible to the program, and try again. The symptoms of this error is that as soon as you try to print the report, you immediately get a 'nothing to print' message.

If you get the opportunity of seeing the Period End clearing posting journal screen and a range of sequences, but clicking Print gives the 'nothing to print' message, then the reverse is true and the data file was lost. This one is harder to fix - you have to run period again and 'hope' that more transactions are cleared and another posting sequence is generated. This might also require a database repair.

Renaming the file solved the problem. Thanks for your help!