Do you have any question about this error?
Message type: E = Error
Message class: CO - PPC order processing messages
Message number: 391
Message text: No requisition exists for sub-operation & &
You want to display the purchase requisition of a sub-operation.
However, no purchase requisition exists for the sub-operation.
You need to change the control key of the sub-operation. Maintain a
control key which requires the sub-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 sub-operation when the production order is saved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CO391 ("No requisition exists for sub-operation & &") typically occurs in the context of production planning and control, particularly when dealing with production orders and their associated operations and components. This error indicates that the system cannot find a requisition (such as a purchase requisition or a stock transfer requisition) for a specific sub-operation in a production order.
Causes:
- Missing Requisition: The most common cause is that there is no requisition created for the specified sub-operation in the production order.
- Incorrect Configuration: The configuration of the production order or the routing may not be set up correctly, leading to missing requisitions.
- Data Inconsistency: There may be inconsistencies in the master data, such as material master records or BOM (Bill of Materials) that prevent the system from generating the requisition.
- Incomplete Planning: The planning process may not have been completed, or the necessary planning runs have not been executed.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or create requisitions.
Solutions:
- Check Production Order: Verify the production order to ensure that all operations and components are correctly defined. Check if the sub-operation in question is correctly linked to a component.
- Create Requisition Manually: If a requisition is indeed missing, you may need to create it manually. This can be done through transaction codes like ME51N (Create Purchase Requisition) or through the production order itself.
- Review Routing and BOM: Ensure that the routing and BOM for the material are correctly set up. Check if the components are assigned to the correct operations.
- Run MRP: If the requisition is supposed to be generated automatically, ensure that the Material Requirements Planning (MRP) run has been executed. This can be done using transaction MD01 or MD02.
- Check Authorizations: Ensure that the user has the necessary authorizations to create or view requisitions. This may involve checking user roles and permissions.
- Consult Documentation: Review SAP documentation or consult with your SAP support team for specific configurations related to your organization’s setup.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to involve your SAP support team or a consultant who can provide more in-depth analysis and troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
CO390 No requisition exists for operation &
What causes this issue? You want to display the purchase requisition of an oper...
CO389 Wage type & not found in plant & (check entry)
Self-Explanatory Message Since SAP believes that this specific error message is ...
CO392 No requisition exists for component
Self-Explanatory Message Since SAP believes that this specific error message is ...
CO393 Number & for object & within critical area
What causes this issue? Almost all the numbers in the allocated number range ha...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.