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

Similar Messages

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

  • 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

  • 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

  • Ek01 / EK02 Ist & Plan Cost in Repair order

    Hello Gurus,
    I´m working in Customer Service. I generate a service order automatically from a sales order item. My service order is copied from Standard SM03. After Confirmation IW42, I perform a DP90 in order to transfer all costs & articles used in the repair process to my sales order...... but now I have a doubt:
    --> Where are transferred the cost?? Do I need a EK01 or EK02 pricing conditions??. If yes, how I should define them in my pricing procedure?.
    --> In my service order I find automatically a task list...... when I generate my service order automatically is determined the pricing condition EK02(planned cost) in my sales order.... THat is normal???
    --> Should my EK01 (Ist cost) after the DP90 be informed?? Till now is always 0!
    Thanks a lot for your help!!! Any idea will be great!!

    Hello PeteA,
    Thanks for your idea!
    I´ve not informed the required values in ODP4..... Should I do it??? Ek02 is informed automatically although I´ve not included in ODP4....
    The process is like this:
    --> When I create my new item type IRRP iin my repair order RAS in order to create in background the Service Order automatically the price condition EK02 is informed. (I´ve defined EK02 in pricing procedure Manual & Statistical). Ek02 has the value of the plan Cost of the hours required for the repair process (Only 1 Task in my task list, for example Inspection 1 Hour, Plan Cost 70 euros).
    --> After confirmation of my Service Order IW42 , I perform dp90 but EK01 is not informed.....
    Any other Idea???
    Thanks in advance!!!!
    sapmcw

  • 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

  • EK01 and EK02 not copied to sales order item

    Dear colleagues,
    Is it possible to have EK01/EK02 transferred to the sales order item for assembly type = "0 no assembly order processing"
    (specified in requirement class definition)? I would like to have planned production costs in EK02/EK01.
    I don't specify costing method, variant and sheet in requirement class definition (transaction ovzg)
    The steps are following:
    1. create sales order
    2. set manually proper item category (which refers to assembly type = "0 no assembly order processing")
    3. MD04 - convert generated planned order (lower-level for HALB) into production order
    4. MD04 - release HALB production order
    5. MD04 - convert generated planned order (higher-level for FERT) into production order
    6. MD04 - release FERT production order
    7. ????? we could expect EK02/EK01 in sales order item coming from production orders ?????
    I have found SAP note 857299 nevertheless it is not stated precisely there.
    Please let me know your observations in this area.
    Regards,
    Wojtek

    Hi..
    Hi
    Small change in the program will copy the PO number from Contract to sales order.In case need take help of ABAPer
    Data which is not copied
    LOCAL: VBKD-FKDAT.
    LOCAL: VBKD-FPLNR.
    LOCAL: VBKD-WKWAE.
    LOCAL: VBKD-WKKUR.
    LOCAL: VBKD-DELCO.
    LOCAL: VBKD-BSTKD.
    LOCAL: VBKD-ABSSC.
    LOCAL: VBKD-BSTDK.
    In your data declaration, you have
    LOCAL: VBKD-BSTDK
    Regds
    MM

  • EK02 - Manual or not

    Hi,
    EK02 is in pricing procedure and also in req class for product costing . Product costing happens automatically , there is no problem . However like to know SAP's recommendation whether it shall be flagged for manual in pricing procedure or not.What is the impact if it is not marked for manual.
    With regards,
    Mrinal

    Hi Mrinal,
    > EK02 gets calculated automatically from the costing setting (Costing ID :B) in requirement  class .
    Agree with this statement, i too explained this....
    > VPRS can not be used as the material is a BOM item .
    This is also True...
    > I saw in one of yr thread stating that EK02 shall be manual always . I have seen SAP doc stating EK02 to be statistical (obviously) but not recommended as manual .
    Please refer SAP note Note 155212 - Customizing settings for conditions EK01/EK02
    The reason behind keeping this EK02 manual always is when this condition type is not associated with any requirement class, it may lead to inconsistencies.....
    SAP also tells to keep this as manual ( as per note)
    > I created this thread to know  the logic in SAP to make it manual when it can be calculated automatically through setting req class.
    One logic which i can think as of now is, when there is no requirement class and you want to know the calculated cost and want to compare with the price of the material, then you can enter this as manual.
    Hope it will help
    Thanks,
    Raja

  • Account determination(EK02) clarification

    Hi this is sai, i want clarification for account determination in Ek01 & EK02
           for Ek01 only balance sheet accounts will be assigned ?
          for EK02 only P&L accounts will be assigned?
    and
    main transaction - 4500(Billing Service Provider)
    sub transaction - 0010(Receivable from Invoicing SP)
    which gl account can i assign here(income/asset).

    Hello,
    PFA
    for Ek01 only balance sheet accounts will be assigned ?
    Yes...this shud be B/s acct and also Recon. account for acct type shud be Contracts Acc receivable
    for EK02 only P&L accounts will be assigned?
    Yes.
    main transaction - 4500(Billing Service Provider)
    sub transaction - 0010(Receivable from Invoicing SP)
    which gl account can i assign here(income/asset).
    Income
    Hope this helps
    Rgds
    Rajendra
    Points!

  • Sales Order cost estimate with variant config

    Hi
    I'm hoping for some advice on costing on a variant material.
    I have created a sales order for a variant material and ran a cost estimate to get costs for the sales order.  Should this populate a cost condition within the sales order pricing?  How can the margin be seen in the sales order?
    Thanks for your help.
    Ashley Shannon

    Hello Ashley
    Yes, if you have done your settings correctly, especially Requirements class set up  (see the documentation link),  then the cost estimate will flow to a condition type in Pricing, usually EK01/EK02 conditions. These conditions are used to calculate sales prices (PR00) in cost-plus (mark-up) scenarios.
    Link: http://help.sap.com/erp2005_ehp_04/helpdata/EN/90/ba6da4446711d189420000e829fbbd/frameset.htm
    However Profit margin  as calculated in a sales order comes from VPRS condition  (which is based in Material Master) and is the difference of net value and VPRS condition value in normal circumstance.
    Hope other more knowledgeable experts will weigh in.

  • Sales order cost estimate with GIT account

    Hi,
    Business introduced Goods - in - Transit (Balance sheet account), so PGI will always post to GIT and Invoice it will get reversed.
    For one of the Configuratble material (MTO) scenario we need the Sales order cost estimate to get the Planned cost.
    When i try to execute the sales order cost estimate it says cost element doesnot exist for GIT GL (WHich is right).
    But with maintaining the GIT how to achieve the sales order cost estimate.
    I tried to create CE category 90 for GIT, in Cost estimate am getting error CE 90 not supported for Cost estimate.
    Kindly help this is kind of urgent req for us
    Thanks,
    Sudha

    Hello Ashley
    Yes, if you have done your settings correctly, especially Requirements class set up  (see the documentation link),  then the cost estimate will flow to a condition type in Pricing, usually EK01/EK02 conditions. These conditions are used to calculate sales prices (PR00) in cost-plus (mark-up) scenarios.
    Link: http://help.sap.com/erp2005_ehp_04/helpdata/EN/90/ba6da4446711d189420000e829fbbd/frameset.htm
    However Profit margin  as calculated in a sales order comes from VPRS condition  (which is based in Material Master) and is the difference of net value and VPRS condition value in normal circumstance.
    Hope other more knowledgeable experts will weigh in.

  • Error while Installment Plan creation

    Dear friends ,
    When i am saving the installment plan i am getting this error can anyone please let me know how to rectify this error
    Internal error: Incorrect use of a function module
    Function module FKK_TAX_EXEMPT_KEY_DETERMINE was called with incomplete parameter specifications. One of the following entries is missing in transfer structure I_FKKTAXEXC:
    Tax code
    Company code

    Hi,
    You check the a/c determination for Inst Plan in EK01 & EK02.
    I beleive that the G/L a/c is incorrectly assigned.
    Regards,
    T

  • Account determination not possible for key 3000

    Hi gurus,
    While generating invoice iam getting the error like
    "Account determination not possible for key 3000" 
    3000 is comapny code.
    it shows the Diagnosis
    "The system could find no entry for the following key combinations in the entries for account determination:"
    "Chart of accounts  
    Posting area Billing Default Values: Repayment Method (R401) 
    Key 3000 
    Field names BUKRS "

    Hi,
    For the error, go to details, and check the main/sub transaction.  From there you can navigate thru error analysis and it will take you to the configuration details in SPRO. Check for the key specified in the error log, if the entry is present or not. If not maintain the entries accordingly.
    Alternatively
    Please check the configuration for Automatic GL account determination.
    Please check if the GL determination is made for the main transaction and sub transaction for which it is giving the error.
    Path -: SPRO -> Financial accounting -> Contract Account receivable and payable -> basic functions -> Postings and documents -> document -> define account assignments for automatic postings -> Automatic GL determination.
    Check for ISU : Define account assigment data related to main transaction and data relevant to transaction.
    Alternatively check tcodes EK01 / EK02.
    Hope this helps!!
    Regards,
    Rajesh Popat

Maybe you are looking for