How To Fix RSDMD104 - Unprocessed new records in table &

RSDMD104 - Overview

• Message type: E = Error

• Message class: RSDMD - Messages for master data

• Message number: 104

• Message text: Unprocessed new records in table &

What causes this issue?

A lock should be set on table &V1&. However, before setting the lock it
was determined that unprocessed, new records exist in the table. It is
for this reason that the lock to table &V1& was not carried out.
The records found possibly come from a previous update that has been
terminated. Further processing would lead to inconsistent data in table
&V1&.

System Response

The lock cannot be set.

How to fix this error?

Delete the unprocessed new records from table &V1& and restart the
process that was terminated by the lock management. In order to delete
the unprocessed new records from the table use the delete function in
the Monitor.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDMD104 - Unprocessed new records in table & ?

  The SAP error message RSDMD104 indicates that there are unprocessed new records in a specific table, which typically relates to issues in the data loading process in SAP BW (Business Warehouse). This error can occur during the data extraction, transformation, and loading (ETL) process when new records are not processed correctly.
  
  Cause:
  
  Data Load Issues: The most common cause is that the data load process has encountered an error, preventing new records from being processed.
  Data Source Configuration: There may be issues with the configuration of the data source or the InfoPackage that is responsible for loading the data.
  Data Quality Issues: The incoming data may have quality issues, such as missing mandatory fields or incorrect data formats.
  Delta Load Problems: If you are using delta loads, there may be issues with the delta mechanism, causing new records to be missed.
  Locking Issues: There may be locks on the data that prevent processing.
  
  
  Solution:
  
  Check the Data Load