How To Fix V1797 - There is no purchase requisition for the selected schedule line

SAP Error Message - Details

• Message type: E = Error

• Message class: V1 - Verkaufsbelegbearbeitung

• Message number: 797

• Message text: There is no purchase requisition for the selected schedule line

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 V1797 - There is no purchase requisition for the selected schedule line ?

  The SAP error message V1797, "There is no purchase requisition for the selected schedule line," typically occurs in the context of sales and distribution (SD) when trying to process a sales order that references a schedule line without an associated purchase requisition. This can happen in scenarios where the system expects a purchase requisition to be created for the items in the sales order, particularly when dealing with stock transport orders or intercompany processes.
  Causes:
  
  Missing Purchase Requisition: The most common cause is that there is no purchase requisition created for the schedule line in question.
  Incorrect Configuration: The configuration settings in the system may not be set up correctly to allow for the creation of purchase requisitions for the relevant sales order types.
  Document Flow Issues: There may be issues in the document flow where the purchase requisition was not generated due to prior errors or missing data.
  Material Availability: The material may not be available in stock, leading to the system not generating a purchase requisition automatically.
  
  Solutions:
  
  Create a Purchase Requisition: Manually create a purchase requisition for the relevant schedule line if it is missing. This can be done through transaction codes like ME51N (Create Purchase Requisition).
  Check Configuration: Review the configuration settings in the SAP system related to sales order processing and purchase requisition generation. Ensure that the relevant settings are correctly configured.
  Review Document Flow: Check the document flow for the sales order to identify any issues that may have prevented the purchase requisition from being created. You can use transaction code VA03 (Display Sales Order) to review the document flow.
  Check Material Availability: Ensure that the material is available in stock or that the system is set up to create purchase requisitions when stock is not available.
  Consult with SAP Support: If the issue persists, consider reaching out to your SAP support team or consulting SAP notes for any known issues or patches related to this error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME51N (Create Purchase Requisition), ME52N (Change Purchase Requisition), and VA03 (Display Sales Order).
  SAP Notes: Check SAP Notes for any updates or patches that may address this specific error message.
  User Documentation: Review user documentation or training materials related to sales order processing and purchase requisition management in your organization.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.