How To Fix LOG_TRM_INTEGRATION035 - Adjustment condition type &1 is used twice for condition type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: LOG_TRM_INTEGRATION - General message class for Logistic to Treasury Integration

• Message number: 035

• Message text: Adjustment condition type &1 is used twice for condition type &2

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 LOG_TRM_INTEGRATION035 - Adjustment condition type &1 is used twice for condition type &2 ?

  The SAP error message LOG_TRM_INTEGRATION035 indicates that there is a conflict in the configuration of condition types within the pricing procedure. Specifically, it means that the adjustment condition type (denoted as &1) is being used more than once for the specified condition type (denoted as &2). This can lead to inconsistencies in pricing calculations and is typically encountered in the context of sales and distribution (SD) or materials management (MM) modules.
  Cause:
  
  Duplicate Configuration: The adjustment condition type has been assigned multiple times in the pricing procedure for the same condition type.
  Incorrect Customization: There may be an error in the customization settings where the same adjustment condition type is inadvertently linked to the same condition type.
  Data Migration Issues: If data has been migrated from another system or if there have been recent changes in the configuration, it may lead to duplicate entries.
  
  Solution:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 (for SD) or M/08 (for MM) to access the pricing procedure configuration.
  Identify the pricing procedure that is being used and check the condition types assigned to it.
  Look for the adjustment condition type (e.g., discounts, surcharges) and ensure it is not listed more than once for the same condition type.
  
  
  
  Remove Duplicates:
  
  If you find that the adjustment condition type is indeed listed multiple times, remove the duplicate entries.
  Ensure that each condition type is only linked to the adjustment condition type once.
  
  
  
  Test Changes:
  
  After making changes, perform a test transaction to ensure that the error no longer occurs and that pricing calculations are functioning as expected.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP functional consultant for best practices regarding pricing procedure configuration.
  
  
  
  Transport Changes:
  
  If you are working in a development environment, ensure that any changes made are transported to the quality and production environments as necessary.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  V/08 - Maintain Pricing Procedures (SD)
  M/08 - Maintain Pricing Procedures (MM)
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the LOG_TRM_INTEGRATION035 error and ensure that your pricing procedures are correctly configured.