How To Fix TFC0117 - No authorization to change task plan & on key date &

SAP Error Message - Details

• Message type: E = Error

• Message class: TFC0 - Messages in FC

• Message number: 117

• Message text: No authorization to change task plan & on key date &

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 TFC0117 - No authorization to change task plan & on key date & ?

  The SAP error message TFC0117 indicates that a user does not have the necessary authorization to change a task plan on a specified key date. This error typically arises in the context of SAP Project System (PS) or SAP Controlling (CO) modules, where task plans are used for project management and cost planning.
  Cause:
  
  Authorization Issues: The user attempting to make changes does not have the required authorization objects assigned to their user profile. This could be due to missing roles or authorizations related to project management or task planning.
  Key Date Restrictions: The key date specified may have restrictions that prevent changes from being made. For example, if the task plan is locked for a specific period or if it is in a closed fiscal year.
  Task Plan Status: The task plan may be in a status that does not allow changes, such as being completed or archived.
  
  Solution:
  
  
  Check User Authorizations:
  
  Review the user’s roles and authorizations in the SAP system. Ensure that the user has the necessary authorizations for the relevant transaction codes (e.g., CJ20N for project management).
  Use transaction code SU53 to analyze the authorization check after the error occurs. This will show which authorization object is missing.
  
  
  
  Adjust Key Date:
  
  If the key date is causing the issue, consider changing it to a date that is permissible for modifications. Ensure that the date falls within an open period for the project.
  
  
  
  Change Task Plan Status:
  
  If the task plan is locked or in a status that does not allow changes, you may need to unlock it or change its status. This may require additional authorizations or actions from a project manager or administrator.
  
  
  
  Consult with SAP Security Team:
  
  If you are unable to resolve the authorization issue, consult with your SAP security team or system administrator. They can help identify and assign the necessary authorizations.
  
  
  
  Documentation and Training:
  
  Ensure that users are trained on the proper procedures for modifying task plans and understand the implications of changing key dates.
  
  
  
  Related Information:
  
  Authorization Objects: Common authorization objects related to project management include C_PROJ (Project Management) and C_TPLN (Task Planning).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ02 (Change Project), and CJ03 (Display Project).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance on authorization problems.
  
  By following these steps, you should be able to identify the cause of the TFC0117 error and implement a solution to resolve it.