How To Fix FARR_RAI689 - Item &2: Condition type &1 was not created


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FARR_RAI - Revenue Accounting Item

  • Message number: 689

  • Message text: Item &2: Condition type &1 was not created

  • Show details Hide details
  • What causes this issue?

    <LS>Condition Type</> was not created in Revenue Accounting.

    System Response

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

    How to fix this error?

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FARR_RAI689 - Item &2: Condition type &1 was not created ?

    The SAP error message FARR_RAI689 indicates that a specific condition type (denoted as &1) for a particular item (denoted as &2) was not created in the system. This error typically arises in the context of the SAP Revenue Accounting and Reporting (RAR) module, which is used for managing revenue recognition processes.

    Cause:

    1. Missing Configuration: The condition type may not have been configured properly in the system. This could be due to missing entries in the customizing settings for revenue recognition.
    2. Incorrect Condition Type: The condition type specified may not exist in the system or may not be valid for the transaction being processed.
    3. Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect master data related to the condition type.
    4. Authorization Issues: The user may not have the necessary authorizations to create or access the specified condition type.

    Solution:

    1. Check Configuration:

      • Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant section for configuring condition types in RAR. Ensure that the condition type is defined and properly configured.
      • Verify that the condition type is assigned to the appropriate pricing procedure.
    2. Validate Condition Type:

      • Check if the condition type exists in the system. You can do this by using transaction codes like V/06 (for condition types) or V/08 (for pricing procedures).
      • Ensure that the condition type is valid for the specific item and transaction.
    3. Review Master Data:

      • Check the master data related to the item in question. Ensure that all necessary data is complete and accurate.
      • Look for any missing entries in the relevant tables that might be causing the issue.
    4. Authorization Check:

      • Ensure that the user has the necessary authorizations to create or modify the condition type. This can be checked with the help of your SAP security team.
    5. Consult Documentation:

      • Review SAP documentation or notes related to the specific error message for any additional guidance or known issues.
    6. Debugging:

      • If the issue persists, consider debugging the process to identify where the failure occurs. This may require the assistance of a technical consultant.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as V/06, V/08, FARR, and others related to revenue accounting.
    • SAP Notes: Check SAP Notes for any updates or patches that may address this specific error.
    • Community Forums: Engage with SAP community forums or support channels for additional insights from other users who may have encountered similar issues.

    By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.

    • 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