CO390 - No requisition exists for operation &

SAP Error Message - Details

• Message type: E = Error

• Message class: CO - PPC order processing messages

• Message number: 390

• Message text: No requisition exists for operation &

What causes this issue?

You want to display the purchase requisition of an operation. However,
no purchase requisition exists for the operation.

How to fix this error?

You need to change the control key of the operation. Maintain a
control key which requires the operation to be carried out externally
(On the detail screen of the control key, the indicator 'ExtProc' must
be set to <ZH>External processing obligatory</>). If this indicator
is set, the system automatically creates a purchase requisition for the
operation when the production order is saved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CO390 - No requisition exists for operation & ?

  The SAP error message CO390 ("No requisition exists for operation &") typically occurs in the context of production planning and control, particularly when dealing with production orders and their associated operations. This error indicates that the system cannot find a requisition (such as a purchase requisition or a production requisition) for a specific operation in a production order.
  Causes:
  
  
  Missing Requisition: The most common cause is that there is no requisition created for the operation in question. This can happen if the operation was not properly set up or if the requisition was deleted or not generated.
  
  
  Incorrect Configuration: The configuration settings for the production order or the material may not be set up correctly, leading to the absence of a requisition.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data, such as the bill of materials (BOM) or routing, which can prevent the system from generating the necessary requisition.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or create requisitions, leading to this error.
  
  
  System Errors: Occasionally, system errors or bugs can lead to this message being displayed.
  
  
  Solutions:
  
  
  Check Requisition Creation: Verify if a requisition has been created for the operation. You can do this by checking the production order details and the associated operations.
  
  
  Review Configuration: Ensure that the configuration for the production order, BOM, and routing is correct. Check if the material master data is set up properly.
  
  
  Generate Requisition: If a requisition is missing, you may need to manually create it or regenerate it through the appropriate transaction (e.g., using transaction codes like ME51N for purchase requisitions).
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create and view requisitions. This may involve checking user roles and permissions.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the error message and its context.
  
  
  Debugging: If the issue persists, consider debugging the process to identify any underlying issues in the system.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO02 (Change Production Order), CO03 (Display Production Order), ME51N (Create Purchase Requisition), and ME53N (Display Purchase Requisition).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or workarounds.
  Training and Documentation: Ensure that users are trained on the processes related to production orders and requisitions to minimize errors.
  
  By following these steps, you should be able to diagnose and resolve the CO390 error in SAP.