Do you have any question about this error?
Message type: E = Error
Message class: RESCAJ - Adjustment for Conditions of SCS
Message number: 060
Message text: Condition type &1: is adjusted like &2
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE RECA_CUSTOMIZED_MESSAGE_INFO OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
RESCAJ060
- Condition type &1: is adjusted like &2 ?The SAP error message RESCAJ060 typically occurs in the context of condition types in the SAP system, particularly when dealing with pricing or cost calculations in the SAP Sales and Distribution (SD) or Materials Management (MM) modules. The message indicates that a specific condition type is being adjusted in a way that is not expected or is inconsistent with the system's configuration.
Cause:
The error message RESCAJ060 can be triggered by several factors, including:
Configuration Issues: The condition type may not be properly configured in the pricing procedure. This could involve missing settings or incorrect relationships between condition types.
Data Inconsistencies: There may be inconsistencies in the master data or transaction data that lead to unexpected adjustments. For example, if the condition records for a specific condition type are not maintained correctly.
Custom Logic: If there are custom enhancements or user exits that manipulate pricing conditions, they may be causing the condition type to be adjusted incorrectly.
Incorrect Condition Records: The condition records for the specific condition type may not be set up correctly, leading to unexpected behavior during pricing calculations.
Solution:
To resolve the RESCAJ060 error, you can take the following steps:
Check Configuration:
- Go to the configuration settings for the pricing procedure in SPRO (SAP Customizing Implementation Guide).
- Ensure that the condition type in question is correctly defined and linked to the appropriate pricing procedure.
Review Condition Records:
- Check the condition records for the specific condition type using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
- Ensure that the records are maintained correctly and that there are no missing entries.
Analyze Custom Logic:
- If there are any custom enhancements or user exits that affect pricing, review the code to ensure that it is functioning as intended and not causing the adjustment issue.
Check Master Data:
- Verify that the master data (such as customer master, material master, etc.) is correctly maintained and does not have any inconsistencies that could affect pricing.
Consult Documentation:
- Review SAP documentation or notes related to the specific condition type and pricing procedure for any known issues or additional configuration steps.
Debugging:
- If the issue persists, consider debugging the pricing procedure to identify where the adjustment is occurring and why it is not behaving as expected.
Related Information:
By following these steps, you should be able to identify the root cause of the RESCAJ060 error and implement the necessary corrections to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RSDA466
Could not delete pending straggler table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDA465
Could not select pending stragglers from table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RESCAJ061
Condition type &1: no adjustment, since not contained in SC settlement
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
RESCAJ070
Condition is not within next settlement period
What causes this issue? The condition begins after the end of the next settlement period or the condition ends before the settlement period begins. H...
Click on this link to search all SAP messages.