How To Fix W5018 - No purchase requisitions can be released with release code &

SAP Error Message - Details

• Message type: E = Error

• Message class: W5 - Messages for MM-WEB Applications and BAPIs

• Message number: 018

• Message text: No purchase requisitions can be released with release code &

What causes this issue?

Release code &V1& is not used in any <DS:GLOS.release_strategy>release
strategy</> for purchase requisitions. The release strategy is defined
in Customizing for Purchasing.

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?

Enter a release code that occurs in a release strategy for purchase
requisitions.
&WHAT_TO_DO& (system administrator)
Check the customizing settings for the release procedure:
<DS:SIMG.OLMEOMGQ>Set up procedure with classification</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message W5018 - No purchase requisitions can be released with release code & ?

  Certainly! Here's detailed information about the SAP error message W5018: "No purchase requisitions can be released with release code &":
  
  Error Message:
  W5018
  
  Text: No purchase requisitions can be released with release code &
  
  Cause:
  This warning message occurs during the release (approval) process of purchase requisitions (PRs) in SAP MM when the system cannot find any purchase requisitions that match the specified release code for release.
  Common reasons include:
  
  
  Incorrect Release Code:
  
  The release code entered or used in the release strategy does not correspond to any purchase requisitions currently waiting for release.
  
  
  No PRs Assigned to the Release Code:
  
  There are no purchase requisitions assigned to the release code in question, either because none have been created or none are currently in the release status that requires this release code.
  
  
  Release Strategy Not Properly Configured:
  
  The release strategy might not be correctly set up, or the release code is not assigned to any release strategy or release indicator.
  
  
  User Authorization Issues:
  
  The user trying to release the PRs may not have the authorization to release PRs with the specified release code.
  
  
  PRs Already Released or Blocked:
  
  The purchase requisitions might have already been released or are blocked, so they do not appear as releasable with the given release code.
  
  
  
  Solution:
  To resolve the issue, consider the following steps:
  
  
  Verify the Release Code:  
  
  Check the release code entered during the release process.  
  Ensure it is correct and corresponds to the release strategy configured for the purchase requisitions.
  
  
  
  Check Release Strategy Configuration:  
  
  Go to transaction SPRO ? Materials Management ? Purchasing ? Purchase Requisition ? Release Procedure ? Set Up Release Procedure for Purchase Requisitions.  
  Verify that the release code is assigned to the correct release strategy and release indicators.
  
  
  
  Check Purchase Requisitions Status:  
  
  Use transaction ME53N or ME55 to check the status of the purchase requisitions.  
  Confirm that there are PRs waiting for release with the specified release code.
  
  
  
  Check User Authorizations:  
  
  Ensure the user has the necessary authorizations to release PRs with the given release code.  
  Authorization objects related to release codes include M_EINK_FRG.
  
  
  
  Check if PRs are Blocked or Already Released:  
  
  Confirm that the PRs are not blocked or already fully released.
  
  
  
  Use Correct Transaction for Release:  
  
  Use transaction ME54N (Release Purchase Requisition) or ME55 (Collective Release) properly, ensuring the release code is correctly entered.
  
  
  
  
  Additional Information:
  
  
  Release Codes:
  
  Release codes are part of the release strategy and represent different levels or types of approval required for purchase requisitions.
  
  
  Release Strategy:
  
  The release strategy is a configuration that defines how purchase requisitions are approved based on criteria such as value, material group, plant, etc.
  
  
  Collective Release:
  
  When releasing multiple PRs collectively (e.g., via ME55), the system filters PRs by release code. If none match, this warning appears.
  
  
  Message Class:
  
  The message class for this warning is usually W5.
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error
  W5018 - No purchase requisitions can be released with release code &
  
  
  Cause
  No PRs found for the release code entered; incorrect release code; no PRs assigned; authorization issues
  
  
  Solution
  Verify release code, check release strategy setup, confirm PR status, check user authorizations, use correct transactions
  
  
  Transactions
  ME54N, ME55, ME53N, SPRO (for config)
  
  
  
  
  If you need help with specific steps or transaction codes, feel free to ask!