HIGHLIGTS OF THE 9705 HFS RELEASE
EN
changes for this release include:
Disencumbrance Hierarchy-ENGL-APPLYPAY common code can now
force the software to ignore payment accounts and only consider originating
encumbered accounts.
Amounts to Post-OHEN-AMOUNTS common code now defines whether
Duty, Discounts, Charges and/or Taxes are included when payments are posted to
relieve encumbrances.
Encumbrance Debug Report-ENREDR debug report was added to
display all EN information about a particular reference and its effect in GL. It
includes and explains all GL option flags, Common Codes, internal statuses and
accumulators.
Closure Date Utility Verbosity-ENUTAD utility to adjust EN
closure dates was changed to eliminate unnecessary lines from its report and
only show records which were corrected.
Year End Account Number Re-mapping-ENUTRE year end rollover
utility was enhanced to allow account numbers on rolled amounts to be changed
via a conversion file when manually rolling encumbrances from one year to the
next.
EN
Method Converter Dates-The stand-alone utility, for Converting to EN, Method
"B" was changed to retain the pre-existing disencumbrance dates.
GL changes for this
release include:
Control-Y Handling in GL Inquiry - The handling of Control-Y
in GL inquiries was modified to be more consistent and intuitive.
Cash Basis in GL Inquiry - Under certain conditions, the
Budget-to-Actual inquiry would display accrual basis information when Cash basis
information was desired. Appropriate accumulators are now reported.
Expense Totals in GL Inquiry - Unnecessary expense totals
have been removed from the Budget-to-Actual inquiry when selecting by a Key Part
and a single Object Code.
Journal Entry Update Screen - Text records have been
relocated in the batch. Since they pertain to a particular JE ID#, they now
immediately follow the transactions having the same JE ID.
Journal Entry Batch Proof - When a Prep-ID is entered, it now
becomes the default and is automatically carried forward until another Prep-ID
is entered. Headers have been improved by now displaying the ledger pair from
the batch records instead of the ledger pair of the user, and multi ledger
batches now properly handle 'NY' offsetting to identical funds in different
ledgers.
Journal Entry Distribution - Account numbers having an object
code type not allowed by the key have been changed to result in a block instead
of a warning.
Recurrent Journal Entries - RJE's have been enhanced to allow
Default Mapping to fill in JL side account numbers automatically when so
configured.
General Ledger Direct-Update Screen - Correct usage of GL-JL
delimiters (on GLUPGN screen 4) has been clarified by making them required for
GL side ledgers and disallowed for JL side ledgers.
Transaction Direct-Update Screen - Browsing to JL side
account numbers in GLUPTR has been improved.
Budget Direct-Update Screen - A compiler bug on DG/UX
machines was circumvented by changing our code. Now default budget versions can
be specified in the JCL for GLBUUP.
Copy Chart-Of-Accounts Utility - A new utility (GLUTSUCP) has
been added to select and copy Chart Of-Account entries from ledger-to-ledger or
machine-to-machine.
Recompute Utility - When the GL side and JL side ledgers used
identical keys and objects, a certain set of conditions would cause phantom
budgets to appear on group-level roll-up accounts. This bug was found and
corrected.
Purge Budget Utilities - The GLUTDIPB utility now handles
selection criteria for keys, objects, parts, and groups. Also, an internal
bounds violation was eliminated. In GLUTDIPU the "Only purge if budgets and
actuals are both zero: RETURN=N:" has been reworded for clarity.
Transaction Collapsing Utilities - In GLUTSUCL, the maximum
number of JL side account numbers associated with each GL side account numbers
in each fiscal period was increased from 1000 to 1500.
Posting Preferences and Mapping Update Utilities The recovery
files for GLUTSPPP and GLUTSPPM were made smaller and moved from the DATA group
to the PERM group to avoid confusion with work-in-progress files (JE batches,
etc.).
Budget Verification Utilities - The option to run validation
on a ledger-by-ledger basis was corrected. The selected ledgers are now shown on
the report. Also, the record-skipping feature was corrected.
Check Number Verification Utility - Inability to locate
detail entries was being mistaken for a job number mismatch, causing overflow of
an internal table. This was corrected.
IFAS IV to VI Batch File Conversion Utility - The GLUTRIBR
utility was improved to convert Batch Ids and handle Intra-Offset fields.
Interface File Conversion Utility - The GLUTRIIJ utility was
enhanced to allow the 222-byte format to contain minus signs, decimal points,
and commas. An internal file was increased to 10000 records and extraneous NUL
characters were stripped from incoming data. Another bug was corrected which
caused TMINFILE errors in the prior release.
Budget Batch Update Screen - The allowable size of the system
generated Budget-ID was increased from 12 to 16 characters.
Budget Batch Proof Headers - The budget batch proof and batch
distribution reports were enhanced to follow record-by-record changes in object
group, displaying the new group names in the header.
Bounds Violation when Editing Report Definition - If the
invalid value of zero was entered for a Data Item Number on the Item Range
Selection screen, a bounds violation occurred. This problem was eliminated.
13 and 14 Fiscal Periods - Internal routines have been
updated to better handle 12, 13, and 14 fiscal periods in a fiscal year.
Questions and Help - All EN, EQ, ES, GL, GQ, GS, RX, and TF
questions now have online help, and vestigial questions have been removed. Many
updates have been placed into the Acrobat Manuals. AP changes for this release
include:
Added to the masks that extract from the approval area is a
report for 'unapproved invoices' (APOHAPUN), and ability sort by Batch ID.
Sorting by Batch ID results in the batch proofs giving more meaningful system
and user totals.
When payments are posted against encumbrances, the dollar
amounts used for the payment can now be controlled via common code OHEN AMOUNTS.
This common code can specify if discounts, charges, taxes, and/or duty should be
included in the disencumbrance amount.
When posting check reversals, you now have the option of
creating an Immediate Pay or Open Hold batch for repayment of the check.
Better warning messages are reported on the check register if
you are entering a void check that already exists. PE changes for this release
include: Security has been added to the product update screens (PEUPPR) to allow
clients control over which users can view and modify product information.
Security can be based on range of product codes, or on a separate value placed
into the commodity code field. The Buyer ID on the product definition screen (PEUPPR)
is now validated. All values placed in this field must first be defined as a
PEID through PEUPPE. An option also exists to require that the PEID be flagged
as a buyer using the select codes. Browsing zip code definitions in PEUPZP has
been enhanced to browse in zip code order and to allow searching for an existing
zip code. Nine digit zip codes that were entered as "123456789" were
displaying and printing just as entered. The name and address lookup routine was
changed to format these as "12345-6789". PO changes for this release
include:
The overhaul of the PO Multi-line screen (POUPMP) has been
completed and is included with this update. This screen has changed slightly to
accommodate additional fields and to make it more readable. Each of the
functions of the multi-line screen have been individually tested and corrected.
General Ledger background parts can now be printed on the PO
using item numbers 174 through 181 for key parts and 182 through 189 for object
groups.
A new mask, POUPRB, has been added that will create an Open
Hold batch to pay for items just received.
A couple minor bugs have been fixed that involved fully
receiving Purchase Orders that contain Stores Inventory products.
A new utility has been added (POUTRC) to allow recalculating
the remaining blanket amounts. SI changes for this release include:
Reprinting Purchase Orders previously caused the On Order
Quantity in Stores (SIUPIN) to be incorrectly increased. With this correction,
running the SI recompute has become an exception instead of the rule.
A previous HFS release added user-defined sorting, totaling,
and page breaks to the transaction file listing (SIREFLTR). This release adds
the ability to report totals only, which can be very useful in reconciling SI
with GL.
Three new standard reports have been added (SIRESR PA, WA,
and TA). These new reports focus on the activity of products, warehouses, and
transactions over user specified periods of time. AR/SY changes for this release
include:
Enhancements have been made to support the PC base product,
Insight. This update must be loaded in order to use Insight. Corrections made to
resolve Insight users occasionally getting hung and inability of the return key
to work properly. This would occur after returning from an SY945
"lookup" screen and exiting. Change made for Insight to function on
reverse byte-ordered machines, e.g. NCR and DG-Intel. UNIX Only
The process spoolit, used in Triad's 4GL Base Ad Hoc report
writer, had a correction to the process which compiles the program spoolit. UNIX
Only
Changes made to allow TRANSPORT to compile on the DG-Intel
machines - specifically the 5900 DG-UX 4.11. UNIX Only
Modifications to mpespooler to print the correct name on the
output banner pages. UNIX Only.
Enhancement to USEFILEs to not require re-creation of the
USEFILE due to a software update which adds or deletes questions in the job. The
process NU010 will automatically prompt the user for the new questions, and add
the response to the USEFILE. Old questions will be removed from USEFILE. USEFILE
will also contain a version number.
The process
which loads ROOTROLL files during software updates will verify the integration
of the file before loading into the ROOTDB.
Improvement to
the NUUPUS (User Information) Job Running and Database security screens to not
allow users to grant security access greater than themselves (sent out on the
HFS 9702), reported several problems on UNIX sites. These problems have been
resolved, as well as some new exceptions found and corrected.
Changes to checking database security to test for multiple AR
Divisions correctly. This will effect AR Inquiry and AR Reports.
The Term file listing was enhanced to include Default Numeric
information and reformatted. The file listing of AR General Information had some
minor corrections. The description on the User Defined Summary Report
definitions has been expanded to 30 characters.
·
Bank Date, Bank
ID, and Bank Slip were added to standard sorting menu for the AR Standard
Reports.
·
AP Batch
conversion to AR Batch has been enhanced to include the conversion of the AP
text information into the AR Batch.
Various improvements and corrections have been made to the AR
screens and field level help throughout the subsystem.
Corrections and changes in AR Direct Transaction Update (ARUPTR)
to support pick lists for Pay Type, Bank ID, etc. Improvements have been made in
the error checking of AR type transactions to not allow CR type data elements,
i.e., Bank ID, Bank Slip, Bank Date, Pay Type, and Pay Reference.
Change to enhance support of Deferred Charges. The AR Undo
process will "remember" the Deferred Charge Plan number to the saved
batch file. If the saved batch file is posted to the AR database again, the
Deferred Charge transactions will be applied as adjustments to the original
plan. Changes to the calculation made in the AR Re-Compute of Deferred Charges
to be the same as total in Standard Reports. PY changes for this release
include:
New option to include direct contributions under 'Other
Payments', as opposed to 'Contributions', on the payroll earnings register (PYPADP,
program PY100).
Previously direct contributions (those which increase NET
pay) have been reported under the contribution section. This new option now
moves it to the Payments area, to be reported with other types of earnings (e.g.
Regular Hourly, Salary, OT, etc.).
New 'Warrant Check Off' register (PYPADP, program PY275) can
be produced during the distribution of payroll. The purpose of this report is to
enable the collection of employee signatures when they pick up their pay check
and/or EFT stub, and to provide the entity with an audit trail/receipt for this
distribution. Information on the report includes: Employee ID, Employee Name,
Check Number, Check Amount (optionally), and Pay Date. Since every site sorts
checks differently, a customization to this process will be needed to meet your
sites' specific need. A sample of the report is included below. Some format
changes have been made for inclusion on this summary. Location Payee ID. Payee
Name Date Check No. Check Amount Signature
When the Contribution / Deduction Registers are printed, the
program will enforce a page break after each specific contribution or deduction
has been printed. A new option has been added that will disable page ejects
after each deduction/contribution is printed helping to save on paper usage.
Created a new payroll Ad-Hoc report writer that will also
create magnetic media output. This process was developed by BI-TECH in an effort
to provide reporting capabilities that do not currently exist in the standard PY
Ad Hoc report writer. In addition to hard copy reports, this process can create
magnetic files as output. This will aid in the development of magnetic reporting
that health care providers, and pension administrators, are now requiring.