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 

Similar Messages

  • Pricing Procedure Condition Type EK02

    Dear, Gurus
    I have an MTO scenario. All is working I mean from the production order the cost is coming to my sales order in condition type EK02. But that is making all other condition types as inactive.
    current pricing schema
    Pr00 Price it is manual.
    Other Z condition types which are also manual.
    Then EK02.
    Gross Sales
    K005
    K007
    Net Sales
    MWST
    ZSED Sales excise duty
    Value after Tax
    VPRS
    also, at the top the net value does not change at all it stays constant and seems to pick up the EK02 price.
    I want all other condition types to be manual but active even if EK02 price is picked up from Production Order.
    How can I set it up to make them all green as active?

    Previously all my condition types were manual entry so all were green.
    Pr00   manual
    Zman  manual
    Zsat   manual
    Zetc   manual
    Also, in PR00 class is B=Prices       Calc Type = C for qty
    All the ZMan, etc is A=discount/Surcharge   calc type=B fixed amount.
    To be scenario all I added was condition type EK02 in pricing procedure and by standard it is in class B=prices     calc type=C for qty, and cond cat=costing
    When production cost transfer to EK02 lets say example 500. All those previous cond are yellow inactive. and then net price equals 500!
    In terms of my terminology and basic understanding you can only have one cond type function as price in class B=prices.
    So either the EK02 or the Pr00 needs to have cond type B for Price. If I make the Pr00 a discount/Surcharge nothing changes in respect to updating the price in sales order.  Lets say even if its all corrected and I have lets say EK02 function as price the Zman and Z condition types are under discount surcharge, that at least should not be inactive?
    Please help
    thanks

  • 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

  • Condition type EK02 In pricing procedure

    I'm having a problem with theis condition type as follows:
    Create sales order
    Add material A to line item
    Pricing procedure kicks in
    EK02 shows fixed value 7700 EUR
    Delete material A from line item
    Add material B to line item
    Pricing procedure kicks in
    EK02 shows fixed value 7700 EUR
    I'm not sure where this value is coming from at this point. Can anyone point in the right direction?
    Thanks, Mark

    Hi mark
    EK02:
    If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
    It has the condition category Q ( costing  )
    Now when you go to VOV8 , in the condition type field you can see the option EK02. because this condition type when used will be flowing to the controlling .That is the reason we assign EK02 to our sales doc type
    Check in V/06 and  select EK02 and go to  its condition type details and check the calculation type field wheather it is in fixed value or not
    Regards
    Srinath

  • 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

  • EK02 condition type on quotation

    We currently see and utlize the EK02 condition type on sales orders for configured parts (assembly order creates).
    However, when creating a sales quotation (VA21), the EK02 condition is not active/not populated.
    Is there a way to get the EK02 condition to calculate on a quotation?  Like maybe some way to attach a simulation production order to it that doesn't really create demand in the system?  Would I need a new production order type for this?
    Gina Feldner

    Hi Gina,
                 First check whats the requirment type for quotation in your system. You can check this by clicking on shipping tab in the overview screen. Then go to the Transaction" OVZH" and see whats the requirment calls associated with it. Once you identify the requirment class, check If you have the entry "EK01" at the condition type line items field in the requirment class. Transaction code for this is "OVZG". If it is not there maintain that. Then go to the conditions screen and see whats the pricing procedure. In V/08 , Check if the condition type "EK02" is maintained there. If it is not ,Maintain the condition type in the procedure .This would resolve the problem. Other wise you can maintain the "EK02" in the sales document cofinguration (VOV8) at condition type lie items and maintain the same in the pricing procedure. Only difference is If you maintain this condition in the sales document type this is valid for all the items in the sales order and If you maintain this in the requirment class, this is valid for only the documents which have this requirmanet type. Kindly please let me know If you need any more help on this.
    Regards.
    Ram Pedarla

  • Config required for EK02 condition type in Sales Pricing procedure

    Dear friends,
    I am trying to derive a costing run for sales order. I would like to know what are the config steps required to arrive a percentage factor for GP.
    Kindly guide me in this regard,
    Thanks in advance,
    Vinayak

    Hi,
    If you are doing sales order costing then you will have to define the condition type EK02. Go to V/08. Select the Procedure used in SD. Click on Control. Enter the condition EK02 - Calculated Cost and mark it as statistics.
    You sales order cost will be stored in such condition type.
    Regards,
    Jigar

  • Pricing authorization at condition type level

    Hi,
    We are using EK02 condition type. Requirement is EK02 should be able to be changed by ORDCHG incomming Idoc and the EK02 price to be overwritten in sales order pricing.
    But all other business users should be able to only input the EK02 once and EK02 should become display only field (non editable) for those users. 
    The change of EK02 to be only applicaple to the EDI Idoc user partner (User).
    Please let me know how to achieve this through price authorization or any other way??
    Note: The condition type EK02 config set is it can be edited like any other manual condition type (V/06)

    Hi
    Please have a look at the following OSS notes. They may be of some help to you to solve the problems.
    105621--Check this one. This will be of much helpful to you
    414058 and 914811

  • Condition type to be hidden

    I wanted condition type EK02 to be hidden from the sale order, I dont want this condition type to be removed from the pricing procedure. Please suggest.
    Prasad

    Hi,
    Since you don't want to remove the condition type from your pricing procedure, you can create a new requirement routine and add it to your condition EK02.
    Let's say you want to hide that EK02 condition only for sales orders where sales document type = OR, then create a pricing requirement routine to check the sales document type.
    To create a requirement routine, transaction is VOFM. From the menu option, select "Requirements / Pricing"
    There you can create a new routine, Enter number between 600 to 999.
    Code:
    SY-SUBRC = 4.
    CHECK: KOMK-AUART EQ 'OR' OR KOMK-AUART_SD EQ 'OR'.
    SY-SUBRC = 0.
    Once generate that, add it against your condition type EK02 in the pricing procedure.
    Then it will be hidden in the pricing procedure only for order type = OR.
    You can use it as you require.
    Best regards,
    Anupa

  • Condition type for pricing came from PC but has not included the additive cost record

    hello all;
    we have the pricing base for the sales order with the estimated cost from pc; our costing process has a posting record for additive cost is not included on the total cost is sent to the condition type EK02.
    question: It is possible to include these kind of postings?, in fact, these record apear on the costing report as part of the cost of sales..
    thanks in advanced...

    Hi Francisco
    Two things,
    1. Your condition type must be EK01 if you wanna use it in
    Pricing
    2. Additive cost in CK74 is at the level of material and plant. It is not at the level of sales order
    If you wish to add costs manually in sales order cost estimate, then use Unit Costing as the costing method in your requirement class
    Or use Product costing as costing method and use a costing sheet
    Br. Ajay M

  • Copying the sales price data into Condition type

    Dear SD Gurus,
    Iam in a typical situation.  my client is into Electrical Installation and services, so based on the tender documents, they quote the project.
    they are doing costing (ie arriving at a supply rate) in quotation. To arrive at a supply rate, they are entering the cost price of the material ie (PR00) in the quotation and adding the profit (for eg : ZPRF condition type) for it. now my problem is i have to add these two condition types into one condition type to arrive at a selling price. how can i achieve this.
    And also while creating the sales order with reference to quotation, these two condition types (ie cost price(PR00) and profit (ZPRF) should not get displayed in the sales order.
    Is there any solution for this method.
    eagerly waiting for your replies.
    Thanking you all in advance
    rgds

    Hi SD
    First of all for project quotation the best practice documentation is available in SAP Discrete Manufacturing ,please  go through it . that will help.
    Secondly for getting costs in quotation level pricing u can use either of 2 conditions EK02 or VPRS that will give cost .
    Add Profit condition to it .
    U can  use different pricing procedure for quotation and sales order and in copy controls give routine to redetermine manually.
    Else  if u r using the same pricing procedure  ,take help of Abap developer for changing table controls in program.
    Check whether u can use  Transaction SHD0.
    Hope this helps
    Regards
    Mandar

  • Condition types not copied correctly from Me11 to Me21

    Dear All,
                I am facing a problem in my client place, it is a import scenario where i create ME11 for a material with a combination of a vendor. After maintaining condition types like J1CV, JSDB when I am creating PO for that vendor condtion types are not copied exactly..system excludes some condtions i dont know why but it is working perfectly ion the Qlty system problem is only in Production..pls help me to over come this problem
    Regards
    Saru

    Hi,
    Mike is right, it is likely to be a problem aith the priccing procedure.
    The procedure allocated to the PO may have been set up without the conditions you used in the Info record?
    Check the assignment of the pricing procedure to the PO (there may be a vendor schema group on the vendor master record purchasing view that is pointing to a different schema)
    Check in SPRO Logistics > Materials management > Purchasing > conditions > define price determination process > define schema determination.
    Look for any setting that uses the schema group from the vendor (if the vendor schema group is blank then the system will use the schema associated qwith a blank schema group).
    Then when you can see what schema the P org and vensdor group are pointing to, check the condition types linked to that in the "define calculation schema" menu above the one you just used in SPRO.
    Steve B
    Steve B

  • Problem in Copying Pricing Condition Type

    Hi All,
    This problem is regarding copying pricing condition type in Sales Order. The problem is given below with an example -
    Qty of Material A - 10 PC.
    Condi Type   Amount  Currency   Per  UOM  Condition value  Currency
    ZP06             100         INR          1     PC      1000.00             INR
    ZP07                2         INR          1      PC         20.00             INR        
    ZP08               98        INR          1      PC        980.00             INR      Statistical
    ZP01               98        INR          1      PC        980.00             INR      Mandatory with ERL A/c Key Active
    The condition types ZP06 & ZP07 have access sequence maintained for them and ZP08 has been derived deducting ZP07 from ZP06.
    I want the above mentioned scenario where the values of Condition Type ZP08 which is a Statistical Condi Type will be copied exactly & entirely to condition type ZP01 where It will remain active alongwith posting key ERL.
    I have tried copying it by 100 % copy but the value is getting changed as 100% instead of 98 INR.
    Considering the above scenario please suggest some soluitons.
    Thanks & Regards
    Priyanka

    Hi Tarpan,
    First of all thanks for checking my post.
    In the problem I am not looking for the value of ZP08 to be maintained manually.I want the system to copy the exact details of ZP08 to ZP01 entirely where the condition type ZP01 will remain active alongwith the posting key ERL.
    I have tried copying the condition type ZP08 by using 100% copy of condition type but in ZP01 the resultant value becomes 100% in place of 98 INR.
    Please suggest some solutions.
    Thanks & Regards
    Priyanka

  • 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.

  • SRM - condition types of central contract not copied to ERP (CentContract)

    Hi,
    When I add several condition types to a contract in SRM (updating). After releasing the condition types are not updated in the contract in ERP.
    How can I resolve this. Is there an OSS note?
    Regards,
    Alexander

    condition types are copied from SRM to ECC

Maybe you are looking for