CISTECH’s Upgrade Assistant tool automates the labor intensive process of determining the impact to your custom applications of MAPICS release upgrades.
Upgrade Assistant analyzes MAPICS modifications, custom application objects including Integrator objects, queries and reports that access MAPICS data and program libraries. It then identifies programs that are impacted by changes to MAPICS programs or files. With this information you can effectively estimate your migration effort, plan the steps required for a successful migration, and minimize risks of program errors after upgrade.
How it Works:
The CISTECH Upgrade Assistant compares custom program libraries in your current MAPICS environment to the target environment, and determines whether MAPICS objects used by those libraries have been modified. After comparing all library objects, a file is created to identify object changes, and indicates whether matching source code exists. Recommendations are made for appropriate actions to resolve object changes. This file can be downloaded to Excel to provide the basis for your upgrade project plan.
Benefits of using Upgrade Assistant:
- Eliminate the time required to manually identify program
and file changes
- Accurately estimate the complexity and effort of your
- Reduce risks of information loss and system downtime
caused by unidentified changes
- Easily manage your upgrade with downloadable Excel file
Upgrade Assistant Features:
- Identifies modified MAPICS program objects
- Identifies custom programs that use MAPICS files, including Integrator objects
- Identifies logical files and queries built over MAPICS physical files
- Prints before and after file layouts for MAPICS files used by your code
- Identifies objects affected when making application changes to an environment (such as moving from PDM to EPDM or from AM to IFM)
- Identifies triggers that you have added
- Creates a text file detailing affected objects
The CISTECH Upgrade Assistant provides a tool and methodology to strategically analyze custom enhancements to the MAPICS XA product and identify areas affected by release upgrades. Custom enhancements may include:
- Modified MAPICS program objects
- Custom programs that use or update MAPICS database files
- Trigger Programs linked to MAPICS files, including Integrator objects
- Logical files built over MAPICS physical files
- Queries that use MAPICS files
- Hard coding of libraries found in custom CL programs
Using the Upgrade Assistant while following the “Five Phases of a MAPICS Upgrade” can help you reduce time and cost and you can be at the new release in record time.
The Five Phases are:
- Planning and Initial Upgrade
- Analysis and the Upgrade Assistant
- Final Upgrade and Go-Live
Planning and Initial Upgrade
Begin your upgrade by reviewing information on the Infor E:Info web site. This valuable resource provides all the information you need to plan your upgrade. You will need to create a separate environment (do not share applications) and perform the upgrade of the MAPICS applications as directed. This environment should be brought up to the latest PCM level with all critical PTFs applied. It will be used for integration and testing of your customizations.
Analysis and the upgrade assistant
For example, if your current environment is MM, the target environment is NN, and all your custom code is contained in two libraries – CUSTOM and CUSTOMF, your configuration would be similar to this:
The Analysis Results file produced by the Upgrade Assistant is in standard comma-separated variable format (.csv) which you can download and import in to EXCEL for use in managing your integration effort. It includes columns for the following information:
The analysis tool makes recommendations as to the action you should take for each referenced object.
0 – No action required for this object
1 – Recompile only
2 – Modified object requires detailed analysis
The first step of the database analysis process involves reviewing the Before/After Record Layouts for changed MAPICS files that were generated by the tool. If you determine that the changes to a file are non-critical, you filter records in the spreadsheet that reference that file and change the action from a ‘3’ to ‘1’ to indicate recompile. If the changes are critical, you change the action flag to ‘2’ indicating that a detailed review of the logic will be necessary. Critical changes may include changes in field length or type, change in keys or select/omit criteria, or deleted fields.
When the data base analysis is complete, you review each custom object to determine if it can be recompiled or if further analysis is required. The action for the object will typically be the highest action assigned to one of its referenced objects. Excel provides easy sorting and filtering to make this task quite easy.
As you integrate the MAPICS changes with your custom applications, you will place all new objects in your test environment, which was installed as a part of the initial upgrade to a new release. When you create this environment, you will use the Trigger Program Definitions generated by the Upgrade Assistant to attach your custom trigger programs to the appropriate physical files. Following is a sample of this report:
The time required to complete the integration process should be reduced considerably and accuracy should be improved.
Thorough review and testing by users in the new release environment is essential to the success of your upgrade. Create a test environment for this purpose, or use the environment where integration has taken place. When the users are satisfied with the success of the upgrade, you are ready to go live.
Final Upgrade and go live
Perform final upgrade and migration tasks in the new release environment and provide support for users.
Prerequisites for Upgrade Assistant: XA R7.7 and higher, Procurement Mgmt, Enterprise Integrator, SMTP messaging for email alerts.