How To Fix OT814 - Line &1: Equivalence condition must only have prerequisite type 'A/C'


SAP Error Message - Details

  • Message type: E = Error

  • Message class: OT - SAP Online Correction Support (SOCS)

  • Message number: 814

  • Message text: Line &1: Equivalence condition must only have prerequisite type 'A/C'

  • Show details Hide details
  • <ZK>&CAUSE&</>
    You have defined an equivalent import condition that does not use
    prerequisite type "A" or "C" in the first line.
    For equivalent import conditions the software component with your
    release must be created in the first line of a logical AND block.
    Accordingly, prerequisite type 'A' or 'C' must be used in the this
    line.
    In the second lines you can only include the support package level.
    Accordingly, this line must contain prerequisite type 'P'.
    It is not possible to create more than two lines.
    This is not the case in the defined equivalent import condition.der

    System Response

    The import condition check is terminated.

    How to fix this error?

    Check the import conditon and correct the entry with errors.
    Import condition with errors (line) : &V1&

    Procedure for System Administrators

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


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message OT814 - Line &1: Equivalence condition must only have prerequisite type 'A/C' ?

    The SAP error message OT814 indicates that there is an issue with the equivalence condition in a condition record, specifically that the prerequisite type must be either 'A' (for "All") or 'C' (for "Customer"). This error typically arises in the context of pricing conditions or other similar scenarios where equivalence conditions are defined.

    Cause:

    The error occurs when the equivalence condition is set up with a prerequisite type that is not allowed. In this case, the system expects the prerequisite type to be either 'A' or 'C', but it has been set to a different type (e.g., 'B' for "Material" or any other type).

    Solution:

    To resolve this error, you need to check and correct the prerequisite type in the equivalence condition. Here are the steps to do this:

    1. Access the Condition Record:

      • Go to the transaction code where you can maintain the condition records (e.g., VK11 for creating or VK12 for changing).
    2. Locate the Condition:

      • Enter the relevant condition type and other required details to find the specific condition record that is causing the error.
    3. Check Prerequisite Type:

      • Review the equivalence condition settings. Look for the prerequisite type field and ensure it is set to either 'A' or 'C'.
    4. Modify the Prerequisite Type:

      • If the prerequisite type is incorrect, change it to 'A' or 'C' as appropriate for your business logic.
    5. Save Changes:

      • After making the necessary changes, save the condition record.
    6. Test the Changes:

      • After saving, test the transaction or process that was previously generating the error to ensure that it has been resolved.

    Related Information:

    • Prerequisite Types:

      • 'A' (All): This means that the condition applies to all relevant documents.
      • 'C' (Customer): This means that the condition is specific to a customer.
    • Documentation:

      • Refer to SAP documentation or help files for more details on condition records and equivalence conditions.
    • Transaction Codes:

      • VK11, VK12: For creating and changing condition records.
      • VK13: For displaying condition records.
    • Support:

      • If you continue to face issues, consider reaching out to your SAP support team or consulting the SAP community for further assistance.

    By following these steps, you should be able to resolve the OT814 error and ensure that your equivalence conditions are set up correctly.

    • 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.


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