Do you have any question about this error?
Message type: E = Error
Message class: SI - Implementation Guide - Status control
Message number: 106
Message text: Remaining expense was reset; check actual expense
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SI106
- Remaining expense was reset; check actual expense ?The SAP error message SI106, which states "Remaining expense was reset; check actual expense," typically occurs in the context of SAP's Controlling (CO) module, particularly when dealing with internal orders, cost centers, or project systems. This message indicates that there is a discrepancy between the planned expenses and the actual expenses recorded in the system.
Cause:
- Data Entry Errors: Incorrect data entry during the posting of expenses can lead to mismatches.
- Budgeting Issues: If the budget for a cost center or internal order has been exceeded or reset, it can trigger this error.
- Settlement Issues: If there are issues with the settlement of costs from internal orders to other cost objects, it may cause discrepancies.
- Configuration Issues: Incorrect configuration in the controlling area or internal order settings can lead to this error.
- Posting Period Issues: If the posting period is closed or not open for the relevant transactions, it can lead to discrepancies.
Solution:
- Check Actual Expenses: Review the actual expenses posted to the relevant cost object (cost center, internal order, etc.) to ensure they are correct.
- Review Budget Settings: Ensure that the budget settings for the cost center or internal order are correctly configured and that the budget has not been exceeded.
- Reconcile Data: Compare planned vs. actual expenses to identify any discrepancies. Use transaction codes like KOB1 (for internal orders) or KSB1 (for cost centers) to analyze the data.
- Check Settlement Rules: If applicable, verify the settlement rules for internal orders to ensure they are set up correctly.
- Open Posting Periods: Ensure that the posting periods are open for the transactions you are trying to post.
- Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific configuration settings that may need adjustment.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP Controlling for further assistance.
Get instant SAP help. Start your 7-day free trial now.
SI105
Degree of processing set to 100 as status set to &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SI104
Planned end & is before the higher-level planned start &
What causes this issue? You have specified a plan end which is before the higher-level plan begin &V2&. The plan end must be after the plan b...
SI107
The specified view does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SI108
No view can be generated of the procedure model activities
What causes this issue? The result of the project analysis contains only activities from the R/3 Procedure Model. No project view can be generated fo...
Click on this link to search all SAP messages.