How To Fix CTSPRJ147 - Both sets of dependency information already exist

SAP Error Message - Details

• Message type: E = Error

• Message class: CTSPRJ - CTS: Projects

• Message number: 147

• Message text: Both sets of dependency information already exist

What causes this issue?

Request &V2& is already flagged as a predecessor and successor of
request &V1&. This means that you must import both requests at the same
time. You cannot remove this flag. However, you can change the
accompanying reason.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CTSPRJ147 - Both sets of dependency information already exist ?

  The SAP error message CTSPRJ147, which states "Both sets of dependency information already exist," typically occurs in the context of SAP's Project System (PS) or when dealing with dependencies in the context of network activities or project planning.
  Cause:
  This error usually arises when you attempt to create or modify a dependency (such as a predecessor or successor relationship) between activities in a project, but the system detects that the dependency information you are trying to create already exists. This can happen if:
  
  You are trying to create a duplicate dependency.
  The dependency was already established in a previous operation.
  There is a data inconsistency or corruption in the project data.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Dependencies:
  
  Review the existing dependencies for the activities involved. You can do this by navigating to the project or network in question and checking the relationships between the activities.
  Use transaction codes like CJ20N (Project Builder) or CN22 (Change Network) to view the dependencies.
  
  
  
  Remove Duplicate Dependencies:
  
  If you find that the dependency you are trying to create already exists, you can either remove the duplicate dependency or modify your approach to avoid creating it again.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the project or network to ensure there are no data inconsistencies. You can use transaction CNO1 (for network) or CNO2 (for project) to check for inconsistencies.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to project dependencies to ensure you are following the correct procedures.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration or version.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N, CN22, CNO1, and CNO2 for managing projects and networks.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.