Scales with COndition Supplements-

[reazuddin_md]

Hai ALL,

Here is a regular issue with the scales,

Req:

is We have Spl Price- ( which is 2% on Basic Price) upto certain no.of components eg: Upto 100 EA.

I have maintained the same in Condition Supplements ( By tick mark in Price Cond type-)

Then,

Created Sales Order -1 , For 30 EA.

System is picking Basic Price & Spl Price-2% - which is correct.

in Sales Order-2, 75 EA

now how the system behaves- means system should pick

70 EA- Basic Price & Spl Price -2%

5 EA - Only Basic Price- ( bcoz as per agreement customer reached 100 EA, above 100 EA- Spl Price is not applicable)

But system is considering 75 EA ( which is below 100 EA) & picking Basic Price & Spl Price-2%, its not considering previous requirement)

how to achieve it.

My issue is: Once Customer reaches more than 100 EA, system should not pick Spl Price-2% ( it should consider previous order req's too)

[Former Member]

Hi,

I did similar development without condition supplements recently. You need to tick "condition update" in your condition:

"Controls whether limit values are relevant for pricing.

E.g.: you can make the use of a particular condition record in the

document dependent on a specified total value.

This total value can be specified in the condition record."

We also needed to implement a scale formula taking care about the calculation of the accumlated values that are stored in S060 when a new order as created.

Good Luck

[Former Member]

Hi,

maintain the scales in condition record like below

upto 100 units----

---

2%

101 units----

---

keep blank

try and revert back please

regards,

sadanandam kasarla

[reazuddin_md]

upto 100 units----

---

2%

101 units----

---

keep blank

Have done this before Posting-itself

System is considering Scale: Upto 100 Units - 2%, for that specific Sales order. It is nt considering previous orders. ( where as Customer already placed 35 Ea in his First Sales order)

In 2nd Sales order, when i entered 70- its treating as "Upto 100 Units"- 2 % is copying, which is not correct.

system should take into considertation of previous sales order qtty, when calculating Scales.

Hope, Now you are clear abt my req.

[Former Member]

Hi

Your requirement is for 100 EA only DIS -2% condition type will trigger after that it should not come into picture.

Suppose your base price for that material is $50.

Goto Tcode V/06 select your condition type and tick the "Condition update" check box.

Save it.

Then, create the condition record (T code VK11) for the condition type, enter the material number, rate, validity period etc.

After filling up all your data, now click on the Menu: Goto-->Additional data.

In the "Additonal Sales data" screen , you will find a field called "Max.cond.base value", here enter value

$50 X 100 = "5000" and save your condition record.

So once the discount condition type reaches 5000 it will stop automatically.

try and reply.

[reazuddin_md]

As per your reply.

Let me tell you onething is,

My Baseprice may not be always 50$, that could be change after 2 months r 4 months in between.

Will it consider Previous order values also? -

[Former Member]

Hi

It will consider all orders falls under VK11 Valid to and valid from dates.

If you will change the base price not the Valid from date, it will consider previous orders also.

For your confirmation, test it in developement server.

Try and revert.

[reazuddin_md]

Can you explain a lit bit.

If it is working fine for you. Will implement same in my case also, bcoz the scenario is matching.

- I have created ZPRO- Price cond

- Spl Price - ZSPR- Special price with Percentage

in Pricing Procedure -

step 10- ZPRO-

Step 20 -ZSPR - From(10)-

Now in VK11- I have maintained cond reocrd for ZPRO only ( not for ZSPR , bcoz ZSPR always depends on ZPRO) -

enter material & amount

clik on additonal cond supplements- entered ZSPR-with %.

in additional data- maintained Max cond base value- 100 EA & save

( which means, upto 100EA ,ZSPR should be active, once customer reaches / cumulative values reached 100 EA, ZSPR should deactivate-)

but its not working as expected. its considering only for this transaction-

ANY MORE SUGGESTIONS

Edited by: SAP.Student on Feb 24, 2009 6:48 PM