CCM - use multiple condition tables within one condition contract

[SD_Jedi]

Dear gurus,

Is it possible to use different rebate percentages across condition tables within the same condition contract? Without summing all of the percentages when settling the contract?

I have following business scenario:

• Rebate: Agreement with customer to pay overall 6% rebate based on business volume. However, for one specific material group (let's call it material group A), the customer receives 8% rebate.
• Accrual: Should follow the same logic as the rebate percentages i.e., 6% overall, but for material group A we want to accrue 8%.

I am trying to achieve this by using 2 condition tables within same access sequence:

• Cond table 1: Condition contract / Material group
• Cond table 2: Condition contract

I am entering both REA1 and RES1 in the condition contract:

• Cond table 1: condition contract nr / material group A = 8%
• Cond table 2: condition contract nr = 6%

Scenario: I only have business volume of sales of material within material group A.
Expectation: Both accruals and rebate would be posted with 8%
The issue I am encountering: At time of settlement both RES1 condition records are found, ending up in 14% instead of 8%. How can I set up my condition contract to achieve my goal? Business wants to avoid to enter all of the material groups, hence, I am trying to use multiple condition tables within one contract.

For the accruals, there is no issue, we can use the exclusive indicator in the access sequence together with routine 67.

Thank you.

[GauthierVictor]

Hi @SD_Jedi, 

Thanks for the detailed explanation—your scenario is standard and should work correctly with proper access sequence setup.

I recommend copying the standard access sequence RE01 and adding your custom condition table (Contract / Material Group). Make sure to activate the "Exclusive" indicator and assign Requirement 75 to the first step. This ensures the system stops searching once a condition is found for the material group and avoids summing multiple rebate percentages. For the fallback step (Contract only), leave the exclusive flag and requirement blank. This configuration should give you the expected behavior: 8% for material group A and 6% otherwise, without doubling values.

If you're still seeing incorrect results, check for any enhancements or custom logic that might be overriding standard pricing behavior.

Best regards,
Gauthier Victor