How To Fix 42120 - The release already exists

SAP Error Message - Details

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 120

• Message text: The release already exists

What causes this issue?

You entered the same release repeatedly, but referred to different
Basis releases.

System Response

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

How to fix this error?

Check your entries.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 42120 - The release already exists ?

  The SAP error message "42120: The release already exists" typically occurs in the context of managing release strategies in SAP, particularly when dealing with purchase requisitions, purchase orders, or other documents that require approval workflows. This error indicates that an attempt is being made to create or assign a release strategy that already exists for the specified document.
  Cause:
  
  Duplicate Release Strategy: The most common cause is that the release strategy you are trying to assign or create is already defined in the system for the same document type or criteria.
  Incorrect Document Status: The document may already be in a status that has an existing release strategy applied to it.
  Configuration Issues: There may be issues in the configuration of the release strategy in the system, leading to conflicts.
  
  Solution:
  
  
  Check Existing Release Strategies: 
  
  Navigate to the relevant transaction (e.g., ME28 for purchase orders) and check if the release strategy is already assigned to the document.
  Use transaction codes like ME53N (Display Purchase Requisition) or ME23N (Display Purchase Order) to view the current release status.
  
  
  
  Review Release Strategy Configuration:
  
  Go to the configuration settings for release strategies (transaction code SPRO -> Materials Management -> Purchasing -> Release Procedure).
  Ensure that the release strategy is correctly defined and that there are no duplicates.
  
  
  
  Adjust Document Status:
  
  If the document is already released, you may need to change its status or revert it to a previous state before attempting to apply a new release strategy.
  
  
  
  Consult with SAP Basis or Functional Team:
  
  If you are unable to resolve the issue, it may be beneficial to consult with your SAP Basis or functional team for further investigation into the configuration and system settings.
  
  
  
  Related Information:
  
  Documentation: Refer to SAP Help documentation for detailed information on release strategies and their configuration.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME28 (Release Purchase Orders), ME52N (Change Purchase Requisition), and ME53N (Display Purchase Requisition).
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may address the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.