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

Similar Messages

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

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.

Basic differnce between 000 and 001 clients.

what is the basic differnce between 000 and 001 clients?
why do we use client 000 as source client while client copy?

Hi Kumar
The basic difference between Client 000 and Client 001 is that Client 000 is client independent instace while Client 001 is Client dependent.
Client 000 is SAP source client while Client 001 doesn't exits for every installation.
Regards
Shashank

Differnce between SAP-XI and SAP PI

hi can any body tell me what is the differnce between SAP-XI and SAP-PI

Hi vijay,
u can get lot of information regarding PI and XI in sdn.There already exists a no. of thread.just search with keyword "XI 3.0 and PI 7.0" u can get a lot.
XI 3.0
1. J2Se adapter engine was replaced with J2EE Adapter Engine.
2. BPM was available from XI 3.0
3. Part of Netweaver 2004
PI 7.0
1XI renames as Process Integration
2.. Part of Netweaver 2004s.
3. Has all features of XI 3.0 and every SP of Pi 7.0 has a corresponding release for XI 3.0.
4. Runs on WAS 7.0 and has same features as XI 3,0
From functional point, there is no difference between XI3.0 and PI7.0. There are changes only wrt SP. For every SP release on PI7.0 a corresponding SP for XI3.0 is also released.
A comparision of the service packs in 2004 and 2004s;
in 2004 - in 2004s
SP12 & < - SP04
SP13 + 14 - SP05
SP15 - SP06
SP16 - SP07
SP17 - SP08
SP18 - SP09
For release notes
ref:http://help.sap.com/saphelp_nw04/helpdata/en/cf/9844428e9cbe30e10000000a155106/frameset.htm
There is no f'nal difference between XI 3.0 and PI 7.0. In order to bring all netweaver releases on par with each other , SAP released / renamed XI as PI and it is a part of NW04s
For every release of PI 7.0, there is a parallel Support Pack on XI.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf">SAP NetWeaver Process Integration 7.1 Overview of New Capabilities</a>
Also check these threads.
Difference between NetWeaver 2004 and NetWeaver 7.0 or 7.1
All the diff between XI 3.0 and PI 7.0
differences between xi 3.0 and pi 7.0
Difference/ changes from XI 3.0 to PI 7.0
regards
Bill

Differnce between AT NEW AND ON CHANGE OF

Hi,
Differnce between AT NEW AND ON CHANGE OF
Iam waiting foryour reply
Thanks & Regards
Raja Sekhar.T

Hai Raja
check the following Documents
1. AT NEW f.
2. AT END OF f.
3. AT FIRST.
4. AT LAST.
5. AT fg.
Effect
In a LOOP which processes a dataset created with EXTRACT , you can use special control structures for control break processing. All these structures begin with AT and end with ENDAT . The sequence of statements which lies between them is then executed if a control break occurs.
You can use these key words for control break processing with extract datasets only if the active LOOP statement is proceesing an extract dataset.
The control level structure with extract datasets is dynamic. It corresponds exactly to the sort key of the extract dataset, i.e. to the order of fields in the field group HEADER by which the extract dataset was sorted .
At the end of a control group ( AT END OF , AT LAST ), there are two types of control level information between AT and ENDAT :
If the sort key of the extract dataset contains a non-numeric field h (particularly in the field group HEADER ), the field CNT(h) contains the number of control breaks in the (subordinate) control level h .
For extracted number fields g (see also ABAP/4 number types ), the fields SUM(g) contain the relevant control totals.
Notes
The fields CNT(h) and SUM(g) can only be addressed after they have been sorted. Otherwise, a runtime error may occur.
The fields CNT(h) and SUM(g) are filled with the relevant values for a control level at the end of each control group ( AT END OF , AT LAST ), not at the beginning ( AT FIRST , AT NEW ).
When calculating totals with SUM(g) , the system automatically chooses the maximum field sizes so that an overflow occurs only if the absolute value area limits are exceeded.
You can also use special control break control structures with LOOP s on internal tables.
Variant 1
AT NEW f.
Variant 2
AT END OF f.
Effect
f is a field from the field group HEADER . The enclosed sequence of statements is executed if
the field f occurs in the sort key of the extract dataset (and thus also in the field group HEADER ) and
the field f or a superior sort criterion has a different value in the current LOOP line than in the prceding ( AT NEW ) or subsequent ( AT END OF ) record of the extract dataset.
Example
DATA: NAME(30),
      SALES TYPE I.
FIELD-GROUPS: HEADER, INFOS.
INSERT: NAME INTO HEADER,
        SALES INTO INFOS.
LOOP.
AT NEW NAME.
    NEW-PAGE.
ENDAT.
AT END OF NAME.
    WRITE: / NAME, SUM(SALES).
ENDAT.
ENDLOOP.
Notes
If the extract dataset is not sorted before processing with LOOP , no control level structure is defined and the statements following AT NEW or AT END OF are not executed.
Fields which stand at hex zero are ignored by the control break check with AT NEW or AT END OF . This corresponds to the behavior of the SORT statement, which always places unoccupied fields (i.e. fields which stand at hex zero) before all occupied fields when sorting extract datasets, regardless of whether the sort sequence is in ascending or descending order.
Variant 3
AT FIRST.
Variant 4
AT LAST.
Effect
Executes the relevant series of statements just once - either on the first loop pass (with AT FIRST ) or on the last loop pass (with AT LAST ).
Variant 5
AT fg.
Addition
... WITH fg1
Effect
This statement makes single record processing dependent on the type of extracted record.
The sequence of statements following AT fg are executed whenever the current LOOP record is created with EXTRACT fg (in other words: when the current record is a fg record).
Addition
... WITH fg1
Effect
Executes the sequence of statements belonging to AT fg WITH fg1 only if the record of the field group fg in the dataset is immediately followed by a record of the field group fg1 .
Basic form
ON CHANGE OF f.
Addition
... OR f1
Effect
Executes the processing block enclosed by the " ON CHANGE OF f " and " ENDON " statements whenever the contents of the field f change (control break processing).
Normally, you use the statement to manipulate database fields during GET events or SELECT / ENDSELECT processing.
Note
There are special control structures for processing control breaks in LOOP s on internal tables or extract datasets AT ).
ON CHANGE OF is unsuitable for recognizing control levels in loops of this type because it always creates a global auxiliary field which is used to check for changes. This global auxiliary field can only be changed in the relevant ON CHANGE OF statement. It is not reset when the processing goes into loops or subroutines, so unwanted effects can occur if the loop or subroutine is executed again. Also, since it is set to its initial value when created (like any other field), any ON CHANGE OF processing will be executed after the first test, unless the contents of the field concerned happen to be identical to the initial value.
Example
TABLES T100.
SELECT * FROM T100 WHERE SPRSL = SY-LANGU AND
                         MSGNR < '010'
                   ORDER BY PRIMARY KEY.
ON CHANGE OF T100-ARBGB.
    ULINE.
    WRITE: / '**', T100-ARBGB, '**'.
ENDON.
WRITE: / T100-MSGNR, T100-TEXT.
ENDSELECT.
Displays all messages with their numbers in the logon language, provided the number is less than '010'.
Each time the message class changes, it is output.
Addition
... OR f1
Effect
Also executes the code whenever the contents of the field f1 changes.
You can use this addition several times.
Example
Logical database F1S
TABLES: SPFLI, SFLIGHT, SBOOK.
GET SBOOK.
ON CHANGE OF SPFLI-CARRID   OR
               SPFLI-CONNID   OR
               SFLIGHT-FLDATE.
    ULINE.
    WRITE: /5 SPFLI-CARRID, SPFLI-CONNID,
            5 SFLIGHT-FLDATE, SPFLI-FLTIME,
            5 SFLIGHT-SEATSMAX, SFLIGHT-SEATSOCC.
ENDON.
WRITE: / SBOOK-CUSTOMID.
The code between ON CHANGE OF and ENDON is executed only if at least one of the fields SPFLI-CARRID , SPFLI-CONNID or SFLIGHT-FLDATE has changed, i.e. there is a different flight connection (which also has bookings).
Notes
Thanks & regards
Sreenivasulu P

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

Differnce Between OBIEE and BO And Cognos

Hi experts.
I would like to know the differnce between OBIEE , BO And Cognos. Is there is any white paper regarding this.
Thanks in advance
Regards
Frnds

Hi Friend ;)
Check out this.. http://www.forumtopics.com/busobj/viewtopic.php?p=543325&sid=21c3e9a1b9dd85679d5e51c335b8a74e
also http://oracle.ittoolbox.com/groups/strategy-planning/oracle-projectmanagement/what-is-obiee-1681803
Thanks & Regards
Kishore Guggilla
Edited by: Kishore Guggilla on Nov 20, 2008 11:52 AM

Differnce between unicode and non unicode

Hi every body i want to differnce between unicode and non unicode and for what purposes this ulities are used explain me little brief what is t code for that , how to checj version, how to convert uni to non uni ?
Advance Thanks
Vishnuprasad.G

Hello Vishnu,
before Release 6.10, SAP software only used codes where every character is displayed by one byte, therefore character sets like these are also called single-byte codepages. However, every one of these character sets is only suitable for a limited number of languages.
Problems arise if you try to work with texts written in different incompatible character sets in one central system. If, for example, a system only has a West European character set, other characters cannot be correctly processed.
As of 6.10, to resolve these issues, SAP has introduced Unicode. Each character is generally mapped using 2 bytes and this offers a maximum of 65 536 bit combinations.
Thus, a Unicode-compatible ABAP program is one where all Unicode checks are in effect. Such programs return the same results in UC systems as in non-UC systems. To perform the relevant syntax checks, you must activate the "UC checks" flag in the screens of the program and class attributes.
With TC: /nUCCHECH you can check a program set for a syntax errors in UC environment.
Bye,
Peter

Differnce between portal and collaboration

Hi All
What is differnce between portal and collaboration & uses as well?
Thanks in advance
Raja.S

Periodic billing is used when you want to bill the customer at different points of time based on the periodicity or progress of the work. Milestone billing can be used for this type of billing purposes when you want to have billing control from the project.
Resource billing is based on the resource consumption for the particular activities. Dynamic Item Processor (DIP) profile is used for the resource related billing.
Further information acn be had from the link
[http://help.sap.com/saphelp_47x200/helpdata/en/aa/96853478616434e10000009b38f83b/frameset.htm]
Hope this is of some help
Venu

Differnce between MMPV and OB52

Wat is the differnce between OB52 and MMPV,
Thanks
Ramki

Hi Ramki,
This question has been answered already in several threads before.
Please use the search before posting new threads.
Hi Priyanka,
Sam has already answered the question.
Why are you replying with same answer and requesting points for that please do not do that.
Thank you

Differnce Between /n and /BEND

Hi,
Differnce Between /n and /BEND?
thanks and regards
sarath

Hi ,
/n ends the particular transaction .
/bend - This means batch end .
This comes only in BDC concept .This is where you transfer data from the legacy system to sap R/3 system .When you are performing recording process and you dont want to continue any more you give /bend .

Differnce between periodic and Resourse billing.

Differnce between periodic and Resourse billing, and how to do it in sap?..
Can anyone suggest me step wise
Thanks in advance

Periodic billing is used when you want to bill the customer at different points of time based on the periodicity or progress of the work. Milestone billing can be used for this type of billing purposes when you want to have billing control from the project.
Resource billing is based on the resource consumption for the particular activities. Dynamic Item Processor (DIP) profile is used for the resource related billing.
Further information acn be had from the link
[http://help.sap.com/saphelp_47x200/helpdata/en/aa/96853478616434e10000009b38f83b/frameset.htm]
Hope this is of some help
Venu

Differnce between business name and physical name

What is the differnce between business name and physical name in OWB

Hi Vibhuti,
What I have noticed is that Physical name is THE important thing that is required while importing and synchronising. It has a length limitation of 30. The mappings appear with this name in the left panel in design center. The Business name is just for reference I believe.
Cheers,
Swagata

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

Differnce between EK01 & Ek02

Similar Messages

Maybe you are looking for