

3. IMPLEMENTATION › 3.8 Implementing Client/Server Accounting
3.8 Implementing Client/Server Accounting
The following is a general checklist for implementing the
accounting strategy recommended in Section 2.8 of the CA MICS
Accounting and Chargeback Concepts and Overview Guide.
___ 1. Identify the service tiers and the rate for each
tier.
Determine if there will be one or more than one basic
rate for connected workstations. There should be
distinct differences between groups of users if more
than one basic rate is used. Next, identify the
premium service tiers and their associated rates.
The cost basis for each rate includes the hardware
software, support personnel and overhead of providing
service.
___ 2. Identify the data sources for charges.
If possible, you should use existing data sources to
create the charges for LAN services. This eliminates
manual data entry and ensures that charges are
current each month. With CA MICS Accounting and
Chargeback, you can define external file sources that
are used for charging.
The following are some potential sources of data
files that might be used to create the charge
records:
o The user-registry files for the LAN or electronic
mail system.
o Databases created by discovery products.
Discovery products are software packages that
create a census of LAN users, their hardware and
software.
o Inventory databases used for financial or help
desk applications that include users and
equipment.
The data source must contain information that can
identify the cost center to be charged and you must
be able transport the data to the system where
CA MICS Accounting Chargeback runs. If there is no
data source to provide the basis for charges, you may
either create the subscription file to be used as the
data source or manually create debit entries (see
Step 5).
___ 3. Define the charging elements to be used.
You must define a charging element for each service
tier to be charged. The charging element definition
must include the following:
Computation Code: A number that you assign to
identify each charging element. User-added
computation codes must be in the 8000 - 9999 range.
Invoice Category: An invoice category of 2400 is
suggested for LAN/Internet charges. Or you may add
your own invoice category.
External File, File Name and Element Name: You must
define the element as coming from an external file
source even if charges will actually be entered as
debits.
If the charges will be entered as debits, enter SDT
for standard or recurring debits in the File Name
field, and enter SDTQNT in the Element Name field.
Otherwise, enter the ID of the external file and the
external file variable that contains the quantity to
be charged.
Refer to Section 4.2.1, Defining Charging Elements,
for additional information on charging elements.
___ 4. Define external file sources.
This must be done if the data identifying the users
and service tiers will be read from a file rather
than entered manually.
You must assign an ID for each external file, specify
the computation codes and rates to be charged, and
generate the JCL that you will run to create the
charges. You can charge for external files at the
complex level and the unit level. Refer to Section
4.4.1, Specifying Complex-Level External File
Characteristics, or Section 4.3.1.2, Specifying
Journal File Characteristics for additional
information.
___ 5. Enter debits for additional charges.
Enter standard or recurring debits for any charges
that cannot be generated from external file sources.
Each entry should specify the cost center to be
charged, the computation code that identifies the
service tier, and the rate. You must enter one debit
for each cost center and service level combination
that is not charged from an external file.
Note that standard debits must be entered each
billing period, while recurring debits remain in
effect until they are deleted.
Copyright © 2014 CA.
All rights reserved.
 
|
|