How To Fix CO673 - Indicator for constraint exists - maintain date(s)

SAP Error Message - Details

• Message type: E = Error

• Message class: CO - PPC order processing messages

• Message number: 673

• Message text: 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 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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CO673 - Indicator for constraint exists - maintain date(s) ?

  The SAP error message CO673, which states "Indicator for constraint exists - maintain date(s)," typically occurs in the context of production planning and control, particularly when dealing with production orders, process orders, or similar objects in SAP.
  Cause:
  This error message indicates that there is a constraint or dependency that has not been satisfied, specifically related to dates. It usually arises when:
  
  Missing Dates: Required dates (such as start date, finish date, or scheduling dates) are not maintained for the production order or process order.
  Invalid Date Ranges: The dates that have been entered may not be valid or may fall outside acceptable ranges.
  Configuration Issues: There may be configuration settings in the system that require certain date indicators to be set, which have not been done.
  
  Solution:
  To resolve the CO673 error, you can take the following steps:
  
  
  Check Dates: Go to the production order or process order in question and ensure that all required date fields are filled in correctly. This includes:
  
  Basic start and finish dates
  Scheduled start and finish dates
  Any other relevant date fields that may be required by your specific configuration.
  
  
  
  Review Constraints: If there are specific constraints set up in the system (like lead times, availability checks, etc.), ensure that these are being met. You may need to adjust the order dates or the constraints themselves.
  
  
  Configuration Settings: If you have access to the configuration settings, check if there are any settings related to date indicators that need to be adjusted. This may involve working with your SAP Basis or configuration team.
  
  
  Consult Documentation: Review any relevant SAP documentation or notes related to this error message. SAP Notes can provide insights into known issues and their resolutions.
  
  
  Testing: After making the necessary adjustments, try to save or process the order again to see if the error persists.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like CO02 (Change Production Order) or CO03 (Display Production Order) to access and modify the order details.
  SAP Notes: Check SAP Notes for any updates or patches that may address this specific error.
  User Roles: Ensure that you have the necessary permissions to make changes to production orders or process orders.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in production planning and control.