How To Fix VE108 - Condition record exists, but has not been set


VE108 - Overview

  • Message type: E = Error

  • Message class: VE - Message ID for condition analysis

  • Message number: 108

  • Message text: Condition record exists, but has not been set

  • Show details Hide details
  • This message tells you that the condition record exists, but has not
    been set in the document. If pricing was carried out again for the
    document item, then the condition would be set.

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    There are different reasons for this:
    The condition was deleted manually in the item condition screen.
    The condition record was created later. Please note that order
    processing and pricing have buffer mechanisms. This means that a newly
    added condition record might only be found after order processing has
    been left completely and then started again.
    If the condition type is used for subsequent settlement (rebate), there
    may be subsequent updating of business volume (the agreement is is
    created retrospectively). The document conditions do not contain the
    condition record, as the condition record was not created when pricing
    was carried out. Updating of business volume is carried out using
    special functions for subsequent settlement.
    When an item was added, the condition record was accessed with key
    fields other than change time. This could lead to different results in
    the requirements check at the time of adding and the change time. This
    can occur when modifications are made.
    In billing (or when copying orders): Certain condition types were not
    determined in the source document (this is usually controlled by the
    pricing requirements). When creating the document, the document flow
    (TVCPF,TVCPA) is processed using a pricing type that does not
    redetermine these condition types, although they are supposed to be
    called via the requirements.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message VE108 - Condition record exists, but has not been set ?
    The SAP error message VE108 ("Condition record exists, but has not been set") typically occurs in the context of pricing and condition records in the SAP system, particularly when dealing with sales and distribution (SD) or materials management (MM) modules. This error indicates that there is a condition record that exists in the system, but it has not been properly assigned or activated for the specific transaction you are trying to execute.
    
    Cause: Missing Assignment: The condition record exists in the database, but it is not assigned to the relevant pricing procedure or the specific transaction (e.g., sales order, purchase order). Incorrect Condition Type: The condition type being used may not be correctly configured or may not be applicable for the transaction. Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the condition record from being applied. Condition Record Status: The condition record may be inactive or not valid

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant