VPRS, EK01 (Actual Cost) and EK02 (Calculated Cost)

Condition Type VPRS, EK01 and EK02

VPRS (Internal Cost):

It cost is mainly used to determine whether 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 (Actual Cost):

It is used to is used to post actual price. 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. It is mainly used for cost-plus contracts in which the sales price depends on the expected costs. It 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. It will be positioned in the first step of all the condition types in Pricing procedure and the values are given manually.

EK02 (Calculated Cost):

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.

___________________________ 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 EK01 EK02 Name Use

Individual Determination Used as basis for pricing 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 u2022 No access sequence 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.

Standard proposal for CTyp EK02, Manu = X, and statistical condition is X, Subtot = B, Req =000 Calfor =000

Manu = Manual indicator

Subto = Subtotal

Req = Requirement

Calfor = Calculation formula