Do you have any question about this error?
Message type: E = Error
Message class: RSL_UI -
Message number: 321
Message text: &1 rows have been cleansed
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
RSL_UI321
- &1 rows have been cleansed ?The SAP error message RSL_UI321 indicates that a certain number of rows have been cleansed during a data processing operation, typically related to data quality or data cleansing tasks. This message is often encountered in the context of SAP Data Services or SAP Information Steward, where data is being validated, transformed, or cleansed.
Cause:
The message indicates that the system has identified and removed or modified rows of data that did not meet certain quality criteria. This could be due to various reasons, such as:
To address the RSL_UI321 message, consider the following steps:
Review the Cleansing Rules: Check the data cleansing rules that are applied to the dataset. Ensure that they are appropriate for the data you are processing.
Analyze the Cleansed Data: Look into the details of the rows that were cleansed. This may involve checking logs or reports generated by the data processing job to understand why those rows were affected.
Adjust Data Quality Rules: If the cleansing rules are too strict or not aligned with your business requirements, consider adjusting them to allow more data to pass through without being cleansed.
Data Validation: Ensure that the data being input into the system is validated before processing. This can help reduce the number of rows that are cleansed.
Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the cleansing process and how to interpret the cleansing results.
Testing: After making adjustments, run tests with a sample of your data to see if the changes have the desired effect.
If the issue persists or if you need more specific guidance, consider reaching out to SAP support or consulting with a data management expert familiar with your specific SAP environment.
Get instant SAP help. Start your 7-day free trial now.
RSL_UI320
&1 rows have been loaded
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSL_UI316
Provider &1 cannot be used in workspace &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSL_UI322
Data has been appended
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSL_UI323
Last Editing Tool: &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.