How To Fix UJC_EXCEPTION028 - Comment ( ID = &3 ) was rejected by work status check in ( &1 - &2 )

SAP Error Message - Details

• Message type: E = Error

• Message class: UJC_EXCEPTION - BPC: Message Class for UJC Exception

• Message number: 028

• Message text: Comment ( ID = &3 ) was rejected by work status check in ( &1 - &2 )

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 UJC_EXCEPTION028 - Comment ( ID = &3 ) was rejected by work status check in ( &1 - &2 ) ?

  The SAP error message UJC_EXCEPTION028 indicates that a comment (identified by the ID specified in the message) was rejected due to a work status check in a specific context (identified by the parameters &1 and &2). This typically occurs in the context of SAP's Project Management or Project System modules, where work statuses are used to control the progress and changes to project elements.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Work Status Restrictions: The work status of the project or element does not allow for comments to be added or modified. This could be due to the project being in a status that restricts changes (e.g., "Completed", "Closed").
  Authorization Issues: The user may not have the necessary authorizations to add comments in the current work status.
  Configuration Settings: The configuration of work status management may not permit comments in certain statuses.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Work Status: Review the work status of the project or element (identified by &1 and &2). Ensure that the current status allows for comments to be added or modified.
  
  If the status is restrictive, consider changing the status to one that allows comments, if appropriate.
  
  
  
  User Authorizations: Verify that the user has the necessary authorizations to add comments in the current work status. This may involve checking user roles and permissions in the SAP system.
  
  
  Consult Configuration: If you have access to the configuration settings, check the work status management settings to see if comments are allowed in the current status. If not, you may need to adjust the configuration or consult with your SAP administrator.
  
  
  Error Logging: If the issue persists, check the system logs for any additional error messages or details that may provide further insight into the problem.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP documentation for further assistance.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to work status management and project comments for a better understanding of how these features interact.
  User Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.