How To Fix FARR_CONTRACT_MAIN273 - POB &1 marked as contr. acquisit. cost cannot be updated to standard POB.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 273

• Message text: POB &1 marked as contr. acquisit. cost cannot be updated to standard POB.

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_MAIN273 - POB &1 marked as contr. acquisit. cost cannot be updated to standard POB. ?

  The SAP error message FARR_CONTRACT_MAIN273 typically occurs in the context of Asset Accounting (FI-AA) when there is an issue with the posting of acquisition costs for a particular asset or contract. The message indicates that a specific Purchase Order (POB) marked as a contract acquisition cost cannot be updated to the standard Purchase Order (POB).
  Cause:
  
  Incorrect Configuration: The configuration settings for asset acquisition or the related purchase order may not be set up correctly.
  Status of the Purchase Order: The purchase order might be in a status that does not allow for updates (e.g., it could be closed or completed).
  Missing Authorizations: The user may not have the necessary authorizations to perform the update.
  Data Inconsistencies: There may be inconsistencies in the data related to the asset or the purchase order that prevent the update.
  System Errors: There could be a temporary system error or inconsistency in the database.
  
  Solution:
  
  Check Purchase Order Status: Verify the status of the purchase order. If it is closed or completed, you may need to reopen it or create a new one.
  Review Configuration: Ensure that the configuration for asset acquisition and related settings in the Asset Accounting module is correct.
  User Authorizations: Check if the user has the necessary authorizations to perform the update. If not, contact your system administrator to grant the required permissions.
  Data Consistency Check: Run consistency checks on the asset and purchase order data to identify and resolve any discrepancies.
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Debugging: If the issue persists, consider debugging the process to identify the exact point of failure. This may require assistance from a technical consultant or SAP support.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), and ME23N (Display Purchase Order) to navigate through the asset and purchase order management processes.
  SAP Documentation: Refer to the official SAP documentation for Asset Accounting and Purchase Order management for detailed guidance on configuration and processes.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.