How To Fix RSM1673 - Can not delete Init for DS &1 from src.sys. &2; System copy is running

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 673

• Message text: Can not delete Init for DS &1 from src.sys. &2; System copy is running

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM1673 - Can not delete Init for DS &1 from src.sys. &2; System copy is running ?

  The SAP error message RSM1673 indicates that there is an issue with deleting an initialization (Init) for a DataSource (DS) because a system copy is currently running. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when you are trying to manage data sources and their initialization processes.
  Cause:
  The error is caused by an attempt to delete an initialization for a DataSource while a system copy operation is in progress. During a system copy, certain operations, including deletions or modifications of DataSources, are restricted to ensure data integrity and consistency.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check System Copy Status: Verify if a system copy is indeed running. You can do this by checking the system logs or monitoring transactions related to system copies.
  
  
  Wait for Completion: If a system copy is in progress, you will need to wait until it is completed. Once the system copy is finished, you should be able to delete the initialization without encountering this error.
  
  
  Review Locks: If you believe that the system copy has completed but you are still encountering the error, check for any locks that might be preventing the deletion. You can use transaction codes like SM12 to check for locks.
  
  
  Check for Background Jobs: Sometimes, background jobs related to data loading or initialization might be running. Use transaction SM37 to check for any active jobs that could be causing the issue.
  
  
  Consult Documentation: If the problem persists, refer to SAP documentation or support notes related to your specific version of SAP BW/BI for any additional troubleshooting steps or known issues.
  
  
  Contact SAP Support: If you are unable to resolve the issue on your own, consider reaching out to SAP support for assistance. Provide them with the error message and any relevant details about your system environment.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  RSA1: Data Warehousing Workbench
  SM12: Display and manage locks
  SM37: Monitor background jobs
  RSCUSTV10: Customizing for DataSources
  
  
  
  SAP Notes: Search for SAP Notes related to RSM1673 or system copy issues in the SAP Support Portal for any specific patches or updates that may address the problem.
  
  
  System Copy Documentation: Review SAP documentation on system copy procedures to understand the implications of running a system copy and how it affects DataSources and initializations.
  
  
  By following these steps, you should be able to address the RSM1673 error effectively.