The Ohio withholding tables have been updated for wages paid on or
after October 1, 2006. The rates will be reduced.
1.2 GENERAL: New STRS Employers Added to Validations
The following STRS districts have been added to the STRS validation file:
BRDDIS has been changed to allow menu driven selections. The user will
now have to choose a 'projection' or 'actual' option. The projection
option will allow the user to run BRDDIS as many times as desired.
BRDDIS projection will not generate a .BATCH file for posting to USAS
in any instance. The actual option will generate a .BATCH file when the
prompt is not blanked out and will no longer ask if the report should
be copied to the PAYROLLCD location. When running the 'actual', the
report output will always be copied for PAYROLLCD purposes.
1.4 CALCPAY: Modify wording of missed deduction message
Modified the wording of the missed deduction message on the error
report. The message now states that the missed deduction amount is
placed in the error adjustment and will be withheld for the next
payroll.
1.5 USPEMS/PERDET: Produce error on report for regular position and no work days
If the position type = "R" (Regular) and there are no work days for the
job, then an error is produced on the report saying "$$ Work days must
be > 0 for a regular position type".
2 Problems Corrected
2.1 BRDDIS: Corrected problem with high numbered deductions not appearing on BRDDIS report
Found a problem with larger districts where it wouldn't process all the
deductions and was missing the high numbered deduction codes. This
caused deductions to be omitted from the reports and batch file and
required districts to run BRDDIS a second time selecting these codes
with the higher numbers.
2.2 CHKPRT: YTD totals incorrect on check stub
The YTD totals on the pay stubs were incorrect for certain types of
deductions. This has been corrected.
2.3 USPSCN/JOBSCN: Validate separation date
Add validation for the separation date. Previously, there was no
validation on the separation date, allowing invalid data in some
instances which caused a problem during USPEMS/USPEMX. This has been
corrected.
3 Technical Enhancements and Changes
3.1 DIRDEP: Allow for a single batch ACH submission file
Updates have been made to allow PAYDIR and PAYDED to produce ACH files containing a single batch. The single batch will contain mixed debit and credit entries. This is to resolve issues that arose after the rewrite of PAYDIR in which banks were unable to process the ACH file which contains two batches, one for debits and one for credits.
DIRDEP/DIRMNT contains a new field labeled "Number of batches". For those districts that are utilizing OLDPAYDIR (placed in OECN_BETA) to produce a single batch ACH file, this field should be set to "S" (single). This will cause PAYDIR to create an ACH file containing a single batch, the same format as OLDPAYDIR produces.
For those districts that have been using the new PAYDIR program without any problems, no updates will need to be made in DIRMNT. The new "number of batches" field will default to "M" (multiple). The DEPRPT option of DIRDEP may be run to verify the setting of the "Number of batches" field.
There will be no visual changes to the PAYDIR and PAYDED programs. The resulting PAYDIR.TXT will also not be affected. The setting of this flag affects ACHTAP.SEQ (PAYDIR) and any HSAACHxxx.SEQ (PAYDED) files.
ITCs that had installed the old version of PAYDIR (known as OLDPAYDIR)
from OECN_BETA should remove this from user access and any MENU files
it may have been added to.
3.2 MASCHG/CHGEMPID: Allow creation of custom parms file
Up to 250 old and new empid values can now be passed to the CHGEMPID
program through the use of a custom parms file.
3.3 STRSCOD.IDX: New STRS Employers Added
The following STRS districts have been added to the STRSCOD.IDX file:
The Ohio withholding tables have been updated for wages paid on or
after October 1, 2006.
3.5 USPDIRDEP.LIB: New flag to allow for single batch
A new field has been added to the USPDIRDEP file to allow PAYDIR to
create an ACH submission file containing a single batch. By default,
this will be set to allow multiple batches. This is consistent with the
current processing of the PAYDIR program where credits are placed into
one batch and debits are placed into another batch so that the ACH
submission file contains two batches.
4 Modifications to Menu Files
5 Documentation
The documentation is maintained by the SSDT and can be found in the
OECN$ROOT:[USPS.V4P2.DIST] distribution directory.
5.1 Documentation Summary
The following are documentation files for the Uniform Staff Payroll System package and a brief description of the contents and intended audience of the document.
Documentation produced for this package was developed with a Digital product called VAX Document. This product enables us to provide two versions of the documentation for various types of printers. The version which has an extension of .LN03 can be printed on a laser printer; while version with the extension of .PS is to be printed on a ScriptPrinter.
| Document File | Revision Date | Description |
|---|---|---|
| USPS_USER_GUIDE | March, 2006 | USPS User Guide |
| USPS_REFERENCE_MANUAL | March, 2006 | USPS Reference Manual |
| USPS_SYSMAN_MANUAL | March, 2006 USPS System Manager Manual |
The users have the ability to print the updates to the documentation manuals since the previous release, without having to print the entire documentation manuals. The updates are contained in a separate file which uses the same naming convention as the normal manual with "_UPDATE" appended. The update files are available in .LN03 and .PS versions. You will find updates to both the user and system manager manuals if changes have taken place.
The update files will include *ONLY* the modified chapters of the documentation manual, a new table of contents, and an index if one exists in the documentation manual. Updated documentation is also included in the normal documentation manuals. Therefore, if you plan to print the newest version of the entire user or system manager manual, it will *NOT* be necessary to print the update file.
It should be noted that even though the purpose of the update files is to allow the users to print only the updates, there may be cases when it would be more practical to print the entire documentation manual, rather than trying to use the update file. For instance, if a new chapter is added at the very beginning of the manual, the numbering for all subsequent chapters will change as well (the size of the update file could be almost as large as the normal documentation manual). SSDT will advise you in the release notes when the changes are so numerous that we recommend that you print the entire documentation manual.
There will only be one _UPDATE file provided each release for every manual. We do not plan to distribute updates for previous releases, as we do for the release notes.
SSDT strongly advises that you print new documentation manuals before you try to utilize the _UPDATE files.
If you print a .PS version of the entire documentation manual, be sure to print the .PS version of the _UPDATE files. The _UPDATE pages will not fit into the manual properly if you try to mix the various documentation formats.
If there are no changes in the documentation manuals, no _UPDATE file
will exist on the release.
6 Package Installation and Logicals
Installing USPS involves first using the OECN_INSTALL procedure to unpack the savesets into the OECN$ROOT:[USPS.V4P2.DIST]. After the distribution directories have been prepared, INSTALL_PACKAGE is used to transfer the package from the distribution directory into the user execution directory. See the VAXMGR_HANDBOOK in OECN$ROOT:[DOCUMENT.DIST] for more information about OECN_INSTALL and INSTALL_PACKAGE.
Prior to executing INSTALL_PACKAGE it is necessary to define several system logicals required by the package. The table below lists the logicals which should be defined prior to executing INSTALL_PACKAGE for USPS:
| Logical | Description |
|---|---|
| OECN$PAY_42 | Shared directory. Contains executables and files shared by all USPS |
| OECN$CDD_PAY_42 | CDD path name (optional, see next section) |
| OECN$MENU$FILES 1 | Location for menu files |
| OECN$HELP 1 | Location of VMS help libraries |
USPS also requires components from the OECN and CSSR packages. These packages should be installed prior to installation of this package. |
The USPS distribution contains optional CDD and DTR definitions that are acceptable for use with DTR, 20/20 and other products that are integrated with DEC CDD/Repository. Data names for COBOL are provided in the record definitions. The CDD definitions are optional and are not necessary to successfully install and utilize the base USPS package. However, the are a few "supported" DTR reports. If you wish to be able to use these reports, you must install the CDD definitions.
The INSTALL_PACKAGE procedure OECN$UTL will load the CDD definitions into the CDD when either the "CDD" or "FULL" option is used to install USPS. INSTALL_PACKAGE is the only supported method for installation of CDD definitions for USPS Version 4.2
The USPS CDD definitions for USPS Version 4.2 will be loaded into the CDD path referenced by the OECN$CDD_PAY_42 logical. This logical must be defined prior to executing INSTALL_PACKAGE and should be defined as a system logical. SSDT recommends that the USPS definitions be placed in a separate CDD directory from other CDD definitions. This increases the efficiency of the CDD, allows the USPS definitions to be treated as a 'database' from 20/20, and simplifies security maintenance. For example:
$ DEFINE/SYSTEM OECN$CDD_PAY_42 CDD$TOP.OECN.USPS42 |
After defining the OECN$CDD_PAY logical, the INSTALL_PACKAGE may be executed. Below is sample run of the CDD installation:
$
$ @OECN$UTL:INSTALL_PACKAGE CDD OECN$ROOT:[USPS.V4P2.DIST]
OECN INSTALL_PACKAGE (V1.1-010) Copyright © 1991, Ohio Dept of Ed, IMS
%OECNINS-I-BEGIN, Begin CDD installation for USPS Version 4.2 on NWOCA0::
at 14-MAR-1994 15:09:36.41
%OECNINS-I-CDD, Loading CDD definitions to CDD$TOP.OECN.USPS42
OECN INSTALL_CDD (V1.0-001) Copyright © 1994, Ohio Dept of Ed, IMS
%OECNINS-I-START, Starting CDD install for USPS Version 4.2
%OECNINS-I-RECORD, Processing record OECN$CDD_PAY.ABSENCE_REC
.
.
.
|
USPS contains a dictionary for use with the UDMS Report Writer product. The dictionary will be installed automatically when OECN$UTL:INSTALL_PACKAGE is executed with either the FULL or UDMS option. If a version of the dictionary has already been installed, INSTALL_PACKAGE will merge the updated version into the local copy. Thus, reports and additional views developed locally will be preserved.
USPS also contains a sharable image which is used by UDMS. The sharable image provides 3GL functions which are used in calculated fields by the UDMS dictionary. To make this image available to UDMS, you must define the following logical during system startup:
$ DEFINE/SYSTEM OECN$USPS_SHR OECN$PAY:USPSSHR.EXE
|
Please implement this release as soon as possible. It is difficult for the SSDT to provide assistance to your problems if you are not utilizing the current version of the software supplied.
Please refer to the documentation files contained on the release tape to obtain a history of the modifications the software has gone through. The release documentation files are named in the format of "RELyymm.DOC" where yymm is the release date.
Should you experience any problems, or have any questions, concerning the OpenVMS/Alpha version of the USPS Version 4.2 software please feel free to contact SSDT for assistance using one of the following options:
Visit the OECN Public Forum at http://forums.oecn.k12.oh.us/forums/oecn/
DAS restricted Forum at http://forums.oecn.k12.oh.us/forums/das/
SSDT Home Page at http://ssdt.oecn.k12.oh.us/
End of Documentation for USPS Version 4.2 Release: 2006.09