How To Fix EEDMIDESERVPROV067 - Second external ID &1 of cat. &2 not unique for all SPs of serv. type &3

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMIDESERVPROV - Service Provider Messages

• Message number: 067

• Message text: Second external ID &1 of cat. &2 not unique for all SPs of serv. type &3

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 EEDMIDESERVPROV067 - Second external ID &1 of cat. &2 not unique for all SPs of serv. type &3 ?

  The SAP error message EEDMIDESERVPROV067 indicates that there is a problem with the uniqueness of external IDs in the context of service provisioning. Specifically, the error states that the second external ID for a given category is not unique across all service providers of a specified service type.
  Cause:
  This error typically arises in scenarios where:
  
  Duplicate External IDs: There are multiple entries with the same external ID for the same category across different service providers.
  Configuration Issues: The configuration of service providers or the external IDs may not have been set up correctly, leading to conflicts.
  Data Migration Issues: If data has been migrated from another system, it may have introduced duplicates that violate the uniqueness constraint.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify Duplicates:
  
  Use transaction codes like SE16 or SE11 to check the relevant database tables (e.g., tables related to service provisioning) for duplicate external IDs.
  Query the database to find all entries with the same external ID and category.
  
  
  
  Correct the Data:
  
  If duplicates are found, you will need to either delete or modify the entries to ensure that each external ID is unique for the specified category and service type.
  Ensure that the external IDs are correctly assigned and do not overlap across different service providers.
  
  
  
  Review Configuration:
  
  Check the configuration settings for service providers and ensure that the external IDs are set up correctly.
  Make sure that the service types and categories are properly defined and that there are no overlaps.
  
  
  
  Test Changes:
  
  After making the necessary changes, test the configuration to ensure that the error no longer occurs.
  Perform any necessary validations to confirm that the data integrity is maintained.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to service provisioning and external IDs for any additional guidance or best practices.
  
  
  
  Related Information:
  
  Transaction Codes: SE16, SE11 (for data inspection), and possibly SPRO (for configuration).
  Tables: Depending on your specific implementation, you may need to look at tables related to service provisioning, external IDs, and service providers.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the steps you have already taken.