What's New in Syniti Solutions 8.0.2

Release Date: 01/04/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.


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 Data Quality (formerly dspMonitor), Master Data Management (formerly dspConduct), 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 Stewardship Tier 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.


Advanced Data Migration

Data Services AutoGen

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

Stewardship Tier

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.


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

Stewardship Tier


  • 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]

Master Data Management

Fixed an issue in the Vertical View on the Data Sources page where the Command Timeout value was being overwritten by the Connection Timeout value when a user updated a value in the CranberryConfigurator. Also, encrypted passwords were being ignored and therefore displayed. The fix stores the values for Connection and Command Timeouts as entered, and passwords remain encrypted as expected. [SST-5]

Changes in Previous Versions

Previous Versions of Help

Help Build Date:May 08, 2023 02:53:23 PM