SoD_V426a SP11PC_Final.doc
Statement of Delivery
SunSystems 4.2.6a SP11
& Option Pack
PC Platforms
Contents
Contents 2
1 Objectives for this release 3
2 Summary of key features included in this release 3
2.1 Platform 3
2.2 Functionality Enhancements 3
2.2.1 Business Rules Enhancements 3
2.2.2 Ledger Accounting Enhancements 3
2.2.3 Sun Business Enhancements 3
2.2.4 New Functionality For Sun Business 3
3 Release Information 3
1 Objectives for this release
The objectives of this software release are:
· To provide SunSystems 4.2.6a on the most widely used platform and database releases.
· Delivery of a number of maintenance projects, selected to address specific customer requests.
2 Summary of key features included in this release
2.1 Platform
This release supports the most widely used service packs of Windows 2003, SQL 2000 and NetWare 6.5 as well as continued support for the latest version of Oracle 9i. This continues to endorse Systems Union’s commitment to providing an open choice for platform and database selection.
2.2 Functionality Enhancements
2.2.1 Business Rules Enhancements
Transfer Manager function checks security permissions on import of records
There is a new action type screen for the Transfer Manager option within Operator Permissions to provide security for all Import functions processed through Transfer Manager.
2.2.2 Ledger Accounting Enhancements
New option to Include Archive under Journal Listing
There is a new flag in JL=Journal Listing to Include Archive transactions. This can only be set to Y-Yes if explicit periods are entered in the Accounting Period From/To boxes.
This will also only be activated if the Ledger Archiving box in LD=Ledger Definition is Y-Yes.
Restrict the posting of a held journal prior to a closed period
When attempting to post a journal that has previously been held, the system will now either post the journal if the period(s) are still open or, if the periods are not open, inform the user with an appropriate message, 'Accounting period(s) not in open period range, journal will be held'. The journal will then be put back on hold. The user will now have the choice to either re-open the closed period and post the held journal, change the open period range and post the held journal or amend the periods on the individual lines. No further alternatives (post 'anyway' or post to current period) are offered.
Record User ID and Date when users make amendments to Allocation Markers in Account Allocation
Users are now able to record the User ID and the Date when users amend or set the Allocation Marker in Account Allocation. A new ledger table is created as part of the ledger file. When the Allocation Marker is set or amended the details are held in this table. A new overlay screen on the Account Allocation called Overlay Identity displays the User ID and the Update Date of the Allocation
Allow user to change the Posting Period during a GP run
In GP=Generate Payments, users are now able to choose the Posting Period. A new field has been added to the Generate Payments / Debits Run screen, with the default value being the current period.
Revision Payment Preview logic - Due Date to be left blank where it is irrelevant
Due Date will no longer be set for Account Types for which this is inappropriate. On upgrade to version 4.2.6 Service Pack 11 any erroneous data (i.e. where due dates are present and do not need to be) will be corrected with a special one-off program.
Where Payment Terms have been entered on the Chart of Accounts, Due Date will be calculated, whatever the Account Type. Where the Account Type is Debtor, Creditor or Client in the CA=Chart of Account record, and if no Payment Terms have been entered, the transaction date will be copied into the Due Date field. This is the same as SP8, but with an Account Type validation. Where the Account Type is Balance Sheet, Profit & Loss or Memo and the Payment Terms are blank, the Due Date will only be calculated if the CA Payment terms are populated.
V4 Over Expenditure checking
If the Over-expenditure Check flag on the Ledger Definition is set to Yes, as each line is entered, it will be checked against budget(s) by checking against (i) the balance on the relevant budget account in conjunction with (ii) current spend already accumulated in the current journal (value held for the corresponding entry on the new work file) plus the amount of the line being entered.
If this check shows the budget is overspent and the user has override permissions (defined by the override commitment flag on Miscellaneous Permissions), the user will be asked to confirm if the over-expenditure is acceptable and the line accepted or rejected accordingly. If user does not have override permissions, the overspend will be flagged as an error and entry blocked.
2.2.3 Sun Business Enhancements
Clear down Commitment Ledger file when Commitment Transfer returns No Data Found
When all the commitments have been cleared by TT=Commitment Transfer, the Commitment Transfer File is cleared. The system has been changed to ensure that the Commitment Ledger File is also cleared when there the message “No Data Found” is displayed.
Extend the Audit Control functionality to record user details when transactions are created, amended, or deleted within POP or SOP
Audit Reports for transactional data in POP and SOP will be available.
Multiple Return Locations
The user is now able to define the Return Location at the Sales Type level, thereby facilitating returns to various locations.
Returns & Exchanges Sales Import
This project is based on the Returns and Exchanges add-on, which was recently upgraded to SunSystems V4.2.6. This project is intended to expand the Returns and Exchanges functionality, such that users can process returns and exchanges transactions as a batch.
Inventory Transfer – select by Movement Reference
Additional selection criteria have been added to IN-Inventory Transfer
Revise Lot number Validation and Apply Lot Number Validation Functionality to Movement/Purchase/Sales Imports
Lot Number Validation can now be applied to Sales, Purchase and Movement Imports.
Additional Header Labels by Sales/Purchase Type
The use of Additional Header Labels can now be invoked at Sales/Purchase Definition
Extended Receipt Reference and include Audit date on inquiries/reports
The Receipt Reference Field has been extended to 15 bytes throughout the whole of Sun Business
2.2.4 New Functionality For Sun Business
Returns and Exchanges Integrated into core V426a SP11
Tracking Codes Integrated into core V426a SP11
Inventory Revaluation Integrated into core V426a SP11
3 Release Information
Pre-issue Confidence Testing commences / Q2 2005Alpha testing commences / Q2 2005
Beta testing commences / N/A
Controlled release date / 7th September 2005
General implementation date / TBC
All previously released functional areas are regression tested in this release.
SunSystems and Partners Internal Use Only