How To Fix FARR_MSG_CUSTOM513 - ContAcqui cost can't be processed; Cost recog not defined for POB &1.

FARR_MSG_CUSTOM513 - Overview

• Message type: E = Error

• Message class: FARR_MSG_CUSTOM - Customizable Messages for Revenue Accounting

• Message number: 513

• Message text: ContAcqui cost can't be processed; Cost recog not defined for POB &1.

What causes this issue?

Performance obligation &v1& is not configured to perform cost
recognition.

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?

Make sure the performance obligation is defined for cost recognition as
follows:
The accounting principle of the performance obligation is defined for
cost recognition in Customizing
<DS:SIMG.FARR_VC_ACCT_PR>Configure Accounting Principle-specific
Settings</>.
The type of the performance obligation is defined for cost recognition
in Customizing
<DS:SIMG.FARR_POB_TYPE>Define Performance Obligation Types</>.
The performance obligation is defined for cost recognition in decision
table DT_PROCESS_POB of BRFplus.
Note: If you don't want certain performance obligations to perform cost
recognition, you can customize this message as a warning message or
simply switch this message off.

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_MSG_CUSTOM513 - ContAcqui cost can't be processed; Cost recog not defined for POB &1. ?

  The SAP error message FARR_MSG_CUSTOM513 indicates that there is an issue with the processing of acquisition costs in the context of a specific Purchase Order (POB) or asset. The message states that the cost recognition is not defined for the specified POB, which means that the system cannot determine how to handle the acquisition costs for that particular asset or transaction.
  
  Cause:
  
  Missing Configuration: The most common cause of this error is that the configuration for cost recognition is not set up for the specific Purchase Order or asset type in the system.
  Incorrect Asset Class: The asset class associated with the asset may not have the necessary settings for cost recognition.
  Missing Master Data: There may be missing or incomplete master data related to the asset or the acquisition costs.
  Transaction Type Issues: The transaction type used for the acquisition may not be properly configured to handle cost recognition.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings