Difference between EK01 & EK02

[Former Member]

What is the difference between EK01 & EK02. Why are these condition types used.

Venkat

[Former Member · Accepted solution]

hi,

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.

thanks

sadhu kishore

[Former Member]

Thanks everbody...I have rewarded the points.

Venkat.

[Former Member]

Hi

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.

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

[former_member183879]

Pls refer to the following links to get better clarity.

http://www.jt77.com/system-dynamics/model-04469.html

http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/condition-type-ek01-ek02-1394665

http://www.sap-img.com/sap-sd/difference-between-condition-type.htm

Message was edited by:

Navaneetha Krishnan

[Former Member]

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.

[former_member227476]

dear venkat,

EK01 and EK02 have been provided for cost transfer of line items.

EK01: If we choose it the result of the sales order costing (integration with controlling) is first printed to the pricing screen for the item. The value can be used as basis for price calculation.

EK02: System simply takes the result of the sales order costing as a statistical value (only for information purpose

rewards if it helps

siva

[Former Member]

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

Regards

AK

reward points if helpful