What's New in SAP Advanced Data Migration by Syniti 7.4.8

Release Date: 2/25/22

This release contains:

Refer to the Product Certification Matrix for the versions of third-party products that this release has been certified against.

INSTALLATION NOTES FOR Stewardship Tier 7.4.8 AND LATER: The SAP transports for Stewardship Tier installations are now split into 2 packages and are documented separately.

  • Core—contains the functions and programs required by Stewardship Tier to extract data via RFC and load via BDC. These transports are distributed with the Stewardship Tier installation in versions 7.4.8 and later.

  • Supplementary—miscellaneous functions, programs, and utilities for supporting SAP-based projects. Contact Syniti Support and raise a support ticket to get this transport.

The code in the Core transports has been modernized to adhere to latest ABAP coding standards. Both the Core and Supplementary transports are compatible with SAP installations of EHP 7 FOR SAP ERP 6.0 [SAP_APPL 617] (based on SAP NETWEAVER 740 [SAP_BASIS 740]) or higher.

NOTE: Customers using older versions of SAP can contact Syniti Support who will assist in locating versions of the required programs and functions that are compatible with their SAP Instance.

Refer to Support Article SAP Transports for 7.4.8 and Above for SAP Transports available when running version 7.4.8.


NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to this version. The collation technology is included in the product in 7.4.5 and later. To uninstall psaCollate refer to the Knowledge Base article psaCollate Incompatible with SST 7.4.5+.

NOTE: When upgrading to Stewardship Tier 7.4.5 AND LATER, data sources are automatically assigned with the Collation Type of General Latin Case-insensitive. This ensures that the ADM AutoGen continues to create SQL tables whose text columns have a case-insensitive collation.

NOTE: When upgrading to Stewardship Tier 7.4.6 AND LATER, open a support ticket with Syniti Support to request a new license in order to use Entity Validation and Migration Reports. If using Entity Validation, you must also request a Melissa license.

NOTE: A new, critical step has been added to the Post Upgrade section of the Installation process. After an upgrade to Stewardship Tier, users must re-create their BAPI templates. Failing to do so will cause the posting of a BAPI template to fail. Refer to Re-create BAPI Templates in the Install Manual for more information.

NOTE IF YOU ARE UPGRADING FROM 7.0.6 OR BELOW: You may need to migrate your security settings to use centralized security. Users of ISA and Mass Maintenance (formerly dspCompose) must update security roles when upgrading to this version. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in this version and later. Consult this manual BEFORE updating to this version, as an analysis of current security assignments must be completed before the SAP Accelerators can be updated.

NOTE IF YOU ARE UPGRADING TO 7.4.2 OR HIGHER: Please be aware that any JavaScript content added is stripped away and any remaining, safe HTML is displayed to users. In Stewardship Tier versions 7.4.1 and earlier, users were permitted to enter HTML and have it rendered in the UI or included in file downloads from the UI. There were no restrictions in place on what HTML/JavaScript text was permitted, leading to potentially dangerous cross-site scripting attacks. Refer to the Unsafe HTML/JavaScript removed in Stewardship Tier 7.4.2 Knowledge base article for more information.


AWS RDS is now supported as a database server with certain configurations. Refer to the section Hyperscaler - AWS Hardware Requirements in the Requirements Guide for more information.

NOTE: For the 7.4.6 version and later of the Stewardship Tier, the source and target for CTS and Promote must both be RDS or both be non-RDS databases.

Advanced Data Migration (ADM)



On the Target Reports and Target Source Reports pages, on the Vertical View, on the Business User Settings Tab, the Sensitive check box and the Business Users Assignment icon are no longer hidden until the report is published. Report administrators can now use these settings to configure granular user access to a report before publishing it. Refer to Grant Users Access to Reports and Sensitive Data for more information.

SQL Auto Gen

While viewing the Automation tab in the Quick Panel, if the Create Target Table icon is clicked, a Target Table is created within SQL Server. If one or more columns are considered "Utility," this action would fail with an Incorrect syntax error due to missing column formatting. The automation process is updated, and the target tables will create as expected without error.

Migration Reports

The Migration Reports WebApp provides a simplified and improved version of Report Delivery. Report Delivery in Transform allows users to access reports for objects in the currently selected wave and process area in the Context bar. The new Migration Reports WebApp allows users to access reports across all objects. Using this WebApp, Business Contacts can quickly navigate to reports and drill down and select reports to add to their Favorite Reports page using a variety of methods. Administrators can easily grant user access to reports by object. Refer to View Migration Reports for more information

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

System Administration

This version contains updates to improve how the Stewardship Tier displays information about column encryption for a data source. The Stewardship Tier indicates when data is in a state of mixed encryption on a single column, and sends an email notification with details on these columns.

These updates include:

  • To track a table’s unencrypted columns, the columns NOT ENCRYPTED COUNT (the total number of unencrypted columns in the table) and TOTAL COUNT (the total number of columns in the table) have been added to the following pages:

  • If the values in the NOT ENCRYPTED COUNT and TOTAL COUNT are not equal, indicating that there is a mix of encrypted and unencrypted data in the column, the Stewardship Tier sends the Data Source Table Column Encryption Report workflow email to the relevant user(s).

  • The Status field on these three pages displays a warning icon when both encrypted and decrypted records exist in a column. The tooltip for this icon has the message Mixed Encryption.

  • In the Data Source Table Column Encryption Report workflow email, the Email From and Email To values were the same in previous versions. The Email From value name now displays the system instance, taken from the Instance field on the Parameters page.

  • The email includes the tables and columns that have mixed encryption and the mixed state indicator.

  • In cases when a column has data in a mixed state, and the encryption state is Not Encrypted, additional steps must be taken to encrypt these unencrypted records. Refer to Resolve Columns with Data in a Mixed State of Encryption for more information.

  • To better support decryption of encrypted data, on the Decrypt page of System Administration, the field Encrypted Data has been increased from 255 characters to 1024 characters.


Previously, when assigning a WebApp group to a role, the ROLE ID list box on the Security Roles page only displayed the description of each role. Now, the ROLE ID list box includes both the role name and the role description.


  • Connection to SAP systems using SAP Router with and without the usage of a Message Server is now supported. When SAP router is used with SAP Message Server, the SAP Gateway Host and SAP Gateway Service attributes must also be populated.

  • TheDebug Logs page was enhanced to provide a limit to the amount of time that debugging is active along with the start and stop times and the number of hours for retention of this log. This will reduce the risk for system slow downs due to this process running.


  • Users can now import a large number of target source tables using Excel Integration on the Tables page. Refer to Use Excel Integration for more information.

  • The ODBCHANA connection type (on the Source Connection Types page) now supports downloading data from a view. This enhancement enables the users to download views via Collect in order to gather the required metadata for the SAP HANA scanner to run. As a result, the Fetch Tables action that is run for a Collect target source where the Connection Type is ODBCHANA now fetches tables and views on a HANA system.


  • An error displayed when attempting to use the Structures-Data “Administration-Role” because the Sub Table “RoleWebAppGroup'' only had key fields set up for the comparison process. This Sub Table now includes non-key fields in the comparison process, allowing the “Administration-Role” Data Structure to work as expected.

  • A new setting on theApplication Parameters and the Packages page is available, called Default Include dgSAP Views. This check box either includes or excludes objects dependent on SQL objects in databases prefaced with “dgSAP” (such as dgSAP_Dev, dgSAP_QE, etc.) from the transport. While the Parameter configuration is applied to all new packages, this setting can be overridden at the package level.

  • When a package is compared, differences are queued to identify what to transport. If any object within the package failed, all objects in the package were excluded from the transport, which made it impossible to tell which objects failed and which transported successfully. The error process has been improved so that if an object fails to transport, another comparison is run so only objects that failed remain queued to transport.

  • Previously, it was mandatory for a table being compared to have at least one non-key column. However, use cases existed where tables that only contained keys needed to be compared and transported. Now, tables that only have key columns (i.e., the KEYS check box on the Structure - Data Table Columns page is enabled) can be Compared and/or Synced.

  • Users may now transport data within a SQL table to the destination server. This feature allows users to move data in mass by clicking the Send Data Toggle icon on the Package - Object Comparison page.

  • Power Users may now temporarily unprotect a database in order to transport SQL Object changes made to delivered applications for a package. Enable the Allow Delivered Database SQL Changes check box on the Application Parameters page and the same check box becomes available on the Packages page. Both settings must be enabled to transport core modifications.

Resolved Issues

Advanced Data Migration (ADM)

  • Fixed an issue within ADM where the key columns of the Error Aggregate tables were exceeding the max length of 500 characters causing the process to fail due to a truncation on the SQL statement. With the fix, the key columns are now set to NVARCHAR(MAX) and the tables are created without issues. [DSP70-1643]

  • Previously, when multiple users attempted to import target fields in Design concurrently, there was the possibility that lookup tables were not added. With this fix, clicking Execute Import on the System Types Import page allows one import to run at a time, ensuring lookup tables are added. [DSP70-1665]


  • Several metrics related to Field Mapping were returning incorrect statistics when a target had multiple target sources including inactive ones. The metrics views did not exclude inactive target sources. Incorrect statistics were also returned when there were multiple target sources for the same source. These issues have been fixed and the metrics are now calculated correctly. [DSP70-1480]

  • Fixed an issue where creating a new wave as a copy of two different source waves that contained segmented target reports was failing to complete the background job. With this fix, both waves are copied correctly and the status in the source wave shows as Procedures Completed as expected. [DSP70-1482]

  • Fixed an issue that occurred when adding a new Migration Milestone to the Waves page. While saving the new milestone, if the field NAME was left blank, the system would save the milestone. With the fix, the NAME field is required and the milestone saves as expected. [DSP70-1463]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

  • Fixed an issue with RFC extracts running on an SAP HANA database that caused the extract to duplicate data. This happened because HANA databases do not sort data in the same way as typical databases. To fix this, a Transport has been added that sorts the order of the records based on primary key once the selection is complete. This new Transport is included in the Stewardship Tier installation. [DSP70-1519]

  • An error message displayed erroneously when creating a Service message for a Service page. The error was "Please ensure that the Service User ID listed below has permission to access this page." The requirement for a Service User to have access to the Service page is no longer in the Stewardship Tier and the error message no longer displays. [DSP70-1429]

  • Fixed an issue where multiple clicks on a page link in the site menu caused the links on the displayed page to not respond. With the fix, the links function as expected. [DSP70-1339]

  • Previously, when directly linking to another page’s Vertical View, and then attempting to filter and select a value from a combo box, instead of populating the filtered results, the page redirected to the Horizontal View of the original linking page. The Filter function on combo boxes in the Vertical View now works as expected. [DSP70-1607]

  • Previously, when a role was assigned to a user with no other roles on the User Roles page, security to that role was not granted until a second role was added. Now, security to the role is immediately granted as expected. [DSP70-1588]

  • Previously, a page rendering with lazy load did not display all records when viewing the screen at a resolution of 100%. Now, a scroll bar is available to allow users to scroll and access all records on the page. [DSP70-1605]


  • Fixed an issue that occurred when attempting to create certain BAPIs (known examples include RCP301_RECIPES_SAVE and RCP301_RECIPES_WRITE) on the Template page within Integrate. After clicking the Create BAPI Template button, the button would remain in a processing mode and the BAPI template would not be created. With the fix, the template is now created as expected. [DSP70-1703]

  • Fixed an issue that occurred with Integrate processes using conditionals when running the Stewardship Tier on an application server using antivirus software that calls the Windows Antimalware Scan Interface (AMSI). The posting was running at over ten times the time of the same template on a system where the AMSI scan was not running. With the fix, the posting of an Integrate process with conditionals now completes in roughly the same amount of time regardless of whether antivirus software calls the Windows Antimalware Scan Interface (AMSI). [DSP70-1608]

  • To support copying of a template or a process on the Copy page, the lengths of the following fields were updated. The Copy To Template Name field had a length of 50 which has been updated to 150. The Copy To Process field had a length of 50 which has been increased to 255 characters. [DSP70-901]

  • An issue occurred when posting data using a template with an After Post rule. The system always used a default timeout of 30 seconds for processing, regardless of the Command Timeout setting set for the data source. To correct the issue and minimize timeouts, postings that use After Post rule templates now use the timeouts set on the Data Source Registry page for the data source. [DSP70-1587]

Enhancement Requests From Users

  • Updated the Password Require Special field on the Parameters page in System Administration to include the special characters.

  • Corrected the description of the Show in Navigation functionality in multiple topics throughout help, including the field description, which was updated to: “If checked, this column displays in the failed records Bulk Execution results. By default, only the first column on the page displays in these results. Refer to View Bulk Execution Results for more information.“

WARNING: Customizations made to any component of the delivered Syniti Solutions will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.


Previous Versions of Help

Help Build Date:April 04, 2022 12:48:41 PM