How To Fix EHPRC_CPM_BOMBOS059 - Cannot save identifier &1 / &2 to product &3

SAP Error Message - Details

• Message type: E = Error

• Message class: EHPRC_CPM_BOMBOS - Messages for BOMBOS Interface

• Message number: 059

• Message text: Cannot save identifier &1 / &2 to product &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 EHPRC_CPM_BOMBOS059 - Cannot save identifier &1 / &2 to product &3 ?

  The SAP error message EHPRC_CPM_BOMBOS059 typically indicates an issue related to the inability to save a specific identifier (like a batch, serial number, or other product-related identifier) to a product in the SAP system. This error can occur in various contexts, particularly in the areas of product lifecycle management (PLM) or materials management (MM).
  Possible Causes:
  
  Missing Authorizations: The user may not have the necessary permissions to save the identifier to the product.
  Data Integrity Issues: There may be inconsistencies or missing data in the product master data or related tables.
  Configuration Issues: The system configuration may not allow the saving of certain identifiers due to business rules or settings.
  Locked Records: The product or identifier may be locked by another transaction or user, preventing changes.
  Invalid Identifier: The identifier being saved may not conform to the expected format or may not exist in the system.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. This can be done by reviewing the user's roles and permissions in the SAP system.
  Validate Data: Check the product master data and ensure that all required fields are filled out correctly. Look for any inconsistencies or missing information.
  Review Configuration: Consult with your SAP configuration team to ensure that the system settings allow for the saving of the identifier. This may involve checking the relevant customizing settings in SPRO.
  Unlock Records: If the product or identifier is locked, identify the user or transaction that is holding the lock and resolve it. You can use transaction SM12 to check for and manage locks.
  Check Identifier Validity: Ensure that the identifier being saved is valid and exists in the system. If it’s a new identifier, verify that it has been created correctly.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like MM03 (Display Material), MM02 (Change Material), or SE11 (Data Dictionary) to investigate the product and identifier details.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Logs and Traces: Review application logs (transaction SLG1) or system logs (transaction SM21) for more detailed error messages or warnings that could provide further insights into the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.