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

SAP Error Message - Details

• 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 the FARR_APPLICATION172 error, you can follow these steps:
  
  
  Review the Error Log: Check the detailed error log for specific information about what failed during the consistency check. This can provide insights into which assets or data points are causing the issue.
  
  
  Run Consistency Checks: Use transaction codes like ABAP or SARA to run consistency checks on your asset data. This can help identify and rectify inconsistencies.
  
  
  Correct Data Issues: Based on the findings from the error log and consistency checks, correct any data inconsistencies. This may involve updating asset master records, correcting values, or ensuring that all required fields are populated.
  
  
  Check Custom Code: If there are custom developments, review the code to ensure it is compatible with the new system. You may need to adjust or rewrite custom logic to align with the new data structures.
  
  
  Configuration Review: Verify the configuration settings in the Asset Accounting module to ensure they are set up correctly for the new environment.
  
  
  Consult Documentation: Refer to SAP Notes and documentation related to the migration process for any specific guidance or known issues related to your version of SAP.
  
  
  Engage SAP Support: If the issue persists after performing the above steps, consider reaching out to SAP Support for assistance. They can provide more targeted help based on your specific system configuration and migration scenario.
  
  
  Related Information:
  
  SAP Notes: Look for relevant SAP Notes that address this specific error or provide guidance on post-migration checks.
  Migration Guides: Review the official SAP migration guides for your version, as they often contain best practices and common pitfalls to avoid.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can share their solutions.
  
  By following these steps, you should be able to identify the root cause of the FARR_APPLICATION172 error and implement the necessary corrections to resolve it.