Condition type EK02 and VPRS.

Hi Everyone,
In our pricing procedure there are two condition types EK02 and VPRS at header level. The profit margin we are getting is in negative. Can any one through some light about the use of EK02 and VPRS condition types and how system picks the values for the condition type EK02 ?
Thanks
Raksha.

Hi,
VPRS condition type is a Statistical Condition Type that returns the cost price of material from material master. It is basically used for comparison purpose. If you want to add it in the pricing procedure, make sure you add it at the last i.e. after adding of all the condition types.
EK02 is also a Statistical Condition Type and used for comparison purpose.
regards,
Sagar

Similar Messages

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

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 type EK02 In pricing procedure

I'm having a problem with theis condition type as follows:
Create sales order
Add material A to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
Delete material A from line item
Add material B to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
I'm not sure where this value is coming from at this point. Can anyone point in the right direction?
Thanks, Mark

Hi mark
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
It has the condition category Q ( costing )
Now when you go to VOV8 , in the condition type field you can see the option EK02. because this condition type when used will be flowing to the controlling .That is the reason we assign EK02 to our sales doc type
Check in V/06 and select EK02 and go to its condition type details and check the calculation type field wheather it is in fixed value or not
Regards
Srinath

Condition type SKTO and SKTV

Hi all,
I wanna ask how the system determine whether use condition type SKTV or SKTO. I know the value is based on term of payment, the case is i do the same think with term of payment in 2 different client, but the result is different, one using condition type SKTV and SKTO for the other one. how is it work? can anybody help me
Thanks
Regard,
Hendry

Hi,
SKTV calculates cash discount before tax
SKTO calculates cash discount after tax
the formulae and configuration are the same.
difference is the requirement in pricing procedure. SKTV is picked before tax, while SKTO is after tax.
you can pay attention to the requirement in both pricing procedures in different clients...
Thanks!

Condition type PB00 and PBXX, coming in the same PO Item

Hi,
In the PO (created with reference to Outline Agreement), condition types PB00 and PBXX are coming in the same line item.
In the PO output, the PB00 value is also showing up and PBXX value is also showing up. User entered PBXX value as 350000 dollars which is right, however system is picking 1.2 million dollar of PB00 from outline agreement which is not intended here. As a result of that the output going to Vendor is exceeding more than 1.2 million dollar instead of 350,000 dollars. I cannot change or delete any othe condition types.THis is a production problem.
Has anyone faced this problem. I appreciate your reply in advance.
Thanks,

Well, thanks Saurav and Prabhakaran, however the problem still stays.
The contract is created for services (1 lot), so the dollar amount can vary depending upon the service rendered by the consultant.
That mean user will only enter the service amount.
Saurav, system should not copy down PB00, it should come by itself when user enters the specific amount. And it comes from contract. PBXX should only appear if there is no PB00 maintained in the contract. This is not the case. The service amount is maintained in the contract. Also, I don't think that PBXX and PB00 should come in one line item together as normal system behaviour & as a normal business process too. Moreover, it is not happeniing in the other two line items - line item 20 and line item 30 are fine. The pricing analysis shows both the conditions as found - PB00 and PBXX, so I could not take any clue from analysis too.
Prabhakaran, system is only behaving incorrectly for line item 10. It is behaving as expected (good ) for other line items and other PO's. So, we cannot touch the pricing procedure as that will affect other line items.
Regards

CIN condition type J1CV and JCDB not appearing in PO history

The 2 above mentioned condition types are appearing in PO conditions tab.
however, after GR was posted, the amount from J1CV and JCDB condition types was not showing up in the PO history tab.
and these 2 condition types did not have their statistic box ticked so by right it should be appearing.
however there's no problem with other condition types like JCV1, JECV, JEDB...etc
anyone can advice?

Hi,
Condition types J1CV and JCDB are stand for what pricing conditions?
There may be any causes for above.
Option-1----- >JCDB (IN Basic customs) is used for Basic Custom duty and this may be added to inventory account of material, so no separate entry in GR document.
Option-2----- >May be J1CV and JCDB (IN Basic customs) condition types have no value and during PO creation, this condition types may be deleted.
Option-3----- > Check J1CV and JCDB (IN Basic customs) condition types are there in MM Calculation Schema.
Regards,
Biju K

Condition types PB00 and PBXX

Dear Experts,
1) Can anybody please explain that can we use Condition type PB00 in number of Pricing procedures. like i have three pricing procedures, local purchase, Import Purchase,
External Service Pricing procedure.
what is recommend, eiether to use same one (PB00) or maintain seperate condition type for each Pricing procedure ?
2) What is the difference between Condition type PB00 and PBXX ?
Waiting for your valuable reply
Thanks in Advance

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

What is the difference between Condition Type PB00 and PBXX

Hallow all,
Can anybody please explain, What is the Difference between Condition type PB00 and PBXX in Materials Management Pricing?
And also please explain control or Application of both on Price determination ??
Thanks in Advance !!!!!

Hi,
PB00 condition type is used for automatic pricing in PO
PBXX condition type is used for manual pricing in PO
In Pricing access sequence play a vital role . If you need pricing automatic in the PO, you have use of Access Sequences and Schema Group of Vendor.You can see the difference in both standard condition type PB00 and PBXX, where as PB00 is assigned to Access sequence(0002)but in case of PBXX no access sequense assigned.
Regards,
Biju K

Condition type EDI1 and EDI2

Dear all,
we have to a requisition that we will receive confirmations of order (ORDRSP) from our suppliers in the future.
In OSS note 456127 (FAQ EDI MM) question 14 it says that prices will only overtaken in the purchase order,
if the condition types EDI1 and EDI2 are part of the calculation schema.
In our calculation schema we do not use EDI1 and EDI2 so far.
I can not find a manual that says what to do.
RM0000 does not contain these two condition types either.
In which way do we have to add EDI1 and EDI2 to our calculation schema?
Thank you for your help in advance!

Check these Schemas
RM2000 - STO scenarios
RMMP00 - Market Price Scenarios
Define Calculation Schema
In this step, you define the calculation schemas.
In the MM area, a calculation schema - a framework of steps used to calculate or determine something - is used among other things to calculate costs, prices, period-end rebates, and taxes.
Note
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.
In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains.
Standard settings
The following calculation schemas are predefined in the standard system. You should not change these schemas.
RM0000 and RM1000
Control the price determination process in POs, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in purchasing document headers with time-dependent conditions (e.g. contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with time-dependent conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price which can be entered for each material.
RM2000
Controls the delivery cost determination process in stock transport orders and stock transport scheduling agreements.
Note
In the calculation schemas RM0000, RM1000, RM0001, and RM1001, the field "Subtotal" must contain the following values in the following lines:
Gross value: 9
Effective value: S
If the interim total 'S' is not set, the PO values cannot be updated in the Purchasing Information System (PURCHIS).
Actions
1. Check to what extent you can use the calculation schemas provided in the standard SAP System.
2. Create new calculation schemas by copying similar existing ones and changing them.
Enter a key (length max. six characters) for the schema you wish to create, and a descriptive text.
For each schema, specify the condition types in the order of their usage, and maintain the relevant data.

Condition type PB00 and PBXX

Dear Gurus,
When system pick condition type PB00 and when it picks PBXX ?
I have made one scheduling agreement having 20 line items. For some line items it has picked condition type PB00 and for rest it has picked PBXX. Why system is picking PB00 for some line items and PBXX for rest ?

Hi,
If you create an Info Record manually or automatically the gross price is entered or adopted is assigned to condition type PB00.
When PO is created with reference to a contract or a quotation a vendor`s gross price for a material is adopted from the Info Record condition. (or where appropriate from PO price history) as default value for condition type PB00.
If no valid info. record condition exists and no order price history can be found, the R/3 system is not able to suggest a price and requires the manual entry of price and a manual entry of net price. The manually entered price is assigned to the condition type PBXX.
These two condition type for the gross price must be available in the calculation schema assigned to the standard PO. In the standard system these are the condition type PO00 and PBXX. An access sequence is assigned to PB00 so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX . PB00 must come before PBXX in the calculation schema. You can also use your own comparable condition type in place of PB00 and PBXX.
At the time a PO is created, is the system finds a condition record belonging to PB00 with valid condition, PBXX is irrelevant. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).
Hope this lengthy answer clears your doubt(s)!!
Reetesh

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 MVK0 and MVK1 in Purchase order

Hi Experts,
In my purchase order, line item for an article (material) there is a condition type MVK0 (Sales Price inc. Tax) and MVK1 ( Sales price excl tax) which appears in Red in IS-Retail server.
The pricing analysis says that the condition has been found without the condition record.
The details for condition type MVK1 is
Condition class:- Prices (B), Calc type:- C (QTY),
Condition category J ( Customer Expected price)
There is no access sequence for this condition type.
Manual entries D Not possible to process manually
The details for condition type MVK1 is
Cond. class B Prices
Calculat.type C Quantity
Cond.category W Expected sales price (including tax)
Access Sequence: Not maintained
Manual entries D Not possible to process manually
I wish to know how to populate values for these condition type.
Also could someone throw light on the condition category Wand J.
what is the importance of MVK0 & MVK1 condition types and How it is linked with SD pricing?
if we want this condition types values in PO what settings needs to be done?
Any Input is highly appreciated.
thanks in advance

How did you resolve this problem? I am currently facing the same issue.

Shipment cost condition types - Insurance and loading/picking

Hello Experts!
I am trying to create a pricing procedure for shipment containing :
-One pricing condition for insurance (the insurance is a % of the total value of the transported goods (value of the delivery)).
-One pricing condition for loading. When the loading is done by the forwarding agent, we have to pay 4 euros/ parcel loaded.
Can you please help me to build those two conditions please?
Thank you!

Dear Pegasus
As the insurance would be fixed percentage, you can very well create a new condition type in V/06 say the name as ZINS and maintain the required fields with access sequence (you can retain the same condition type as your access sequence in V/06. Now go to V/07, select this ZINS and maintain the required combination. It may be for customer or Customer / Material. Now go to VK11, input the condition type and maintain the percentage and save. Create a sale order and see whether the insurance percentage calculates correctly.
With regard to loading charges, what do you mean by parcel ?? I mean, how it is packed ?? That is one parcel contains how many quantities ?? If this is fixed, then you can create a condition record for this also as explained above. Alternatively, you can maintain a header condition type for this and include the same in billing manually. While generating invoice, you know how many parcels are loaded and calculate the total value and input the same in condition tab at header level. Once you input this tab, click on Activate button at the bottom screen in condition tab so that the value will be equally allocated to all line items.
thanks
G. Lakshmipathi

Condition types MWSI and MWVO for TAXES

Hi,
I am trying to create the new condition types MWSI, MWVO and accounting keys SIV, SIO for new tax keys (TAXES) for the report RFIDESM340. I didnu2019t find any instruction about the parameters behind MWS and MWVO.
Can someone advise me on this?
Thanks and Regards,
Detlef
Edited by: Detlef Weiss on Mar 15, 2010 1:06 PM

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

Condition type EK02 and VPRS.

Similar Messages

Maybe you are looking for