Do you have any question about this error?
Message type: E = Error
Message class: CO - PPC order processing messages
Message number: 369
Message text: Changes in order & critical due to rel. status of requisition
Order &V1& contains purchase requisitions which have the status
'released'.
Once a purchase requisition is released, it cannot be changed. This
means that you can still make changes in the order, but any changes
relevant to purchasing (such as changes in dates and quantities) are
not updated in the purchase requisition.
INCLUDE 'NA_ALLG_NOVERARBEITUNG' OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CO369, which states "Changes in order & critical due to rel. status of requisition," typically occurs in the context of production orders or purchase requisitions. This message indicates that there are restrictions on making changes to the order because of the release status of the associated requisition.
Cause:
- Release Status: The requisition associated with the production order is in a status that does not allow changes. This could be due to it being fully released or already processed in a way that prevents further modifications.
- Dependencies: The order may have dependencies on other documents or processes that are preventing changes.
- Configuration Settings: Certain configuration settings in the SAP system may enforce strict rules regarding changes to orders based on the status of related requisitions.
Solution:
- Check Requisition Status: Review the status of the associated requisition. If it is in a released state, you may need to revert it to a draft or change its status to allow modifications.
- Unlock the Requisition: If possible, unlock or change the status of the requisition to allow for changes in the production order.
- Consult with a Supervisor: If you do not have the necessary permissions to change the requisition status, consult with a supervisor or someone with the appropriate authority.
- Review Configuration: If this issue occurs frequently, it may be worth reviewing the configuration settings in SAP to see if they can be adjusted to allow for more flexibility in changing orders.
- Use Transaction Codes: Utilize relevant transaction codes (like ME52N for changing requisitions or CO02 for changing orders) to check and modify the necessary documents.
Related Information:
If the problem persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.
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 | ![]() |
![]() |
CO368 Changes to purchase req. & & not possible because of release status
Self-Explanatory Message Since SAP believes that this specific error message is ...
CO367 Number range & is not created for object &
What causes this issue? The number ranges for &V2& have not been assign...
CO370 Classification presently not possible - class locked
Self-Explanatory Message Since SAP believes that this specific error message is ...
CO371 Maintain short text to material & in language &
Self-Explanatory Message Since SAP believes that this specific error message is ...
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.