To see what happened during the posting:

1. In System Administration (00), select System Utilities
2. Execute Program:
OTS946
No switches
No parameters
NOTE: This will generate a report named otlog.Lxx. This program is diagnostic only and does not correct any issues.


The report is reading the data that is stored in the ##OTT file, where ## is the Division number.  Unless the file pair (##OTT and ##OTT.idx) is very large, they should not be deleted so the log will show any reoccurring problems.

The otlog report will show the AP Batch#, the Date Processed,  Business Date, User, Obligation if applicable, the number of entries in the batch and the Status.

The bulk of entries will have a status of Z.  This means that everything posted correctly.  The other statuses indicate where in the process the posting stopped.  If the status is anything other than a Z, posting of the batch did not get as far as posting to the General Ledger.

 

The statuses are:
A= Posting in progress OTSS022A/OTSS027A (posting to OT* files)
B= Posting in progress OTSS022A/OTSS027A (posting to OCC and OCD files)
C= Posting in progress OTSS021C (posting to OTE file)
D= Posting in progress OTSS021D (creating TP files for GL poster)
R= Check register print in progress (manual checks)
P= Posting in progress CSTA22 (gl poster)
1= check writing in progress OCWS030E  (extraction routine for check writing)
2= check writing in progress OCWS0301 (Print checks)
3= check writing in progress OCWS030P (creating TP files for OTS026)
4= check writing/logging in processes have calle AP Poster OTS026
5= check logging in progress OCWS035A
Z= Posting complete

 

Because the ott error may be caused by problems with another file, it is important to use FileMaint to see if there are errors showing on files that may be stopping the posting.
For example, when a status of B was listed, we found an error 6 on the OCB file (file contains 1 or more incomplete records)
When a status of A was listed, we found the same errors on the OTBH and OTI files.
If the status is a P, it would make sense to look at the CS* files, as the system is attempting to post to the GL at that point.
Those files must then be corrected in order to keep the problem from happening again.