CDQ Data Quality as Service
Idea Portal
Idea Portal
Idea Portal
Currently, after Curation, the customer receives a response that requires manual interpretation to understand whether changes occurred in the dataset. The customer needs optimized logic to automatically indicate whether changes in the address data were substantive (content-related) or merely formatting changes.
Efficient evaluation of API responses to significantly reduce manual effort. The customer's internal logic should not have to individually verify each dataset for changes. Instead, it should rely on an explicit, easy-to-understand response code from the API.
Initially, consider using SAP's existing "Assignment Codes" documented here. If the existing Assignment Codes do not fully meet the requirements, then introduce the following custom status codes within the SAP DQM API (Curation) response payload:
Response Code |
Description |
|
Input and output data are identical; no changes, not even formatting |
|
Input and output data are identical in content, but formatting changes were applied |
|
Input and output data differ in actual content |
|
Data is correct and valid |
|
Data contains errors or inconsistencies and is invalid |
|
The address sent in the request was blank. No cleansed address is returned. |
Reduced manual effort for the customer
Efficient and automated processing of API responses
Clear and quick assessment of changes made
Faster processing of mass data, as only datasets with actual content changes require manual review
