How To Fix CRMS4_PS_TOOLS_UI129 - Due date rule type &3 does not exist (SXP item ID &2, version ID &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: CRMS4_PS_TOOLS_UI - Messages for UI functions

• Message number: 129

• Message text: Due date rule type &3 does not exist (SXP item ID &2, version ID &1)

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 CRMS4_PS_TOOLS_UI129 - Due date rule type &3 does not exist (SXP item ID &2, version ID &1) ?

  The SAP error message CRMS4_PS_TOOLS_UI129 indicates that there is an issue with a due date rule type in the context of SAP CRM (Customer Relationship Management) or SAP PS (Project System). The error message specifies that the due date rule type referenced does not exist for the specified SXP item ID and version ID.
  Cause:
  
  Missing Due Date Rule Type: The specified due date rule type (indicated by &3) is not defined in the system. This could be due to a configuration issue or because the rule type was deleted or never created.
  Incorrect Configuration: The system might be referencing an incorrect or outdated configuration that does not match the current setup.
  Data Inconsistency: There may be inconsistencies in the data related to the SXP item ID (&2) and version ID (&1), leading to the system being unable to find the corresponding due date rule type.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for due date rules in your SAP system. Ensure that the due date rule type specified in the error message exists and is correctly configured.
  You can check this in the SPRO transaction under the relevant CRM or PS settings.
  
  
  
  Create or Modify Due Date Rule Type:
  
  If the due date rule type does not exist, you may need to create it. Consult with your SAP configuration team or refer to the documentation to create a new due date rule type.
  If it exists but is not configured correctly, make the necessary adjustments.
  
  
  
  Validate SXP Item and Version:
  
  Verify that the SXP item ID and version ID are correct. Check if they correspond to valid entries in the system.
  If there are discrepancies, you may need to correct the entries or update the references in your configuration.
  
  
  
  Transport Requests:
  
  If the issue arose after a transport request, ensure that all necessary objects were included in the transport and that they were successfully imported into the target system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to due date rules in CRM/PS for any additional insights or specific steps that may be required.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO (for configuration), SE11 (for data dictionary), or SE80 (for object navigator) to investigate further.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.