How To Fix PSSC_CUST027 - Due date rule type &1 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: PSSC_CUST - Messages regarding Customizing

• Message number: 027

• Message text: Due date rule type &1 does not exist

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 PSSC_CUST027 - Due date rule type &1 does not exist ?

  The SAP error message PSSC_CUST027 indicates that a due date rule type specified in your configuration does not exist in the system. This error typically arises in the context of SAP's Project System (PS) or similar modules where due date rules are used for scheduling and planning.
  Cause:
  
  Missing Configuration: The due date rule type referenced in the transaction or configuration does not exist in the system. This could be due to a typo, or the rule may not have been created or activated.
  Incorrect Customization: If you are using a custom due date rule, it may not have been properly defined in the system.
  Transport Issues: If the configuration was transported from another system, the due date rule may not have been included in the transport request.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the relevant configuration transaction (e.g., SPRO) and navigate to the section where due date rules are defined.
  Verify that the due date rule type you are trying to use is listed and correctly configured.
  
  
  
  Create or Modify Due Date Rule:
  
  If the due date rule does not exist, you may need to create it. This typically involves defining the rule parameters and ensuring it meets your business requirements.
  If it exists but is incorrectly configured, modify it as necessary.
  
  
  
  Check for Typos:
  
  Ensure that the due date rule type is correctly spelled in the configuration or transaction where the error occurs.
  
  
  
  Transport Requests:
  
  If the configuration was recently transported, check the transport logs to ensure that the due date rule was included in the transport request.
  If it was not included, you may need to create a new transport request that includes the necessary configuration.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on how to set up due date rules correctly.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration or CJ20N for project management to access the relevant settings.
  SAP Notes: Check SAP Notes for any known issues or updates related to due date rules and the specific error message.
  User Roles and Authorizations: Ensure that you have the necessary authorizations to view and modify the configuration settings.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.