How To Fix /PLMI/RCA_CALC063 - You selected "GSS Recipe to BOM"; calc. class will not be considered

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/RCA_CALC -

• Message number: 063

• Message text: You selected "GSS Recipe to BOM"; calc. class will not be considered

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/RCA_CALC063 - You selected "GSS Recipe to BOM"; calc. class will not be considered ?

  The SAP error message /PLMI/RCA_CALC063 indicates that there is an issue related to the selection of a "GSS Recipe to BOM" (Bill of Materials) in the context of a calculation class. This error typically arises in the SAP PLM (Product Lifecycle Management) module, particularly when dealing with recipes and their integration with BOMs.
  Cause:
  The error message is triggered when the system detects that a calculation class is not applicable or relevant for the selected GSS (Generic Substitution Strategy) recipe to BOM. This can happen due to several reasons, including:
  
  Incompatibility: The selected recipe may not be compatible with the calculation class you are trying to use.
  Configuration Issues: There may be configuration settings in the system that prevent the calculation class from being applied to the selected recipe.
  Missing Data: Required data or settings for the calculation class may be missing or incorrectly set up in the system.
  Incorrect Selection: The user may have selected an inappropriate recipe or BOM that does not align with the expected calculation class.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Recipe and BOM Compatibility:
  
  Ensure that the selected GSS recipe is compatible with the calculation class you intend to use. Review the documentation or configuration settings related to the recipe and BOM.
  
  
  
  Review Configuration Settings:
  
  Check the configuration settings in the SAP system for the calculation class and ensure that it is set up correctly to work with GSS recipes.
  
  
  
  Validate Data:
  
  Ensure that all necessary data for the recipe and BOM is correctly maintained. This includes checking for any missing or incorrect entries in the master data.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details about the calculation class and its intended use with recipes and BOMs.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance. They may provide insights based on system logs or specific configurations.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide updates and patches.
  Transaction Codes: Familiarize yourself with transaction codes related to PLM, recipes, and BOMs, such as C201 (Create Recipe) or CS01 (Create BOM).
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.