Do you have any question about this error?
Message type: E = Error
Message class: 06 -
Message number: 657
Message text: Not possible to determine a condition type for the price
When it attempted to generate the
<DS:GLOS.3526C06CAFAB52B9E10000009B38F974>time-dependent conditions</>
for the price you entered, the system was unable to determine a
<GL:condition_type>condition type</>. Price determination is therefore
not possible.
Contact your system administrator.
The latter can maintain the calculation schema assigned to the
purchasing document using the Implementation Guide (IMG).
<DS:SIMG.SIMG_CFMENUOLMEOMER5>Define calculation schema</>
Error message extract from SAP system. Copyright SAP SE.
The SAP error message "06657 Not possible to determine a condition type for the price" typically occurs in the context of pricing in sales documents, purchase orders, or other transactions where condition types are used to determine pricing. This error indicates that the system is unable to find a valid condition type for the price determination process.
Causes:
- Missing Condition Records: The condition records for the relevant condition type may not be maintained in the system.
- Incorrect Pricing Procedure: The pricing procedure assigned to the document may not include the necessary condition types.
- Inconsistent Master Data: Issues with master data, such as customer or material master records, can lead to this error if they do not have the necessary pricing information.
- Condition Exclusion: The condition type may be excluded from the pricing procedure due to configuration settings.
- Incorrect Configuration: The configuration of the pricing procedure or condition types may be incorrect or incomplete.
Solutions:
Check Condition Records:
- Go to transaction code
VK11
(Create Condition) orVK12
(Change Condition) to verify 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 code
V/08
to review the pricing procedure assigned to the sales area or purchasing organization.- Ensure that the required condition types are included in the pricing procedure.
Verify Master Data:
- Check the customer master (transaction code
XD03
) and material master (transaction codeMM03
) to ensure that they have the necessary pricing information.- Ensure that the customer and material are correctly linked to the pricing procedure.
Check Condition Exclusion:
- Review the configuration to ensure that the condition type is not excluded from the pricing procedure.
Consult Configuration:
- If you have access to the configuration settings, check the settings for condition types and pricing procedures in transaction code
SPRO
.- Ensure that the condition types are correctly configured and linked to the appropriate pricing procedures.
Debugging:
- If the issue persists, consider debugging the pricing procedure to identify where the determination process fails.
Related Information:
Transaction Codes:
VK11
, VK12
: For maintaining condition records.V/08
: For reviewing pricing procedures.XD03
, MM03
: For checking master data.SPRO
: For accessing configuration settings.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 the root cause of the error and implement the necessary solutions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
06656 Please enter valid scope of list
INCLUDE NA_WERT LANGUAGE ENError message extract from SAP system. Copyright SAP...
06655 No contract items of category & allowed
What causes this issue? The contract item specifies the item category "mat...
06658 Not possible to determine a condition type
What causes this issue? The system was not able to find a <GL:condition_type...
06659 No condition type chosen
What causes this issue? A <GL:condition_type>condition type</> is r...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.