4. CUSTOMIZATION › 4.12 Accounting for Multiple Sites (Multi-Sites)
4.12 Accounting for Multiple Sites (Multi-Sites)
Installations that run accounting at multiple, physically
separated sites have the option of producing their invoices
at a single site. Each remote site can run a standard job to
create an output file for use at the central site. The
central site runs a job to merge the remote site files into
one file. The merged files are used at the central site in
its standard reporting. To accomplish this, appropriate
options must be selected for the remote and the central
sites.
REMOTE SITE INSTRUCTIONS
To use multi-site accounting, each remote site must specify
the files that are to be transmitted to the central site.
The Financial Recap File is always transmitted. The Standard
Credit File may also be transmitted.
Each remote site must also code a TAPEFMT DD statement on the
Remote Site Specifications panel (MWF;4;2;3;2;4;1). This DD
statement defines the SAS data set to which the specified
files are copied. Refer to Section 4.12.1 for more
information on coding the remote site specification
parameters.
The ACTMSULD job is generated by the Accounting Options
generation process, ACTXOPTM, whenever remote site
specifications are entered or changed. At the end of each
accounting period, each remote site submits
sharedprefix.MICS.CNTL(ACTMSULD) to copy the specified files
to the data set defined by the TAPEFMT DD. Refer to the
online help for the Remote Site Transmit Files Creation panel
(MWF;4;2;2;4;1) for more information on submitting ACTMSULD.
It is each remote site's responsibility to transmit the data
set to the central site. The output data set created by the
ACTMSULD job is in SAS tape format. This type of data set
gives you maximum flexibility in your transmission method.
The data set can be written to either tape or disk. The
output data set defined in the TAPEFMT DD statement can be
either a GDG (Generation Data Group), cataloged by you, or it
can be a permanently cataloged data set. If you choose to
use a permanent data set, you must make provisions to clear
out the data set prior to the submission of the ACTMSULD job.
NOTE: Only charge, budget, and credit records are used at
the central site; all discounts, surcharges, and zero
balance adjustments are made on the basis of the
parameters specified by the central site.
In addition, invoices will be created based on the
central site's invoice level specification and the
contents of its Cost Center Attributes file. This may
require some additional coordination between the
remote and central sites to ensure synchronization
between the remote data and the central site
parameters.
CENTRAL SITE INSTRUCTIONS
The central site must code an input data set name for each
remote site that creates accounting information by running
the ACTMSULD job (see REMOTE SITE INSTRUCTIONS above) on an
input panel. Each panel statement defines a data set
containing the files transmitted from a remote site. These
specifications are made in the Central Site Specifications
panel (MWF;4;2;3;2;4;2). Refer to Section 4.12.2 for more
information on coding the central site specification
parameters.
The ACTMGTAB job is generated by the Accounting Options
generation process, ACTXOPTM, whenever central site
specifications are entered or changed. At the end of each
accounting period, after all of the remote site data sets
have been received at the central site, the central site must
submit sharedprefix.MICS.CNTL(ACTMGTAB), which copies the
remote site files to the Installation Accounting application
database (sharedprefix.MICS.TABLES) to create consolidated
files. Refer to the online help for the Central Site Merger
of Remote Site Files panel (MWF;4;2;2;4;2) for more
information on submitting ACTMGTAB. The central site can
then submit the Multi-Site Consolidated Invoice job,
INVOICEM, in sharedprefix.MICS.CNTL. Refer to the online
help for the Central Site Consolidated Invoice Report panel
(MWF;4;2;2;4;3) for information on submitting this report.
The following sections describe how to specify your
multi-site specifications:
1 - Defining Remote Site Specifications
2 - Defining Central Site Specifications