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

Release Date: 03/02/23

This release contains:

Product Certification

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.

IMPORTANT UPGRADE NOTES

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: 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 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 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 Advanced Data Migration 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 Knowledge base article Unsafe HTML/JavaScript removed in Stewardship Tier 7.4.2 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.

Enhancements

Advanced Data Migration

Data Services AutoGen

Due to a security flaw, the BODS AutoGen service has been deprecated.

Stewardship Tier

  • It is now possible to configure Single Sign On (SSO) for the Stewardship Tier and the Knowledge Platform for a seamless and secure user experience. Refer to Enable Single Sign On for more information.

  • To improve auditing and allow for stricter compliance, the Stewardship Tier now displays failed login attempts by users when they are working with electronic signature. Users can view all failed attempts or attempts by a specific user. Refer to View Failed LogIn Attempts During Electronic Signature for more information.

Common

Within the Data Source Registry page for SAP Application Server, a validation has been added to warn when the SAP Use Namespace field is unchecked as this configuration is not expected since the Stewardship Tier does not currently support NonNamespace for the SAP functions.

Syniti Data Replication

This version of the Stewardship Tier is compatible with Syniti Data Replication 9.8.2.

Resolved Issues

Advanced Data Migration

Map

Fixed an issue on the Mapping Approval page when a user selected multiple rows and clicked the Approve or Complete icons. Sometimes the event took too long to complete. With the fix, clicking Approve or Complete on the Mapping Approval page with multiple rows selected results in the actions being performed on the selected rows and no timeout in processing. [DSP70-1939]

Stewardship Tier

Collect

  • Resolved an issue within Collect for the Advanced View Builder page where the job’s resulting debug log was revealing the database connection string. With the fix, the debug logs no longer provide the database connection strings as expected. [SST-4]

  • When building SSIS packages in Collect for MS-SQL Server 19 as a target or source database, sometimes an error similar to: “Exception from HRESULT: 0xC0048021 at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()” displayed. The issue has been fixed, and the SSIS package now builds as expected.

    NOTE: As part of resolving this issue, it was discovered that if you are using the Oracle data source connection type, it requires the Unmanaged Oracle Client Drivers, which Oracle only supplies up to version 12c. Use the Oracle data source connection type If you need to connect to an older Oracle system. If you are using a later version of the Oracle Client Tools, use ODBC or OleDB as the connection type. [SST-2]

  • Corrected an issue within theTables page where the Target Source Table Package for Package Types of "SAP Data Services with RFC" was ignoring added Where Clause values during the Data Service Data Flow query. The fix adds the Where Clause to the job build package when it is initially built and applies changes including the Where Clause for existing SAP Data Services jobs. [DSP70-1415]

  • Corrected an issue within the Tables page where the Target Source Table Package for Package Types of 'SAP Data Services' was ignoring added Where Clause updates when packages were rebuilt. The fix rebuilds the package including Where Clause changes. [DSP70-1645]

  • When filtering on the Tables page, if a user selected the Checked or Unchecked option in the Built section, a validation error displayed: “The entered value is not a valid integer.” With the fix, these filters can be used without receiving this error. [DSP70-1972]

Integrate

Fixed an issue where a Template created using a BAPI was failing due to BAPI download tables having incompatible data type / lengths compared to SAP DATS and TIMS data types. This fix increases the field length of SAP data types DATS and TIMS from 8 characters to 10 characters for (DATS) and from 6 characters to 8 characters for (TIMS). [DSP70-737]

Promote

Corrected an issue within the Structures - Data Sub Tablespage for Collect - Target Source Table where the table columns and the SQL Command details were not included when moving a Collect Target/Source/Table structure to a new system. With the fix, these two sub-tables are included in the promotion. [DSP70-1814]

Known Issues

In Collect, provided two solutions to an issue within Schedule Groups page where a Collect job in the queue for Data Services jobs with other pending jobs produces inaccurate overall processing time.

  • A suggestion is to put all Data Services packages for a Source in a Collect Target Source and then have that Target Source use a separate queue created specifically for the Data Service related collect jobs. Also, make sure that the Service Pages page queue has enough threads so that Services pages are not backed up.

  • An alternate solution is to increase speed for the interval on the Common Data Services Job polling within the Service Pages page to cut down the wait time between when the Data Services job finishes and when the second job is created.

Previous Versions of Help

Help Build Date:May 08, 2023 03:00:53 PM