Do you have any question about this error?
Message type: E = Error
Message class: 62 - Message Texts for Real Estate
Message number: 950
Message text: SU contains posted, but not yet settled cost collectors
Caution
You want set a deletion flag on the settlement unit. At least one cost
collector of this settlement unit was posted, but not yet settled.
Using the itemization of the settlement unit, check the postings to the
cost collectors.
If you set the deletion flag, the posted costs of this settlement unit
are no longer taken into account during the service charge settlement.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE 'CUSTOMIZED_MESSAGE_INFO' OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
62950
- SU contains posted, but not yet settled cost collectors ?The SAP error message "62950 SU contains posted, but not yet settled cost collectors" typically occurs in the context of settlement processes in SAP, particularly when dealing with internal orders, projects, or cost collectors. This error indicates that there are cost collectors (such as internal orders or WBS elements) that have posted costs but have not yet been settled.
Cause:
Unsettled Cost Collectors: The primary cause of this error is that there are cost collectors associated with the settlement unit (SU) that have incurred costs but have not been settled. This means that the costs are still in the cost collector and have not been transferred to the final destination (like a cost center or asset).
Incomplete Settlement Process: The settlement process may not have been completed for all relevant cost collectors, leading to this error when trying to perform further actions (like closing the period or executing a settlement).
Configuration Issues: There may be configuration issues in the settlement profile or the assignment of cost collectors that prevent proper settlement.
Solution:
Check Cost Collectors: Identify the cost collectors associated with the settlement unit. You can do this by using transaction codes like KOB1 (for internal orders) or CJI3 (for project-related costs) to view the posted costs.
Perform Settlement: Once you have identified the cost collectors, perform the necessary settlement for each of them. You can use transaction KO88 for internal orders or CJ88 for WBS elements to settle the costs.
Review Settlement Profiles: Ensure that the settlement profiles and rules are correctly configured. Check if the cost collectors are correctly assigned to the appropriate settlement rules.
Check for Errors: After attempting to settle, check for any errors or warnings that may indicate why the settlement did not occur. This can help in troubleshooting any underlying issues.
Consult Documentation: If the issue persists, refer to SAP documentation or consult with your SAP support team for further assistance.
Related Information:
Transaction Codes: Familiarize yourself with relevant transaction codes such as:
SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
User Authorization: Ensure that you have the necessary authorizations to perform settlements and view cost collector details.
Training and Documentation: Consider training sessions or documentation on internal order management and project accounting in SAP to better understand the settlement process.
By following these steps, you should be able to resolve the error and successfully settle the cost collectors associated with the settlement unit.
Get instant SAP help. Start your 7-day free trial now.
62949
A settlement unit flagged for deletion is assigned to MSU &
What causes this issue? You are executing a service charge settlement / option rate determination for master settlement unit <ZH>&v1&&l...
62947
Customizing for Plant Maintenance in CoCd &1 incomplete
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
62951
Advance payment in lease-out &1 in M/L-tape more than once
What causes this issue? Caution! The advance payments for this lease-out appear more than once in the individual M3 records of the M/L-tape. The rea...
62952
Multiple records for lease-out &2 (CoCd &1) in D-tape
What causes this issue? Caution! There are multiple records in the D-tape for this lease-out. However, it is only possible to process one record for ...
Click on this link to search all SAP messages.