|
Process Number: 43 |
Revision Date: 11/9/2001 12:30:52 PM |
| Revision #: 5 |
GL Post Errors
| Office Responsible: | DCS - District - Computing Services |
Process Type: | internal |
| Position Title: | Sr. Programmer Analyst | Author: | JMoody | ||
| Cross Trained Staff: | rdoidge | Manager: | MMooney | Vice Pres.: | RTemple |
| Timeline (Deadlines or Time-Constraints) : |
| as requested |
| What must be done before this process is started: |
| GL Postings receives an error message (see ProcessNo 184). |
| Which processes are waiting for this process: |
| GL Postings rerun to post corrected transactions. |
| Source documents or communication with information needed for this process: |
| GL.POST.ERROR file. |
| What is the end-result of this process, or the hand-off |
| Transactions in GL.POST.ERROR corrected and returned to GL.POSTINGS. |
| What steps must be taken independent of the computer system (Manual Process) |
| Decide whether problem can be resolved locally or if need to call Datatel (see ProcessNo 63). Example of local fix: fiscal services authorizes account, no editing required, just copy. Financial incidents currently in my Notes.doc. Financials as a subset of one incident log? |
| Which steps must be taken on a computer (Electronic Process): |
| To see post errors: LIST GL.POST.ERROR GLPE.GL.NO GLPE.DEBIT GLPE.CREDIT To correct fund#: ED GL.POST.ERROR (each @ID) (GLPE.GL.NO) C /0100/4000/G After errors corrected, COPY FROM GL.POST.ERROR TO GL.POSTINGS ALL LIST GL.POSTINGS @ID ALL CLEAR.FILE GL.POST.ERROR |
| Related Documents to Process (e.g. Datatel documentation, Government code books, etc.) |
| Datatel`s General Ledger Manual. |
| Notes (Cautions, suggestions for improvement, etc.) |
| Be very cautious with GL.POSTINGS - inadvertant changes to it could be very bad. |
|
Process Number: 43 |
Revision Date: 11/9/2001 12:30:52 PM |
| Revision #: 5 |