What's New in Syniti Solutions 8.0.6

Release Date: 12/27/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: SQL 2022 no longer supports SQL Server Native Client. If using any data connections that rely on this Data Provider, you must switch to a new provider, such as MSOLESQLDB. Refer to SQL Server Native Client for more information.

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: When upgrading to Stewardship Tier 8.0.5 AND LATER, open a support ticket with Syniti Support to request a new license in order to use Remediate, which is part of Master Data Management.

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.

WARNING: In Mass Maintenance, the External Request Scenarios and the External Data Processing with an External Data Role functionalities are no longer supported and will be deprecated in a future release. Both of these features utilize External Data Email Account which is currently dependent on Transport Layer Security (TLS) version 1.0. This version of TLS is being disabled across major platforms, including AWS, Windows and Google, and mail servers are now requiring TLS 1.2 and above.

Since Mass Maintenance is no longer available to new Customers, and these two functionalities are not widely used by existing customers, per our Delivery stakeholders, we have opted to deprecate these functionalities rather than invest in the resources required to upgrade the Stewardship Tier to support TLS 1.2 or above.

New Features

Master Data Management

  • We added the New Task Creation Log button under the Default Configuration label of the Create New Task From Existing Table page and Create New Task From Integrate Template page. Clicking this button displays a page with these logs.

  • We added a new event to the Custom Business Rule configuration called PreFinish. This occurs when you click the Finish button on a request’s role before the Inherit Validation process is run. Refer to Add Custom Business Rules for more information.

  • We added a Mass Change Page Log button on the Category page's Vertical view to track the creation of pages and objects for a Category’s Mass Change page.

  • We added the Role Log button to the Request Role page. When clicked, the Request Role Log page displays a log of actions performed for a selected role in a request.


Master Data Management

  • We updated the process for capturing the Validation Error messages from the Validate event from using CR LF characters to separate the validation messages to using a vertical pipe symbol ‘|’. Users can now use the following function to turn the pipe delimited text into an HTML ordered list:

  • We added the Condition Check Log parameter on the Parameters page. When set to true, logging begins and the condition log is displayed on the Conditions page.

  • The Include All Org Units field is now available on the Category Org Unit Type page. If this value is set to True, the ‘*’ org unit value is added to be selected on the Positions pages. If the '*' value is selected for a Category Org Unit, it will add all the available org unit values within the category to all the roles or specific roles. This provides the ability to select all org unit values at one time.

  • We added the Finish Reject button to the Reject To Roles page. This allows you to create and process requests to complete the rejection for all rejected roles on this page.

  • We added a Condition Check Log on the Conditions page that displays detailed information about the condition check for requests. Additionally, we added the Condition Log button to the Archived Requests page, which displays a log of the archived requests.

  • The Instructions button has been added to the Request Role Task page. When clicked, the Task Instructions page displays. This button is only available when instructions are configured for the task.


  • We updated the order of operations of the Refresh Quality Console Jobs and Send Workflow service so that the table cleanup rule runs first and the table remains populated with the last set of workflow records.

  • When you use the apiSetRequestStatusWorkflow API procedure to cancel or delete a request, a workflow is triggered alerting the role owners and request submitters of the change in the Request status. If a role has no owners, all users in the role are alerted based on the Role Notification configuration for the position that has given them access to the request.

  • We added the Enforcement Status and Enforcement Priority fields to the Quality Console page's Horizontal view. These values are configured for the Quality Report in the SKP.

  • We added the Informational report status on the Mappings page. This status is for reports that are used indirectly for a remediation process and not directly mapped to an MDM Remediation.

Resolved Issues

Advanced Data Migration


Resolved an issue where the Target Sources (Update Row) page prevented the same table name being used for two different sources. [SST-235]

Master Data Management

  • Resolved an issue where a Custom Audit Detail view configured for a Role did not display as being used when that Role was added to a Scenario. [SST-211]

  • Resolved an issue with the Request Role chart where Dependency Complete roles were not the proper node color as shown in the chart legend. [SST-263]

  • Resolved an issue that resulted in the incorrect creation of child requests based on the dependencies between scenarios in the same Business Process. Now, child requests are created based on the priority and the completed dependent scenarios. [SST-308]

  • Resolved an issue where the order of scenarios in the Request Details chart did not reflect the priority order of the scenarios. [SST-314]

  • Updated the sorting indicator so that a point-up triangle indicates smallest value to largest value sorting (ascending sort) and a point-down triangle indicates largest value to smallest value sorting (descending sort). [SST-225]

  • We updated the Audit Details Importer process to include an evaluation to the service that prevents the job from running multiple times. Previously, if the import took longer than one minute, the same Audit detail records could be imported by two different runs of the service page. With the fix, the process prevents multiple imports of the same audit data. [SST-304]

  • The Inherit Validation popup logic has been updated so that GUID values in validation views are no longer shown in the result grid for the validation. Previously, this logic only prevented a few specific GUID values from appearing. [SST-310]

  • We updated an internal object, webRequestRole_WorkflowMessageParameterUpd, in order to maintain consistency across the platform. [SST-301]

Stewardship Tier


Resolved an issue where Collect did not use the SAP Max Pool Size parameter from the dspCommon Data Source Registry for RFC extracts. [SST-238]


  • Changes have been made to the Promote application in an effort to better support mixed collations in a table’s columns. Specifically, efforts have been made to support Case Sensitive Key Fields (e.g. SPRAS) used in databases where the Database Default collation was case insensitive. We strongly discourage mixed collations and suggest avoiding using non-default collations for table keys. [SST-71]

  • Resolved an issue with Promote Packages where changing the Data Set for an existing Package would leave invalid configuration used for the Comparison process. This resulted in warnings about data that did not exist in the Host and data loss in the Destination system if the Package fully processed. [SST-330]

  • Resolved an issue with how Promote determines a table’s primary key. Previously, if a table was created with a primary key that had a non-standard object name, the primary key was not always found during the comparison and promotion process. With the fix, tables created with a primary key with non-standard object names are being transported. [SST-276]

System Administration

Resolved an issue where users could not change their user settings information when their SST account password had expired, even when their account was set to use Windows Authentication. [SST-305]

Changes in Previous Versions

Previous Versions of Help

Help Build Date:December 27, 2023 10:05:37 AM