How To Fix FSBP_FND_INBOUND058 - Combination of addresses with and without ADDR_GUID is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: FSBP_FND_INBOUND -

• Message number: 058

• Message text: Combination of addresses with and without ADDR_GUID is not permitted

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 FSBP_FND_INBOUND058 - Combination of addresses with and without ADDR_GUID is not permitted ?

  The SAP error message FSBP_FND_INBOUND058 indicates that there is an issue with the combination of addresses being processed in the system. Specifically, it suggests that there is a mix of addresses that have an ADDR_GUID (Address Global Unique Identifier) and those that do not, which is not allowed in the context of the operation you are trying to perform.
  Cause:
  
  Inconsistent Address Data: The error typically arises when the system encounters a situation where some address records are linked to a GUID while others are not. This inconsistency can occur during data import or integration processes where address data is being processed.
  Data Mapping Issues: If you are importing data from an external system, there may be a mapping issue where some addresses are not being assigned a GUID correctly.
  Incorrect Configuration: There may be configuration settings in the SAP system that are not aligned with the expected data structure for addresses.
  
  Solution:
  
  Check Address Data: Review the address data being processed. Ensure that all addresses either have an ADDR_GUID or do not have one. You may need to clean up the data to ensure consistency.
  Data Import Process: If you are importing data, verify the mapping and transformation rules to ensure that addresses are being handled correctly. Make sure that the source data is consistent.
  Use of GUIDs: If your process requires the use of GUIDs, ensure that all addresses are assigned a GUID before processing. If GUIDs are not required, ensure that none of the addresses have them.
  Debugging: If you have access to debugging tools, you can trace the process to identify where the inconsistency is occurring. This may involve looking at the inbound data and how it is being processed.
  Consult Documentation: Refer to SAP documentation or notes related to address handling and the specific transaction or process you are working with. There may be specific guidelines or best practices to follow.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context on handling address data.
  Transaction Codes: Familiarize yourself with transaction codes related to address management in SAP, such as BP (Business Partner) or XD01 (Customer Creation).
  Data Quality Tools: Consider using data quality tools or features within SAP to validate and clean your address data before processing.
  
  By addressing the inconsistency in the address data and ensuring that all records conform to the expected format, you should be able to resolve the error message FSBP_FND_INBOUND058.