How To Fix FARR_PROCESS_CHECK036 - Condition type &2 of POB &1 is deleted and changed at the same time

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_PROCESS_CHECK - Messages for Input Checks in Process Layer

• Message number: 036

• Message text: Condition type &2 of POB &1 is deleted and changed at the same time

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_PROCESS_CHECK036 - Condition type &2 of POB &1 is deleted and changed at the same time ?

  The SAP error message FARR_PROCESS_CHECK036 indicates that there is a conflict in the processing of a condition type in the context of a Purchase Order (POB). Specifically, it states that a condition type (identified by &2) for a particular Purchase Order (identified by &1) has been both deleted and changed simultaneously, which is not allowed.
  Cause:
  This error typically arises in the following scenarios:
  
  Concurrent Changes: There may be multiple users or processes trying to modify the same condition type for a Purchase Order at the same time, leading to a conflict.
  Inconsistent Data: The system may have inconsistent data where the condition type is marked for deletion while also being modified.
  Custom Logic: If there are custom enhancements or modifications in the SAP system that affect the processing of condition types, they may inadvertently lead to this error.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check for Concurrent Processes: Ensure that no other users or processes are trying to modify the same Purchase Order or condition type at the same time. If possible, coordinate with other users to avoid simultaneous changes.
  
  
  Review Change Logs: Check the change logs for the Purchase Order to identify any recent changes made to the condition type. This can help you understand if there were conflicting changes.
  
  
  Revert Changes: If you identify that a condition type was marked for deletion but also modified, revert the changes to a consistent state. You may need to restore the condition type if it was deleted.
  
  
  Data Consistency Check: Run a consistency check on the relevant data to ensure that there are no inconsistencies in the condition types and Purchase Orders.
  
  
  Consult Documentation: Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They may provide insights based on the specific configuration and customizations in your system.
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) or ME22N (Change Purchase Order) to review the Purchase Order details and condition types.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  User Exits and BAdIs: If there are custom developments in your system, check for any user exits or BAdIs that might be affecting the processing of condition types.
  
  By following these steps, you should be able to identify and resolve the issue causing the FARR_PROCESS_CHECK036 error in your SAP system.