Define Pricing Procedure

Select the pricing procedure which is the standard and copy it and create our own pricing procedure. Highlight it and double click the Control icon in the LHS screen. We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types. The detail description o each column is gi!en below.

Step"

#umber that determines the se$uence o the conditions with in a procedure. %t indicates the position o the condition type in pricing procedure. &'." 1(, 1) etc.

Counter"

System uses the counter to count the steps and also it can be used to count mini steps o same condition types. So that number o steps can be reduced in the pricing procedure and hence enhancing the system per ormance. *ccess number o the conditions with in a step in the pricing procedure. +uring automatic pricing, the system takes into account the se$uence speci ied by the counter.

Condition Type"

%t represents pricing element in pricing procedure as a base price, discount, reight and ta'. The condition type is used or di erent unctions. %n pricing, or e'ample, the condition type lets you di erentiate between di erent kinds o discount, in output determination, between di erent output types such as order con irmation or deli!ery note, in batch determination, between di erent strategy types. &'." -.(( / -rice

0((1 / 2aterial +iscount 0(() / Customer32aterial +iscount 0((4 / Customer +iscount. +escription"

System copies description o condition type rom its description 563(67.

8rom and To" 1. 8rom" This can be used as a base to the condition type or calculating urther !alue. 9. 8rom and To" The range between the steps rom and to can be used to speci y the range between same condition types. So that depending upon the condition type, the system deducts or adds the total !alue o those condition types rom speci ic common source. 2anual"

This indicator speci ies whether the speci ic condition type can be determined manually during sales order processing. % we check the bo' then the entry is going to be manual, i we uncheck it, it is going to be automatic. 8or :ase -rice and Ta'es, the entry should be automatic. 8or +iscounts and 8reights, The entry should be manual. % we check the bo', in 6*(1 when we go to conditions at the header3item le!el, the condition type will not be listed. % we re$uire we will ha!e to manually enter it. % we uncheck the bo', in 6*(1 when we go to conditions at the header3item le!el, the condition type will be listed.

2andatory"

This indicator speci ies that particular condition type is mandatory in the pricing procedure. % we check the bo', then in 6*(1 at the header3item le!el in the conditions tab, i we delete the !alue in the condition type and try to sa!e the document then system will not allow us to do it and throws an error. % we uncheck the bo', then in 6*(1 at the header3item le!el in the conditions tab, i we delete the !alue in the condition type and try to sa!e the document then system will allow us to sa!e it, without gi!ing any error. 2andatory check bo' should be checked in condition types which are compulsorily re$uired in pricing procedure. &'." -.((, 2WST. % the condition type is checked with mandatory option, then !alue should be maintained or that condition type, otherwise the system will not allow the user to process the document.

Statistical"

This indicator i it is acti!ated will not allow the !alue o the condition type to be taken into net !alue calculation. %t is used only or in ormation purposes only. This indicator causes a surcharge or discount to be set in the document statistically 5that is, without altering the !alue7. This is commonly used or condition types
o o

S0T; / Cash +iscount 6-.S / Cost 52o!ing a!erage price3Standard -rice7.

-rint"

The !alue o this ield speci ies whether line item can be printed or not in the sales document and at what le!el it is to be printed.

Subtotal"

The !alue o this ield determines where the !alues o subtotals to be captured i.e. in which table and which ield. Controls whether and in which ields condition amounts or subtotals 5 or e'ample, a customer discount or the cost o a material7 are stored. % the same ields are used to store di erent condition amounts, the system totals the indi!idual amounts. These condition amounts or subtotals are used as a starting point or urther calculations. <ou may, or e'ample, want a subtotal o all the discounts included in the pricing o a sales order.

.e$uirement"

%t is a routine that is written by an *:*- consultant according to the business re$uirement. :y de ining .e$uirement in condition techni$ue we can restrict the access o condition type. To understand the concept, we will take the e'ample o the .ebates. .ebates are to be included during the billing document processing and not in the sales document processing. *s rebates are gi!en on the deli!ered $uantity and not on the ordered $uantity 5in case o cut/o period or rebates7. 8or rebates we use the condition types :;(1 to :;(), and in the .e$uirement column we gi!e the !alue 91 which is =;nly in :illing +ocument=.

This .e$uirement will ensure that these condition types will appear only during the billing document processing. % new .e$uirements are to be de ined we ollow the procedure gi!en below.
o o o

>o to T.Code" 6;82. / 2aintain .e$uirements ? 8ormulas Click on the =.e$uirements= in the top menu and then click on =pricing=. We ha!e a list o re$uirements, we can ask *:*- consultant to create new re$uirement based on the client re$uests. *nd we assign the application type like 6 / Sales3+istribution etc.

*ltCty / Condition ormula or alternati!e calculation type"

%t is again a .outine that is written by *:*- Consultant. %t is an alternati!e ormula or the condition type that can be used instead o standard ormulas. 8or e'ample, let us take the -ro it 2argin which can be both @ 3 / , so here this routine will help us in generating the !alue which can be either @ or /. -ro it margin is not a condition type so it cannot be classi ied as @!e or /!e in the 63(6. &'." A)( ( -ro it 2argin 11. So we assign 11 / -ro it 2argin. % new routines are to be de ined we ollow the procedure gi!en below.
o o o

>o to T.Code" 6;82. / 2aintain .e$uirements ? 8ormulas

Click on the =8ormulas= and then on the =Condition 6alues=. We ha!e a list o routines, we can ask *:*- consultant to create new routines based on the client re$uests. *nd we assign the application type.

*ltC:6 / *lternati!e ormula or condition base !alue"

8ormula or determining the condition basis as an alternati!e to the standard. %t is again a .outine that is written by *:*- Consultant. %t is used as a basis to calculate !alue o the condition type instead o using it rom the =8.;2= column. &'." 8reight / 08((.

8reight is calculated based on weight, !olume etc. and not on the base price. %n pricing there is no entry o weight rom which the !alue can be re erred like we do or discounts using base price. We ha!e to get the !alue rom the 2aterial master. %n this column we can mention the !alue as 19 / >ross Weight or 1B / #et Weight. +uring pricing, the system will consider the !alue that is mentioned in this column and determine the reight based on this !alue. Suppose we ha!e #et weight" 1(( kgs and >ross Weight" 1)( kgs. *nd i we mention 1B in this column then the 8reight condition 08(( will be calculated using the weight as 1(( kgs.

*cy0y / *ccount 0ey3 *ccrls / *ccruals"

The !alues o the Sales .e!enues, Sales +eductions, 8reight .e!enues, Ta' .e!enues, and .ebate *ccruals etc. are going to be posted in the respecti!e >3L accounts in 8i 2odule. %n order to do this we assign account keys3 accruals to the di erent condition types based on their classi ication. The classi ication shown below.
o o o o o

&.: .ebate sales deduct. &.8 8reight re!enue &.L .e!enue &.S Sales deductions &.C .ebate accruals

8or &'.,
o o

8or all -rice condition types like -.(( etc. we assign &.L / .e!enue. 8or all +iscount condition types like 0((1, 0(() etc. we assign &.S / Sales +eductions. 8or all 8reight condition types 08(( etc. we assign &.8 / 8reight .e!enues. 8or all .ebates condition types :;(1 to :;() we assign in *ccount key &.: / .ebates Sales deductions and or *ccruals &.C / .ebate *ccruals.

o o

This account keys and accruals are in turn assigned to respecti!e >3L accounts. So the system posts respecti!e !alues in respecti!e >3L accounts in 8i/Co 2odule. This also one o the areas o S+ / 8i %ntegration. S+ consultants assign the account keys and 8i Consultants assign the respecti!e >3L accounts in T.Code"60;*