Do you have any question about this error?
Message type: E = Error
Message class: 63 - Messages for Real Estate Management
Message number: 579
Message text: For SU & & & cost collector for & is not unique
You have specified a cost collector using the settlement unit key and
the reference date. The system could not determine a unique cost
collector.
This is probably a programming error.
Inform your system administrator.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
63579
- For SU & & & cost collector for & is not unique ?The SAP error message 63579, which states "For SU & & & cost collector for & is not unique," typically occurs in the context of SAP's Project System (PS) or Controlling (CO) modules. This error indicates that there is a conflict or ambiguity regarding the cost collector associated with a specific service unit (SU) or cost object.
Cause:
- Duplicate Entries: The error often arises when there are multiple cost collectors assigned to the same service unit or cost object, leading to ambiguity in the system.
- Configuration Issues: Incorrect configuration in the cost collector settings or in the assignment of service units can also lead to this error.
- Data Integrity Issues: There may be inconsistencies in the master data or transactional data that result in multiple cost collectors being linked to the same service unit.
Solution:
Check Cost Collector Assignments:
- Navigate to the relevant transaction (e.g., CJ20N for Project Management or KP26 for Cost Planning) and check the assignments of cost collectors to the service unit.
- Ensure that each service unit has a unique cost collector assigned.
Review Configuration:
- Go to the configuration settings for cost collectors and service units in the SAP system. Ensure that the settings are correctly defined and that there are no overlaps or duplicates.
Data Cleanup:
- If duplicates are found, you may need to delete or modify the conflicting entries to ensure that each service unit has a unique cost collector.
- Use transaction codes like SE16 or SE11 to check the underlying tables for any inconsistencies.
Consult Documentation:
- Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
Testing:
- After making changes, perform tests to ensure that the error does not reoccur and that the system behaves as expected.
Related Information:
If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP CO/PS modules for further assistance.
Get instant SAP help. Start your 7-day free trial now.
63578
No cost collector generated for SU & & & for &
What causes this issue? Before accounts can be assigned to a settlement unit, cost collectors have to be generated for the defined period. In this ca...
63577
No RUs assigned to participation ID from & to &
System Response The system searched for rental units with the participation ID &v3& &v4& in the period &v1& to &v2&. ...
63580
No history available
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
63581
Partner &, address ID &: No valid address on &
What causes this issue? Partner &V1& with address ID &V2& has no valid address on &V3&.System Response The system issues an ...
Click on this link to search all SAP messages.