Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SM - Address Definition/Administration
Message number: 813
Message text: Data inconsistency, address & in table SADRP. Change not possible
System data inconsistency, probably caused by a transport. The address
number &V1& is used as a key in both table SADR and SADRP. This is not
allowed.
The System can not change the address &V1&
The OSS note 25182 describes how to solve the problem.
This information is available in the System in the general text
ADDRESS_TRANSPORT_INFO.
The program RSADRNNR can be used as a repair program (follow the
program documentation carefully!).
Error message extract from SAP system. Copyright SAP SE.
SM813
- Data inconsistency, address & in table SADRP. Change not possible ?The SAP error message SM813 indicates a data inconsistency issue related to address data in the table SADRP (which stores address data for various entities in SAP). This error typically arises when there is a mismatch or inconsistency in the address data that prevents changes from being made.
Cause:
- Data Inconsistency: The most common cause is that the address data in the SADRP table is inconsistent with other related tables or with the business logic defined in the system.
- Locked Entries: The entry you are trying to change may be locked by another process or user.
- Missing or Incorrect Data: Required fields may be missing or contain incorrect data that violates data integrity rules.
- Custom Enhancements: Custom code or enhancements may be interfering with standard processing.
Solution:
Check Data Consistency:
- Use transaction codes like SE16 or SE11 to view the SADRP table and check for inconsistencies.
- Compare the data in SADRP with related tables (like ADRC for general address data) to ensure consistency.
Review Lock Entries:
- Use transaction SM12 to check for any lock entries that might be preventing changes to the address data.
- If you find locks that are no longer needed, you can delete them (ensure you have the necessary authorizations).
Correct Data:
- If you identify any missing or incorrect data, correct it directly in the relevant tables or through the appropriate transaction.
- Ensure that all mandatory fields are filled out correctly.
Check for Custom Code:
- If there are custom enhancements or modifications, review them to ensure they are not causing the issue.
- Consult with your ABAP team if necessary.
Use Transaction Codes:
- Use transaction code
SAD1
to display address data and check for any inconsistencies.- Use transaction code
SAD2
to change address data if applicable.Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or related issues.
Contact SAP Support:
- If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the issue causing the SM813 error message in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
SM812
Define at least one field
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SM811
No selection made
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SM02000
Counter set to value &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SM02001
Client list could not be obtained
All the clients in this system are listed in table T000. Your selection in this table did not work.Error message extract from SAP system. Copyright S...
Click on this link to search all SAP messages.