The SAP CO error message KI235, “Document & already posted in Controlling Area,” indicates that there is an attempt to post a document in SAP Controlling (CO) that has already been posted in the specified controlling area. This error is typically encountered when there is an attempt to post a duplicate or identical document within the same controlling area.
Here are steps to address this error:
- Check Document Number:
- Use transaction codes such as KSB1 or KSB2 to display the CO document mentioned in the error message. Verify that the document number in question has indeed been posted.
- Document Status:
- Review the status of the CO document. If the document is already posted, it should have a status reflecting this. Ensure that the document status is consistent with the posting attempt.
- Reconciliation of Posting:
- Conduct a reconciliation to ensure that the document has not been inadvertently posted multiple times. Check other related modules or systems for duplicate entries.
- Check for Locks:
- Verify if the document or related objects are locked by other users. Locks can prevent modifications or postings. Transaction SM12 can be used to check for locks.
- Document Reversal:
- If the document has been erroneously posted and needs to be reversed, consider using transaction code KB02 for manual reversal or automatic reversal, depending on the scenario.
- Review SAP Notes:
- Search the SAP Service Marketplace for relevant SAP Notes related to error code KI235. SAP Notes often provide specific solutions or workarounds for known issues.
- Check User Authorization:
- Ensure that the user attempting the posting has the necessary authorizations to perform such actions. In SAP, authorizations are often a factor in controlling what actions users can perform.
- Consult SAP Support:
- If the issue persists or if it involves complex data inconsistencies, consider creating an OSS message or consulting SAP support for assistance. Provide detailed information about the error, including the specific document number and any relevant system configurations.
Always exercise caution when making changes in a live SAP environment, and consider testing solutions in a non-production environment first. If unsure, involve your SAP Basis or support team to ensure the proper resolution of the issue.