Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TU - Billing/Scheduling/Budget Billing
Message number: 369
Message text: Changes from R994 ignored due to inconsistencies in BB plan
Changes made to the budget billing amount from R994 have caused
inconsistencies in the budget billing plan. As a result, the system uses
the budget billing plan that was created before the call from R994.The
changes from R994 are ignored.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you use your own function module in event R994, correct it
accordingly.
If you use the function module supplied by SAP, write a problem message.
Error message extract from SAP system. Copyright SAP SE.
TU369
- Changes from R994 ignored due to inconsistencies in BB plan ?The SAP error message TU369, which states "Changes from R994 ignored due to inconsistencies in BB plan," typically occurs in the context of the SAP Advanced Planning and Optimization (APO) module, particularly when dealing with the Business Blueprint (BB) planning process. This error indicates that there are inconsistencies in the planning data that prevent the system from applying changes made by the R994 report.
Cause:
The error can be caused by several factors, including:
Inconsistent Data: There may be inconsistencies in the planning data, such as missing or incorrect master data (e.g., material master, location master) or planning parameters.
Locked Objects: Certain objects may be locked, preventing the system from making the necessary changes.
Incorrect Planning Versions: The planning version being used may not be compatible with the changes being applied.
Data Integrity Issues: There may be issues with the integrity of the data in the planning book or data views.
Configuration Issues: Incorrect configuration settings in the planning area or planning book can lead to inconsistencies.
Solution:
To resolve the TU369 error, you can take the following steps:
Check Data Consistency:
- Use transaction codes like
/SAPAPO/SDP94
or/SAPAPO/SDP95
to check for inconsistencies in the planning data.- Review the master data for the materials and locations involved to ensure they are correctly set up.
Review Planning Versions:
- Ensure that the planning version you are using is correct and that it is not locked or in a state that prevents changes.
Unlock Objects:
- If certain objects are locked, you may need to unlock them or wait until the lock is released.
Run Consistency Checks:
- Use the consistency check tools available in SAP APO to identify and correct any data integrity issues.
Review Configuration:
- Check the configuration settings for the planning area and planning book to ensure they are set up correctly.
Consult Logs:
- Review the application logs for more detailed error messages that can provide additional context on the inconsistencies.
Re-run the R994 Report:
- After addressing the inconsistencies, re-run the R994 report to see if the changes can now be applied successfully.
Related Information:
/SAPAPO/SDP94
(for planning book) and /SAPAPO/SDP95
(for planning area).If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TU368
Due item &1 cannot be changed. Change from R994 not accepted.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TU367
Payment plan &1 is not adjusted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TU370
No JVL obj. created; field JVL participation in contr.acc. &1 has value 0
What causes this issue? No yearly advance payment object is created for the contracts in contract account &V1&, because 0 (no participation) ...
TU371
No JVL object created, tests in user exit R425 negative
What causes this issue? No yearly advance payment object is created in contract account &V1& as the checks in user exit ISU_SAMPLE_R425 do no...
Click on this link to search all SAP messages.