How To Fix /PLMI/CR_BO067 - Partner ID &1 does not exist. Change record not saved

/PLMI/CR_BO067 - Overview

• Message type: E = Error

• Message class: /PLMI/CR_BO -

• Message number: 067

• Message text: Partner ID &1 does not exist. Change record not saved

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 /PLMI/CR_BO067 - Partner ID &1 does not exist. Change record not saved ?

  The SAP error message /PLMI/CR_BO067 Partner ID &1 does not exist. Change record not saved typically occurs in the context of the SAP Product Lifecycle Management (PLM) module, particularly when dealing with change records or change management processes. This error indicates that the system is unable to find a partner ID that is required for the operation you are trying to perform.
  
  Cause:
  
  Non-Existent Partner ID: The partner ID specified in the change record does not exist in the system. This could be due to a typo, or the partner may not have been created yet.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables that store partner information.
  Authorization Issues: The user may not have the necessary authorizations to access the partner ID or related data.
  
  Configuration Issues: The configuration settings for partner management may not be set up correctly, leading to the inability to recognize