Migration Reports

Topics related to this section:

• Deployment Reports

• Reporting Features

• Working in Multiple Execution Environments

Prerequisites for Displaying Migration Reports

These reports are built within the Mappings section. They are maintained by developers for use in migration testing runs. 

Security Access

• Users who view these reports must be in an SKP User Group that contains a Role which grants access to view Migration Reports or the reports are not displayed. This section of Syniti Migrate is generally not granted access to the validation users because they have access for specific Deployments. However, if Deployments are not necessary then they may be setup for Migration Reports, but this is not recommended because anyone with access to Migration Reports will be able to see all "Active" reports, even if they are not "Published".  Refer to Manage User Security for more information.

• Within each report details stored in Mappings, a level of sensitive data security may be set at report level. These reports are only visible to the list of users assigned withing the report details page in Mappings. Users who do not have access do not see the report in Migration Reports page. Refer to Migrate > Mappings > Maintain Target Reports for details of this process.

Note

Enabling the Active flag on reports now makes them available in Migration Reports for review across Environments. Enabling the Active and Publish flag makes reports available in Deployment Reports.

Working with Migration Reports

View the following page by navigating to Validate > Migration Reports from the Syniti Migrate Homepage. Migration reports are grouped by Release, Dataset, and Type of report. In this way, the team members assigned to generate reporting can focus on the reports of their specific Dataset (Ex: Sales Orders, GL Balances, Material Master).

This section of Validate is for data that does not require filtering by a Deployment.  As example, Material Master might setup Deployments by Product line, and Finance may setup GL Account Deployments by Company code to limit the exposure of data to users. 

Users may select from a Release, a Subject Area, or a Type of report to view the list of Reports or Errors.

The Migration application supports configurable Environments for projects that require multiple active environments.  The ability to separate the MOCK LOAD environment from the DEVELOPMENT environment in order to better support Mock Loads and reporting.  As can be seen in the image below, this set of Deployment Reports are set to pull from the DEV Environment.  Double - click on the tab label for the Environment to open the Environment Selection window and select the Environment. Once complete, click on Save icon or Cancel icon to exit. 

Refer to Administer > Environments and Working in Multiple Execution Environments for more information on this process, how to plan for setting up multiple execution environments, and how data moves through environments using the same production code in Migrate.

Note

The reports display regardless of whether there is an actual count of records.

Click the button (either for Reports or Errors) to display the list of reports for that type (Release, Dataset, or Report Type). Notice that the menu path is displayed in the left header (For example, Migration Reports: March_ETL)

Migration Reports provide access to a user to review and download the reports for conversion validation and save these reports locally to their drives.

The Migration Reports listing page provide the following columns:

The last column provides options for the user such as displaying history, refreshing the report, viewing the report, or download to local drive.  See the details for these icons below:

Note

• Reports may only be refreshed by the migration team and not as part of this validation process. Therefore, the Refresh Icon is hidden for this page.

• The Segment icon will be active only if the Segment By field has been entered with a valid column name for the report on the Report Details page.

• If the Segment By field is entered with a valid column name and the report has zero records, the Segment By icon becomes Inactive.

Details Relevant to Migration Reports list page

Only the reports with record counts provide View and Download icons Active. The Record Count History column provides a spark line of the counts for each report. 

The spark lines are built from the history of runs for the report. As shown in the image below, the report history date, and record counts are stored within the History icon of the Options column. The spark lines build as the report is run to build the history and if there is no spark line, then it means that the report has not been run multiple times to build one.

Edit Migration Report Details

Depending upon the user's access within Migration application, they may have access to maintain certain fields of the Migration Report Details page.  Click Edit  icon provides the page and certain fields may have access for changes.

As can be viewed in the image, most of the fields are Display ONLY.  However, the user may alter the values for fields - Limit and Random Sample to provide the list that they need from the report.

Note

Fields Business Impact and Recommendation are filled in by the developer.  If there are no values in these fields, they are hidden from validation to reduce clutter on the page.

When finished with edits, click the Save  icon to complete.

Reporting Features for filtering, grouping, and other report functions on page

Once the user decides to view the report, they can use on page filters and grouping to pinpoint their results. Refer to section Migrate > Reporting Features for more details of this process.