How To Fix FARR_APPLICATION172 - POB &1: Post migration custom consistency check failed

FARR_APPLICATION172 - Overview

• Message type: E = Error

• Message class: FARR_APPLICATION - General Revenue Accounting Applications and Code

• Message number: 172

• Message text: POB &1: Post migration custom consistency check failed

What causes this issue?

After contract data is migrated it is being checked by FARR_CONTR_MON
transaction API. Only after this check the data can be saved in
database. If any custom error category is found for any performance
obligations of the contract during this check then whole the contract is
excluded from migration and error message is written in the processing
log.

System Response

Affected contract is not migrated.

How to fix this error?

Analysis via debugging is necessary here as in this case temporary data
is checked.

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_APPLICATION172 - POB &1: Post migration custom consistency check failed ?

  The SAP error message FARR_APPLICATION172 indicates that a post-migration custom consistency check has failed in the context of the Asset Accounting (FI-AA) module. This error typically arises after a migration process, such as when migrating from a legacy system to SAP S/4HANA or during a system upgrade.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Data Inconsistencies: There may be inconsistencies in the asset data that were not resolved before the migration. This could include missing or incorrect values in key fields.
  
  
  Customizations: If there are custom developments or enhancements in the asset accounting area, these may not be compatible with the new system or may not have been properly adjusted during the migration.
  
  
  
  Configuration Issues: Incorrect configuration settings in the Asset Accounting module can lead to inconsistencies that trigger this error.
  
  
  Missing Master Data: Required master data for assets may be missing or incomplete, leading to validation failures during the consistency check.
  
  
  
  Solution:
  To resolve