Share your experience using Syniti Data Quality

Syniti Data Quality's use case is similar to what we do in SAP Information Steward. You can create a data quality report and your business Steward, which is more into cleansing the data. They will get the report about the quality of data and how many errors are in your report, and then you can go to your business Steward and ask them to fix those data errors.

You can only see the data and get the error report in SAP Information Steward. So, it is a read-only thing in SAP Information Steward. If you are using Syniti Data Quality, you can see the error and fix it by directly configuring Syniti Data Quality to write back to SAP. Syniti Data Quality allows you to update the source system.

In SAP Information Steward, you can't upgrade the source system. You can just see the data and go on to the source system manually by logging in to SAP, and then you have to fix those errors. With Syniti Data Quality, you can integrate SAP and directly fix errors from Syniti Data Quality instead of logging into SAP and then fixing them.

It would be good if Syniti Data Quality could integrate more AI in the future.

I have been using Syniti Data Quality for two years.

I rate Syniti Data Quality a nine out of ten for stability.

More than 250 users are using the solution in our organization.

I rate Syniti Data Quality an eight out of ten for scalability.

The solution's deployment is very quick and easy. Its integration with SAP is very good, and you won't find any issues with integration. The solution supports most of the ERPs and databases, which is a good thing.

On a scale from one to ten, where one is difficult, and ten is easy, I rate Syniti Data Quality an eight out of ten for the ease of its initial setup.

Syniti Data Quality can be deployed both on-premises and on the cloud.

Overall, I rate Syniti Data Quality ten out of ten.

We use it to migrate data to SAP. Both master and transactions data. We validate the data using the rules built in Syniti and then migrate it. We'll validate the data in both the legacy systems. Once the data has been moved, we'll run the rules in Syniti and then take reports on how the data is migrated to SAP.

We were using this as the migration tool. The data has been moved now. We'll be using the Syniti tool, and we'll be validating the quality of the data by using rules which were built in. 

We will be running the rules again as to the source data, and then the data will just be migrated to the target data. And preparing the reports and giving to the users how the data has been migrated. So that's how we've used it.

The predefined rules built into Syniti, the address validation, and the ease of migration.

Syniti has built-in 80%  of the solution, and we only need to customize 20 to 25% of the features. It is easy to run and pre-load reports. 

The customization of the data needs improvement. We need to build basic SQL queries rather than being able to do it within the tool. We need to be able to analyze the SQL queries and then rerun them based on customer usage.

We should be able to tune the existing process by using simple SQL queries based on the customer's requirements.

In future releases, I would like to see more features around Preload and postload reports. From the end-user point of view, it is not very feasible to read. 

I need to know how the data has been migrated. I need to know whether the complete data has been migrated, only the required data has been migrated, and how it was migrated.

So the postload reports will give validation between the source data and the target source. It would give exact picture of the data migration.

I have been using this solution for four years. 

I would rate the stability a nine out of ten. It is a stable solution. We didn't have any issues. We have been working with this solution from a long run now. 

I would rate the scalability a nine out of ten. Scalability is good. There are more than a hundred end users. 

Our customers are mostly medium enterprise businesses. 

We have to wait a little bit for the support to respond to our inquiries. However, once the communication channel is established, the support is good.

I would like to improve the response time for support inquiries

Neutral

The initial setup is not very difficult, but it's not easy either. 

We need to have a minimum understanding of SQL and the tool. If we have that basic understanding, then we can do it.

I would rate my experience with the initial setup of Xfinity Data Quality a seven out of ten, where one is difficult and ten is easy to set up. 

There is only a little bit of complexity because 80% of the customization is already there. We only need to customize 20 to 25%. 

The integration with SAP Data Services is easy. However, if it is not integrated with SAP Data Services, I would give it a nine out of ten. The integration with other services can be more difficult.

The deployment took approximately four to five hours. You need to have the database installed, then you need to review the space availability, and then you need to deploy the solution.

I would rate the pricing a six out of ten, where one is cheap, and ten is expensive.

The pricing depends on the workload and other factors. There are additional costs to the standard license. 

I would advise other users to carefully evaluate the specific requirements and choose the solution that best meets their needs.

Overall, I would rate the solution an eight out of ten because 80% of the data solutions are already provided. This means you can click and play, and then customize it according to your specific requirements.  

I've learned that the custom solutions we have built. You don't need to develop from scratch. Most of the tables are already mapped to SAP.

Most of the target tables are already configured. So, you only need to configure the switch and then push the data.