How To Fix /ISDFPS/MM174 - Releases for purchase requisition &1 &2 were reset

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/MM -

• Message number: 174

• Message text: Releases for purchase requisition &1 &2 were reset

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 /ISDFPS/MM174 - Releases for purchase requisition &1 &2 were reset ?

  The SAP error message /ISDFPS/MM174 Releases for purchase requisition &1 &2 were reset typically occurs in the context of the SAP Materials Management (MM) module, particularly when dealing with purchase requisitions (PRs) and their release strategies.
  Cause:
  This error message indicates that the release (approval) status of a purchase requisition has been reset. This can happen for several reasons, including:
  
  Manual Reset: A user with the appropriate authorization may have manually reset the release status of the purchase requisition.
  Release Strategy Changes: Changes in the release strategy configuration or the criteria for release may lead to the resetting of the release status.
  Document Changes: If there are changes made to the purchase requisition (like changes in item details, account assignment, etc.), it may trigger a reset of the release status.
  Workflow Issues: If the purchase requisition is part of a workflow, issues in the workflow process can also lead to this error.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Check Release Status: Verify the current release status of the purchase requisition using transaction codes like ME53N (Display Purchase Requisition) or ME54N (Release Purchase Requisition).
  Review Changes: Investigate any recent changes made to the purchase requisition that might have triggered the reset. This includes checking for changes in item details, account assignments, or any other relevant fields.
  Release Strategy Configuration: If the release strategy has been modified, ensure that the changes are correctly configured and that they align with the business requirements.
  User Authorization: Ensure that the user attempting to release the purchase requisition has the necessary authorizations to do so.
  Consult Logs: Check the system logs for any additional error messages or warnings that might provide more context on why the release was reset.
  Re-release the PR: If the issue is resolved, you may need to re-release the purchase requisition using the appropriate transaction.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME53N (Display PR), ME54N (Release PR), and ME55 (Collective Release).
  Release Strategy Documentation: Review the documentation for the release strategy configuration in your SAP system to understand how it is set up and what might affect the release status.
  SAP Notes: Check for any SAP Notes related to this error message for potential bug fixes or additional guidance.
  User Training: Ensure that users involved in the purchase requisition process are adequately trained on the release process and the implications of changes to PRs.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the MM module for further assistance.