EK01 AND EK02

hi friends,
Can any one explain about actual cost (EK01) and caliculated cost (EK02). where we can use these condition types EK01 and EK02. In which scenario we can use EK01 and which scenario we can use EK02.
Explain about Actual cost and caliculated cost, in functional wise also.
Thanks & Regards

Hi Narayana
The standard system contains the following condition types that can be used in connection with unit costing, product costing, and preliminary order costing in assembly processing:
Condition Types for Pricing
Condition Type
Meaning
EK01
Cost of goods manufactured (CGM)
EK02
CGM (statistical)
EK03
Fixed CGM (statistical)
Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
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 EK03 offers the capability of transferring the fixed costs of a cost estimate into the conditions.
The costs are transferred from the cost component view Cost of goods sold into the condition type.
The above-mentioned condition types must be of category Q. Whether a condition type of category Q is only used in pricing as a statistical value or for price calculation is controlled in the pricing procedure.
The condition type is created in Customizing for Sales.
The condition type can be selected as follows:
Through the sales document type
Condition types EK01 and EK02 are specified in the CndTypLineItems field in the sales document type.
Through the requirements class
This enables you to define different condition types for different sales document items of a sales document.
Condition types EK01 or EK02 are specified in the CndTypLineItems field in the requirements class.
Condition type EK03 is specified in the CondTypLinItFix field. You can only use condition type EK03 in conjunction with the requirements class.
http://help.sap.com/saphelp_47x200/helpdata/en/90/ba6d8a446711d189420000e829fbbd/frameset.htm
Reward if useful to u

Similar Messages

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

EK01 and EK02 costing difference

Dear Friennds,
In construction co which condition should I take for cost estimation, as management used to add their profits in the estimation only then how I can make the pricing procedure by selecting the right condition type for cost. It should be EK02 or EK01 or VPRS or something else and how can find the profit margin.
Please guide me
Regards,
Atul.

Atul,
EK01: If this is assigned, then system carries out sales order line item product costing and can be used to calculate net value for a line item as a basis.It is usually used to manage 'follow through type' of orders. Example you purchase something directly on behalf of the customer (outside normal stock) and then you sell it to the customer with a mark-up.
EK02: If this is assigned, sales order line item cost can be used only to compare with net value by which the profit margin can be calculated. It has close integration with Controlling. It may be used for BOM and configurable material.It Usually allows you to hold the cost of the item and therefore allow accurate accounting later on during the process and yes it should be added to the relevant pricing procedure if you want to use this type of process
Also
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.
EK02 is used for calculating the magin in line item of order while in case price is based on cost + markup for example then EK01 is used
Reward if this helps...
Regds
MM

Pricing conditions EK01 and PR00 in pricing procedure

Hi Gurus,
We have a process in which a SD billing request is generated by using DIP profile (DP90). Pricing condition used in the pricing procedure for the sales document is EK01 (which brings the actual cost of the service order that creates the Billing request through DP90) but it happens sometimes that EK01 is not desired but instead PR00 ( another price agreed with a certain client instead of the actual cost in the order).
In order to match this need, best would be to combine both conditions (EK01 and PR00) in the same pricing procedure, and as a general rule, EK01 will apply in the billing request price, but in case PR00 condition exists, then this one will prevail and EK01 will be in the price conditions but will not be taken into account in the price calculation--> how can this be done in the pricing procedure?
Another possibility would be using different pricing procedures so that one has EK01 as pricing condition and the other one has PR00. The pricing procedure will be assigned by using document pricing procedure assigned to a different document type but this is not the desired solution as it makes much more tricky the design: another dynamic item profile would be needed so that proper document type is assigned.
Thanks for your great help in advanced!
VL

Hi Victor,
You can put both of the conditions in the same pricing procedure and use the exclusion group to compare the conditions and choose the favourable as per you requirement.
I hope this will certainly help you in solving your problwm.
Regards,
VB

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

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

Importance of EK01 in Sales order costing

Hi all,
What is the importance of EK01 in sales order costing and what is the diff between Ek01 and EK02.
Thanks

Check this link http://help.sap.com/saphelp_pserv472/helpdata/EN/90/ba6e67446711d189420000e829fbbd/frameset.htm
Regards / KOTA

About ek01

hi gurus,
Only thing is ask some one how this pricing will be done. Like if
estimated cost comes through easy cost planning.
My concern is how the final will will be derived, by adding some
formula, that will take condition base value as EK01 or thru some way.
Becvause profit margin is different every time
if I write some formula then it will take fixed % every time
getting me.

Hi Narayana
The standard system contains the following condition types that can be used in connection with unit costing, product costing, and preliminary order costing in assembly processing:
Condition Types for Pricing
Condition Type
Meaning
EK01
Cost of goods manufactured (CGM)
EK02
CGM (statistical)
EK03
Fixed CGM (statistical)
Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
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 EK03 offers the capability of transferring the fixed costs of a cost estimate into the conditions.
The costs are transferred from the cost component view Cost of goods sold into the condition type.
The above-mentioned condition types must be of category Q. Whether a condition type of category Q is only used in pricing as a statistical value or for price calculation is controlled in the pricing procedure.
The condition type is created in Customizing for Sales.
The condition type can be selected as follows:
Through the sales document type
Condition types EK01 and EK02 are specified in the CndTypLineItems field in the sales document type.
Through the requirements class
This enables you to define different condition types for different sales document items of a sales document.
Condition types EK01 or EK02 are specified in the CndTypLineItems field in the requirements class.
Condition type EK03 is specified in the CondTypLinItFix field. You can only use condition type EK03 in conjunction with the requirements class.
http://help.sap.com/saphelp_47x200/helpdata/en/90/ba6d8a446711d189420000e829fbbd/frameset.htm
Reward if useful to u

Debit and Credit on FI-CA

Dear FI-CA gurus.
On FI-CA, how debit and credit is defined for FPE1?
I could not find any configuration about Debit&Credit on
EK01 or EK02.
BR
Y.Kaneko

Hi,
You need to first configure the main and subs for the company code, the contract account belongs to in the following SPRO path-
IMG->Financial Accounting->Contract AR&P->Basic functions->Posting&Documents->Document->Maintain Document Assignments->Define Account Assignments for Automatic Postings->Maintain Transactions for IS-U->Maintain Transactions for Other Receivables.
When you are configuring you will find one option whether to set the main\sub as debit\credit.
It depnds on whether you configure the main\subs for the company code at contract account level (division-independent) or the contarct level (division-dependent).
After , you have performed the above activity, you need to maintain the GL account assingment of main\subs through t.code EK01 and EK02 respectively.
String fro EK01-Company code, Account determination ID, main transaction, Debtors account...
String for EK02-Company code, Account determination ID, main transaction, subtransaction, revenue account.....
Both EK01 and EK02 are used for GL account determination.
Here also configure the main\subs for the company code at contract account level (division-independent) the contarct level (division-dependent) depends on the decision that you want to post document at CA level or Contract level.
After you have performed the above activity, go to t.code FPE1 to post a document aginst the CA\Contract using the particular set of main\sub.
Hope it helps.....
Thanks,
Amlan

SD Questions Please Send The Answers

Hai
            Here i have attached some SD Interview Questions .Please Send the Answers .
Awaiting For Ur Replay - Please Mail Me [email protected], And [email protected]
Thanks
S.Siva
1.     Five steps of implementation with full details.
2.     What is ticket? Process flow ticket?
3.     What is ticketing tool? What is SODA?
4.     How to stop PGI?
5.     Details about SLS.
6.     Details about the Gap analysis. (What are the gaps you have faced?)
7.     What is meant by landscape? (Landscape of your project for example)
8.     In which scenario we go for different pricing procedure at orders and billing?
9.     Cut over activity means what?
10.     In real-time project, how many pricing procedures to be used?
11.     What are the tools used to communicate with the client?
12.     Any three major issues faced in the support project?
13.     Difference between SD account key and FI account key?
14.     How to post goods receipt from storage location to warehouse? What is the movement type?
15.     Tcode for listing blocked documents?
16.     What is the advantage of using the text as reference instead of duplicating it?
17.     Have you ever applied BPR (Business Process Reengineering) in an implementation project?
18.     To perform material configuration, which system one has to use in landscape?
19.     What is the tcode for creating number range for a sales order type?
20.     Difference between centralized credit mgmt and decentralized credit management.
21.     Where do u configure in development server or application server or in testing server?
22.     Details about clients.
23.     What is an abap query? Why it is used?
24.     What are the steps for end user training in sap SD module?
25.     Difference between discount and rebate.
26.     When is material determination got triggered?
27.     A customer wants to buy two materials / one is 3rd party material (Item category: TAS) / another one is normal material (Item category: TAN). His requirement is he wants a single invoice for both items without splitting? How can we do this?
28.     In consignment fill up, we deliver goods to customer site, is there any agreement with customer? If yes means, what type of agreement relating price?
29.     Details about VAT configuration.
30.     What is the use of pricing date in condition type?
31.     In R/3, we represent a companys structure by defining and assigning corporate structure elements. What is the purpose of doing that?
32.     What are the different partner functions can a customer master record serve?
33.     What is the difference between condition type EK01 and EK02?
34.     What is retroactive billing? Who will create that?
35.     In your functional role, how you gather technical specifications for your technical team members from your client?
36.     Is it possible to change existing item categories?
37.     For cash sale, how will availability check be done?
38.     How is the access sequence controlled?
39.     User specific parameter means what? How to create that one?
40.     What is the difference between listing and exclusion?
41.     Difference between customization and configuration.
42.     How to customize rebate processing in sap sd?
43.     LSMW important step is what?
44.     What is the extract used in condition technique of pricing?
45.     Can we create credit management separately for two different materials?
46.     Work center means what?
47.     If the client logon screen deleted while requirement is urgent, then what to do?
48.     What is meant by time bond deliveries?
49.     After implementing sap in production environment, while creating sales order, client wants to give discount for first 10 sales orders? How to do this?
50.     What are the Three different kinds of messages? What is the difference between them?
51.     Details about testing at sap sd.
52.     What is the access sequence for header conditions?
53.     Details about actual GI date and planned GI date .Can actual GI dt differ from planned GI dt?
54.     Influencing factors for account determination for invoices.
55.     Details about sap best practices.
56.     To start a transaction, how many ways are there? And what are they?
57.     Who will create transportation request?
58.     In realization phase, what will be doing?
59.     Is it possible to release change request without releasing task?
60.     Details about lean warehouse management.
61.     How to customize excise duty, insurance and cess condition type in pricing procedure?
62.     How to stop PGI?
63.     Data dictionary or repository means what?
64.     How do you transfer request from development instance to production or quality instance?
65.     What is the importance of release status in condition table?
66.     Why does account group controls customer?
67.     What are the deliverables in your blue print?
68.     If you generate bill more than credit limit, then what will happen?
69.     What is the value class used for material creation?
70.     Why do we maintain sales office?
71.     Is it possible to substitute one product for another? If so, how it can be achieved?
72.     What is the difference between ATP check and availability check? How these reflect in sales order?( Which check system considers) what are the img steps for the same?
73.     Explain process and steps involved in returns third party order processing.
74.     What is the client specific data? Give 2 examples of client specific data.
75.     What is the most critical field in delivery document?
76.     What is the relation between sap sd and ABAP?
77.     What is the functionality of negative posting in billing document?
78.     In real time, when we start system in first, what screen we get and tell me the process how to log on screen? (IBM question)
79.     How can you check in sap system, how, when and by whom, which fields in the customer master record were changed?
80.     What is variant and its configuration?
81.     After logging into R/3 system, if you want an end user to see a specific menu. How could you do that?
82.     Is it possible to automate output processing?
83.     Which data is relevant for crediting credit and debit memos?
84.     In system landscape, where the sandbox and golden box client exists?
85.     What is the user exists? /how can we create user exists? What is the purpose of that?
86.     Details about value sap.
87.     Is there any difference between product selection and material determination?
88.     How do you transfer request from development instance to production or development instance?
89.What part of the company is responsible for the type of shipping, the necessary shipping materials and the means of transport?

What is ticket? Process flow ticket
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
To begin with , we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
Regards.

Error while creating Invoice

Hi Experts,
While Creating Invoice i am getting below error
G/L account 0001 11002 cannot be posted to, please correct your entry
Message no. >0205
Diagnosis
This G/L account is blocked against posting or is a reconciliation account and cannot be posted to directly.
System Response
The G/L account cannot be posted to.
Procedure for System Administration
Check you entry for errors, or change the master record of the G/L account: Proceed.
I have taken lot of experts advises, but unable to solve. I have checked FS00, EK01 and EK02 and unable to find what problem is with these Tcodes.
When i was trying to check Tcode FS00 i found G/L Account is "11002 - Constructions" and when i tried to see account group it was Balance Sheet Account and by experts advise i changed it to P&L Statement Acct, when i am opening Initially after saving Account Grp.Tcode FS00 it is showing Acct. Grp. as P&L Statement Acct and when i am choosing other tabs in FS00 the Acct Grp is Changing back to Balance sheet acct.. I am unable to find what wrong with this.
I want to ask whether the problem is with above mentioned thing or with other, i believe i have explained my error in detail. Please advise how can i overcome this error.
Regards,
Kushal
Moderator note - thread locked, same issue identified in G/L error while posting an amount - TXN: FPE1 - SAP ISU and Error while trying to do Billing

Hi friends,
The error thats triggered is "For object RV_BELEGnumber range 19 does not exist".
I have deleted all the existing no ranges in VN01 and customized the nuber range for invoice doc and set it at Z1(Internal no range :1000-1999) and the existing no range entry in OBA7 for RV is 18(1800000000- 1899999999).
Z1(Internal no range :1000-1999) for Invoices
Z2(Internal no range :2000-2999) for Deliveries
Z3 (Internal no range :3000-3999) for sales orders
So my VN01 entries consists of Z1(Internal no range :1000-1999) ,Z2(Internal no range :2000-2999) ,Z3 (Internal no range :3000-3999) .
The sales orders and deliveries are working out fine but while generating the invoice its triggering the above message.
Pl help on this.
Thanks
Ivy

Error while doing billing

Hi every one'
i got an error while doing billing
Error :sub transactions in schema Z step 0001 inconsistent,
this error is comming while using transaction eamabi,
the schema is worked properly since i updated a line item for additional TAX,
and we created new sub transactins for additional vat,AND for the sub transactions i have added a new GL account,
and i have added those Sub transactions in the respective field of the rate,
I have maintained properly all the fica setting for the sub trasactions...like ek01 and ek02 and table te305 & tfktvo as well. Dont understand where the setting have been missed..Please let me kow if you come acrosee this kind of situation.
later i have deleted all the line items in tha same schema,and i have given only quanti01 variant
and does not have any vat related line item maintained at schema even though the same error proposed.
regards
BekMs

I think you need to ask FICA person to fix the subs, This is not billing or rate error. There must be some config missing in sub's and main. If you give another try with any other subs it should work. This will help you to double check too.
GG

Revenue Planning to cost elements

Hi,
I am Working on Project system object.
When i am trying planned revenue is added on the project, I need to find if there is a way to assign the revenue amount on the lowest WBS to a cost element. This is required for revenue amounts to appear in costing reports. CJ42 is used to add planned revenue manually.

hi anuradha,
Revenue Planning
Use
Revenue planning can be necessary when you perform results analysis on a sales order item and use a results analysis method that uses the planned revenues to calculate the results analysis data.
Features
The net value (revenue) for sales-order-related production is determined in pricing in Sales and Distribution (SD). Pricing depends on specific conditions which you maintain in Sales and Distribution.
A particular customer orders a particular quantity of a product on a particular day. The variable factors customer, product, quantity ordered, date determine the final price for the customer.
The system uses the conditions you specified to calculate the gross price at which the customer is invoiced; any discounts applying to the customer, for example; and other values such as freight charges and tax.
Pricing is controlled by a pricing procedure which is selected through the sales document type. Price elements such as prices, surcharges and discounts, freight costs and taxes are saved in Sales and Distribution as condition types. The pricing procedure determines which condition types are used and the sequence in which they are calculated in the sales order.
Condition Types
The standard system contains the following condition types that can be used in connection with unit costing, product costing, and preliminary order costing in assembly processing:
Condition Types for Pricing
Condition Type
Meaning
EK01
Cost of goods manufactured (CGM)
EK02
CGM (statistical)
EK03
Fixed CGM (statistical)
Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
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 EK03 offers the capability of transferring the fixed costs of a cost estimate into the conditions.
The costs are transferred from the cost component view Cost of goods sold into the condition type.
The above-mentioned condition types must be of category Q. Whether a condition type of category Q is only used in pricing as a statistical value or for price calculation is controlled in the pricing procedure.
The condition type is created in Customizing for Sales.
The condition type can be selected as follows:
Through the sales document type
Condition types EK01 and EK02 are specified in the CndTypLineItems field in the sales document type.
Through the requirements class
This enables you to define different condition types for different sales document items of a sales document.
Condition types EK01 or EK02 are specified in the CndTypLineItems field in the requirements class.
Condition type EK03 is specified in the CondTypLinItFix field. You can only use condition type EK03 in conjunction with the requirements class.
Planned Revenues
Revenue elements from the SD pricing procedure that are not statistical are updated as planned revenue on the sales order item that carries costs and revenues, and can be viewed in the Product Cost Controlling Information System. Sales deductions can also be assigned to revenue elements through account determination, and updated on the CO object for the sales order item.
The condition type is selected through the sales document type.
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 selected for sales document type TA (standard order). Pricing is carried out on the basis of condition type PR00. To maintain this price, choose Logistics ® Sales/distribution ® Sales ® Master data ® Prices ® Material prices and enter a material price. 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.
Actual Revenue in Product Cost by Sales Order
Use
In Product Cost by Sales Order, actual revenues are updated to the sales order item that carries costs and revenues at the time of invoicing.
Integration
You can view the actual revenues in comparison with the planned revenues and costs in the Product Cost Controlling Information System at any time.
You can settle the costs and revenues that are updated to the sales order item to a profitability segment in Profitability Analysis (CO-PA) during period-end closing for Product Cost by Sales Order. When you perform results analysis, the results analysis data are settled to CO-PA.
The processing in Product Cost by Sales Order therefore differs from the processing in Product Cost by Order or Product Cost by Period (make-to-stock production and with a valuated sales order stock without a sales order item that carries costs and revenues).
If you perform this type of product cost controlling (such as in addition to Product Cost by Sales Order), then in Product Cost by Order or Product Cost by Period the revenues from invoicing are transferred to CO-PA.
If you are using the cost-of-sales accounting in Financial Accounting (FI) and are using a valuated sales order stock, you do not need to perform results analysis in order to transfer the cost of sales to FI. The cost of sales is transferred to Financial Accounting at the point of the goods issue posting.
Prerequisites
To ensure that the revenues are displayed on the sales order item, you must create revenue accounts and possibly sales deduction accounts as primary cost elements of cost element type 11 (revenues) or 12 (sales deductions). Make the necessary settings in Customizing under Controlling ® Overhead Cost Controlling ® Cost and Revenue Element Accounting ® Master data ® Cost Elements.
To be able to settle the costs to Profitability Analysis, you must make the necessary settings in Customizing for Profitability Analysis. Make the necessary settings in Customizing under Controlling ® Profitability Analysis.
Features
Billing
Billing invoices the customer for the goods and services delivered for a sales order.
In Sales and Distribution, you create an invoice (billing document) on the basis of a reference document. In order-related billing, the reference document is the standard order or the delivery document with delivery-related billing.
The data such as prices and quantities are transferred from the previous documents into the billing documents. The price can be calculated in the following ways:
Using pricing on the basis of conditions (such as material or customer)
On the basis of the incurred costs if you want to use resource-related billing
When you enter a billing document, the system proposes a billing type depending on the reference document.
The billing type determines the following:
Which pricing procedure is used for account determination for Financial Accounting
Whether the invoices are passed immediately to Financial Accounting
Account assignment is controlled by the following parameters:
The chart of accounts
The sales organization
The account assignment group of the customer (in the Account group field in the Invoicing screen of the customer master record)
The account assignment group of the material (in the Account assignment group field in the Sales 2 view of the material master record)
The account key in the pricing procedure
thanks
karthik
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 15, 2008 3:10 PM

SD questions - very urgent

kindly send me SD Questions
[email protected]
thanks

hi
) How you will release change request in SD module? How often you release them?
2) How to create tasks. What are the maximum number of tasks you were created in you are previous project?
3) What is the difference between task and change request?
4) Is it possible to release change request, without releasing task.
5) Is functional module configuration comes under workbench request or customization request?
6) What is the tool you are using for testing purposes in your project?
7) What is the landscape you are following, which one you prefer to test functional module level changes?
8) Could you explain about sales deals?
9) Product attributes means?
10) What do you mean by drop shipment?
11) Can you explain about Higher-level item category and item usage?
12) What do you mean by condition index, how you configured in you project?
13) What do you mean by sort key(company code data in CMR) ?
14) What is the difference between ERB and ERU account keys?
15) What is the difference between general item category group and item category group ( sales org2 in MMR)?
16) What is the difference between alternative calculation type and alternative condition base value?
17) Is it possible to have different pricing procedure for sales order and invoice?
18) Consumption based planning?
19) Difference between billing and invoice?
20) How to stop PGI?
21) What do you mean by user specific parameters?
22) Explain about common distribution channels and common divisions and combined distribution channel and combined divisions, what is use?
23) How to extend material and customer to other sales areas?
24) Why does account group controls customer?
25) How can you use R/3 project management in implementation?
26) What are the Enhancements you done as a support team member and explain any two?
27) To get pricing in billing what are configuration you done in your project?
28) To extend material one plant to another plant what are the configuration you done in your project?
29) What do you mean by POD(proof of delivery) what is the use of pod? What are the con figuration you done in your project?
30) What is the significance of products under system application and products?
31) Why do you need project IMG?
32) What is the client specific data? Give two examples of client specific data?
33) What is the use of sales area?
34) How we assigned sales organization to delivering plant?
35) In system landscape where the sand box and golden box exists?
36) What are the challenges you faced in your previous implementation project?
37) What are the inter faces do you know?
38) Explain about smart forms?
39) From where system picks VAT registration number?
40) What is condition update? Can you give condition update for product, which is already given condition update?
41) What is the difference between customization and configuration?
42) While I am creating a customer in ship to party account group you have shipping and billing partner function tab pages, client wants to shift all important fields in billing like payment terms, incoterms , and tax classification into shipping tab page. He wants only shipping partner function only, how does you customize?
43) In material determination how you configure the system should propose when product A is not available then only system substitute with product B. If A is available 60% quantity. How do you do in the situation?
44) In which phase you transfer data into SAP R/3?
45) Explain EDI and its usage?
46) Sales order is created 1st November for 200 tooth pastes 100 brushes free of goods(2+1 free goods).At the time of delivery on 15th November you have shortage of brushes by 40. offer closed on 15th November . How do you solve in this scenario?
47) Can you assign one sales organization to multiple company codes? If yes how? If no why?
48) In real time what user name and password we use?
49) In real-time when we start system in first what screen we get and tell me process how to logon sap screen? I faced this question in IBM?
50) Where you worked with ABAPers?
51) How do you calculate net price on MRP based?
52) Have you worked on debugging? Explain any of one of the example?
53) How many user exists have you developed in your current project? Name at least 10 user exists you have developed and used in your current project?
54) Explain about SOP (service operating procedure) and your role in it?
55) Can you do account determination without account keys? And explain how?
56) Explain about minimum value surcharge calculated?
57) What you done business blue print, realization, final preparation, and go live support in your previous project?
58) How many SAP versions you know? And what is difference between them?
59) Without delivery can you do billing?
60) Is it possible to do delivery without shipping point?
61) Quotation has been created for product-D, 10 quantities, sales order is created with reference to the quotation, system copies 10 quantities in sales order. How do you restrict in sales order end user should not change quantities, system should not allow for changes by en user?
62) What are the business processes in your project?
63) How system picks up pricing while doing billing?
64) How SAP support to the client to know the customer requirements?
65) What are Z errors?
66) What are the training documents while giving training session for users?
67) What are the time bound deliveries?
68) What are the GAP analysis you identified in your project?
69) Can you explain about actual GI (gods issue) date and planned GI date? Can actual GI date differ from planned GI date?
70) Which module integration is required in output determination? 71) What are the two user exits you have used in your project?
72) What is the importance of release status and dynamic field check in condition table/condition record?
73) How sales document is structured?
74) What is the use of pricing date in condition type?
75) What is the use of condition type in pricing procedure determination?
76) In sales order how system does picks up plant?
77) What happens if inspection lot is rejected?
78) Can one have multiple packing for delivery?
79) What happens to the material listing/exclusion if the payer is different from the sold to party?
80) Can one create delivery with reference to the project?
81) An order item with different shipping point copied into the sales deliveries?
82) Can one specify user specific dates in delivery documents?
83) How does the rule MALA decide the picking location?
84) Why do I use condition indexes? How do you activate them?
85) How can we process out bound deliveries without shipping point?
86) Stock transfer?
87) What is the use of VPRS, EK01 and Ek02? For material cost we are using VPRS why we need EK01 and EK02?
88) When I am saving customer master (internal number range), system generating number range like 5000211,500216and 500221 instead of giving 500211,500212 and 500213.why system generating like this?
Re: int que

EK01 AND EK02

Similar Messages

Maybe you are looking for