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

Similar Messages

  • 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

  • Error with VPRS condition type in Quotation

    Hi,
    When go through the pricing conditions of my quotations, I see a red signal indicating error before the VPRS Condition type (Condition category G). When i do the condiotn analysis, the diagnosis read as below.
    "Error in quantity / value updation"
    Diagnosis:
    This condition has not been determined using condition records. The amount or value should be determined from another data source. For cost (condition category 'G') it is read using conditions from the material valuation segment, for a cash discount condition it is read using conditions from the terms of payment table.
    In this transaction an error occurs - the material valuation segment or the terms of payment table could not be read or a currency translation has failed.
    System Response
    The condition has been provided with the deactivated indicator 'X'.
    Could you please let me know what could be causing this?
    regards,
    Ashok

    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

  • 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

  • Hide values for certain condition types in Quotation Saleorder and Invoice

    Hi All,
    I have written code to hide values for certain condition types in LV69AFZZ,
    this works fine in the ITEM LEVEL.
    But for the same condition types, I could not hide the values in the HEADER LEVEL.
    Unless I hide it at header level also, this is useless.
    Please guide me how to do it.
    Thanks & Regards
    Pradeep

    Hi,
    We have been using FORM USEREXIT_FIELD_MODIFICATION of LV69AFZz for item level & FORM USEREXIT_FIELD_MODIFIC_KOPF of LV69AFZZ for hiding heade level conditions.
    I hope this helps,
    Regards
    Raju chiutale.

  • Conditions Types during creation of Quotation

    Dear All ,
              I want to know from where the condition types are fetched during creation of quotation in ME47 . These condition types are not fetched from vendor schema thats for sure . I want to know which pricing procedure is responsible for quotation creation .
              My requirement is I have to create a quotation comparision sheet for my vendor and I want to know from which table I should take the values of condition types to achieve my target .
    Regards
    Abhijit Das

    Hi Sachin ,
    I am trying to create a Quotation in ME47 .The condition types I can find init to maintain are
    P000 : Gross Price
    R000 : Discount On gross
    R001 : Discount Of quantity
    R002 : Absolute Discount
    R003 : Discount % on net
    But my client requires more condition types like Packing & Forwarding ,Excise , CESS , VAT /CST , FREIGHT .
    I want to know how I will enter these condition types in Quotation . After maintaining these entries only I want to compare the quotations through ME49 .
    But system is not allowing me to enter these conditions
    HI Sachin
    I am Kalyan,
    To Maintain these conditions in Quotation, use Transaction ME47, Go to Maintain Quotation Overview Screen
    Now select the Line item for which u like to add the conditions as u mentioned, choose the Item conditons Icons (Shift + F6),
    Now, Select / Choose the Validity period will proceed to another screen, where we can edit the changes.
    Here u can add additional Price like freight, discount etc. here. And SAVE it.
    Thanks and Regards
    Kalyan,

  • CRM Table for Condition Type value

    Hi All,
    Can you please let me know the table name from where I can get the value of the pricing condition EK02 in CRM.
    I have a document number from which i can manage to get the item guid. From this I need to get the value of the EK02 condition type that we can see from the Item Condition screen.
    Hence i need a table which maintains a relation between Item Guid + EK02 + value.
    Thanks in advance,
    Regards,
    Pradeep

    Hi,
    My requirement is that I want to dynamically update the EK02 value when a quotation is sent for costing. In CRM, costing is not in standard for quotations. Hence I want to call the costing module of CO from CRM when a quotation is saved, this module will return me the EK02 value. So with the quotation screen open, will the data be available in some buffer so that I can pump in this value to the pricing structure?
    I also came accross the function modules which aid in updating pricing elements of an order. Some of them are as below:
    PRC_PD_ITEM_CHANGE_COND
    PRC_PD_ITEM_CHANGE_COND_MULTI
    PRC_PD_ITEM_CHANGE_MULTI
    PRC_PD_ITEM_CONFIGURED_MULTI
    PRC_PD_ITEM_CREATE
    PRC_PD_ITEM_CREATE_BY_IMPORT
    PRC_PD_ITEM_CREATE_BY_IMPORTM
    PRC_PD_ITEM_CREATE_MULTI
    PRC_PD_ITEM_CREATE_WITH_REF
    PRC_PD_ITEM_CREATE_WITH_REFM
    Which one of this should i use? The CRM version is 5.0 hence its IPC 5.0
    Thanks in advance.
    Regards,
    Pradeep

  • 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

  • Chaning  Condtion types in quotation

    Hi all..,
      I am facing problem in changing condition types in quotation using bapi BAPI_CUSTOMERQUOTATION_CHANGE . Istead of changing the existing value,i am getting duplicate records fot it. Can any one help me out of this problem.
    thanks

    SOLD TO CUSTOMER
      WA_PARTNER-PARTN_ROLE = C_SOLDTOPARTY.
      WA_PARTNER-PARTN_NUMB = V_SOLDTOPARTY.
      WA_PARTNER-ITM_NUMBER = P_ITM_NUMBER.
      APPEND WA_PARTNER TO I_PARTNER.
      CLEAR WA_PARTNER.
    'U' AS UPDATEFLAG
      I_HEADERX-UPDATEFLAG = C_UPDATEFLAG.
    'C' AS LOGIC SWITCH FOR PRICING
      I_LOGIC_SWITCH-PRICING = C_PRICING.     "C
    UPDATE THE PRICE
          WA_CONDITION-ITM_NUMBER = P_ITM_NUMBER.
          WA_CONDITION-COND_TYPE = V_DIRECT_DISCNT.
          WA_CONDITION-COND_VALUE = P_DIRECT_PRICE.
          WA_CONDITION-COND_UPDAT = C_UPDATEFLAG.     "U
          APPEND WA_CONDITION TO I_CONDITION.
      CALL FUNCTION 'BAPI_CUSTOMERQUOTATION_CHANGE'
        EXPORTING
          SALESDOCUMENT        = P_P_DOC_NUMBER     "QUOTATION NUMBER
          QUOTATION_HEADER_INX = I_HEADERX          "UPDATE FLAG
          LOGIC_SWITCH         = I_LOGIC_SWITCH     "PRICING UPDATE FLAG
        TABLES
          RETURN               = P_P_RETURN
          QUOTATION_ITEM_IN    = I_ITEM
          PARTNERS             = I_PARTNER
          PARTNERCHANGES       = I_PARTNERCHANGES
          CONDITIONS_IN        = I_CONDITION.          "PRICING
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

  • Condition type line items

    Hi all,
    Can anybody plz lemme know how the EK01 n EK02 (Condition type line items) which u can find in defintion of a sales document(like OR) in billing tab? I hv read its help in IDES, But wud somebody tel me how we use them n what for n wats the difference between them?
    Thx. Good day!
    Prashant

    dear prashant,
    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

  • 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: UTXJ is not getting re-determined in Quotation/ Sales Order

    Dear All,
    I had created one Quotation with
    Customer-Tax Classification as 1 - Taxable, and
    Material _ Tax Classification as 0 - Tax Exempt
    Condition Records (T.Code: VK11) wasn't maintained.
    Later on, I got informed that Material is also taxable. So, I changed the Material - Tax Classification to 2 - Service Tax.
    Then, I maintained Condition Records (in VK11).
    Now, still taxes are not getting calculated in Quotation.
    When i tried to check Condition Type: JSER - Service Tax; Its still showing A0 - 0% Output Tax in Field: Tax Code instead of AA - O/P (interim) 12.36%
    Also, when i tried to Upadte - Pricing Type: Copy Pricing Elements unchanged and redetermine Taxes in Tab: Conditions; System give following Log:
    Maintain the chapter ID for material LSGENOTHERS J_1IMTCHID
    Please, assist.
    Note: When i tried to create new quotation with same Parameters (Customer & Material for the same Sales Area) taxes are getting calculated.

    Hi Pramod,
    Check following things.
    Check teh pricing date of the Earlier Quotation.
    And now check the Condition reocrds validity date which u created later.
    Ur condition record must be valid on the pricing date, thenonly it will be picked up by the system.
    After u adjust the validity of the condition record, click update pricing.
    also check the material tax clasification in Sales Item level under Billign Document tab, it should be 2, if it is not then change it accordingly and regenerate the pricing.
    Hope this will resolve your issue.
    for anything further pls revert.

  • 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

  • Tax Conditions types not appearing in CRM orders and quotations

    Hello All,
    I have created a new tax condition type in ECC and through initial load replicate the same to CRM. pricing procedure repliction with new tax condition is also successful.
    But, the new tax condition is not appearing in condition tab at item level when i create quotation in CRM. other condition types are coming. data for this condition type is there in custom condition table. mapping of tax classifiction to tax group is also done in SPRO.
    Please advise.
    THank and Regards
    Sudhir Grover

    Hello Sudhir,
    You should check the trace log for pricing at first. Set the user parameter:PRC_TRACE as 'X' on T-cd:SU01 for your user and check the Access analysis on the condition tab.
    Regards,
    Masayuki

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

Maybe you are looking for

  • Error:Message could not be delivered will remain in Outbox

    The error message further states that "The server*** cannot be contacted on port 25" This happens when the computer is sleeping and an alarm is sent from iCal. On my older computer, the mail would open automatically and display the alarm message as s

  • Swing Timer issues on a faster machine.

    Hi everyone, I'm having some trouble using Swing Timers. I have built a system which uses three javax.swing.Timers, these are as follows: timerLeft = new Timer(timerDelay, new ActionListener() { public void actionPerformed(ActionEvent evt) {if(pathPo

  • Importing a SWF file into AS3 FLA

    Hi, I've imported some SWF files I've built, under base class flash.display.MovieClip, into an AS3 code-only (Flash 9 on Macintosh) file. The visuals work fine when I call importedMovieClip.play(), but there's no sound. My current method is pretty si

  • Insert multiple rows with one sql statement in access

    Hi, I'm trying to copy a table into another. What I want to do is to use "Insert into table1 select * from table2 where field > val". Something like that. I know a lot of databases support it. I was wondering if ms access ODBC driver also supports it

  • Non static method

    I have the following: import java.io.*; import java.util.*; public class BranchB2      public static void main(String[] args)           int pathCost, source, destination, count=0;           int userSource, userDestination;           String tempRead;