Counter in priceing procedure

Hi Guys ,
How the counter works in priceing procedure and how to to define counters in priceing procedure .
RB

Hi,
The counter column in pricing procedure is just a sub-step within the actual step. For example, you may have all your freight surcharges assigned to step 100, however there may be 3 condition types where each represents a different surcharge.
Thus you may assign a freight condition type to step 100 counter 1, another to step 100 counter 2, another to step 100 counter 3.
Thanks

Similar Messages

Counter in pricing procedure.

Hi All,
Can somebody tell the functionality and the Implications(read implications) of using the counter in pricing procedure for condition types. We have to make use of counters in some pps but not quite sure of the implications.

Hi.,
We use counter just for sub numbering,Where is step we mention as 10,20,10 and we configure a pricing procedure., and if at any there may be a need to modify the pricing proceure so at that time we may need to add some extra condition types between them,SAo for the flexiblity we can give the number as 11,12,13 for the condition types.,
For this purpose we use the counter
REWARD if helpfull
Thanks & Regards
Narayana

MM pricing procedure doubt!!!

Hello All
1) Would like to know where we connect PO doc type to the MM pricing procedure? or it is not at all connected?
2) Suppose i am creating a standard PO, so how system actually knows which pricing procedure to pick up out of so many maintained in SPRO?
3) What is the meaning of Step and Cntr in MM pricing procedure?
Thanks
Anjan

Hi,
All I can do is to confirm that there is NO LINK between document type and pricing procedure.
The procedure is determined by the Vendor and the P org (via groups).
The exception is the transport orders these have their own condition schemas (that is why there is a control field on the PO document types, so that you can indicate the document taypes that are for STOs)
the step and counter fields are simply methods of pointing the calculation to the correct conditions types etc.. the step is a sequence numbering when multiple condition types are to be processed in the same step.
Steve B

Error in pricing procedure

Hi all,
I am facing difficulties while adding a condition in pricing procedure.
I have created a condition type ZWTC and assigned it to the pricing procedure ZSRV01in "Define Calculation Schema" in SPRO.
But at the time of PO creation i am getting an error message
"Condition ZWTC is missing in pricing procedure A M ZSRV01"
How can i rectify the error.
Thanks & Regards
Prasant Sekhar

significance of step and counter
suppose i have 3 condition type avilable for frieght then hoe to map this in sap
so let us step for them is
step counter condition
20       0           frc1
20      1           frc2
20      2           frc3
counter means the sequence in whihc system will acess the condition type from calculation sequence
.so first prefre. is to    fc1 thne to frc2 then frc3
and same is the logic for step
that which condition type is accessed in which sequence from calculaton schema

Pricing Procedure to be configured for calculating excise

Hello ,
I have new pricing procedure to be configured for calculating excise on base value , the procedure is as under
Base Price                              -
                   X Amount
Surface transport                    -
               Y Amount.
Crush Charges                        -
              Z Amount.
Base for Excise Duty               -
             X + Y + Z
Excise Duty 10 % on base value i.e X+Y +Z
Education cess 2%
Secess              1%
Net Inclusive of Excise Amount.
Clean Energy Charges -
A
Freight Charges            -
   B
Other charges               -
C
Net Total          -    ( Net charges inclusive of Excise Duty + A + B + C )
CST                 2% 0n Net total.
I need to configure the above pricing procedure with Taxcode with Excise and CST .Request for valuable suggestions.
Thanks
Guru.

Hi,
To configure pricing procedure we need to following Condition Technique
1. Create condition table -v/03
2. Access Sequence - v/07
3. Condtion Type v/06
4. Pricing procedurev/08 -
5. Determination of pricing procedure. ovkk
Now to create your new pricing procdure you need to create first conditon type to enter in pricing procedure
You can create new pricing procedure by copying existing one RVAA01 is the pricing procedure given by SAP & then do changes according to your requirement.
Step - enter no
counter-
Condition Type
FROM & TO - here put counter no to do calculations as per your requirement
to Make conditon manual /required/staticatl - click as per u r requirement
Print conditons
set other fields as per your requirement.
Hope this will help you.
You can also search threads for the same also for more infomation.
Thanks
Trupti

Counter in pricing ?

hi ,
how does the counter(step) in pricing procedure work ?
any examples if possible ?
regards
sriram

Counter:
     System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
     Access number of the conditionswithin a step in the pricing procedure.
     During automatic pricing, the system takes into account the sequence specified by the counter.
Eg:
This is used to show a second mini-step within an actual step. For example, you may have assigned all you freight surcharges to step 100. However there may be three condition types, each representing a different freight surcharge. Thus you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3 and so on.
Message was edited by:
        sam masker

Pricing Procedure for UK

Dear Experts,
I want the pricing procedure for UK country. My client had started new operations in UK.. currently he dont know wat all taxes and prices will be there in UK so anyone plzz suggest me wat all i must have to be configured in Pri pro , kindly do the needful.
Regards
abhi

Hi,
Basic Price in USD
Exchange rate for vendor
Vendor invoice
Freight
Insurance
Add: LC/Forward cover charges
Exchange rate for customs
Assessable value
Customs Duty @ 5 % on Assessable Value
Counter Vailing Duty @ 8 %
Education cess @ 2%
Total Duty
Education Cess on total duty @ 3%
SAD
Total Duties
Wharfage
Throughput charges
CHA Expenses
SGS Survey Quantity
SGS Survey Quality
Safety Surveyor
Demurrage charges
Duties on Demurrage charges
Administraiton charges
Stamp Duty
Customs Overtime/Bonding charges
Shifting Charges
Micellaneous
Out Harbour HPC Charges
Total Port
Freight
Hope it helps
Uts
Award if helpfull

Calc schema in pricing procedure for PO

Hi All..
Anybody.. explain me Defining Calculation Schema table for a set of condition type with roles played by each column used to get final Total value in Condition tab of PO at Item level with how countrs and steps work.
Condition typs used:
PB00
PBXX
RA01 discount
ZPF Packin & forwarding
-total material price=
ZED 16% Excise duty
ZCES 2% Cess on ED
ZSHC 1% Secondry cess on ED
-Effective price=
ZVAT 12%
ZOCT Octrie
-Net value=
Thanks

Hi Vicky,
Excise duty anfd ECess will flow from tax procedure and not from pricing procedure.
Coming to pricing procedure create all condition types and assign access sequence to condition types if the price has to flow automatically after that assign all these condition types in calculation schema.
for example if you have a component like discount and it can be percentage or fixed value at that time we use counter.
Step1 counter 1 discount percentage
step 1 counter 2 discount fixed value
Regards
Pavan

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Related Pricing procedure

Dear Gurus...,
Can any body guide me the pricing procedure..
I am looking to that , but i am not able to understand the following things.
While going M/08 Transaction -
> selecting pricing procedure -
> clicking the controls
I am finding the table like this.
Step-Counter-Condition typeDescription-FromToManual-RequiredStatisticsPrint-Sub totalRequirement-Call type--Base Type-Account Key----Accruels;;;;;;;
Can any body explain this meaning and functions of this -
( I understood condtion type , Description , From , To)
Please explain the remaining things clearly
Rgds
Surya

Step - Number that determines the sequence of the conditions within a procedure.
Counter-Access number of the conditions within a step in the pricing procedure.
Condition type - The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Description u2013 Description of the condition type.
From - Condition step, the value of which is the basis for percentage surcharges.(calculates the amount from the references step)
To - Condition step up to which the condition values of the previous steps are totaled. .(calculates the amount up to the references step)
Manually u2013 Conditions need to be entered manually.
Mandatory - Indicates whether the condition is mandatory when the system carries out pricing using this pricing procedure.
Statistical u2013 This will not include the amount to the net price.
P-Print u2013 Prints in PO. u2018Su2019: Condition line is printed in totals block u2018Xu2019: Condition line is printed at item level.
Sub total - Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored. 9 u2013 Gross value, s u2013 effective value.
Requirement u2013 It should fulfill the specified requirement.
Alternative calculation type- Alternative formula to the formula in the standard system that determines a condition.
Alternative formula for condition base value-Formula for determining the condition basis as an alternative to the standard.
Account key - The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.
Accruals - Key which identifies various types of G/L accounts for accruals or provisions. With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
Hope thsi helps
Rakesh

Standard Pricing Procedure Control Options

Hi,
Need to know the use of columns in control tab of the pricing procedure like: counter, From & To with an example.
Say i have 10 - 100 steps ....
In the 50th step i have From as 10 and To as 40......what will happen for the 50 th step condition value....Also, in the 50 th step you have condition type and condition records are maintained.......
Regards

Hi,
Hope the below reply helps you.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1. From: This can be used as a base to the condition type for calculating further value.
2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

Columns in Pricing Procedure

Hi..
What is the meaning of this column in the pricing procedure?
Regds
Shriniwas

hi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/16FieldsDescriptioninPricing+Procedure&
16 columns - 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 of each column is given below.
Step:
 Number that determines the sequence of theconditionswithin a procedure.
 It indicates the position of the condition type in pricing procedure.
 Ex.: 10, 15 etc.
Counter:
 System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
 Access number of the conditionswithin a step in the pricing procedure.
 During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
 It represents pricing element in pricing procedure as a base price, discount, freight and tax.
 The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
 Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
 System copies description of condition type from its description (V/06).
From and To:
1. From:This can be used as a base to the condition type for calculating further value.
1. {}From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
 This indicator specifies whether the specific condition type can be determined manually during sales order processing.
 If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
 For Base Price and Taxes, the entry should be automatic.
 For Discounts and Freights, The entry should be manual.
 If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
 If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
 This indicator specifies that particular condition type is mandatory in the pricing procedure.
 If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
 If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
 Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
 If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
 This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
 It is used only for information purposes only.
 This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
 This is commonly used for condition types
o SKTO - Cash Discount
o VPRS - Cost (Moving average price/Standard Price).
Print:
 The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
 The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
 Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
 If the same fields are used to store different condition amounts, the system totals the individual amounts.
 These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
 It is a routine that is written by an ABAP consultant according to the business requirement.
 By defining Requirement in condition technique we can restrict the access of condition type.
 To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
 For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
 This Requirement will ensure that these condition types will appear only during the billing document processing.
 If new Requirements are to be defined we follow the procedure given below.
o Go to T.Code: VOFM. - Maintain Requirements & Formulas
o Click on the "Requirements" in the top menu and then click on "pricing".
o We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
o And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
 It is again a Routine that is written by ABAP Consultant.
 It is an alternative formula for the condition type that can be used instead of standard formulas.
 For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
 Ex.: 950 0 Profit Margin 11.
 So we assign 11 - Profit Margin.
 If new routines are to be defined we follow the procedure given below.
o Go to T.Code: VOFM. - Maintain Requirements & Formulas
o Click on the "Formulas" and then on the "Condition Values".
o We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
o And we assign the application type.
AltCBV - Alternative formula for condition base value:
 Formula for determining the condition basis as an alternative to the standard.
 It is again a Routine that is written by ABAP Consultant.
 It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
 Ex.: Freight - KF00.
 Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
 In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
 During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
 Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
 The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
 In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
o ERB Rebate sales deduct.
o ERF Freight revenue
o ERL Revenue
o ERS Sales deductions
o ERU Rebate accruals
 For Ex.,
o For all Price condition types like PR00 etc. we assign ERL - Revenue.
o For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
o For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
o For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
 This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
 This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
Reward if USeful
Thanx & Regards
Naren..

Pricing procedure(Condition technique)

Hi All
Can someone provide me all the configuration steps in pricing procedure in MM...

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 of each column is given below.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1.From: This can be used as a base to the condition type for calculating further value.
1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
or
Hi,
Pricing Procedure in MM
The steps are:
SPRO->MM->Purchasing->Conditions->Define Price dertermination process
1. Define Condition Table:
2.Define Acces Sequence,
3.Define Condition Type,
4.Define Claculatin Schema,
5.Assign Calulation Schema,Acces Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organisation,
8.Assign Schema Group Of Vendor to Purchasing Organisation,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

Complicated pricing procedure

Hello All
I am working on CRM 5.0 I want to make a pricing procedure that has can counts number of free items in a cretin period and what more than this items in this period will charge an (X) price and after this period expired the same item will charge (Y) price
Note: if the customer did not use the free items in the period the system should start charge him Y price after the period expired
Thanks in advance
Khaled Fahim

Can you give some more details like How you plan to configure your free goods access sequence? You can put some logic regarding your scenerio using free goods pricing user exit. But it would be nice if u give details.

Pricing procedure i

hii Experts
I know how to configure pricing procedure in MM
Now some experts can tel me how i can develop more knowledge MM pricing procedure in SAP.???
what is best way to become good in pricing procedure ....
Explain me the way with some some future examples ...
Thanks

Hi,
Access sequence:* An access sequence is a search strategy with the aid of which the SAP System searches for valid condition records of a certain condition type from the valid table and fetches the value in PO. *Condition type:* The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or delivery costs in the SAP System. These are stored in the system in condition records. Basically in Pricing procedure there 16 step/ column which are their own importance in pricing procedure the derive the value based on this configuration. Would like brief each and every field as under. *Step:* Number that determines the sequence of the conditions within a procedure. (This starts calculation based on from and to) *Counter:* Access number of the conditions within a step in the pricing procedure. During automatic pricing, the system takes into account the sequence specified by the counter. Ex if you are having freight condition type it is be possible to have different freight combination as per qty freight, fixed value freight & freight % on gross in this case you can have same from but o,1,2 different counter as whichever is applicable system will draws this condition fro step & counter. *Condition type:* The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount, gross, freight, *Description:* Description of the condition type. *From:* Condition step, the value of which is the basis for percentage surcharges. If you specify a to reference step at the same time, the condition values of the two steps specified and the conditions values of the steps in between are totalled. *To:* Condition step up to which the condition values of the previous steps are totalled. Percentage surcharges are calculated on the basis of the total. If you specify a from reference step at the same time, the condition values of the two steps specified and the condition values of the steps in between are totalled. *Manual:* Conditions, that are given this indicator in the pricing procedure, are only included in determination either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process. Here user has to enter the value system will determine automatically *Requirement:* Indicates whether the condition is mandatory when the system carries out pricing using this pricing procedure. For example, you always want to include a tax condition (VAT or sales tax) during pricing; you can set this indicator for the appropriate tax condition type. *Statistical:* This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value or adding to the value Ex; if Gross + discount+ freight= 1000 this is statistical value). *Print:* Controls issue of condition lines when printing documents such as order confirmations or invoices. *Subtotal:* Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored. If the same fields are used to store different condition amounts, the system totals the individual amounts. Ex if you wish to add freight to the Gross then taxes on the gross have to use subtotal 4 condition value of which will added to the gross. *Requirement:* If the requirement is fulfilled then output determination also takes into consideration output type or the access sequence, for which the requirement has been specified. *Calculation type:* Alternative formula to the formula in the standard system that determines a condition. *Condition base* calculation: Formula for determining the condition basis as an alternative to the standard. *Account key:* Key that identifies different types of G/L account. The account key enables the system to post amounts to certain types revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account. *Accruals:* Key which identifies various types of G/L accounts for accruals or provisions. Hope this helps you.
Edited by: Shubham RT on Aug 17, 2010 1:53 PM

Counter in priceing procedure

Similar Messages

Maybe you are looking for