How To Fix PJ660 - Activity element & defined twice (Check your entry)

SAP Error Message - Details

• Message type: E = Error

• Message class: PJ - MPX interface messages (Download and Upload)

• Message number: 660

• Message text: Activity element & defined twice (Check your entry)

What causes this issue?

The MPX files has the same name several time for the same field
<ZH>Activity notes</>. The project system creates the number for the
activity element from the activity notes during the upload.

System Response

INCLUDE 'NA_ALLG_NOVERARBEITUNG' OBJECT DOKU ID TX

How to fix this error?

Check the names you have used for activity notes in Microsoft Project
(R) and make any changes necessary.
Please note:
The numbers for the activity elements in a standard network may not be
identical to each other or to the activity numbers (Field <ZH>activity
notes</>).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PJ660 - Activity element & defined twice (Check your entry) ?

  The SAP error message PJ660, which states "Activity element & defined twice (Check your entry)," typically occurs in the context of project management within SAP, particularly when dealing with project structures and activity elements in the Project System (PS) module.
  Cause:
  This error arises when you attempt to create or modify an activity element (such as a work package or task) in a project, and the system detects that the same activity element has already been defined within the same project or within the same hierarchy. This can happen due to:
  
  Duplicate Entries: You may have inadvertently entered the same activity element more than once.
  Incorrect Data Entry: There might be a typographical error or misconfiguration in the activity element's identification.
  Project Structure Issues: The project structure may not be set up correctly, leading to conflicts in activity definitions.
  
  Solution:
  To resolve the PJ660 error, you can take the following steps:
  
  
  Check for Duplicates:
  
  Review the project structure to identify if the activity element has already been defined. You can do this by navigating to the project in the Project Builder (transaction code: CJ20N) or using the Project Structure Overview (transaction code: CJ03).
  Look for any duplicate entries in the activity list.
  
  
  
  Correct the Entry:
  
  If you find a duplicate, decide whether to delete the duplicate entry or modify it to ensure that each activity element is unique.
  If the entry is correct but still causing issues, consider renaming the activity element to avoid conflicts.
  
  
  
  Check Hierarchy:
  
  Ensure that the hierarchy of the project is correctly set up. Sometimes, issues in the hierarchy can lead to confusion in activity definitions.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for additional guidance on managing project structures and activity elements.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists after checking for duplicates and correcting entries, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ03 (Display Project), and CJ02 (Change Project) for managing project activities.
  SAP Notes: Check SAP Notes for any updates or patches that may address this specific error.
  User Roles: Ensure that you have the appropriate permissions to create or modify activity elements in the project.
  
  By following these steps, you should be able to identify and resolve the cause of the PJ660 error in SAP.