Condition type EK01

Hi
the status of Condition type is inactive in my item ..
How to activate this condition type..
Thanks in Advance..

A condition type can be inactive in a transaction for varoius reasons.
1. Condition exclusion can be reason. Pls check whether this c.type is exclusive of any other c.type in the exclusion procedures.
2. A condition type can also be inactive if it is configured in pricing procedure as Manual entry only, but a value appears automatically due to presence of condition records.
Pls check in which category, the condition type falls, and do the rectification.
Reward if this helps.

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.

SERVICE ORDER COST IS NOT FLOWING TO CONDITION TYPE EK01 IN SALES ORDER

hi all,
My requirement is that the cost incurred in service order should flow to the condition type ek01.
we will be running the transaction dp90 to calculate the cost for the resources used.
the cost are getting calculated at service order level but this cost are not flowing to the billing item being generated from dp90 in the billing request.
the settings that i have made are as follows: I have maintained the condition type ek01in the sales pricing procedure. are there any other settings required by me to make.
valuable answers will be be rewarded fullpoints.
regards,
ashish

Hi prince
Check out in Control data of Condition Type--PB00..Enter "NO Limitations" in Manual Entries. and check the 'Amout' and 'Value' and 'Delete' so that u can make changes to that condition type in line item in sales order.

Condition type EK01 missing in pricing procedure A V (error message V1206)

Hi gurus,
We get error message "condition type EK01 missing in pricing procedure A V" when creating a Billing request from a SErvice Order through TX-DP90.
We reviewed customizing regarding this issue:
ODP4 - SD Document linked to condition EK01 (this condition shall bring the actual cost in the order)
ODP1 - Dinamyc item profile to create Billing Request.
Pricing procedure: sales area assignments, condition types (including EK01)
but error still shows.
Any idea what additional setting is necessary in customizing so EK01 is transfered to the SD doc in DP90?
Thanks,
VL

Hi Lakshmipathi,
Thanks for your answer.
I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
Thanks for your always great help,
VL

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

Pricing unit in condition type..

Hi folks,
I have a problem with " pricing unit".
Iam using condition type EK01 . Under normal circumstance, the pricing unit takes the value of 1..
Suddenly, it is taking 100 as value.
Can anyone give a clue from where this, Pricing Unit picks this value i.e 1 or 100.
and now how it is suddenly taking 100..
where we need to make settings for this...
thanks in advance,
Sourav

Hello Saurabh,
Please check following things -
1. MM02 - Accounting data1 tab, Price unit - should be "1"
2. In EK01 condition under heading "changes can be made" remove tick for quatity conversion.
Hope either of this will you to resolve the issue.
Regards,
Satish

Condition type JTX1 missing

Hi,
I'm practicing on home pc IDES 4.7. I have done copy client from 000 to 800 to use CIN in IDES, and now I can see the calulation procedure TAXINJ assigned to country IN which was not there before coping the client.
I have done the customization for CIN ( yet to test ) also. But now Im getting one error while creating CMR & MMR i.e. tax condition JTX1 not defined. I can see the condition default in CMR & MMR but not classification value and while doing so in "Define tax determination rules" it is giving the error that "Condition type JTX1 is not defined for taxes" although I can see it assigned to country IN but if u click enter it will throw the error.
So my query is that how come these conditions are missing as these are default condition type and can we create these conditions manually & if yes which access sequence should we assign to it and what are other settings for it ?
Plz help me out I'm a SAP learner and unable to create CMR & MMR bcoz of this error.

Hi Lakshmipathi,
Thanks for your answer.
I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
Thanks for your always great help,
VL

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 for Amortisation cost

Dear friends,
I hve created condition type for amortisation cost in pricing.
It is adding the value for the gross price+ amortisation cost and flowing it to calculation of excise Duty in BASB.
For ex.
P001 - 1000
ZDIE - 100
so BASB - 1100
Excise Duties are calculated on 1100...That is also OK
But when the calculation of CST- As per system it is calculated on 1100 (BASB)....
And here client requirment is to calculate on P001(Gross Price).
Again calculation of
A/P Price + ED + VAT it is taking A/P Price as 1100.
Our requirement is to take it P001 as 1000.
How to take amortization cost to be considered only for the calculation of excise duties and rest calculation in tax procedure being considered on Gross Price.......
Plz. suggest
Thanks in Advance,
navin

I hope you have searched regarding the topic.
Refer following SDN wiki link for all your anwers:
- [ EK01/EK02/VPRS |http://wiki.sdn.sap.com/wiki/display/ERPLO/VPRS,+EK01(ActualCost)andEK02(Calculated+Cost)]
Regards
JP

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

Problem with Condition Type in BAPI_QUOTATION_CREATEFROMDATA2 for Txn VA21

Hi All,
I am using BAPI_QUOTATION_CREATEFROMDATA2 for Sales Quotation by txn VA21.
In this txn,There are 22 condition types available in my system.
The problem is,it is updating every condition type twice.
Pls give me the solution.
Regards,
Shiv Kant

Hi,
I am giving billing document code, we are using BAPI to upload billing documents into SAP.
you can check pricing conditions code. we are using only two pricing condition types. our technical consultant hardcoded condition types.
wa_billingdata-salesorg = wa_bill5-sorg.
    wa_billingdata-distr_chan = wa_BILL5-dist.
    wa_billingdata-division = wa_BILL5-div.
    wa_billingdata-doc_type = 'ZSO5'.
    wa_billingdata-ordbilltyp = 'FX'.
    wa_billingdata-bill_date = wa_BILL5-BDATE.
    wa_billingdata-sold_to = wa_BILL5-CUSTNO.
*    wa_billingdata-price_date = WA_BILL1-BDATE.
   wa_billingdata-country = wa_BILL5-CNTRY.
    wa_billingdata-bill_to = wa_BILL5-custno.
    wa_billingdata-currency = WA_BILL5-CURR.
    wa_billingdata-wbs_elem = wa_bill5-wbsele.
    wa_billingdata-xblnr = wa_bill5-billno.
    wa_billingdata-zuonr = wa_bill5-invoiceno.
flag1 = 1.
endif.
translate wa_bill5-matdesc to upper case.
    SELECT MATNR FROM MARA INTO IT_MARA up to 1 rows WHERE MATNR = WA_BILL5-MATDESC.
            endselect.
    if sy-subrc = 0.
      wa_billingdata-plant = wa_BILL5-PLANT.
      wa_billingdata-NO_MATMAST = ' '.
      wa_billingdata-material = WA_BILL5-MATDESC.
      wa_billingdata-REQ_QTY = '1'.
      wa_billingdata-ACCTASGNMT = '05'.
   else.
       wa_billingdata-ACCTASGNMT = '05'.
       wa_billingdata-NO_MATMAST = 'X'.
       wa_billingdata-SHORT_TEXT = 'ADAGE MATERIAL'.
       wa_billingdata-TAXCL_1MAT = '0'.
       wa_billingdata-SALES_UNIT = 'EA'.
       wa_billingdata-material = WA_BILL5-MATDESC.
       wa_billingdata-REQ_QTY = '1'.
   endif.
flag = flag + 1.
    wa_billingdata-ref_item = flag.
    append wa_billingdata to billingdata.
    wa_conditiondata-data_index = flag.
     wa_CONDITIONDATA-cond_value = WA_BILL5-ADVERTISCOST.
    wa_conditiondata-cond_type = 'EK01'.
    append wa_conditiondata to conditiondata.
clear wa_conditiondata.
    wa_conditiondata-data_index = flag.
     wa_conditiondata-cond_value = WA_BILL5-COMM.
    wa_conditiondata-cond_type = 'ZCOM'.
    append wa_conditiondata to conditiondata.
clear wa_conditiondata.
IF TESTRUN IS INITIAL.
move-corresponding wa_bill5 to wa_bill2.
wa_bill2-status = 'P'.
append wa_bill2 to it_bill2.
modify zzbilling from table it_bill2.
commit WORK.
ENDIF.
REFRESH IT_BILL2.
endloop.
flag1 = 0.
flag = 0.
IF TESTRUN IS INITIAL.
CALL FUNCTION 'BAPI_BILLINGDOC_CREATEMULTIPLE'
*   EXPORTING
*     CREATORDATAIN         = creaord
*     TESTRUN               = 'X'
*     POSTING               = 'X'
    TABLES
     BILLINGDATAIN         = billingdata
     CONDITIONDATAIN       = conditiondata
*     CCARDDATAIN           =
*     TEXTDATAIN            =
*     ERRORS                =
      RETURN                = bapiret
      SUCCESS               = succ.
Regards,
Chandra

Condition Type for CoGS

Dear SD Gurus,
Is it possible to transfer the Cost of Goods Sold (CoGS) amount to a condition type? Can I use EK01 or EK02? Or any idea?
Thanks,
Soo

VPRS Condition type to transfer can be used to transfer cost of Goods Sold price.
The condition type VPRS goes into the valuation segment in the material master and determines from this the standard price or average price.
Settings in Customizing
The condition type VPRS is labeled as a statistical condition in the pricing procedure.
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.
The profit margin is determined using the calculation formula 11 assigned in the pricing procedure. In this calculation formula the cost price is subtracted from the subtotal of net value 2.
Regards
Prashant

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

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

How to prevent consecutive entries of same condition type in a sales order

Hi,
My client is using manual condition type for the basic price "ZBPR". Now system allowing multiple entry against this condition type in the pricing screen during order creation i.e in the first line if we put Condition Type "ZBPR" and putting some value as amount, then again if I put "ZBPR" as condition type and give some other value as amount then system is allowing this and doing all the subsequent calculation.This is not acceptable by the client.
The functional person regarding this is saying this can be done by using routine.Can some body tell me which routine should I take for this if that is possible by routine and the required code.Also say if there is other way to solve this.
Thanks,
Manas.

Hi ,
u can do it thru VOFM(tcode)--->Menu -> Formulas>condition value , but in this case u need to derive the value of this condition type by using ur own logic.
Re: vofm-routine
Regards
prabhu

Condition type EK01

Similar Messages

Maybe you are looking for