How To Fix FARR_CONTRACT_MAIN882 - Deferred Cost 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: 882

  • Message text: Deferred Cost 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
    Deferred Cost 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 <ZK>Deferred Cost</> account. This account is determined
    by the rules in the <LS>Deferred Cost</> 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_MAIN882 - Deferred Cost acct. cannot derive for per. ob. &1 ?

    The SAP error message FARR_CONTRACT_MAIN882 indicates that the system is unable to derive a deferred cost account for a specific period and object. This typically occurs in the context of contract accounting or asset accounting when the system is trying to post a transaction but cannot find the appropriate account to use for deferred costs.

    Cause:

    1. Missing Configuration: The most common cause is that the necessary configuration for deferred cost accounts is not set up in the system. This could be due to missing account assignments in the relevant configuration tables.
    2. Incorrect Master Data: The master data for the contract or asset may not be correctly maintained, leading to the inability to derive the account.
    3. Period Issues: The specified period may not be open for posting, or there may be restrictions on posting to that period.
    4. Account Determination Issues: The account determination settings may not be correctly defined for the specific transaction type or object.

    Solution:

    1. Check Configuration:

      • Go to the configuration settings for account determination in the SAP system. This can typically be found under SPRO -> Financial Accounting -> Accounts Receivable and Payable -> Account Determination.
      • Ensure that the deferred cost accounts are correctly defined for the relevant transaction types and that the necessary account assignments are in place.
    2. Review Master Data:

      • Check the master data for the contract or asset involved in the transaction. Ensure that all required fields are filled out correctly and that the account assignments are valid.
    3. Verify Posting Period:

      • Check if the posting period is open. You can do this by navigating to Transaction Code OB52 to see the open and closed periods.
      • If the period is closed, you may need to open it or post the transaction in an open period.
    4. Test Account Determination:

      • Use transaction OBYC to check the account determination settings for the relevant transaction type. Ensure that the correct accounts are assigned for deferred costs.
    5. Consult Documentation:

      • Review SAP documentation or help resources for any specific notes related to this error message. There may be additional guidance or patches available.
    6. Contact Support:

      • If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as OBYC (for account determination), OB52 (for posting periods), and FBL1N (for vendor line items) to help diagnose the issue.
    • SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal, as there may be specific fixes or recommendations provided by SAP.
    • Testing: After making any changes, perform a test transaction to ensure that the issue is resolved.

    By following these steps, you should be able to identify and resolve the cause of the error message FARR_CONTRACT_MAIN882 in your SAP system.

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