How To Fix CPCL_VERS170 - BOM &1 cannot be used for successive versions

SAP Error Message - Details

• Message type: E = Error

• Message class: CPCL_VERS - Task List Version

• Message number: 170

• Message text: BOM &1 cannot be used for successive versions

What causes this issue?

The MBOM entered cannot be used for this routing version. This is
because, in customizing, the <ZK>Successive </>checkbox has been
selected in the version profile entered in the <ZK>Version Profile</>
field. In this case, only the latest released MBOM version and the
in-process MBOM version can be assigned to this routing.

System Response

The MBOM entered is not valid and the system issues an error message.

How to fix this error?

Select the latest released MBOM version or the in-process MBOM version.
Or, you can enter a different version profile in which the
<ZK>Successive</> option is not selected.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CPCL_VERS170 - BOM &1 cannot be used for successive versions ?

  The SAP error message CPCL_VERS170 indicates that a Bill of Materials (BOM) cannot be used for successive versions. This typically occurs when there are issues related to the versioning of the BOM in the system. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Versioning Issues: The BOM version you are trying to use may not be set up correctly for successive versions. This can happen if the BOM is not marked as a successive version or if the versioning settings are not configured properly.
  BOM Status: The BOM might be in a status that does not allow it to be used for successive versions. For example, it could be marked as obsolete or inactive.
  Configuration Settings: The configuration settings for BOM versioning in the system may not be aligned with the requirements for using successive versions.
  Data Inconsistencies: There may be inconsistencies in the data related to the BOM, such as missing or incorrect entries.
  
  Solution:
  
  
  Check BOM Versioning Settings:
  
  Go to the BOM transaction (e.g., CS02) and check the versioning settings for the BOM in question.
  Ensure that the BOM is marked as a successive version if that is required for your process.
  
  
  
  Review BOM Status:
  
  Check the status of the BOM. If it is marked as obsolete or inactive, you may need to activate it or create a new version of the BOM.
  
  
  
  Adjust Configuration Settings:
  
  Review the configuration settings for BOM versioning in the system. This may involve checking the settings in the customizing (SPRO) related to BOM management.
  
  
  
  Create a New Version:
  
  If the current version cannot be used, consider creating a new version of the BOM that meets the requirements for successive versions.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on BOM versioning and the requirements for using successive versions.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  BOM Management: Understanding how BOMs are managed in SAP, including versioning, statuses, and the implications of different settings.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CS01 (Create BOM), CS02 (Change BOM), and CS03 (Display BOM).
  SAP Notes: Check for any SAP Notes related to BOM versioning issues that may provide additional insights or fixes.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.