How To Fix FARR_APPLICATION161 - POB &1: POB with Start Date Type 3 is not supported

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 161

• Message text: POB &1: POB with Start Date Type 3 is not supported

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_APPLICATION161 - POB &1: POB with Start Date Type 3 is not supported ?

  The SAP error message FARR_APPLICATION161 indicates that there is an issue with a Purchase Order (POB) that has a start date of type 3, which is not supported in the context of the application you are using. This error typically arises in the context of Asset Accounting (FI-AA) or related modules where certain date types are expected.
  Cause:
  The error is caused by the following:
  
  The Purchase Order (POB) you are trying to process has a start date that is classified as type 3. In SAP, date types are used to define how dates are interpreted and processed. Type 3 may refer to a specific type of date that is not compatible with the operations you are trying to perform.
  The configuration or settings in the system may not support this type of date for the specific transaction or process you are executing.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Start Date: Review the start date of the Purchase Order (POB) in question. Ensure that it is set to a valid date type that is supported by the system. You may need to change the date type to one that is compatible.
  
  
  Review Configuration: Check the configuration settings in the Asset Accounting module or the relevant module you are working with. Ensure that the date types and their usage are correctly defined.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on date types and their implications in your context. This can provide insights into what date types are supported and how to configure them.
  
  
  Contact SAP Support: If you are unable to resolve the issue through the above steps, consider reaching out to SAP support for assistance. They can provide guidance based on the specific version of SAP you are using and any customizations that may be in place.
  
  
  Testing: After making any changes, perform testing to ensure that the error no longer occurs and that the Purchase Order can be processed as expected.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context on handling date types in your version of SAP.
  Transaction Codes: Familiarize yourself with transaction codes related to Asset Accounting and Purchase Orders, as they may provide additional insights into the data and settings you need to review.
  User Forums: Consider visiting 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 cause of the error and implement a solution to resolve it.