Do you have any question about this error?
Message type: E = Error
Message class: RSAU - Update rules
Message number: 323
Message text: Unprocessed data records discovered
When attempting to remove a lock for characteristic &V1&, it was
established that table &V2& does not yet contain processed data
records.
Tables:
M : Master data table
T : Text table
This points to a previous loading process that was canceled and
temporary data records in table &V2& of characteristic &V1& that has
not been deleted.
The System canceled the loading process in order to avoid
inconsistencies.
Using the master data utility delete the temporary records from the
corresponding table and restart the process.
Error message extract from SAP system. Copyright SAP SE.
RSAU323
- Unprocessed data records discovered ?The SAP error message RSAU323, which states "Unprocessed data records discovered," typically occurs in the context of the SAP system's data processing, particularly when dealing with data extraction or data transfer processes. This error indicates that there are records in the data source that have not been processed successfully.
Causes:
- Data Quality Issues: The records may contain invalid or incomplete data that prevents them from being processed.
- Configuration Errors: Incorrect settings in the data extraction or transfer configuration can lead to unprocessed records.
- System Performance: If the system is under heavy load, it may not be able to process all records in a timely manner.
- Authorization Issues: Lack of proper authorizations for the user or process trying to access or process the data.
- Technical Errors: Bugs or issues in the SAP system or the specific data processing program can lead to unprocessed records.
Solutions:
- Check Data Quality: Review the records that are unprocessed to identify any data quality issues. Correct any invalid or incomplete data.
- Review Configuration: Ensure that the configuration settings for the data extraction or transfer process are correct. This includes checking the source and target system settings.
- Monitor System Performance: Check the system performance and load. If the system is under heavy load, consider scheduling the data processing during off-peak hours.
- Check Authorizations: Verify that the user or process has the necessary authorizations to access and process the data.
- Review Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into why the records were not processed.
- Reprocess Records: After addressing the underlying issues, attempt to reprocess the unprocessed records. This can often be done through the same transaction or program that initially processed the data.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
RSAU322
Internal error when trying to set a lock
What causes this issue? An internal error occurred when attempting to set a lock. Here we are dealing with the table &V2& of characteristic &...
RSAU321
<- End import postprocessing update of master data (attributes)
What causes this issue? System Response After all data records for a request have been saved in a temporary version in the master data table, then re...
RSAU324
No access permission as table is already locked
What causes this issue? The attempt to lock table &V2& in characteristic &V1& failed, because the table is already locked by another ...
RSAU325
-> Start import postprocessing update of texts
What causes this issue? System Response After all data records for a request have been saved in a temporary version in the text table, reprocessing o...
Click on this link to search all SAP messages.