How To Fix R7B643 - External UUID key deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: R7B - BW Metadata (InfoCube, InfoObject, InfoObject catalog)

• Message number: 643

• Message text: External UUID key deleted

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 R7B643 - External UUID key deleted ?

  The SAP error message R7B643 "External UUID key deleted" typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when there is an issue related to the UUID (Universally Unique Identifier) that is used to identify objects in the system. This error can arise during data extraction, loading, or processing when the system cannot find the expected UUID for a particular object.
  Causes:
  
  Deleted Objects: The UUID associated with a data object (like a DataSource, InfoObject, or InfoProvider) has been deleted or is no longer valid.
  Data Consistency Issues: There may be inconsistencies in the metadata or data model, possibly due to manual deletions or changes in the system.
  Transport Issues: If objects were transported between systems (e.g., from development to production), the UUIDs may not match or may have been lost during the transport process.
  System Upgrades or Changes: Changes in the system configuration or upgrades may lead to UUID mismatches.
  
  Solutions:
  
  Check Object Existence: Verify that the object associated with the UUID still exists in the system. If it has been deleted, you may need to recreate it or restore it from a backup.
  Recreate UUID: If the object is missing, you may need to recreate it, which will generate a new UUID.
  Consistency Check: Run consistency checks on the data model to identify and resolve any inconsistencies. This can often be done using transaction codes like RSA1 (for BW) or relevant tools in HANA.
  Transport Management: If the issue arose after a transport, check the transport logs and ensure that all necessary objects were included in the transport request.
  System Logs: Review system logs (transaction SLG1) for additional details that may provide context for the error.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSCUSTV10 (for customizing BW settings), and SLG1 (Application Log).
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Documentation: Review SAP documentation related to BW and HANA for best practices on managing UUIDs and object dependencies.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.