Do you have any question about this error?
Message type: E = Error
Message class: RESCSH - Error Messages When Creating Settlement Hierarchy
Message number: 012
Message text: No condition type could be determined for &1 SCK &2
The system could not determine a condition type for &v1& service charge
key &v2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check:
The settlement participation
If there is an entry for service charge key &v2& in Customizing in the
<DS:SIMG.REFX_V_TIVSCDEFCOND>Assignment of Service Charge Key to
Condition Type</> IMG activity.
Error message extract from SAP system. Copyright SAP SE.
RESCSH012
- No condition type could be determined for &1 SCK &2 ?The SAP error message RESCSH012 indicates that the system could not determine a condition type for a specific item in a sales document or pricing procedure. This error typically arises in the context of pricing in sales and distribution (SD) or materials management (MM) modules.
Cause:
- Missing Condition Records: The most common cause is that there are no condition records maintained for the specified condition type in the pricing procedure.
- Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary condition types.
- Condition Exclusion: The condition type might be excluded from the pricing procedure for the specific sales area or document type.
- Incorrect Master Data: The master data (like customer master, material master, etc.) may not be set up correctly, leading to the inability to determine the condition type.
- Pricing Procedure Assignment: The pricing procedure may not be correctly assigned to the sales area, customer, or document type.
Solution:
Check Condition Records:
- Go to transaction VK11 (Create Condition) or VK12 (Change Condition) to check if the condition records for the relevant condition type exist.
- If they do not exist, create the necessary condition records.
Review Pricing Procedure:
- Use transaction V/08 to review the pricing procedure and ensure that the required condition types are included.
- Check if the condition type is marked as active and is not excluded for the relevant sales area or document type.
Verify Master Data:
- Check the customer master data (transaction XD03) and material master data (transaction MM03) to ensure that they are correctly set up and that the relevant pricing information is maintained.
Check Assignment:
- Ensure that the pricing procedure is correctly assigned to the sales area, customer, and document type. This can be checked in transaction V/08 or V/07.
Debugging:
- If the issue persists, consider debugging the pricing procedure to identify where the determination is failing. This may require technical expertise.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
By following these steps, you should be able to identify and resolve the issue causing the RESCSH012 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
RESCSH011
No flow type could be determined for &1 condition type &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RESCSH010
&1 is already settled up to &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RESCSH013
Next settlement period for &1 is &2 and not &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RESCSH014
SU &1 is distributed by consumption - but PS &2 does not have a meter
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.