CDQ Data Quality as Service

As a PowerUser or Bureaucrat, I would like to view the LastLoginDate of users to better understand their activity and usage of the CDQ Services. This information would also be valuable for managing and cleaning up CDQ access, as an extended period...

The postal code in NL has 4 digits and 2 letter, with a space in between (format: NNNN AA). External reference data sources maintain the postal code sometimes with and sometimes without the blank space. The BP Lookup performs an exact search for t...

Both Apps (Batch Business Partner Curation and Batch Address Curation) allow to select the same configuration, the job behind is likely identical because it uses the same API. However, if I want to get the address curation report I have to start a...

Please consider adding Names of the address fields so that "Value" is replaced by "City", "Region" etc. in FTR. With the current setup, it is not super user friendly when a user performs manual validation of a Business Partners' data without seein...

As a DSC member, I want to be able to manage the users and their roles. Today I only see: Name, Email, number of roles. If I have 50+ users, I don't want to click on every user to find out, which role it has. Tomorrow I want to see: Name, Organiza...

Please consider adding Business Partner’s international name into Response Results. By doing this the process of verifying Response result for Business Partners with Local Name and International Name could be significantly improved. Thank you. Ann...

For "one ID concepts" or "common supplier/customer concepts" expecially in organisations with fragmented system landscapes it would be beneficial to know where and in which source an existing business partner record is stored. The idea is, during ...

The current framework in the data mirror for mapping general data of business partners to the CDQ data model reflects the R3 customer/vendor data model (flat table, STCD1-4, STCEG). It would be nice to provide the option of mapping multiple tables...

Currently maintaining a validation configuration is cumbersome, because each rule has to be selected individually, there is not sufficient filtering/grouping possibilities and it is hard to identify newly released rules or any other change to the ...

We drastically increase the number of jobs in DQaaS. At some point however, it is no more possible, directly in the app, to directly visualize the source and its corresponding jobs and reports. You must deep dive in a report and look at the source...