The yearly split and aging of the Ledger File is accomplished in each database unit at the same time that the yearly CA MICS product files are split. However, if the Special Accounting Dates feature has been activated, you must run the YEARACT job to split the Ledger Files. Other than use of the YEARLY or YEARACT jobs, there are no major steps to follow at year end. The items that follow are for your information: o The Year-to-Date Financial Recap File is aged during the second accounting period when the CLOSETBL job is submitted from the sharedprefix.MICS.CNTL library. o The Budget File (ACTBGT00) records are transferred to the ACTBGT01 file based on the Budget Effective Date variable (BGTDATE) value. When the date is reached, the records are transferred when the CLOSETBL job is submitted from the sharedprefix.MICS.CNTL library. o You can use IS Revenue Projection and Rate Analysis to download the current year's data to the workstation and project next year's revenue and budgets. OBJECTIVES The accounting administrator's objectives for yearly processing are to perform the following: o Confirm that the new budgets are entered into the Budget File (ACTBGT00) with a BGTDATE value that allows the CLOSETBL job to transfer them to the ACTBGT01. o When the second accounting period is reached, ensure that the year-to-date charges for the new fiscal year are on the reports that show year-to-date charges. o If you change rates at year end, make sure the new rates are placed in effect at year end. Figure 5-3 is a diagram of the yearly update flow.
CA MICS UNIT DATABASES sharedprefix.MICS.TABLES +----------------+ +----------------+ | LEDGER FILE | | Month Financial| | +----------------+ | Recap File | | | LEDGER FILE | | | | | +----------------+ |----------------+ | | | | LEDGER FILE | | Year-to-Date | | | | | | | Financial Recap|-+ | | | Batch Charges | | File | | | | TSO Charges | | | +----| | CICS Charges | | | | | IMS Charges | | | +----| VM Charges | +----------------+ | User Charges | | +----------------+ | | | +----------------+ | | YEARLY or |----------------+---------+ | YEARACT job | | | | | +----------------+ +-----------------+ | | Close out | Yearly | Year-to-Date sharedprefix.MICS.TABLES | Installation |------------Financial Recap | Accounting | File | | +-----------------+ | | -------------------------------------- | | | IS Revenue Projection Enter Establish and Rate Analysis New Budgets Rates
Figure 5-3. Yearly Accounting System Flow
YEARLY PROCESSING CHECKLIST
Follow this checklist to ensure that standard yearly
processing was successful.
__ 1. Ensure that the yearly update completed successfully
for all databases in which CA MICS Accounting and
Chargeback is installed. This is normally
accomplished by the YEARLY job that is submitted by
the CA MICS System Administrator. However, if you
activated the Special Accounting Dates feature:
o Submit prefix.MICS.CNTL(YEARACT) by using Option
5;1 from the Installation Accounting Primary
Options Menu. Run the job after the special
accounting period closes. This job ages the
Ledger Files when you are using a special
accounting period.
It is not necessary for the CA MICS YEARLY job to run
before year-end accounting processing can proceed.
+---------------------------------------------------+
| Reference(s): Section 4.3.3 in the Planning, |
| Installation, Operation, and Maintenance Guide |
+---------------------------------------------------+
__ 2. If this is the final reporting period for the year,
you must update the Budget File (ACTBGT) prior to the
end of the next accounting period. Select Option 1;3
from the Installation Accounting Primary Options
menu.
+---------------------------------------------------+
| Reference(s): Section 4.14 |
+---------------------------------------------------+
__ 3. If this is the final reporting period for the year,
you may want to use IS Revenue Projection and Rate
Analysis to project your revenue for the next
financial year. Extract the data for the workstation
by selecting Option 4;5;1;2 from the Installation
Accounting Primary Options Menu.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |