Do you have any question about this error?
Message type: E = Error
Message class: KD - CO Settlement
Message number: 135
Message text: Cross company settlement is not supported (&1/&2)
You are trying to settle a sender with company code &V1& to a receiver
with company code &V2&.
The system does not allow a settlement between two different company
codes.
Change the settlement rule accordingly.
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.
KD135
- Cross company settlement is not supported (&1/&2) ?The SAP error message KD135 "Cross company settlement is not supported (&1/&2)" typically occurs in the context of controlling (CO) when you are trying to perform a settlement process that involves multiple company codes. This error indicates that the system does not support the settlement of costs across different company codes.
Cause:
- Cross-Company Code Settlement: The primary cause of this error is that the system is configured to prevent cross-company code settlements. In SAP, each company code is treated as a separate legal entity, and certain processes, including settlements, are restricted to within the same company code.
- Configuration Settings: The configuration settings in the controlling area or the settlement profile may not allow for cross-company code transactions.
- Master Data Issues: The master data for the cost objects involved may not be set up correctly to allow for cross-company code transactions.
Solution:
Check Configuration:
- Go to the configuration settings in the SAP system (Transaction SPRO).
- Navigate to Controlling > Cost Center Accounting > Settlement > Define Settlement Profile.
- Ensure that the settlement profile does not restrict cross-company code settlements if that is intended.
- Check the controlling area settings to ensure that it allows for cross-company code transactions.
Use Same Company Code:
- If cross-company code settlement is not required, ensure that the cost objects (e.g., internal orders, cost centers) involved in the settlement belong to the same company code.
Review Master Data:
- Check the master data for the cost objects involved in the settlement. Ensure that they are correctly assigned to the appropriate company codes and controlling areas.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific configurations related to your organization's setup.
Custom Development:
- If cross-company code settlements are necessary for your business processes, consider discussing with your SAP technical team about potential custom development or enhancements that could allow for this functionality.
Related Information:
OKZ1
(Settlement Profile) and KOB1
(Order Information System) to analyze and manage settlements.If the issue persists after checking the above points, it may be beneficial to engage with SAP support or a consultant who specializes in SAP CO for further assistance.
Get instant SAP help. Start your 7-day free trial now.
KD134
&1 is not supported for settlement of additional currencies
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KD133
Receiver company must have same fiscal year variant as sender company
What causes this issue? You are settling to a receiver in a company (&V2&) that is different from the company of the settlement sender (&...
KD136
Order with Event-Based Posting is not relevant for settlement
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KD137
Object with Event-Based Revenue Recognition not relevant for settlement
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.