cancel
Showing results for 
Search instead for 
Did you mean: 

Cumulative Pricing

sri_ram18
Participant
0 Kudos

Hi All,

I have got the requirement for cumulative pricing, also got to know that Condition type KUMU can be used, but i am not sure how its gonna work. Someone please explain in detail.

For instance here is the requirement,

Customers orders for 1562 items of same material

   Scale        Unit Price

1-500               15 Rs

501-1250          20 Rs

1251-2000        23 Rs

Now the system has to calculate as (500*15)+(750*20)+(312*23)

KUMU doesn't have any access sequence and this particular field StrucCond has been defined by a value B for which there is no access sequence. Where can this be placed(step) in pricing procedure.

Please let me know how can this be maintained in SAP.

Thanks,

Sriram

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Do you know about condition type PR02? it is used for pricing on graduated scale. Please maintain that settings in PR00 like scale type D and test. I am not sure about your requirements, but please check. It will surely have multiple lines for same condition type, but for each scale value. Just give it a try

sri_ram18
Participant
0 Kudos

Thanks Harish,

Maintained the following

1. Copied the standard Condition type PR02 to ZPR2,

2. Assigned it to the procedure.

3. Created the condition record with scale

Created the order in Va01for 15Qty, here is the screenshot,

it has calculated the wrong way, which should be (10*100)+(5*150)

Please Suggest.

Thanks,

Sriram

Former Member

Dear Sri

You have to maintain the condition records in a different way. Since it is "to" scale , you should maintain as to 10 qty - 100 rs and to 20 qty - 150 Rs.. Then your pricing will be correct. Please check and confirm

Answers (5)

Answers (5)

Former Member
0 Kudos

Maintain the condition record, a as I mentioned yesterday.

1-Rs 15

500-Rs.15

501-Rs.20

1250-Rs.20

1251-Rs.30

You have to see the condition record again.

Former Member
0 Kudos

Hi,

there an number of condition type according to which you can use them but that condition type should contain scales that should be of graduated basis .

follow some conditions for cumalative pricing procedure.

Cumulative conditions cannot be used as header conditions.

When you copy a sales document to a billing document, the condition rate and
the condition value of a cumulative condition is ‘frozen’. This means that the
condition is not redetermined when it is copied regardless of the pricing type.
The net value of the total is not redetermined even if the individual net values
have changed

sri_ram18
Participant
0 Kudos

Hi All,

Thanks for your time. As suggested did the changes to PR00 condition Type here is the screen shot

and scale has been defined in VK11 as below screenshot,

and after all these settings created an order with quantity 1 now the condition tab in Item level shows the duplicate price entry, screen shot as below

Please help.

Thanks,

Sriram.

former_member184065
Active Contributor
0 Kudos

Hi Sri,

I think u didnt save or else you were not maintain condition record with scales for these condition types for which you want.

please create condition record with scales for that condition type before put in relevant pricing procedure.

please  check which pricing procedure picked in sales document type in sales in header level

Thanks,

Naren K

Shiva_Ram
Active Contributor
0 Kudos

You are making changes in PR00 in VK11/12, where as your pricing screen shot reads ZVPR. Which one is correct one? Make the changes in the correct condition type and do the testing.

Regards,

Former Member
0 Kudos

Hi,

Change the scales in Control Data 2 in Condition Type as D.

And you can give this scales in condition Record.

Shiva_Ram
Active Contributor
0 Kudos

Please search the forum before posting as similar questions are answered many times in the past. For doing the required calculation, in t.code V/06,in the pricing condition type, go to scales box and add value D-graduated-to interval scale in the field scale type. You need not use KUMU condition type for this. If you need more info check at http://help.sap.com/saphelp_40b/helpdata/en/93/743505546011d1a7020000e829fd11/content.htm

Regards,

sri_ram18
Participant
0 Kudos

Hi Shiv Ram,

Thanks for the info and advise. As per your suggestion changed the condition Type PR00 Scales as below,

i have also maintained the Condition record PR00 VK11 as

Scale        Unit Price

1-500               15 Rs

501-1250          20 Rs

1251-2000        23 Rs

but still no joy in Sales order. Am i missing something here. Kindly let me know.

Thanks,

Sriram.

Shiva_Ram
Active Contributor
0 Kudos

Once changes are made in SPRO, you need to create a new sales order and test. Did you try with new sales order?

Regards,

sri_ram18
Participant
0 Kudos

Yes. It's still calculating on Flat scale.

Regards,

Sriram.

sri_ram18
Participant
0 Kudos

Hi,

Any Pricing Specialist who can help me on the requirement.

Sriram

Former Member
0 Kudos

Hi Sriram,

Try to check again in Condition Record, I believe your problem will be resolved. Maintain the different prices in Scale-Condition Record. Moreover, In condition type, V/06 scale basis should be maintained as C.

Message was edited by: Krishiv Krishna

bsivasankarreddy_reddy
Active Contributor
0 Kudos

hi

sai

you want from scale or to scale , v/06 pr00 settings like below screen  ,

check from scale , i maintain the condition records for PROO , at scale based

01-9 = 100

10-19 = 110

20-    = 120

after i create the sale order , here

9 Quanity = 100

10 quantity = 110

19 quantity = 110

20 quantity = 120

sri_ram18
Participant
0 Kudos

Thanks Shiva,

Problem comes into picture at the time of calculation.

For instance Customers orders for 1562 items of same material

    Scale(No. of Units)        Unit Price

001-500                                15 Rs

501-1250                              20 Rs

1251-2000                            23 Rs

Now the system has to calculate as (500*15)+(750*20)+(312*23)

Thanks,

Sriram.

bsivasankarreddy_reddy
Active Contributor
0 Kudos

hi

you can remove the

field AT v/06 ,

Check value - B ( ascending ) , it make blank , then you will check ,

and conform

sri_ram18
Participant
0 Kudos

No Change.