How To Fix FARR_CONTRACT_MAIN880 - Recognized Revenue acct. cannot derive for per. ob. &1


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

  • Message number: 880

  • Message text: Recognized Revenue acct. cannot derive for per. ob. &1

  • Show details Hide details
  • What causes this issue?

    None of the account determination rules that you have defined return the
    <ZK>Recognized Revenue</> account as expected.

    System Response

    The system prevents the performance obligation and its contract from
    being created or updated. The contract is listed in the Contracts with
    Errors worklist for review.

    How to fix this error?

    Make sure that at least one of the determination rules can return a G/L
    account as the Recognized Revenue account. This account is determined by
    the rules in the <LS>Recognized Revenue</> section.
    <ZH>Note</>: This typically occurs when the attributes of the
    performance obligation and the reference account do not match any of the
    determination rules that you have defined for this account.

    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 FARR_CONTRACT_MAIN880 - Recognized Revenue acct. cannot derive for per. ob. &1 ?

    The SAP error message FARR_CONTRACT_MAIN880 indicates that the system is unable to derive the recognized revenue account for a particular period obligation. This typically occurs in the context of contract accounting or revenue recognition processes in SAP, particularly when using the SAP Revenue Accounting and Reporting (RAR) module.

    Cause:

    The error can be caused by several factors, including:

    1. Missing Configuration: The recognized revenue account may not be properly configured in the system. This could be due to missing settings in the revenue recognition configuration or in the account determination settings.

    2. Incorrect Account Assignment: The account assignment for the revenue recognition may not be correctly set up in the contract or the related master data.

    3. Period Obligation Issues: The specific period obligation referenced in the error message may not have the necessary data or configuration to derive the recognized revenue account.

    4. Missing Master Data: Required master data (like revenue accounts, cost elements, etc.) may be missing or incorrectly maintained.

    5. Transaction Type Issues: The transaction type used in the contract may not be linked to the correct revenue recognition process.

    Solution:

    To resolve the error, you can take the following steps:

    1. Check Configuration:

      • Go to the configuration settings for revenue recognition in SAP (Transaction code: SPRO).
      • Ensure that the recognized revenue accounts are correctly defined in the account determination settings.
    2. Review Contract Settings:

      • Check the contract associated with the period obligation to ensure that all necessary account assignments are correctly maintained.
      • Verify that the contract type is correctly set up for revenue recognition.
    3. Validate Period Obligation:

      • Review the specific period obligation mentioned in the error message to ensure it has the necessary data and is correctly configured.
    4. Check Master Data:

      • Ensure that all relevant master data (like revenue accounts, cost elements, etc.) is correctly maintained and available in the system.
    5. Consult Documentation:

      • Refer to SAP documentation or help resources for specific guidance on the configuration of revenue recognition and account determination.
    6. Testing:

      • After making changes, perform tests to ensure that the recognized revenue account can now be derived correctly.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as:

      • SPRO: For configuration settings.
      • FARR: For revenue accounting and reporting.
      • SE11: For checking table definitions related to revenue recognition.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.

    • User Forums: Engage with SAP community forums or user groups for additional insights and solutions from other users who may have encountered similar issues.

    If the problem persists after following these steps, it may be beneficial to consult with an SAP functional consultant who specializes in revenue accounting and reporting for further assistance.

    • 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