Installation
Please download the beta version from :
Stable release version (Only this version is allowed for clients):
Installation steps can be found in the following page:
Note: Please restore the SCOA database attached in the download link, either manually or via the installation script! This will contain the new 6.2 SCOA tree.
Note: Always make a backup of the MPBM database when upgrading!
Prerequisites
- MPBM database must be on version 1.9XXXX
- The MPBM database must NOT contain any validation errors.
- This release can only be used for internal testing.
- This release must not be installed at clients.
Find below the latest version of the validation script, needed to prepare for the prerequisites:
Release notes
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)
- New budget types are added for the outer years:
- 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.
- 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>>>>
- <<<<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.
Constraints
- _as_MPBM_SegmentModel
- Code and Scoaversion
- NodeGuid, Internalbreakdownnumber and scoaversion
- _as_MPBM_AccountExtension
- Name and Scoaversion
- SegmentModel0ID,SegmentModel1ID,SegmentModel2ID,SegmentModel3ID,SegmentModel4ID,SegmentModel5ID,SegmentModel6ID and SCOAVersion
- _as_MPBM_accountsallversions
- Master_sub_Account and SCOAVersion
- Accountlink and SCOAVersion
- cGLSegment0Code,cGLSegment1Code,cGLSegment2Code,cGLSegment3Code,cGLSegment4Code,cGLSegment5Code,cGLSegment6Code and SCOAVersion
- _as_MPBM_AccountExtensionAllVersions
- Name and SCOAversion
- SegmentModel0Guid,SegmentModel1Guid,SegmentModel2Guid,SegmentModel3Guid,SegmentModel4Guid,SegmentModel5Guid,SegmentModel6Code,SCOAVersion
- SegmentModel0Code,SegmentModel1Code,SegmentModel2Code,SegmentModel3Code,SegmentModel4Code,SegmentModel5Code,SegmentModel6Code,SCOAVersion
- AccountExtensionId and SCOAVersion
- _as_MPBM_SegmentModelallversions
- Code and SCOAVersion
- NodeGuid, InternalBreakdownNumber and SCOAVersion
- _as_MPBM_BudgetLine
- BudgertYearID and AccountExtenstionID
- BudgertYearID and AccountExtenstionID
- _as_MPBM_Budgetyear
- SDBIPGoalsID and BudgetType
- SDBIPGoalsID and BudgetType
_as_MPBM_SDBIPGoals
- SDBIPID and YearID
Version 2.0.0.3 Updates (Released 3 PM - 15/03/2018)
- Revised the deletion of objects within the MPBM
- Update on editting account description in MPBM
- Checkbox to show previous SDBIP years
- Budget year end procedure adds new SDBIPGoals and Budgetyears
- Budget year end procedure sets the old current year on Approved, and final as active
- Budget year end procedure sets all outer years budget types to approved.
Version 2.0.0.4 Updates (Released 5PM - 16/03/2018)
MSCOA tree in settings, in which you can preventions of selection/showing of budgets.
SDBIP version selector is removed. From now on only the current SCOA version can be selected. (Automated)
Fixed on SCOA switch truncation error _etblGLSegments (based on Ulundi database)
Updated the ActiveSCOATree storedprocedure to handle the visible and active columns.
Rewrote code to push in the budgets to Sage.
Budgettracker is updated to Current year Outeryear 1 and 2
Update on editting account description in MPBM (Fixed bug when not clicking on pencil)
Account mapping report overview is updated with more details and layouting is fixed
- Updating the mapping in 6.2 while having 6.2 active, will update the _as_MPBM_AccountExtension and _as_MPBM_AccountExtensionAllVersions (_as_MPBM_AccountExtension will get status 5)
Version 2.0.0.5 Updates (Released 2PM - 19/03/2018)
- On mscoa creation, MSC segments pre-selected by Function will appear on the top of the grid
- Added UDF's to Accounts table to indicate the mapped accounts in Evolution (will be updated at db upgrade, and with sage push)
- Fixed column display error on Account Mapping Report page
- Estimated Costs are mandatory for the current year + the two following years
- Superadmin passwords that are still 'superadmin' will be updated to the password provided by Dumisani. (please contact Asamco or Dumisani for password)
- Fixed error opening new budget type on SDBIP
- Default budget page to the Active budget type, not the latest budget type
- Added Current Scoa Version and Rolling Year to top nav bar
- Menu and logo do not overlap anymore
Version 2.0.0.6 Updates (Released 10PM - 19/03/2018)
- Fixed error when adding budgets
- Fixed problems caused by trying to select the 0th account to map
- Functions can no longer link to multiple MSC segments
- Costing segment is default to "Default" in mscoa creation across all SDBIP
- Account Mapping Report references the SDBIP
- Added loading message to Account Mapping Report, SCOA report, SCOA master-detail report and Old & New report
- Removed segment defaults from KPA
Loading bar on Segment links
Version 2.0.0.7 Updates (Released 6pm- 21/03/2018)
- Hotfix on mapping feature for MSC, which was causing errors.
Version 2.0.0.8 Updates (TBA)
- Fixed issue on account mapping, preventing the display of a segment.
- Updated the Budget year end procedure, old version caused errors in new budgetheaders.
- Added safetly check to prevent having accounts on lower version than the current MSCOA version.
- Switching budget years only allowed to a higher version than the current year
- Fixed issue where no new budget type could be created after switching to new budget year
- Added auditing to the all versions tables (AccountExtension, Accounts and SegmentModels)
- Extra security checks on saving of budget lines
- Prevented timeout of database backup on scoa and year switch
- Updated message during mass approving of accounts because this functionality does not take hours anymore!
Outstanding issues
Revise core / Non core to be done per function instead of global.
- SDBIP Segment defaults now work for Project, Costing and MSC
Constraints on employee number/ (and use that as a unique indentifier)
Prevention of switching of SDBIP years, if we budgets linked.
Budgetlines are blocked when trying to change them (Active flag seems to be ignored)
Amounts can be added on funding segment level. Budget amounts are compared against the fund/grant limits.