VPRS vs EK01

Hi,
What is the difference between VPRS (cost) and EK01 ( actual cost) and where these are used?
Rewarded for correct answer
Thanks,

Hi
VPRS
VPRS cost is mainly used to determine weather the material is having the standard price or moving average price
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
in this ,Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
The condition category S always accesses the standard price whereas condition category T always accesses the average price.
EK01
1)EK01 can be used as a basis for determining a price for the make-to-order item.
2) EK02 is a statistical condition which can used instead of VPRS to calculate the profit margin for the assembly item.
3)Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
4)Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.
thanks
madhan

Similar Messages

Difference between VPRS and EK01

Hi,
Can someone suggest me the difference between VPRS and EK01. In which circumstances they should be used.
Thanks
Phani.

Hi,
EK01 is used to carry out costing in sales document item (item in an inquiry, quotation or an order) to find out the planned costs for this item. This is called sales order costing.
Sales order costing can be carried out using the following methods:
1)Product costing-Product costing calculates the cost of the sales order item on the basis of the sales order BOM
2)Unit costing-Unit costing is used if the system cannot access a sales order BOM.
You can copy the results of sales order costing to the SD conditions. Copying can be carried out:
a)as a basis for pricing-If you want to use sales order costing as a basis for pricing in SD, you can use the standard SAP condition type EK01.
b)at a statistical level-You can copy sales order costing at a statistical level, if you do not wish to determine the price on the basis of this costing, but you wish to use the costs determined to calculate the profit margin in SD. EK02 is the condition type provided for this in the standard system.
VPRS is used, you may want to compare the prices with costs or even implement contribution margin accounting.
The condition type VPRS goes into the valuation segment in the material master and determines from this the standard price or average price.
a)The condition type VPRS is labeled as a statistical condition in the pricing procedure.
b)Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
c)The condition category S always accesses the standard price whereas condition category T always accesses the average price.
d)The profit margin is determined using the calculation formula 11 assigned in the pricing procedure. In this calculation formula the cost price is subtracted from the subtotal of net value 2.
Regds.........
Sumit

BOM not picking correctly in Sales Order Costing

Hi,
During Sales Order costing of configurable material Say ABC is configurable material(finished material) and it has 4 components. I am using standard sales order costing variant as PPC4. During sales order costing from VA22(quotation) of the material ABC(finished material) system take its first two components during costing. Remaining two components system does not take. It shows correctly BOM usage as 2. But two components are missing during calculation.. What may be reaon or special configuration is required for sales order costing ?
Best Reagrds,
Samrat

Dear,
please check your condition type : Ek02
It is used for statistical posting. If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price. So, this can be can used instead of VPRS to calculate the profit margin for the assembly item.
Please note the following points:
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.
So, EK01 & EK02 are the condition type that will display the results of the unit costing for certain type of sales document and can be used in Make To Order scenario.
Sales order cost estimate can be flow to COPA. Where you have to maintain setting in COPA in Define access to Standard cost estimate for costing key select sales order cost estimate.
For transfer SD to COPA you have to use Transaction KE4I here enter SD conditions with COPA Value fields.
So, whether EK01 or EK02, these will determine from Requirement class configuration. Requirement class in turn there is requirement type and requirement type is determined by item category and MRP type when you cost a sales order (valuated/non valuated sales order) at that time when save the cost estimate then the cost value automatically gets populated in your condition tab. Hence, if the item is not relevant to sales order costing then the cost comes from VPRS.
For more details please check below links
http://wiki.sdn.sap.com/wiki/display/ERPLO/VPRS%2C+EK01%28ActualCost%29andEK02%28Calculated+Cost%29
Std Cost Calculation in Sales Order - EK02 and by T-Code CK11N
Thanks,
Ram

VPRS,EK01,EK02 DIFFERENCE

Hai guru,s
Thank u very much all sdn members who are helping and sharing the knoweldge........
For material cost we are using VPRS..
what is the use of EK01, EK02...In which senario its use....what r the controls
regards
anjan

Hi,
VPRS in requirement is 4,This pulls the condition type,and in item category we mention determine cost,With the help of this the cost of the material is dragged to the sales order
VPRS is the condition which fetches the moving avg pricce of the material which gets determined by the invoice verification value for purchse orders. it may vary or be constant depending on the fact if its MAP or std price. these settings are in the material master acc./costing views. VPRS works for non-BOM scenarios. in BOM scenarios there is a cond called KUMU. kumu adds the costs of all the shild components to the header part. VPRS and KUMU form and exclusion grp i.e only once can be present in the sales order.
For EK01 and EK02:
Both are used to arrive at Cost of Goods Manufactured, while EK02 is statistical.
Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.
Condition type EK02 is mainly used when the sales price is a market price and the expected costs are only used for informational purposes
Condition type EK02 is selected for sales document type TA (standard order). Pricing is carried out on the basis of condition type PR00. The material price is updated under condition type PR00, while the values from the cost estimate are updated under condition type EK02 and can be used for informational purposes.
Hope this helps you.
Regards,
Rakesh

Difference bet EK01, EK02 and VPRS

Hi Gurus,
pls explain me what is the main difference between EK01, EK02 and VPRS. In which scenarios these costs are specifically using in the business process.
Thanks in advance,
Venkat.

Hi
VPRS
VPRS cost is mainly used to determine weather the material is having the standard price or moving average price
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
in this ,Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
The condition category S always accesses the standard price whereas condition category T always accesses the average price.
EK01
1)EK01 can be used as a basis for determining a price for the make-to-order item.
2) EK02 is a statistical condition which can used instead of VPRS to calculate the profit margin for the assembly item.
3)Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
4)Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.
thanks
madhan
reward points if useful

Condition types EK01 & Ek02

What are condition types Ek01 & Ek02 used for and what is the difference between them?
Regards,
Jay

HI
HI
EK02 is used for calculating the margin in line item of order while in case price is based on cost + markup for example then EK01 is used.
i.e.
EK01 is basically used when a calculation is based on a farmula e.g. SALING PRICE - COSTPRICE = PROFIT,
whereas EK01 is used where the all amount remain same and do not varies e.g.
VPRS CONDITION TYPE
These are the condition type that will display the results of the unit costing for certain type of sales document.
EK01 :
If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.

Cost condition type for MTO senario EKO2 or VPRS

Hi
We are having MTO scenario. So do we need VPRS condition for any purpose in this process or just EK02 is sufficient for costing purpose.
Also will user add value for EK02 manully? Or is there any other way to call this value automatically. Also in profit analysis document VPRS cost will come or EK02 value will come?
Client want to hide the cost of material form users, so what process can be followed. Can we create screen variant userid specific
Thanks

I hope you have searched regarding the topic.
Refer following SDN wiki link for all your anwers:
- [ EK01/EK02/VPRS |http://wiki.sdn.sap.com/wiki/display/ERPLO/VPRS,+EK01(ActualCost)andEK02(Calculated+Cost)]
Regards
JP

VPRS condition not floating in to sales order...

Good evening every body...
My query is VPRS condition not floating in to sales order...
Please give your valuable inputs
I checked Pricing procedure analysis
giving error requirement 004 not fulfilled
Note:
I checked determine cost in Item category (TAN)
VPRS condition in my pricing procedure
I maintained Standard price in Accounting1 tab of MMR
Valuation class I maintained in MMR
VPRS condition type I maintain condition category-"G"
Anything I missed out???
Regards,
Krishna

In my view, the information provided by you is not sufficient to provide you an exact solution.
As based on & differs business scenario to business scenario you are following.
Like whether it is BOM, MTO/MTS, Free Goods, batches, third party sales, Order-related billing or Delivery-related billing:...
Business Process
Source of costing
- Order-related billing
Valuation price of the material master
- Delivery-related billing
Goods issue
Further there are various way to carry out costing at Sales order, like
- Product costing
- Unit costing
So, you can check whether EK01/EK02 or any other cost related is executing prior/take preference to VPRS in your pricing
Also. kindly check your entries for Account Determination for valuation area(T001K) by using TCode OMWD.
If everything is fine, then test run a Sales cycle till Billing, so as to see whether at billing VPRS is reflecting or not.
If in case you need further assistance, do let us know.
Regards
JP

Contion Type Line Items:EK01

Dear SAP Guru's,
What is the Use of Condition type line items in the TC: VoV8
Sales document : In the billing Tab
.In the Condition type in V/06 there is no access sequence defined for the same.
Is it same as the condition type VPRS .
Assuring for good Points reward,
regards,
Amlan Sarkar

You can carry out costing for a sales document item (item in an inquiry, quotation or an order) to find out the planned costs for this item. This is called sales order costing.
Sales order costing can be carried out using the following methods:
Product costing
Product costing calculates the cost of the sales order item on the basis of the sales order
BOM. A sales order BOM could be part of a super BOM and the configuration object
dependencies.
Unit costing
Unit costing is used if the system cannot access a sales order BOM. You enter the items to
be costed manually in unit costing.
The system determines the prices of the materials and services involved according to the
valuation variants saved in the costing variant.You can use sales order costing to determine the manufacturing costs and total production costs of a material managed as sales stock. As well as the direct material costs and the direct costs of production, you can also determine material overhead costs, production overhead costs,distribution and administration costs or transportation and insurance costs.
Sales order costing is controlled mainly via the costing variant. The costing variant is stored in the requirements class as a proposal value. In the requirements class, you also store the costing method and the costing sheet.
Copying Sales Order Costing to the SD Conditions
You can copy the results of sales order costing to the SD conditions. Copying can be carried out:as a basis for pricing
If you want to use sales order costing as a basis for pricing in SD, you can use the
standard SAP condition type EK01.
at a statistical level
You can copy sales order costing at a statistical level, if you do not wish to determine the price on the basis of this costing, but you wish to use the costs determined to calculate the profit margin in SD.
EK02 is the condition type provided for this in the standard system.You can save the condition type in the sales and distribution document type. If you want to define the condition type with reference to the sales document item, then you can also save the condition type in the requirements class.
In the requirements class, you can also store a condition type for the transfer of the fixed costs
proportion of the planned costs. EK03 is the condition provided for this in the standard system.
In Pricing, you may want to compare the prices with costs or even implement contribution margin
accounting.
To do this, you can use the condition type VPRS as the cost price.
The condition type VPRS goes into the valuation segment in the material master and determines
from this the standard price or average price.
The condition type VPRS is labeled as a statistical condition in the pricing procedure. Using the condition category G, the condition type VPRS goes into the valuation segment of the material master and determines from here the standard or average price.
The condition category S always accesses the standard price whereas condition
category T always accesses the average price.
The profit margin is determined using the calculation formula 11 assigned in the pricing
procedure. In this calculation formula the cost price is subtracted from the subtotal of net
value 2.
regds
Jude

EK01 and EK02 costing difference

Dear Friennds,
In construction co which condition should I take for cost estimation, as management used to add their profits in the estimation only then how I can make the pricing procedure by selecting the right condition type for cost. It should be EK02 or EK01 or VPRS or something else and how can find the profit margin.
Please guide me
Regards,
Atul.

Atul,
EK01: If this is assigned, then system carries out sales order line item product costing and can be used to calculate net value for a line item as a basis.It is usually used to manage 'follow through type' of orders. Example you purchase something directly on behalf of the customer (outside normal stock) and then you sell it to the customer with a mark-up.
EK02: If this is assigned, sales order line item cost can be used only to compare with net value by which the profit margin can be calculated. It has close integration with Controlling. It may be used for BOM and configurable material.It Usually allows you to hold the cost of the item and therefore allow accurate accounting later on during the process and yes it should be added to the relevant pricing procedure if you want to use this type of process
Also
EK01 :
If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.
EK02 is used for calculating the magin in line item of order while in case price is based on cost + markup for example then EK01 is used
Reward if this helps...
Regds
MM

Cost(vprs) of free goods with batch managment

Dear Gurus,
I have a problem ahout free goods with batch management.
Cost(VPRS) is not accumulated in billing(free goods is not relevant for billing).
My configurations are shown as below:
Ordered goods (and batch) item category :zta1(copied from tan)
Free goods (and batch) item category :zann (copied from tann) pricing:B ;not relevant for billing;dermination cost:X
copy control(from delivery to billing):
ztan: accumulation cost :X
If I use the material without batch management,Cost of free goods(without batch) is accumulated to main item(ordered goods).
So, what can I do?
Thanks and Best Regards,
Lykin Kan

Hi,
These notes are useful:
SAP Note 1365939 - VPRS logic and Customizing settings in SD
SAP Note 547570 - FAQ: VPRS in pricing
If you have the problem in the transfer from SD conditions to CO-PA, check if you transfer only invoices to COPA, if you don't invoice the deliveries of free goods, then you don't transfer this 'sales' or costs of 'gifts' to COPA. You can check the customizing of COPA in tcode ORKE (IMG for COPA). SAP Note 74486 - INFO: Overview of consulting notes for CO-PA is a good summary about this issue.
I hope this helps you
Regards,
Eduardo
PD: I forgot SAP Note Number 33968 SD/CO-PA: Characteristics from sales doc tables
Edited by: E_Hinojosa on Sep 10, 2010 9:44 AM

VPRS updated incorrectly for SO with item cat Ind PO

Hi SAP Gurus
We created a SO with item cat (Individual Purchase Order - Account
Assignment M in PO).In PO we have checkd the item as free goods.
However during billing the VPRS was not captured from PO price (which
is 0.00) but it was updated from material master. As for normal items,
VPRS was updated correctly from PO.
Pls advise for free goods how can we have the VPRS updated correctly from PO instead of material master.
Sanjay

Hi,
Goto VOV7, select item category-In business data tab - tick determine cost.
check in MR21 for material price.
Thanks,
Mohanprabu C.
Edited by: mohan prabu on Jul 7, 2009 9:12 AM
Edited by: mohan prabu on Jul 7, 2009 9:12 AM

Price condition equal to VPRS cost of goods

I have a senario ,which we will create sales orders for customers with sales price equals to the MAP(moving average price) at the time when the SO being input .And the sales price in sales orders should be copy to the billing whether the MAP has changed or not .
Now I have set up an pricing procedure ,which use VPRS as the sales price condition type ,but here comes another question when I create billing according to the delivery . When I create the billing document ,the net value is defferent with the net value of the sales order ,because the MAP has changed during the goods issue.
Is there any idea that can make sure the sale price equals to the MAP , and the billing net value is same as sales order net value?
can you give me some advice ? thanks for you help！

Hi,
The pricing type (Copy control) is an extremely important field. It is worthwhile keeping this entry
in mind when creating your pricing condition types. As a rule of thumb, you should
have all item categories for a particular sales document with the same settings.
Generally, you may use pricing type B (carry out new pricing), G (copy pricing
elements unchanged and redetermine taxes), or C (copy manual pricing elements
and redetermine the others).
When using condition B all manual pricing condition types are lost.
If you want to copy the sales order to the invoice without changing the sales order
conditions, use pricing rule G. This will copy the pricing conditions from the order into the
invoice without changing them, but will redetermine the taxes.
Regards...
SBC

Free of Charge order: COGS (VPRS) is not transferred to CO-PA

Dear SD gurus
I have FOC order and I’d like to transfer its cost to CO-PA.
Initially, only delivery process exist, but I noticed that without
billing, data is not transferred to CO-PA.
So, we added billing process with no accounting doc.
But, condition type VPRS seems to be NOT transferred to CO-PA.
Is there any solution?
Yoshi

Have a look at this document
COGS not posted to costing based CO-PA during Goods Issue - ERP Financials - SCN Wiki
G. Lakshmipathi

Transfer cost price from free of charge item to main item but not for VPRS

Hi,
I want to transfer cost price from free of charge item to main item but not for VPRS but for a new Z contidion type.
For CO-PA proposes. Can you help me with This?
Catarina Alves

hi,
transfer of cost from sub item to main item is configured in the delivery to billing copy control for the main item. go to VTFL > select the required item cateogry > here at the bottom you will find a check box Cummulate cost. Tick it.
Not really what you meant COPA purposes. But the pricing conditions are mapped to COPA value fields at KE4I transaction.
regards
sadhu kishore

VPRS vs EK01

Similar Messages

Maybe you are looking for