Question regarding usage of CRM pricing conditions using date ranges

[Former Member]

Hi,

I wonder if someone has a suggestion regarding how to set up pricing conditions in CRM to accomplish the following scenario:

For existing customers we want to “freeze” the product price for certain customers,
but at the same time let other customers get another prize for the same product
and period.

(We have scenarios where the product price changes retroactively, years back in time, but only for those custoemrs that  fulfill a specific criteria at the time where the prize change was decided to take place..)

We want the prize to be dependent on the customer status AND when this status was set
(before a specific date), but there doesn’t seem to be a way to set up pricing
conditions with date ranges (i e "customer status changed before YYYYMMDD
renders prize X").

Since we are talking about quite a lot of customers we do not want to add each and every
one of them as “individual price items” in the pricing conditions tables.

Does anyone have an idea regarding how to set this up?

Thanks

/Marika Wasserman

[baris_yalcin]

Hi Marika,

condition records have validity (FROM - TO). Let us assume you have a condition record for product A with 50 EUR per piece and this record is valid from 01.01.2014 until 31.12.2014.
If you create CRM Sales Order having product A at 4.12.2014 and this date is used as pricing date for the conditon determination, then it will find this condition record with price 50 EUR per piece. This 50 EUR should be the froen price.

Now how can you achieve that for the same CRM Sales Order another product price is determined for certain customer or a certain customer group?

The idea is to pass an additional pricing attribute, e.g. customer group. Then you can create a new condition table with this field with the key fields product and customer group. In the access seqeunce first the new condition table is checked and if no record is found, then the second conditon table is checked as shown below:

Access Sequence ABC

• Access 10: condition table with key fields product + customer group
• Access 20: condition table only key field product

Instead of customer group you define also any other field. You create your own implementation of the BAdI  CRM_COND_COM_BADI that passes this field with a value to pricing.

Best regards,
Baris Yalcin