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.

Similar Messages

SERVICE ORDER COST IS NOT FLOWING TO CONDITION TYPE EK01 IN SALES ORDER

hi all,
My requirement is that the cost incurred in service order should flow to the condition type ek01.
we will be running the transaction dp90 to calculate the cost for the resources used.
the cost are getting calculated at service order level but this cost are not flowing to the billing item being generated from dp90 in the billing request.
the settings that i have made are as follows: I have maintained the condition type ek01in the sales pricing procedure. are there any other settings required by me to make.
valuable answers will be be rewarded fullpoints.
regards,
ashish

Hi prince
Check out in Control data of Condition Type--PB00..Enter "NO Limitations" in Manual Entries. and check the 'Amout' and 'Value' and 'Delete' so that u can make changes to that condition type in line item in sales order.

Condition type EK01 missing in pricing procedure A V (error message V1206)

Hi gurus,
We get error message "condition type EK01 missing in pricing procedure A V" when creating a Billing request from a SErvice Order through TX-DP90.
We reviewed customizing regarding this issue:
ODP4 - SD Document linked to condition EK01 (this condition shall bring the actual cost in the order)
ODP1 - Dinamyc item profile to create Billing Request.
Pricing procedure: sales area assignments, condition types (including EK01)
but error still shows.
Any idea what additional setting is necessary in customizing so EK01 is transfered to the SD doc in DP90?
Thanks,
VL

Hi Lakshmipathi,
Thanks for your answer.
I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
Thanks for your always great help,
VL

Condition type EK01

Hi
the status of Condition type is inactive in my item ..
How to activate this condition type..
Thanks in Advance..

A condition type can be inactive in a transaction for varoius reasons.
1. Condition exclusion can be reason. Pls check whether this c.type is exclusive of any other c.type in the exclusion procedures.
2. A condition type can also be inactive if it is configured in pricing procedure as Manual entry only, but a value appears automatically due to presence of condition records.
Pls check in which category, the condition type falls, and do the rectification.
Reward if this helps.

EK01 & EK02 Condition Type

Dear Friends
In Sales Document type in Billing Section Condition Type Line Item=EK02 and
In Standard Pricing Procedure RVAA01 used EK01 and EK02 What is the use of it where it will affect?
Please clarify my doubts
Thanking You
Arun

Dear Customer,
a describtion for EK01/EK02
The unit cost estimate is the planned cost of goods manufactured for the material to be sold. The estimate is calculated based on the materials you intend to use, the services you intend to carry out, and additional costs such as shipping and insurance. In addition, you can use cost items to calculate overhead surcharges. The unit cost estimate is calculated in Controlling (CO-PC). The cost estimate is then copied into the sales document and can be used for pricing or for calculating the profit margin.
Condition type          Name                    Use
EK01               Individual Determination          Used as basis for pricing
EK02               Unit cost estimate u2013 statistical     Used to calculate profit margin
The condition type EK01 can be used as a basis for pricing a make-to-order item in a sales document. The system calculates the cost of manufacturing and copies the result as an EK01 condition type into the pricing screen of the sales document.
You can use the condition type EK02 to calculate the profit margin of a make-to-order item in a sales document. The system calculates the cost of manufacturing and copies the result as an EK02 condition type into the pricing screen of the sales document. The EK02 has no direct effect on pricing.
2.     Settings in Customizing
Condition type configuration (for both EK01 and EK02)
u2022     Basic configuration:
Condition class      [KOAID]      B Prices
Calculation type      [KRECH]     C Quantity
Condition category      [KNTYP]     Q Costing
u2022     No access sequence
u2022     EK01/EK02 can only use as item condition. Group condition flag should not be set.
Pricing Procedure Configuration
u2022     EK01 and EK02 should be checked as manual in the pricing procedure since their value is not derived from SD condition records.
u2022     EK02 must be set as Statistical in the pricing procedure.
u2022     Subtotal value u201CBu201D should be assigned to the EK02 condition.
See note 155212 and online documentation for additional details.
I hope that the information are helpful.
regards
Claudia Neudeck

Copying condition type EK02

Hi,
I am using Unit costing to determine the prices of the materials and services at quotation level. With this I am getting EK02 at item level.
I want to use sales order costing as a basis for pricing in SD, for this I want to use the standard SAP condition type EK01.
I want detailed input on how can I copy the EK02 to EK01. So that I may use EK01 as basic price and add some surcharges to determine the net price.
regards
Suman

Hi Sonia,
This condition comes from your backend system, so is calculated there and the results sent to CRM. In CRM you don't have the condition defined in your pricing procedure and therefore you get the error that the condition is missing. You should make sure your pricing customizing in both systems is consistent.
Regards, Ignacio

Condition type EK02 and VPRS.

Hi Everyone,
In our pricing procedure there are two condition types EK02 and VPRS at header level. The profit margin we are getting is in negative. Can any one through some light about the use of EK02 and VPRS condition types and how system picks the values for the condition type EK02 ?
Thanks
Raksha.

Hi,
VPRS condition type is a Statistical Condition Type that returns the cost price of material from material master. It is basically used for comparison purpose. If you want to add it in the pricing procedure, make sure you add it at the last i.e. after adding of all the condition types.
EK02 is also a Statistical Condition Type and used for comparison purpose.
regards,
Sagar

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

EK01 & EK02

Hi Gurus,
In config part of sales documents, there is a field 'CONDITION TYPE LINE ITEMS',
the possible entry fields are EK01 AND EK02,
what will be the impact in performance by selecting these fields,and if we don't select anyone of these,
Regards,
Sailaja.

Hi sailaja
Difference between Condition Types EK01 and EK02
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 point :
1) The condition type must have condition category Q (costing).
Regards
Srinath

Ek01, ek02 in variant configuration...

hi all,
how can i use the condition type EK01 or EK02 in variant configuration. (i want to see calculated cost for config. materials in sales order)

hi,
hi ,
Ek01 : this is condition type used to get the actual cost from the material master and post in the sales order.
Ek02: this condition type used to get the calculated cost based on the master master which are selected at the time of the sales order.
example if i have material cpu = cost 10,000 in material master. Monitor = 5 000 , keyboard = 300.
if the monitor 15 inches : 5000 , 17 inches = 7000.
so the if we select variants CPU + Monitor 15 " + keyboard 15,300.
If we select variants CPU + Monitor 17 " + keyboard = 17,300. - Calculated cost.
so at to profit is calcualted based on EK02.
thanks
Kuntla

Differnce between EK01 & Ek02

Hi Experts,
Can anyone tell me what is diff. betwwen EK01 & Ek02

Hi sanjay
Difference between Condition Type EK01 ( Actual Cost) and EK02 (Calculated cost)
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.
Regards
Srinath

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

Pricing unit in condition type..

Hi folks,
I have a problem with " pricing unit".
Iam using condition type EK01 . Under normal circumstance, the pricing unit takes the value of 1..
Suddenly, it is taking 100 as value.
Can anyone give a clue from where this, Pricing Unit picks this value i.e 1 or 100.
and now how it is suddenly taking 100..
where we need to make settings for this...
thanks in advance,
Sourav

Hello Saurabh,
Please check following things -
1. MM02 - Accounting data1 tab, Price unit - should be "1"
2. In EK01 condition under heading "changes can be made" remove tick for quatity conversion.
Hope either of this will you to resolve the issue.
Regards,
Satish

Condition type JTX1 missing

Hi,
I'm practicing on home pc IDES 4.7. I have done copy client from 000 to 800 to use CIN in IDES, and now I can see the calulation procedure TAXINJ assigned to country IN which was not there before coping the client.
I have done the customization for CIN ( yet to test ) also. But now Im getting one error while creating CMR & MMR i.e. tax condition JTX1 not defined. I can see the condition default in CMR & MMR but not classification value and while doing so in "Define tax determination rules" it is giving the error that "Condition type JTX1 is not defined for taxes" although I can see it assigned to country IN but if u click enter it will throw the error.
So my query is that how come these conditions are missing as these are default condition type and can we create these conditions manually & if yes which access sequence should we assign to it and what are other settings for it ?
Plz help me out I'm a SAP learner and unable to create CMR & MMR bcoz of this error.

Hi Lakshmipathi,
Thanks for your answer.
I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
Thanks for your always great help,
VL

Planned cost with VPRS condition type

Hi,
Planned cost of sales order corresponding to condition type VPRS does not
appear in report like KKBC_KUN though it appears for condition type like
EK02. How to get planned cost also for VPRS in report like KKBC_KUN.
With regards,
Mrinal

Hi Ashok,
Your problem seems intresting, may be this thread can help you
[SCN|VPRS- Error in quantity/value determination]
Please provide feedback after getting it solved.
Thanks,
Raja

Condition types EK01 & Ek02

Similar Messages

Maybe you are looking for