Summary
In MPBM version 2.0.0.0 (and upwards) we've added functionality to allow for a switch between different SCOA Versions while retaining the budgets on the accounts. In short, our principle is:
Keep all GL Accounts intact, but update the Master_Sub_Account name, the segments and the description based on this description according to the new SCOA version.
To achieve this we've created the following tables:
- _as_MPMB_AccountsallVersions
- This table contains the information per account per version. This means that a single (sage) accountlink has multiple lines inside this table. (One line for each SCOA version). These lines are separated with the column called 'SCOAVersion'
- _as_MPMB_AccountExtensionAllVersions
- This table contains the information per account per version. This means that a single (MPBM) account (ID) has multiple lines inside this table. (One line for each SCOA version). These lines are separated with the column called 'SCOAVersion'
- _as_MPMB_SegmentModelAllVersions
- This table contains the information per segment per version. This means that a single (MPBM) segment(ID) has multiple lines inside this table. (One line for each SCOA version). These lines are separated with the column called 'SCOAVersion'
- Keep in mind that the segments are different per SCOA version, meaning there could be new segments in SCOA version 6.2, which are not there in 6.1. (This is based on the mapping done by the Consultant/Municipality)
Since the reference between the 'Allversion' tables does not change, when switching from SCOA version based on
- _as_MPMB_AccountsAllVersions and Accounts
- The column AccountLink and SCOAVersion is the unique link between the two tables
- _as_MPMB_AccountExtensionAllVersions and _as_MPMB_AccountExtension
- The column ID is the unique link between the two tables (called accountExtensionID in the _as_MPMB_AccountExtensionAllVersions table) in combination with the SCOAVersion column
- _as_MPMB_SegmentModelAllversion and _as_MPMB_SegmentModel
- The column Code and SCOA version is the unique link between the two tables.
Entity Relationship Diagram
