How To Fix FARR_CONTRACT_MAIN887 - Cost correction posted but no goods issue found for per. ob. &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 887

• Message text: Cost correction posted but no goods issue found for per. ob. &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_CONTRACT_MAIN887 - Cost correction posted but no goods issue found for per. ob. &1 ?

  The SAP error message FARR_CONTRACT_MAIN887 indicates that a cost correction has been posted, but there is no corresponding goods issue found for the specified period. This error typically arises in the context of contract management and asset accounting, particularly when dealing with asset-related transactions.
  Cause:
  
  
  Missing Goods Issue: The primary cause of this error is that a goods issue (GI) has not been posted for the asset or contract in question. This means that while the cost correction has been recorded, the system cannot find a corresponding goods movement that would justify this cost.
  
  
  Timing Issues: The goods issue may have been posted in a different period than the one specified in the error message, leading to a mismatch.
  
  
  Incorrect Configuration: There may be configuration issues in the asset accounting or materials management modules that prevent the system from recognizing the goods issue.
  
  
  Data Inconsistencies: There could be inconsistencies in the data related to the asset or contract, such as missing or incorrect entries.
  
  
  Solution:
  
  
  Check Goods Issue: Verify if a goods issue has been posted for the asset or contract in question. If it has not been posted, you will need to create a goods issue to resolve the error.
  
  
  Review Posting Periods: Ensure that the goods issue is posted in the correct period. If the goods issue was posted in a different period, you may need to adjust the posting or correct the period.
  
  
  Reconcile Data: Check for any inconsistencies in the data related to the asset or contract. This may involve reviewing the asset master data, contract details, and any related transactions.
  
  
  Configuration Check: Review the configuration settings in the asset accounting and materials management modules to ensure they are set up correctly.
  
  
  Consult Documentation: Refer to SAP documentation or support notes related to this specific error message for additional guidance and troubleshooting steps.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MB1A (Goods Withdrawal), MB1B (Transfer Posting), and F-90 (Asset Acquisition) to manage goods issues and asset postings.
  SAP Notes: Look for SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.