Migration of Application from 2013 to 2015, is a 2 setup process using the Migration Utility.
Migration utility takes existing database as ‘source’ and creates a new target database (user can specify the name and server) with the required schema for the target application version (2015.x) and migrates the data into this database from the source (i.e. current) database. Both Steps are Briefly Explained :
PA5G Pre-Migration Report : This creates a temporary table called ‘PA5GMigration’ in the source database. Which is used in step 2. This table stores a list of issues that may occur or Data merging that can affect the application. Later each issue is described in detail. It also allows user to select the data that user wants to import, user can choose to import the Input data and Calculated (Result) data while migrating from 2013 to 2015. If user chooses not to import Calculated Result Data, all the scenarios in the 2015 application will appear not calculated.
Setup 2015.1 Database : In this step the data is migrated from old database to new database. the Utility asks for a destination server and Database name. It uses the the PA5G migration report to migrate the old database to new database.
This procedure creates a temporary table (PA5G Migration) in source database that stores a report. This report contains information for migration of Schema from 2013 to 2015.
2014 / 2015 application has a major change - Time-periods. While migrating, time-periods get automatically created in 2015, from the distinct time-periods used in 2013 Scenarios. So, x number of scenarios 2013 will result in same number of scenarios in 2015 and same / lower number of time-periods (lower number of time-periods in case 2 scenarios in 2013 have the exact same time associated with them).
For example, in this case, 3 scenarios in 2013 resulted in 3 scenarios in 2015 and 2 time-periods.
2013, Scenarios :
Scenario1 - April 2013
Scenario2 - May 2013
Scenario3 - May 2013
2015 Scenarios & Time-periods :
Scenario1 - - - mapped to - - - Timeperiod1 (April 2013)
Scenario2 and Scenario 3 - - - mapped to - - - Timeperiod2 (May 2013)
Scenario data from 2013 application now gets split into model and time period data. In 2013 application, there is support for different Version (in 2013, version were stored as Model Structures) where each version has a ModelStructureId and Separate Data like Costs, GL Accounts, Drivers & other Model Specific data. These features are moved in newer 2015 application as Versions.
The data is divided into 2 types of Data :
Global, like GL Accounts (Entities), Costs, Drivers - Utility creates tables like VersionCosts, VersionDrivers, VersionEntities, VersionEntityCostAllocation (RP to Process Assignment), VersionEntityEntityAllocation (RP to RP Assignment), VersionMetrics). So all Model specific data is stored in 2015 application as version.
Time-period specific data
As mentioned before, Utility allows selecting whether to migrate Result Data. Result date refers to results that were previously calculated for the scenarios processed in 2013 application, and Input Transaction data that was in older PA5G . So overall the customer can choose if he wishes to take forward only his ‘models & input data’ and/or ‘calculated results’.
All Model Level data, Time Period related data, Input Transactions from AUC or any other Form, all Income Statements and Results of calculations that were run previously get copied to the newer application.
Related Topics: