Migration Reports
  • 25 Mar 2024
  • 5 Minutes to read
  • Contributors
  • Dark
  • PDF

Migration Reports

  • Dark
  • PDF

Article summary

Topics related to this section:

Prerequisites for Displaying Migration Reports

These reports are built within the Mappings section.  They are maintained by developers for use in migration testing runs.  The reports must be set to Publish for the reports to be present within this section of the Migration application. 

Security Access -

  • Users who view these reports must first be setup within configuration to have 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 they have access for specific Deployments.  However, if Deployments are not necessary, then they may be setup for Migration Reports.  Refer to section  Administer > Security > User Management for further details.

  • 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 section Migrate > Mappings > Maintain Target Reports for details of this process.

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 section Administer > Environments for more details of this process.

Migration Reports: Environment Selection


Reports display in the Migration Reports list if they are marked within Migrate > Mappings > Target > Reports as Publish Active.  The reports display regardless of whether there is an actual count of records.

Migration Reports

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 (Ex: Migration Reports : ECC to S4 / BP-Customer / Preload)

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

Migration Reports: Reports list

The Migration Reports listing page provide the following columns:




Name of the Report.


Sequence of the Reports. Value increases by factor of 10 for each new entry.


The Report Type categorizes each report and setup for flagging in the All Errors report for errors produced .


The detailed description of the report.

Record Count History

These are spark lines that show the progression of counts for the report in a graph.  See section below for spark lines for details.

Last Run

Date this report was run last.


Count of records processed successfully.


The quantity of records that default as output to prevent excessively large reports.


Default value of 1000 at time of save may be changed after saving.


Check Box to show if report is using a random sample of data within the output of this report.  This field works with Limit field.


The check box is selected within Edit Details.


Provides icon to indicate that this report contains sensitive data that only a list of users may view.


This column contains four icons (History, Refresh, View, and Download).  Each icon produces the outcome indicated in their name

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:





The History icon displays a grid of history for each run of the report with count and date.


The View icon displays the report data on page.


The Download icon saves the current report to the user's local drive.


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.

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. 

Migration Reports: spark lines

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.

Migration Reports: Report History display

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. 

Migration Report: Edit Report Details

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.


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.

Was this article helpful?


Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence