Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: CO - PPC order processing messages
Message number: 671
Message text: An automatic determination of planned costs is not intended
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.
CO671
- An automatic determination of planned costs is not intended ?The SAP error message CO671, which states "An automatic determination of planned costs is not intended," typically occurs in the context of controlling (CO) and product costing processes. This error indicates that the system is unable to automatically determine planned costs for a particular cost object, such as a cost center, internal order, or production order.
Causes:
- Costing Variant Configuration: The costing variant may not be set up correctly to allow for automatic cost determination.
- Missing Master Data: Required master data (like cost centers, activity types, or material master data) may be missing or incorrectly configured.
- Costing Type: The costing type used may not be configured for automatic cost determination.
- Costing Run Settings: The settings for the costing run may not allow for automatic determination of planned costs.
- Transaction Type: The transaction type being used may not support automatic cost determination.
Solutions:
Check Costing Variant: Review the configuration of the costing variant in the controlling area to ensure it is set up to allow for automatic cost determination.
- Transaction Code: OKKN (Costing Variants)
Verify Master Data: Ensure that all necessary master data is correctly maintained and available. This includes:
- Cost centers
- Activity types
- Material master data
Review Costing Type: Check the costing type settings to ensure it is configured for automatic cost determination.
- Transaction Code: OKTZ (Costing Types)
Adjust Costing Run Settings: If you are running a costing run, check the settings to ensure that automatic determination is enabled.
- Transaction Code: CK40N (Product Costing)
Check Transaction Type: Ensure that the transaction type you are using supports automatic cost determination. If not, consider using a different transaction type or adjusting the current one.
Consult Documentation: Review SAP documentation or help files related to product costing and controlling for additional insights and troubleshooting steps.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
CO670
Order category & is not permitted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO669
Inconsistencies occurred in configuration of collective orders
What causes this issue? In the configuration of <GL:collective_order>collective order</> various variant classes were used for the compon...
CO672
Output device for order type &, plant &, MRP & not correctly maintained
What causes this issue? For one of the lists to be printed no entry was found in the output device the entry in the output device could not be evalua...
CO673
Indicator for constraint exists - maintain date(s)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.