Release notes new version MPBM; Front end 2.00.00 ; Back end 2.0.0.0 ; Database version 20
********************************************************************************************
*************************************BETA BUILD*******************************************
********************************************************************************************
* Implementation of MSCOA 6.2
- SCOA database is updated with new 6.2 database
- Added the new MSCOA tree in MPBM
This applies on the:
- MSCOA lookup overview
- Inside the SDBIP account creation.
- Account edit overviews.
- Mapping functionality scoa tree.
- Database restructure to cater for multiple account version (Accounts are kept per SCOA version).
- New table created for:
- _as_MPBM_accountExtensionAllversions (Contains the MPBM all versions accounts.)
- _as_MPBM_SegmentModelAllversions (Contains the MPBM all versions Segments.)
- _as_MPBM_accountsAllversions (Contains the Sage all versions accounts.)
- Updated existing tables to contain SCOA versions.
- New table created for:
- Added new feature to map existing accounts to different SCOA versions.
- Based on the provided NT files, a new MSCOA was added to the system (6.2)
- Mapping suggestions are created based on GUIDS between 6.1 and 6.2
- suggestions are split in:
- Certain mapping.
- To be specified in more detail (New lower level posting level)
- Mapping not known (tool will show the highest know segments based on the mapping)
- Mapping can be done per batch, which can be specified by the user.
- Mapping can be done on new mappings, but also on already mapped accounts (overwrite)
- Validation based on 6.1 is applied on the mapping. (segment combinations)
- Added validation checks based on SCOA version and MPBM accounts.
- suggestions are split in:
- Added account mapping report/grid.
Shows the mapped version under the current version MPBM Accounts
*<<<<TO BE FINALIZED>>>>
- Added functionality to switch between SCOA versions.
* Switching from lower to higher requires all accounts to be mapped.
* switching from Higher to lower does not require all accounts to be mapped. (is preferred however)
* All SCOA trees will be updated to selected version.
* All MPBM accounts are switched (if account is mapped) to selected version.
* All Sage accounts are switched (if account is mapped) to selected version.
* All MPBM Segments are switched (if account is mapped) to selected version.
* All Sage Segments are switched (if account is mapped) to selected version.
- Validation scripts are updated to 6.2
* Old version validation (6.1) is used to upgrade database to version 20. And will block upgrade if any errors are thrown.
* Moving onwards, validation script (6.2) must be used to validate database.
- MSCOA version switching is blocked if there are errors in the 6.2 validation
- Validation onwards is done on the correct SCOA database. (this is done automatically in the script)
- Updated the Account type scripts and tables.
* New 6.2 has an additional account type : "Surplus / Deficit [Expenditure]"
* Logic is rewritten for 6.2
* Account types are recalculated based on Item segments when switching SCOA version.
- Year end procedure is added for the budgets in the MPBM.
* New budget types are added for the outer years:
* DR2 Outer year 2 Draft The outer year 2 Draft
* OB2 Outer year 2 Original The outer year 2 Original
* AB2 Outer year 2 Adjusted The outer year 2 Adjusted
* FB2 Outer year 2 Final The outer year 2 Final
* DR1 Outer year 1 Draft The outer year 1 Draft
* OB1 Outer year 1 Original The outer year 1 Original
* AB1 Outer year 1 Adjusted The outer year 1 Adjusted
* FB1 Outer year 1 Final The outer year 1 Final
* When running the end procedure:
* Outer year 1 budget are moved into: DR1,OB1,AB1,FB1
* Outer year 2 budget are moved into: DR2,OB2,AB2,FB2
* Current year is untouched.
* Final budgets are set to Draft figures for the new year.
* Backup is created automatically before running this procedure (However ALWAYS make a backup)
- Added Function - MSC mapping.
* Mapping per MSC can be done on the function.
* When selecting the Functions in the MSCOA tree the MSCs are defaulted.
- Budget estimates are forced as limits on the SDBIP.
* The amount filled in the SDBIP goal tab, are used to compare the budgets per year against the estimates.
* The estimates cannot be over crossed unless you un-tick "Allow budgets surplus" inside the General settings.
* differences are displayed in the budget overviews.
- Update on the SDBIP overview
* Number of accounts are displayed
* Active budget type is shown.
- The SCOA tree inside the SDBIPS can be limited between Core and Non core function.
* this is a drop down under General.
- GPS can be forced to be filled in.
- can be set on general.
- If you leave it un-ticked, GPS must still be filled in for SDBIP's with capital segments.
- Updating of MPBM account from the MPBM application.
* <<<<TO BE FINALIZED>>>>
- Breakdown selection box when creating and updating a breakdown is increased in size.
- Improved loading times on all windows (especially on SDBIP load)
- Added password policy, can only be accessed by "superadmin"
- New logo is added to the header.
- New menu structure is applied
- New Settings overview is added.
********************************************************************************************
*************************************BETA BUILD*********************************************
********************************************************************************************