|
|
|
CA MICS Accounting and Chargeback daily processing starts
with the daily update for the first CA MICS product in the
unit for which accounting has been activated. It ends with
the DAY199 step after the month-to-date ledger, audit, and
journal run status files have been written. The processing
spans several product update steps.
Although you do not usually run external journal file update
jobs, much of this section also applies to them because they
are processed like standard journal files except that the
data source is read in by the external file processing
routine instead of a CA MICS product format routine.
DATA FLOW
The generated accounting algorithm selects specific data
elements and their associated rates for accounting. The
algorithm is generated on a CA MICS product file-by-file
basis as a part of the installation process. When the
algorithm is invoked, it creates an accounting journal file.
To avoid passing the input data twice, the journal file is
created concurrently with the CA MICS product file. The major
steps in the data flow are as follows:
1. The raw data source (for example, SMF or the monitor
log file) is read by the product format routine
(DYcccFMT).
2. The format routine performs date range checking on an
input record-by-record basis utilizing the time stamp
information retained in the unit's Checkpoint data set.
This checking ensures that data that was previously
input cannot inadvertently update the database again.
3. Data element range checking is performed on specific
data elements where the maximum and/or minimum
allowable values are known to ensure their validity.
Invalid values are changed to missing values.
4. The generated accounting algorithm (#ACTXfff) is
activated by a file-specific exit just prior to the
output of the CA MICS product. The algorithm outputs a
journal file observation for each CA MICS product file
observation that meets the algorithm qualification
criteria specified in the Rate Table. No observation
is output for work units when all quantities charged
are less than or equal to zero or when all rates are
missing.
5. When the last CA MICS product update step for the unit
has completed, the CA MICS Accounting and Chargeback
daily update step (DAY199) is initiated. This step
completes the daily accounting processing as follows:
o The contents of each journal file is written to the
month-to-date audit file (DAY1). A second copy of
this file (DAY2) is made to allow the to-date file to
be restored in the event of a failure during the
DAY199 step processing.
Refer to Sections 7.4.1 through 7.4.3 for more
information on the DAY1 and DAY2 audit files. Refer
to Section 5.4, Producing Audit Reports, for
instructions on printing the unit level audit report.
o The journal files are combined and summarized to a
single ledger file in the DAYS timespan of the unit.
The ledger file retains cost center information but
loses the identification of the individual unit of
work (job, session, etc.).
o The DAYS timespan ledger file is further summarized
into a month-to-date file in the MONTHS timespan.
o The Journal Run Status Log File is updated.
o Data is automatically extracted for Daily IS Revenue
Analysis on the workstation, if you put it in the
production reporting jobstream associated with the
DAILY job. Refer to the MICF Reference Guide,
Section 5.1.6, for instructions.
OBJECTIVE
The accounting administrator's objective for daily processing
is to ensure the data is valid and complete. This consists
of:
o Confirming the accounting daily update process completed
normally.
o Reviewing the Journal Run Status Log (MWF;4;2;4;5;1;1) to
ensure that all expected journal files were created and
that the charges for each are within reason.
o Reviewing the Daily Charges Summary Report produced from
the Accounting Administration Process Control menu,
(MWF;4;2;4;5;1;3), or from JCL prefix.MICS.CNTL(BGTCNTL)
member for the target trial balance amounts established by
your organization.
o Checking that no unusual amounts of data were deleted for
content or format reasons, such as short records, out of
date range, or invalid data.
o Using Daily IS Revenue Analysis on the workstation to spot
daily charges that are out of line with the normal trend.
(You can use the Daily Revenue Analysis option on the
Process Control Menu (MWF;4;2;4;5;1;2) to extract the data
or you can put it in the production reporting jobstream
associated with the DAILY job so the data is automatically
extracted.)
Rapidly identifying problems with the input data reduces the
amount of time spent in reprocessing and adjustments.
HOW TO IDENTIFY PROBLEMS
Use the Journal Run Status Logs to identify the journal files
created by the daily run and review the total billable,
non-billable, and unidentified charges in each one. For more
detailed information, select each journal file created and
review the charges by bill date, SYSID, APU, and computation
code. A quick way to spot charging element problems is to
use the SHOW command to display all records with 0 charges:
SHOW 8 $0.0000
Use the Daily Charges Summary Report to review the charges by
customer (COSTCTR1) and invoice category.
Use Daily IS Revenue Analysis on the workstation to review
the graphs of the last 35 day's charges. This can help you
spot variations from normal processing patterns.
The CA MICS administrator should resolve problems with data
volume or content.
Figure 5-1 is a diagram of the daily update flow.
+------------------+ +------------------+ +------------------+ | Daily CA MICS | | Daily CA MICS | | Daily CA MICS | | Product | | Product | | Product | | Update | | Update | | Update | | (DAYnnn) | | (DAYnnn) | | (DAYnnn) | +------------------+ +------------------+ +------------------+ | Generated | | Generated | | Generated | | Accounting | | Accounting | | Accounting | | Algorithm | | Algorithm | | Algorithm | +--------+---------+ +--------+---------+ +---------+--------+ | | | | | | +--------+---------+ +--------+---------+ +---------+--------+ | ACT Journal File | | ACT Journal File | | ACT Journal File | | (00 Work cycle) | | (00 Work cycle | | (00 Work cycle | +--------+---------+ +--------+---------+ +---------+--------+ | | | +------------------------------------------+---------------------------------------------+ | +-----------------+ | | | Daily | | Installation | | Accounting | | (DAY199) | +-----------------+ | | +----------------------+----------------------+---------------------+ | | | | | | | | Accounting Journal Month-to-Date Tape Day Ledger File Month-to-Date Journal Files Audit Files Ledger File Run Status | | | Log | | | Audit Report <--or--> Audit Report | Daily Charges Summary Report
Figure 5-1. Daily Accounting System Flow
DAILY PROCESSING CHECKLIST
Follow this checklist to ensure that standard daily
processing was successful.
__ 1. Ensure that the daily update ended normally. If the
DAILY job abends, refer to Section 5.5, Recovering
From Processing Problems, for instructions on
restoring the database.
+---------------------------------------------------+
| Reference(s): Section 4.2.5 in the CA MICS |
| Planning, Installation, Operation and Maintenance |
| Guide |
+---------------------------------------------------+
__ 2. Review the Journal Run Status Log and the Daily
Charges Summary Report to verify the results of the
daily processing. You may also want to use Daily IS
Revenue Analysis to verify that the journal entries
for the previous day are consistent with the normal
processing volume.
Review the Journal Run Status Log, Option 5;1;1 on
the Enterprise IS Financial Reporting Menu.
The Daily Charges Summary Report can be produced by
selecting Option 5;1;3 on the Enterprise IS Financial
Reporting Menu or by entering the following TSO
command:
SUB 'prefix.MICS.CNTL(BGTCNTL)'
Data is automatically extracted for Daily IS Revenue
Analysis on the workstation, if you put it in the
production reporting jobstream associated with the
DAILY job. You can also extract the data by
selecting Option 5;1;2 on the Enterprise IS Financial
Reporting Menu.
+---------------------------------------------------+
| Reference(s): Sections 5.1 and 6.5.1.3 |
| MICF Reference Guide, Section 5.1.6 |
+---------------------------------------------------+
__ 3. You do not have to run the update job for external
journal files on a daily basis. However, when you run
it, review the Journal Run Status Log and the Daily
Charges Summary Report, as described in Step 2, to
verify the processing results.
__ 4. At any time during the month you may need to review
the entries within the Application Database files
(for example, Debits and Credits). You can create
the reports in Sections 6.5.1.5.1 through 6.5.1.5.5
by selecting Option 5;1;5 from the Enterprise IS
Financial Reporting Menu or by entering the following
TSO command:
SUB 'sharedprefix.MICS.CNTL(PRINTTBL)'
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |