Microsoft Announces the Availability of Management Reporter for Microsoft Dynamics ERP

Microsoft has now announced the general availability of Management Reporter for Microsoft Dynamics ERP. Management Reporter, formerly codenamed Management Reporter 2.0, will act as the replacement for Microsoft FRx,

www.newscom.com/cgi-bin/prnh/20000822/MSFTLOGO

Management Reporter extends the proven functionality of Microsoft FRx and enables people to quickly and easily create, generate, help secure and publish professional-looking financial statements, such as profit and loss statements, balance sheets, and cash flow reports, and will also allow them to take advantage of the following:

• Custom reports without IT assistance. These reports reduce the burden on the IT department by empowering the finance team to create its own financial statements.

• Deep cross-functional analysis. Management Reporter provides easy and accurate financial reporting, intercompany reconciliations and eliminations.

• Reduced training time and increased productivity. A familiar user interface and reporting tools minimize training time since users will easily be able to transition from Microsoft Office applications to the similar navigation pane and toolbars in Management Reporter.

• Strong data integrity and report accuracy. Management Reporter supports regulatory requirements, such as generally accepted accounting practices and international financial reporting standards.

"Management Reporter is like Microsoft FRx on steroids — it takes the familiar building blocks of Microsoft FRx and revolutionizes the way reporting and business intelligence can be delivered," said Les Wright, senior consultant, BDO Canada LLP, a Microsoft Dynamics partner. "This is something customers have been asking for and provides even more value to their Microsoft Dynamics ERP solutions."
Microsoft FRx customers making the transition to Management Reporter will experience a variety of new features including the following:

• Direct integration to the Microsoft Dynamics ERP general ledger. This integration aids in simplified, real-time reporting with greater accuracy.

• Reusable building blocks. Blocks of Report, Row, Column and Tree definitions can be mixed and matched to produce a wide variety of boardroom-quality reports.

• A Report Library. A Report Library is where reports can be secured, stored, and viewed

Management Reporter is available for Microsoft Dynamics GP 2010 customers at NO ADDITIONAL COST and will be available with future releases of other Microsoft Dynamics ERP solutions.

To assist customers currently using Microsoft FRx make the transition to Management Reporter, a migration tool, detailed guidance and information is available at

www.microsoft.com/dynamics/en/us/products/management-reporter.asp

Direction of Microsoft Dynamics NAV

Based on Microsoft Dynamics NAV Statement of Direction – April 2010

Microsoft has now announced that NAV is going to support for Unicode with the release of Dynamics NAV "7", which will be released next year - 2011. This will also mean that we are finally going to say goodbye to Navision's native database, which otherwise have served very well basically since the release of the first DOS version of Navision in 1987. It is a goodbye to this REALLY GREAT & SUPER STABLE database.

Unicode has been too much of a worry to the average Navision customer. But for international customers, who have been working with many different countries in the same database, then it's going to be a great help.

NAV "7" will also be another goodbye. With the release of NAV “7”, "Forms" are also going to be disappeared. "Forms" have been the data presentation object until NAV 2009; however with the introduction of the “Role Tailored Client” - “RTC”, it is now the "Pages" which is providing the data presentation to the user. The "Forms" are still used in the Classic Client, but now with the removal of the "Forms" then the typical NAV user will no longer be able to use the Classic Client. (Fortunately) Developers will still have to use the Classic Client, until new development tools will be available in the “Role Tailored Client” with NAV "8" in 2013.

Future of NAV Development Environment

The C/SIDE development environment is going to be replaced from Classic Client to RTC. As you know, still we have to depend on the NAV Classic Client for making any customization, even though we do the implementation in RTC, but this structure is going to replace with the upcoming versions of Dynamics NAV. Some of the highlights would be as follows;

1. No Object Designer! Simple. This will be replaced with Designer Home Center; it will be another role center which allows developers/consultants to make any changes to the standard objects of the application.

2. Page Designer will be replaced with another page where it will allow you to proceed with your table customizations. This feature will be brought into the other object types as well.

3. In the Object List, developer will find the all objects including data about where they used and information about the usage.



4. No Visual Studio! Own simple editor for making all changes in Code Units.



5. The structure of the Editor would be more towards to the look & feel of the Visual Studio. For example the Symbol menu is to be replaced; any parameter that you define will be available in the top of the code lines.

To be continued …

Source:
www.dynamicsuser.net/blogs/kine

Navision Employee Portal

Employee Portal provides a Web-based interface that gives employees quick access to mission-critical business information such as invoices, customer data, and some selected reports. Moreover, it real time integrates with the standard Microsoft Dynamics NAV database while collaborating with Microsoft® Windows® SharePoint® Services 3.0 (WSS 3.0) or Microsoft Office SharePoint Server 2007 (MOSS 2007) to provide you a browser based interface.

Depending on the volume of transactions and the number of concurrent users, you can setup Employee Portal to run with either WSS or MOSS. However with MOSS, you would get additional support for making further developments.

Employee Portal can also be identified as a Web Portal for Sales Persons who travels all over the country. In such instances, salesperson can logging to NAV and start creating Sales Orders or Sales Quotes as required by them.

Let’s look at some typical screens available in the default Web pages.

Item List /Product List Page
This page can be configured as a combination of List Web Part and Card Web Part page in such a way that Item List is available in the top side of the page. Once user clicks on the ‘Card’ hyperlink on the list then user is directed to the Item Card of the particular Item in the bottom of the page.


What is Employee Portal

There are number of options available in the Item Card where user can modify or even delete the existing items from the system. It also gives some reporting options such as ‘Quantity Explosion of BOM’, ‘Rolled-up Cost Shares’ and ‘Detailed Calculation’



Sales Order Page
As in Item Page, existing Sales Orders can be displayed in the top of the page. As and when user clicks on the particular Sales Order Number then user can be directed to Sales Order Card screen where both the header and the line information are displayed.



However there is no static principle in designing the web pages in Navision Employee Portal. With the given Web Parts, you always have the flexibility to for designing each web page according to the user requirement. For example, in the sales Order screen, instead of showing all existing sales orders in the system, you can display all existing customers in the system. From the Customer List you can filter respective sales orders list belongs to particular customer and then you display the card view of a selected sales order.

Since the installation and setup process takes a very sensitive path, it is recommended that you must strictly follow the standard Microsoft Installation and Configuration Guidelines without any change.

To be continued…

Upgrade from NAV 5 to NAV 2009 SP1 – A Quick Guide

Regardless of the version from which you are trying to do the upgrade, the whole process can be divided into two main phases as Object Upgrade and the Data Upgrade. Let’s first look at the Object Upgrade.

In Object Upgrade, you have to identify all the customizations done in the current live version of the customer database and implement the same in a new 2009 SP1 database. Please remember that there are no short-cuts for this process. This is entirely a manual process, but you can make use of the existing tools such as Developer Toolkit. Using the Developer Toolkit you can compare/merge the original version 5 db and the current customer database wherein you can identify the differences between the two databases and implement the modifications in a new 2009 SP1 fresh database. Once you complete this process, you are through with the phase no 1. Remember that this is the most time consuming phase in an upgrade project. If you make any mistakes then you have to suffer a lot in the subsequent processors.

Let’s look at the phase number two which is the Data upgrade. In this case, I am giving you the main steps for continuing with the data upgrade.

1. Prepare for the data conversion.
a. Make a copy of the database in which you will perform the conversion.
b. Verify that both your partner development license file and customer license file have been upgraded to Microsoft Dynamics NAV 2009 SP1.
c. Identify a User ID and password of a super user in the system or create a new super user in the system that you can use for the upgrade process. Log in as the super user when you perform the upgrade.
d. Make a backup of the entire database before you start.
e. Test the database for everything except table/field relationships.
f. Test the database for table/field relationships.
g. Compile all objects and resolve what to do with those objects that do not compile.
h. Uninstall Microsoft Dynamics NAV 5.0 from the developer computer.
i. Install Microsoft Dynamics NAV 2009 SP1 on the developer computer, and then start the Classic client.

2. Convert the database to Microsoft Dynamics NAV 2009 SP1.
a. Create a new database in Microsoft Dynamics NAV 2009 SP1 and restore the backup of the customer’s existing database into the new database.
b. You can also open a copy of the customer’s existing database with the Classic client in Microsoft Dynamics NAV 2009 SP1 and convert the database.

3. Delete all objects except tables.
Delete all forms, reports, dataports, XMLports, codeunits, and MenuSuites, from the database. Do not delete the tables.

4. Import the new customized objects that you created under the Object Upgrade Phase.
In this case, you are supposed to replace all objects using the Import Worksheet window. Once all the conflict objects are found, you can replace all objects by clicking the OK button.

5. Compile all objects in the new database.


6. Upgrade data common to all companies.
Upgrade Security Roles and Permissions
If you are upgrading Microsoft Dynamics NAV with Microsoft SQL Server®, then you must synchronize the security system. In the Classic client, on the Tools menu, point to Security, and then click Synchronize All Logins.

7. for each company, initialize the company in the upgraded database.
You can do this by running the codeunit 2, Company-Initialize.
Close the company and open it again.
Open form 531, Setup Checklist, to update the checklist for the Microsoft Dynamics NAV 2009 SP1 data structure.


8. Install the new clients.
Make a backup of the new upgraded database.
Remove all previous versions of Microsoft Dynamics NAV from the client computers. Install Microsoft Dynamics NAV 2009 SP1 on all client computers. Also install the other tiers in the Microsoft Dynamics NAV architecture.

9. This is the end of the upgrade process from NAV version 5 to the 2009 Classic Client, but before going into Live, TEST… TEST… TEST…

To be continued...

How to run an External Application within Dynamics NAV

Perhaps you may have inquired the possibility of executing an external program within Dynamics NAV due to many reasons such as;

1. To run an external application like Windows Calendar or Skype within NAV
2. To run a Crystal Report using a Icon available in NAV

Whatever the reason, concept for making this a reality would be as follows;

Initially you may have to find out the directory path where the executable file of the external application is located. For example, let's assume that you are in need of calling the windows Calendar within Payment Journal Screen. You can search the calc.exe file where it is located. Mostly this is available in the windows System32 directory. Therefore the relevant directory path could be defined as 'C:\WINDOWS\system32\calc.exe'. In CAL, you could call the Calendar Control by giving the following command;

SHELL('C:\WINDOWS\system32\calc.exe');

This can be achieved by placing an additional command button in the Payment Journal Screen. In the 'OnPush' trigger, once you place the following CAL code you can display the Windows Calendar on top of the Payment Journal Screen.



For example, if you want to direct your browser to open a particular Web Site, for example www.microsoft.com you can do it by placing the following command;

HYPERLINK('http://www.microsoft.com');

Let's say if you want to open a PDF document you could do it by giving the following command in CAL;

HYPERLINK('D:\MyDocuments\80042A_00.pdf');

In the above case, D:\MyDocuments\ is the directory path where the relevant PDF file is located and the 80042A_00.pdf' is the PDF file name.

For instance, if you want to call an External Program using the Menu Structure, you will be able to do it by giving a reference to Code Unit in the relevant Menu Object; in the 'OnRun' trigger of the Code unit you can place you CAL commands to call the external application as explained above.

Trace Flag is no more Required

You may remember that customers who were running NAV 5.0 and NAV 2009 with SQL Server option were required to enable the Trace Flag 4616 in the SQL server database. However, this is no longer required with the latest NAV 2009 SP1 version, as it uses “VIEW SERVER STATE” permissions to enable visibility to the required connection information for each user. Therefore, now it is recommended that Trace Flag to be disabled after upgrading it 2009 SP1. If you are going for new installation, of course this is not required at all.
In most cases, we enabled the Trace Flag by adding it to the startup parameters by opening the "Configuration Tools" folder of the "SQL Server Configuration Manager". However, you can disable it now by following the below steps;

1. Go to Start-> Run and select the "Microsoft SQL Server 2005/2008" program group, select the "Configuration Tools" of the "SQL Server Configuration Manager" tool.
2. Double-click on the SQL Server service.
3. Select the "Advanced" tab
4. In the list of values double-click on the one called "Startup Parameters"
5. In the list of values for this parameter (mostly at the end), remove the following: ';-T4616'
6. Click OK to save the change.
7. Restart the SQL Server service


Note:
In certain instances, you may have done this by using the DBCC TRACEON command. If that is the case, you could also do this by SQL Server Query Window.

Role Center Configuration

What is Role Center

Role Centers are one of the most attractive features available in the latest of Microsoft Dynamics NAV 2009. Basically, a Role Center is designed to assist users by identifying the specific roles played in their day to day life. It improves the user friendliness of the ERP system by providing them an overview of the tasks and information relevant to their job and helps to plan their daily work.

A role center is a Dash Board Screen for a specific segment of users where all the frequently used options of the ERP could be organized and make available in one single screen. These selected options may contain different data entry screens, batch jobs, reports, analysis screens, data integration objects such as Data ports, XML Ports and even URLs of frequently visiting web sites & email inbox / outbox as well.

Microsoft Dynamics NAV 2009 delivers with 21 default Role Centers and they could be further optimized as per the specific needs of the customers. These Role Centers can be customized by each individual according to their priorities so that it promotes the most commonly used data, actions, and reports in their respective role centers.

The default 21 Role Centers available in the System

Profile ID	Role Center ID
ACCOUNTING MANAGER	9019
AP COORDINATOR	9002
AR ADMINISTRATOR	9003
BOOKKEEPER	9004
CEO	9019
DISPATCHER	9016
IT MANAGER	9018
MACHINE OPERATOR	9013
ORDER PROCESSOR	9006
OUTBOUND TECHNICIAN	9017
PRESIDENT	9019
PRESIDENT - SMALL BUSINESS	9020
PRODUCTION PLANNER	9010
PROJECT MANAGER	9015
PURCHASING AGENT	9007
RESOURCE MANAGER	9014
SALES MANAGER	9005
SHIPPING AND RECEIVING	9008

Role center Configuration and Personalization

The difference between configuration and personalization is that configuring a Role Center changes the user interface for all users with the same profile, whereas personalizing a Role Center only changes the user interface for a single user. This means that configuration is something done by the System Administrator or the System Manager mostly at implementation time, whereas Personalization is something done by the individual users depending on the priorities of their day to day life and it will not affect the role centers of other users.

To be able to configure a Role Center, you must satisfy the followings;
1. You must be an administrator with the role SUPER.
2. You must be the owner of the particular Role Center

Role center configuration tasks would be typically performed by an administrator, SUPER user, or Microsoft partner. Alternatively, this could be delegated among the groups’ heads of each users segment.
Once you open the application in the configuration mode, you could start doing the following tasks;

• Configure the Actions pane.
• Configure the FactBox pane.

How to open the application in Configuration Mode

1. Decide on the Role Center to be customized. In this case, let’s assume that we are going to configure the order processor Role center. Firstly, you must be the owner of the order processor Role Center. To do this; go to Administration -> Application Setup -> Role Tailored Client -> Profiles

2. Through the Profile List, go to the Profile Card and select the ORDER PROCESSOR as the profile id. Define the Owner Id as your account. This will transform your account as the owner for the ORDER PROCESSOR role center.

3. Now you are required to assign ORDER PROCESSOR role center as your default role center. To do this; go to Administration -> Application Setup -> Role Tailored Client -> User Personalization

4. Retrieve your account in the User Personalization Card. Now assign order processor as the profile id.

5. Go to the Administration, expand the Application Setup node, and then click RoleTailored Client, and open Profiles.

6. Go to the command line mode and change to the directory into the place where the RoleTailored client executable file is available. For example, type the following command: cd c:\Program Files\Microsoft Dynamics NAV\60\RoleTailored client



7. Once the directory path is changed, type the following command in order for opening the RoleTailored client in configuration mode
cd c:\Program Files\Microsoft Dynamics NAV\60\RoleTailored client\ Microsoft.Dynamics.Nav.Client.exe -configure -profile:"order processor"



This will open the Dynamics NAV 2009 application in the configuration mode, where you will be able to proceed with your customization affecting all users whom will be assigned with the current applicable Role Center.

To be continued....

Dynamics Navision Presentation at ANC

Thank you very much for your participation in the Seminar...

It was on 3rd Feb 2010 from 4.00 p.m. to 6.00 p.m. at ANC Auditorium. Our session was all about Dynamics NAV and its attractive features among the other ERP systems in the market. We shared our knowledge on MS Dynamics NAV and its various aspects;

a) Brief introduction on "what is ERP" and the impact of ERP on business process? - By Apsara who is a Project Manager - MS Dynamics NAV

b.) Integration facilities available in the MS Dynamics NAV with SQL server, SharePoint, MS BizTalk Server and other related technologies.

c.) Some useful facts on upgrading earlier versions of Microsoft Navision into the latest version of MS Dynamics NAV 2009 and its Role Tailored Architecture

d.) Flexibilities and the features available in MS Dynamics for customization in tailor-making the software according to the individual customer requirements.

c.) In the arena of ERP implementation, who are the Partners and their role? what are the Services?

And many more.....

Again thank you... and our special thanks to NetAssist Team for organizing such an interactive session...!!!

Navision Application Server

MS Dynamics NAV – Setting up an Application Server (NAS)

In MS dynamics NAV, there are lots of discussions about NAS and its behavior & functionality and also about installing NAV correctly. Lets’ first see what is meant by NAS?
What is NAS?
Navision Application Server is a middle-tier server that runs as a service. It is designed to provide access from external clients to the MS Dynamics NAV Navision database. The database could be either MS SQL Server or Native Navision Database Server. Whatever database platform it runs, NAS acts as a bridge to the NAV database when it is integrated other external applications. In this case, external applications mean any other applications apart from the typical Navision client.

The key role of the application server is in the e-business solutions. For example, Navision Application Server provides connectivity between a Web client (such as Navision Employee Portal) and Navision Database Server; between an external application (such as Microsoft Business Solutions–Axapta) or a Navision client and the database; and between third-party devices (such as Automatic Data Capture System) and Navision. The application server can also serve the Navision client itself, with automated posting and printing.
How to install NAS
First we see the authentications structure of the NAS. Simply NAS needs a windows login into the Database. In other words, the existing database login accounts already created in the database have nothing to do with a NAS. Therefore, if you are managing with the database authentication at the moment, the first task you should do is creating a windows login to the database. This is because it is service and inability to assign a database login in a service. The service needs a windows login to launch it. Therefore you will be required to create a login in the domain or in the server to accomplish this task.
Once you create a windows login, you will have to grant the rights for this new account. So, you need to create that Windows login in the SQL server and assign him the sysadmin role.
Now you can login to the SQL server with the new windows accounts, but still this is not enough for login to the NAV. Therefore, you have create a Windows Login Account in NAV. When doing this, you have to assign SUPER role for this windows account.
Now it is time for you to install NAS. To do this, take the NAV installation CD and launch the ..\NAS\setup.exe file. You may just accept all the default values given in the installation process, however make sure to remember the installation path of the NAS directory as you would need it when configuring the NAS in the next step.
In general, it would more advisable to manually create required NAS instances. You should not use the default two instances created by the installation which are namely, Microsoft Dynamics NAV application Server-[machine name]-SQL & Microsoft Dynamics NAV application Server-[machine name]-Classic. Therefore, the next important step what you should is disabling the above mentioned services from the pc as they would unnecessarily consume the system memory. In the next phase you setup your own NAS instances as follows;
Please note that this will be manual process and you will do this using the command prompt. In other words, you have to use command line instructions for install/start and uninstall/stop of the NAS. My experience is that it always to easy to copy and maintain the following commands in a proper place and make use them whenever I am in need of changing any of the given parameters.
There are the steps for creating a NAS;
1. Go to the sub directory of the NAS installations
2. Paste the following in the command prompt in the NAS sub directory.
nassql.exe appservername=TheNasName, NETTYPE=TCP, servername=TheSQLServer, database=TheSQLDatabase, company="The Company", nettype=tcp, startupparameter=”THEPARAMETER”, objectcache=40000, installasservice
The above will create a new service as TheNasName. To start the service, you may give the following in the command prompt.
Net start TheNASName
In case you want to stop the service, you provide the below in the command prompt.
Net stop TheNASNAME
In case you want to uninstall it
Nassql.exe appservername =TheNASName, uninstallasservice

Suppose if want to setup a Navision Application Server, but still you are running Navision Native Database you could do it by providing the below instructions on the command prompt
nas.exe appservername=TheNasName, NETTYPE=TCP, servername=TheNAVServer, company="The Company", nettype=tcp, startupparameter=”THEPARAMETER”, objectcache=40000, installasservice
In case you want to stop the service which is created on top of the Navision Database Server, you provide the below in the command prompt.
Net stop TheNASNAME
In case you want to uninstall the NAS which is created on top of the Navision Database Server, you may provide the below instructions on the command prompt
Nassql.exe appservername =TheNASName, uninstallasservice
Now I am giving you the meaning each parameter defined in above mentioned processors.
1. Appservername: This would be the name of the Navision Application Server you would define. Please note that this name is only used as reference in your windows operating system and this name has nothing to do with Navision. Please also make sure to avoid any spaces or special characters for this name.
2. Server name: This would be the name of the SQL Server or Navision database server.
3. Database: this is only used in SQL Server and it is the name of the database for which you are trying to create a NAS.
4. Startupparameter: This is the unique name used by Navision for it’s all references. The value which you defined for the parameter will be used by Navision inside the C/AL. The value you define here will be used in the NASHandler trigger of the Application Management Code unit (code Unit No 1). For example, if your purpose is to define a NAS for Navision Employee Portal, you must define the start up parameter as NEP_1, NEP2 etc. If you purpose is to setup the NAS for Commerce Gateway/BizTalk Server Integration in NAV then you must define the startup parameter as CG. However, please note that only alpha numeric characters should be given for defining the startup parameters.

Now it is time to run and see the Navision Application Server. So you may go the windows services area. You could also do this by typing “run service.msc”. Now do the followings;
1. Locate the newly created service which is TheNasName
2. Open the service
3. Define the start up type as Automatic
4. Go to the Log On tab
5. Provide the Windows user Account and the password you defined at the beginning.
This should successfully create the Navision Application Server. However, you can further check the NAS whether it is working fine by locating the Windows event viewer. You could open the Event Viewer by typing eventvwr.msc

Navision Upgrades

Let’s see the main steps involved during a version upgrade. In this case, it is assumed that the customer is running a version of Microsoft Business Solutions Navision 3.7 or more.

1. Get a backup of the current customer database and restore it in a 2009 client.

2. Identify all the objects modified in the customer database. For this process, Developer Toolkit for MS Dynamics NAV is recommended and all modifications that are done in the current client installations will be highlighted by the Developer Toolkit. Text form all objects files of both current customer database and cronus database should be provided to the Developer Toolkit as the inputs.

3. Analyze the modifications in the customer db and decide whether they are really required in the new version. For example, similar functionality may have been introduced by the new version. In such cases the modifications done in the old version may become obsolete. For example, from ver. 3.6 to NAV 2009 several areas have been redesigned a lot such as Jobs & Resources, Approval & Work Flow management area. Therefore, it will be a must to understand this and decide on the modifications are to be continued with the new version.

4. Integration: If there are any modifications done in the customer database in regard to any integration, a separate analysis need to be done against them. For example, if the upgrade is coupled with the SQL migration in which case database plat form will be changed from Navision Database Server to the MS SQL Server. Consequently, the some of the integration technologies such as C/FRONT, CODBC, NODBC need to be changed as per the SQL server environment. Certain C/FRONT development becomes obsolete and a separate developments need to be done using.NET technology. Before going live, these new developments should be tested thoroughly.

5. Create a new empty database and load 2009 objects. Once this is completed, you can load all 50k range objects of the customer database also into the new 2009 db as they do not need merging.

6. Start text comparing and indentify the changes and make the same changes in the new 2009 database. The merging option available in the Developer Toolkit is not recommended at all for this process even though it is possible, as it may crop up unwanted issues in the down the line. Therefore the modifications in the new 2009 db must be done through a manual process. Simply, the developer toolkit should be used ONLY as a comparison tool and NOT as a merging tool.

7. Use transformation toolkit to move the forms into pages in the new 2009 DB

8. Go through all reports and create layout for RTC (Role Tailored Client)

9. Once the objects have been upgraded it would be time for you to do the data upgrade.

10. Get a backup of the current customer database which is restored in a 2009 client under the step 1.
11. Load the 2009 upgrade toolkit on it and follow through the process. It is highlighted that if you are upgrading db other than Navision worldwide version it is important for you to override the worldwide upgrade toolkit objects with the relevant localized upgrade toolkit objects. When it is prompted to run the ‘Upgrade NAV 2009 – Step 1’ process, you may say ‘yes’, but make sure to leave the pc uninterrupted till the process completes as it may require more resources / memory.

12. When the ‘Upgrade NAV 2009 – Step 1’ process finishes, load the Step 2 objects of the upgrade toolkit. As in the above step, make sure to load any localized upgrade toolkits if you are upgrading db other than Navision worldwide version.

13. Once the step process is over, load the new roles and permission to the database. This will enable in grating rights for the new features and functionalities.

14. Do a thorough functional testing. The upgraded database should be validated by a complete integration testing done in the customer site before going into live. The integration testing should get the participation of users and their scenarios.