Do you have any question about this error?
Message type: E = Error
Message class: CO - PPC order processing messages
Message number: 360
Message text: The float before production cannot be reduced by more than 100 %
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.
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.
CO360
- The float before production cannot be reduced by more than 100 % ?The SAP error message CO360, "The float before production cannot be reduced by more than 100 %," typically occurs in the context of production planning and scheduling within the SAP system. This error indicates that the system is trying to reduce the float (the amount of time that a task can be delayed without delaying the project) for a production order or operation beyond the allowable limit.
Cause:
- Float Calculation: The float is calculated based on the scheduled start and finish dates of operations. If the system attempts to schedule an operation in such a way that it would require reducing the float to a negative value, this error will occur.
- Scheduling Conflicts: There may be conflicts in the scheduling of operations, such as overlapping tasks or insufficient resources.
- Incorrect Configuration: The configuration settings for production scheduling may not be set correctly, leading to unrealistic scheduling attempts.
- Dependencies: There may be dependencies between operations that are not being respected, causing the float to be reduced excessively.
Solution:
- Review Scheduling: Check the scheduling of the production order and ensure that the operations are sequenced correctly. Adjust the start and finish dates as necessary to allow for adequate float.
- Adjust Float Settings: If applicable, review the float settings in the production order or operation. Ensure that the float is set to a reasonable value that allows for flexibility in scheduling.
- Check Resource Availability: Ensure that the resources required for the production order are available and not causing scheduling conflicts.
- Recalculate Dates: Use the scheduling functions in SAP to recalculate the dates for the production order. This may involve using transaction codes like CO02 (Change Production Order) or CO01 (Create Production Order) to adjust the order.
- Consult Documentation: Review SAP documentation or consult with your SAP support team for specific configuration settings that may need to be adjusted.
Related Information:
By addressing the underlying causes and following the suggested solutions, you should be able to resolve the CO360 error and proceed with your production planning activities.
Get instant SAP help. Start your 7-day free trial now.
CO359
The cost log is empty
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO358
Routing selected without lot size
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO361
Enter costing sheet
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO362
Overhead key & not found
Overhead key &V1& cannot be entered in this field for one of the following reasons: The overhead key is not maintained. In this case, define ...
Click on this link to search all SAP messages.