Do you have any question about this error?
Message type: E = Error
Message class: 06 -
Message number: 659
Message text: No condition type chosen
A <GL:condition_type>condition type</> is required for your current
processing.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Choose a condition type.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message "06659 No condition type chosen" typically occurs in the context of pricing in sales documents, such as sales orders or quotations. This error indicates that the system could not find a valid condition type for pricing determination, which is essential for calculating the price of items in the document.
Causes:
- Missing Condition Records: There may be no condition records maintained for the relevant condition types in the pricing procedure.
- Incorrect Pricing Procedure: The pricing procedure assigned to the sales document may not be set up correctly or may not include the necessary condition types.
- Condition Type Configuration: The condition types may not be properly configured in the system, leading to them not being recognized during pricing determination.
- Document Type Issues: The document type being used may not be linked to the correct pricing procedure.
- Master Data Issues: The customer or material master data may not have the necessary information for pricing determination.
Solutions:
Check Condition Records:
- Go to transaction code
VK11
(Create Condition) orVK12
(Change Condition) to verify if the necessary condition records exist for the relevant condition types.- Ensure that the condition records are maintained for the specific combination of customer, material, and other relevant criteria.
Review Pricing Procedure:
- Use transaction code
V/08
to check the pricing procedure assigned to the sales document type.- Ensure that the pricing procedure includes the necessary condition types and that they are correctly configured.
Verify Condition Type Configuration:
- Check the configuration of the condition types in transaction code
V/06
(Maintain Condition Types) to ensure they are set up correctly.- Ensure that the condition types are active and assigned to the appropriate pricing procedure.
Check Document Type Settings:
- Verify that the document type being used is linked to the correct pricing procedure in transaction code
V/08
.Review Master Data:
- Check the customer master data (transaction code
XD03
for general data) and material master data (transaction codeMM03
) to ensure that all necessary pricing information is available.Test Pricing Procedure:
- Use transaction code
V/LA
to simulate the pricing procedure and see if the condition types are being determined correctly.Related Information:
Transaction Codes:
VK11
, VK12
: Create/Change Condition RecordsV/08
: Maintain Pricing ProceduresV/06
: Maintain Condition TypesXD03
: Display Customer MasterMM03
: Display Material MasterV/LA
: Pricing Procedure SimulationDocumentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections 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 | ![]() |
![]() |
06658 Not possible to determine a condition type
What causes this issue? The system was not able to find a <GL:condition_type...
06657 Not possible to determine a condition type for the price
What causes this issue? When it attempted to generate the <DS:GLOS.3526C06CA...
06660 Confirmation control key &1 not allowed
What causes this issue? You have changed the confirmation control key in a sche...
06661 No authorization for conditions of purchasing organization &
INCLUDE NA_BERECHTIGUNG LANGUAGE ENError message extract from SAP system. Copyr...
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.