How To Fix 61144 - Purchase requisition has not yet been released

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 144

• Message text: Purchase requisition has not yet been released

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 61144 - Purchase requisition has not yet been released ?

  The SAP error message 61144, which states "Purchase requisition has not yet been released," typically occurs when a purchase requisition (PR) is in a status that prevents it from being processed further, such as creating a purchase order (PO) or performing other actions that require the PR to be released.
  Cause:
  
  Release Strategy Not Met: The purchase requisition may be subject to a release strategy that has not been fulfilled. This means that the necessary approvals have not been obtained.
  Incomplete Data: The PR may be missing required information or may not meet the criteria set in the release strategy.
  User Authorization: The user attempting to process the PR may not have the necessary authorizations to release it.
  Status of the PR: The PR might be in a status that does not allow it to be released, such as being blocked or in a draft state.
  
  Solution:
  
  Check Release Status: Verify the release status of the purchase requisition. You can do this by navigating to the PR in the SAP system and checking its status. If it is not released, you will need to follow the release process.
  Complete Required Approvals: If the PR is subject to a release strategy, ensure that all necessary approvals are obtained. This may involve contacting the relevant approvers.
  Review PR Data: Ensure that all required fields in the purchase requisition are filled out correctly. Check for any missing or incorrect information that might prevent the release.
  User Authorization: Confirm that you have the necessary permissions to release the PR. If not, contact your SAP administrator to obtain the required access.
  Consult with Procurement Team: If you are unsure about the release strategy or the process, consult with your procurement or purchasing team for guidance.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like ME53N (Display Purchase Requisition) to view the details of the PR and its status.
  Release Strategy Configuration: If you are involved in the configuration of the release strategy, you may need to review the settings in the customizing transaction (SPRO) under Materials Management > Purchasing > Purchase Requisition > Release Procedure for Purchase Requisitions.
  Documentation: Refer to SAP documentation or help files for more detailed information on release strategies and purchase requisition processing.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.