How To Fix PMEVC_UI138 - BOM in prod. version &1 does not exist: using BOM appl. for BOM selection

SAP Error Message - Details

• Message type: E = Error

• Message class: PMEVC_UI -

• Message number: 138

• Message text: BOM in prod. version &1 does not exist: using BOM appl. for BOM selection

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 PMEVC_UI138 - BOM in prod. version &1 does not exist: using BOM appl. for BOM selection ?

  The SAP error message PMEVC_UI138 indicates that there is an issue with the Bill of Materials (BOM) in the production version you are trying to access. Specifically, it states that the BOM for the specified production version does not exist. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing BOM: The BOM for the specified production version is not created or has been deleted.
  Incorrect Production Version: The production version you are trying to use may not be correctly assigned to the material or may not exist in the system.
  Data Inconsistency: There may be inconsistencies in the master data, such as the material master or BOM master data.
  Authorization Issues: The user may not have the necessary authorizations to view or access the BOM for the specified production version.
  
  Solutions:
  
  
  Check BOM Existence:
  
  Go to transaction CS03 (Display BOM) and check if the BOM exists for the material and the specified production version.
  If it does not exist, you may need to create it using transaction CS01 (Create BOM).
  
  
  
  Verify Production Version:
  
  Use transaction C223 (Maintain Production Versions) to check if the production version is correctly assigned to the material.
  Ensure that the production version is active and correctly linked to the BOM.
  
  
  
  Create or Update BOM:
  
  If the BOM is missing, create a new BOM for the material using transaction CS01.
  If the BOM exists but is not linked to the correct production version, you may need to update the production version settings.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the BOM and production version data. This may involve checking user roles and permissions.
  
  
  
  Data Consistency Check:
  
  Run consistency checks for the material master and BOM data to identify any discrepancies. This can be done using transaction C223 or other relevant tools.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to BOM and production versions for any specific guidelines or known issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  CS01: Create BOM
  CS02: Change BOM
  CS03: Display BOM
  C223: Maintain Production Versions
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to BOM and production versions.
  User Roles: Ensure that the user has the appropriate roles assigned in the SAP system to access BOM-related transactions.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it. If the issue persists, consider reaching out to your SAP support team for further assistance.