Do you have any question about this error?
Message type: E = Error
Message class: RSAR - Data Transfer and Metadata Maintenance
Message number: 670
Message text: Source system cannot be deleted in Content system
If a source system is deleted in the Content system, the shadow tables
for all source system-dependent objects for this source system release
are also deleted. You can configure a user as a non-Content user by
using a SET-GET parameter. You can then use this user to delete the
system, and then the above-named objects are not changed during
deletion.
The function is completed.
Logon as user ACTIVATE, and repeat your actions.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
RSAR670
- Source system cannot be deleted in Content system ?The SAP error message RSAR670 indicates that a source system cannot be deleted in the Content system. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BW/4HANA when you are trying to remove a source system that is still being referenced or has dependencies in the system.
Cause:
- Active Data Flow: The source system may still be involved in active data flows, such as data extraction or transformation processes.
- Open Requests: There may be open data requests or data loads that are still referencing the source system.
- Dependencies: Other objects, such as InfoProviders, DataSources, or InfoPackages, may still be linked to the source system.
- Authorization Issues: Lack of proper authorizations to delete the source system can also lead to this error.
Solution:
To resolve the RSAR670 error, you can follow these steps:
Check Dependencies:
- Use transaction
RSA1
(Data Warehousing Workbench) to check if there are any active data flows or dependencies related to the source system.- Look for any DataSources, InfoProviders, or InfoPackages that are still linked to the source system.
Deactivate or Delete Related Objects:
- If you find any active data flows or dependencies, deactivate or delete them before attempting to delete the source system.
- Ensure that there are no open requests or data loads that are still referencing the source system.
Check for Open Requests:
- Use transaction
RSA3
to check for any open requests related to the source system. If there are any, you may need to process or delete them.Authorization Check:
- Ensure that you have the necessary authorizations to delete the source system. You may need to consult with your SAP security team if you suspect authorization issues.
Use Transaction
RSC1
:
- If you are sure that there are no dependencies, you can try to delete the source system using transaction
RSC1
(Source System Maintenance).Consult SAP Notes:
- Check for any relevant SAP Notes that may provide additional guidance or patches related to this error.
Related Information:
By following these steps, you should be able to identify the cause of the RSAR670 error and take appropriate actions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RSAR669
Port description contains errors: Incorrect destination &1
What causes this issue? Destination &V1& is defined in port &V2&. However, destination &V3& is stored in BW.System Response ...
RSAR668
Source system & not of type file or external system
What causes this issue? Source system &V1& is neither a file system nor an external system.System Response The source system is not imported...
RSAR671
Source system release &1 is not the same as local information &2
What causes this issue? The replicated system information (table RSBASIDOC) indicates that syste m &V& has Basis Release &V&. However...
RSAR672
No metadata upload since upgrade
What causes this issue? DataSource replication has not been performed since the source system up grade&V1&.System Response The Content that ...
Click on this link to search all SAP messages.