Do you have any question about this error?
Message type: E = Error
Message class: RSAR - Data Transfer and Metadata Maintenance
Message number: 672
Message text: No metadata upload since upgrade
DataSource replication has not been performed since the source system up
grade&V1&.
The Content that is assigned to this source system is obsolete.
Refresh the metadata completely for this source system.
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.
RSAR672
- No metadata upload since upgrade ?The SAP error message RSAR672 "No metadata upload since upgrade" typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with the metadata synchronization between the source system and the BW system after an upgrade. This error indicates that the system has not been able to upload the necessary metadata from the source system since the last upgrade.
Cause:
- Upgrade Issues: The upgrade process may not have completed successfully, leading to inconsistencies in metadata.
- Missing or Incomplete Metadata: The metadata required for the data transfer might be missing or incomplete.
- Configuration Issues: There may be configuration issues in the source or target system that prevent the metadata from being uploaded.
- Transport Issues: If the transport of metadata was not executed properly, it could lead to this error.
- Authorization Issues: Lack of proper authorizations for the user performing the metadata upload can also cause this error.
Solution:
- Check Upgrade Logs: Review the upgrade logs to identify any issues that occurred during the upgrade process. Resolve any errors found.
- Re-upload Metadata: You can try to re-upload the metadata manually. This can be done using transaction codes like RSA1 (Data Warehousing Workbench) and navigating to the relevant InfoObjects or DataSources.
- Check Source System Connection: Ensure that the connection to the source system is correctly configured and that the source system is accessible.
- Run Metadata Synchronization: Use the transaction code RSA1 to run the metadata synchronization process. This can help in refreshing the metadata.
- Check Authorizations: Ensure that the user has the necessary authorizations to perform metadata uploads.
- Transport Requests: If the metadata was supposed to be transported, check the transport requests to ensure they were imported correctly.
- SAP Notes: Check for any relevant SAP Notes that may address this specific issue. SAP frequently releases notes that provide fixes or workarounds for known issues.
Related Information:
By following these steps, you should be able to diagnose and resolve the RSAR672 error effectively.
Get instant SAP help. Start your 7-day free trial now.
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...
RSAR670
Source system cannot be deleted in Content system
What causes this issue? If a source system is deleted in the Content system, the shadow tables for all source system-dependent objects for this sourc...
RSAR673
Destination &1 has incorrect Unicode setting; adjust it to destination
What causes this issue? The Unicode settings for destination &V1& do not match the source system.System Response Conversion errors might occ...
RSAR674
InfoObject catalog was updated
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.