How To Fix FARR_CONTRACT_MAIN883 - Recognized 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: 883

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

What causes this issue?

None of the account determination rules that you have defined return the
<ZK>Recognized COGS</> 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>Recognized COGS</> account. This account is
determined by the rules in the <LS>Recognized COGS</> 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_MAIN883 - Recognized Cost acct. cannot derive for per. ob. &1 ?

  The SAP error message FARR_CONTRACT_MAIN883 indicates that the system is unable to derive the recognized cost account for a particular period object. This typically occurs in the context of contract accounting or asset accounting, where the system needs to determine the appropriate account for recognized costs based on the configuration and data provided.
  Cause:
  
  Missing Configuration: The recognized cost account may not be properly configured in the system. This could be due to missing entries in the relevant configuration tables or settings.
  Period Object Issues: The period object (&1) referenced in the error may not be correctly set up or may not have the necessary data associated with it.
  Account Determination: The account determination process may not be able to find a valid account based on the criteria defined in the system.
  Master Data Issues: There may be issues with the master data related to the contract or asset that is causing the account determination to fail.
  
  Solution:
  
  
  Check Configuration:
  
  Navigate to the configuration settings for account determination in the relevant module (e.g., Contract Accounting or Asset Accounting).
  Ensure that the recognized cost accounts are correctly defined for the relevant period objects.
  
  
  
  Review Period Object:
  
  Check the details of the period object (&1) mentioned in the error message.
  Ensure that it is correctly set up and that all necessary data is populated.
  
  
  
  Account Determination Process:
  
  Review the account determination process to ensure that it is correctly configured to derive the recognized cost account.
  You may need to consult the documentation or configuration guides for the specific module you are working with.
  
  
  
  Master Data Validation:
  
  Validate the master data for the contract or asset involved. Ensure that all required fields are filled out and that there are no inconsistencies.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the recognized cost account can now be derived correctly.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBYC (for account determination) or OAA3 (for asset accounting) to check and modify the relevant settings.
  Documentation: Refer to SAP Help documentation for detailed information on account determination and recognized costs in the context of your specific SAP module.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.