How To Fix FARR_INFLIGHT_CHECK017 - C1801: POB-PAOBJNR <> POSTING-PAOBJNR, Contract &1/POB &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 017

• Message text: C1801: POB-PAOBJNR <> POSTING-PAOBJNR, Contract &1/POB &2

What causes this issue?

For the following post category, the profitablity segement is different
from the one on the POB.
-,,(RV)Revenue
-,,(ED)Exchange difference
-,,(IC)Invoice correction
-,,(CO)Cost
-,,(CC/CE)Cost correction/Exceptional cost correction

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

RAI processing is stopped or manual interaction is stopped.

How to fix this error?

You can search for SAP Note by the term FARR_INFLIGHT_CHECK and C17, and
implement related notes

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_INFLIGHT_CHECK017 - C1801: POB-PAOBJNR <> POSTING-PAOBJNR, Contract &1/POB &2 ?

  The SAP error message FARR_INFLIGHT_CHECK017 C1801 indicates a mismatch between the object numbers in a contract and a purchase order (POB). Specifically, the error message states that the POB-PAOBJNR (the object number from the purchase order) does not match the POSTING-PAOBJNR (the object number from the posting). This typically occurs in the context of contract management and procurement processes in SAP.
  Cause:
  
  
  Data Mismatch: The most common cause of this error is that the object numbers associated with the contract and the purchase order do not match. This can happen if:
  
  The contract was modified after the purchase order was created.
  The purchase order was created with incorrect references.
  There are inconsistencies in the data due to manual entry errors or system issues.
  
  
  
  Incorrect Configuration: There may be configuration issues in the system that lead to incorrect object number assignments.
  
  
  Incomplete Document Flow: If the document flow between the contract and the purchase order is not properly maintained, it can lead to discrepancies.
  
  
  Solution:
  
  
  Verify Object Numbers: Check the object numbers in both the contract and the purchase order. Ensure that they are correctly linked and match as expected.
  
  
  Review Document Flow: Ensure that the document flow between the contract and the purchase order is intact. You can do this by checking the related documents in SAP.
  
  
  Correct Data Entry: If there are discrepancies due to manual entry, correct the entries in the relevant documents.
  
  
  Recreate Documents: If the issue persists and cannot be resolved through corrections, consider recreating the purchase order or contract to ensure that the object numbers are correctly assigned.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes or updates that may address this specific error. Sometimes, SAP releases patches or notes that provide solutions for known issues.
  
  
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant transaction codes.
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) and ME33K (Display Contract) to review the details of the documents involved.
  SAP Documentation: Refer to SAP Help documentation for more information on contract management and purchase order processing.
  User Forums: Check SAP community forums or user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.