It shows:"Posting journal-must print and clear first!" So I went to post - print posting journal, it shows posting sequence from 4 to 77, but when I click print, it shows: there is nothing to print. click oK, it prints posting errors batch 4,which I have corrected in batch 5 and posted in sequence 5.
What's the problem? Thanks a lot.

In the Company Profile, disable the option "Allow posting journal purge". Make sure that you have all the printouts you want of your posting journals. The year end process will purge the posting journals.

BTW - if you are doing the year end on the general ledger that has an account of the wrong type, mentioned in a previous post, you should get that fixed.

David:

It's often easier (cheaper) to fix your account type problem if done prior to running year end.

For everyone reading this thread, this problem occurs when the posting journal data file gets out of synch with the expected posting sequence range that is stored in the company profile. In David's case, a posting sequence range of 4 to 77 was expected (the first and last unpurged sequence in the company profile), but when the Print button was clicked, there were no posting sequences in the posting journal data file from 4 to 77.

The usual reason behind this exact scenario is that the posting journal data file was manually deleted, rather than using the print process to purge it. Or the posting journal data file was not backed up, and the company data was restored from that incomplete backup.

The other possible behaviour is that immediately attempting to print the posting journal gives a message that there is nothing to print, but Year End indicates that the posting journal file is not purged. The same reason of being out of synch has occurred, but in the opposite way. The company profile doesn't expect there to be any posting sequences unpurged, but the posting journal data file exists with a size greater than zero bytes.

The usual reason behind this scenario is that the posting journal was printed and purged, but the network held onto the file and didn't let it get cleared correctly.

Andrew's solution will bypass both of these out of synch scenarios, but of course it can only be done at year end.

Thank you all for your help. I really appreciate your time and I have learned a lot from you.