06658 - Not possible to determine a condition type


SAP Error Message - Details

  • Message type: E = Error

  • Message class: 06 -

  • Message number: 658

  • Message text: Not possible to determine a condition type

  • Show details Hide details
  • What causes this issue?

    The system was not able to find a <GL:condition_type>condition type</>
    for the item. Price determination is therefore not possible.

    How to fix this error?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message 06658 - Not possible to determine a condition type ?

    The SAP error message "06658 Not possible to determine a condition type" typically occurs in the context of pricing and condition records in SAP. This error indicates that the system is unable to find a valid condition type for a pricing procedure during the processing of a sales document, purchase order, or other related transactions.

    Causes:

    1. Missing Condition Records: The condition type required for the pricing procedure may not have been defined or maintained in the system.
    2. Incorrect Pricing Procedure: The pricing procedure assigned to the sales area, customer, or material may not be set up correctly.
    3. Inconsistent Master Data: There may be inconsistencies in the master data, such as customer master, material master, or info records.
    4. Condition Exclusion: The condition type may be excluded from the pricing procedure due to configuration settings.
    5. Incorrect Access Sequence: The access sequence for the condition type may not be correctly defined, leading to the inability to find the condition records.

    Solutions:

    1. Check Condition Records:

      • Go to transaction code VK11 (Create Condition) or VK12 (Change Condition) to verify if the necessary condition records exist for the relevant condition type.
      • Ensure that the condition records are maintained for the specific combination of sales organization, distribution channel, and other relevant fields.
    2. Review Pricing Procedure:

      • Use transaction code V/08 to review the pricing procedure assigned to the relevant sales area.
      • Ensure that the condition type in question is included in the pricing procedure and is correctly configured.
    3. Verify Master Data:

      • Check the customer master data (transaction code XD03 for display) and ensure that the correct pricing procedure is assigned.
      • Verify the material master data (transaction code MM03 for display) to ensure that the material is set up correctly for pricing.
    4. Check Access Sequence:

      • Review the access sequence assigned to the condition type (transaction code V/07).
      • Ensure that the access sequence is correctly defined and that the necessary fields are included.
    5. Consult Configuration:

      • If you have access to the configuration, check the settings in the SPRO transaction under Sales and Distribution > Basic Functions > Pricing > Pricing Control to ensure everything is set up correctly.
    6. Debugging:

      • If the issue persists, consider debugging the pricing procedure to identify where the determination process fails.

    Related Information:

    • Transaction Codes:

      • VK11, VK12: Create/Change Condition Records
      • V/08: Pricing Procedure Configuration
      • XD03: Display Customer Master
      • MM03: Display Material Master
      • V/07: Access Sequence Configuration
    • 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 corrections to resolve it.

    Artificial intelligence solution provided by tomco.ai.
    Disclaimer
    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Feature Free Access Free Trial
Basic SAP error explanation T-Code Explanation T-Code Explanation 2
Step-by-Step Usage Guide Step-by-Step Step-by-Step 2
Interactive SAP Coach Assistance Interactive SAP Interactive SAP 2
AI Troubleshooting for T-Code Errors AI Troubleshooting AI Troubleshooting 2

Related SAP Error Messages

Click the links below to see the following related messages:


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.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author