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.

Similar Messages

Stastical Condition Type is not working in Purchase Order

Hi All,
I created a pricing procedure and Bank charges are created as a condition type which is stastical. I assigned a account Key and Accural key for the same condition type. We activated Purchase Account Management
Purchase order is raised with USD 100, ank charges(%) which will be calculated on Base price, for example Bank charges is 1% then bank charges will be USD1.
I want these bank charges should not be added to the material cost. But when we are doing GR accounting entries as below.
Stock account 101     +
GR/IR     100     -
Pur acc     100     +
Pur Offset     101     -
Bank chargesAccount key     10 +
Accural     10     -
In the above Bank Charges are added to Stock account which is not required.
Even though I created the Bank charges Condition type as Statical still the value is adding to the stock account.
Thanks and Regards
durga

Hi Durga,
Most importantly whenever we create a condition type with statistical check box it means that value will not be included in Net price calculation this is the only purpose of statistical check box.(Like any freight charges it will go to your stock a/c even though statistical check box is there in your Pricing procedure)
When you create condition type for any charges with Cond.category B Delivery costs and Accrual check box in M/06 by default it will go to stock account, but you can restrict that by using a functionality
Check this link for complete process
http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount

Condition type for deduction in service purchase order

Hi All,
Our client has scenario where in transport service Purchase order, client wants to deduct some part of amount as a security fund.
E.g client takes transport service from vendor amounting Rs. 1000 and client deducts Rs. 10 as a security fund so payment to vendor is Rs. 990. This deduction amount should go to separate GL.
Kindly let me know how can we map this scenario? I guess we can do this with the help of condition type but dont know from where to start and what will be the nature of condition type.
Thanks in advance.
Regards,
Nisha.

Hi
What client is going to do with security deposit? Do they settle over a period of time?
Based on that you can do the config setting.
Case 1) Retaining of security deposit.
If client is not paying back and wants to keep the security deposit. They Wants to have track record of the same. Then you can use Z condition type by copying R002 discount using M/06 and assign GL in OBYC for that condition type.
Case 2) paying back security:
Create Z condition type by copying any freight condition and assign GL in OBYC
While creating PO use condition type.
While repayment of security deposit FI will use same GL as Db and vendor account as Cr using F-44.
Rgs

Condition Type Value Not appearing in Purchase Order

Dear All,
I have created a condition type and assigned it to a Pricing Procedure. Correct value is being captured in <b>Scheduling Agreements</b> but in <b>Purchase Orders</b> the Condition value is being captured as zero (All fields for SA and PO have same values). I have already assigned Correct Pricing Procedure to Purchasing Docs (As correct PP is being captured in SA and PO). Please Assist even if you have a slight idea.
Regards,
Sudhanshu

Hi Sukdev,
Have you checked the respective pricing procedure for From and To reference step maintained against the condition type ZSUR?
Regards,
T.R.S.Praveen

Condition Type MVK0 & MVK1 and How it is linked with SD pricing ?

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.
Regards,
Selvakumar. M

CLOSED

Dynamic taxes and charges of Purchase Order

Hi
We have the following issues in purchase order:
The discounts offered by vendors vary from PO to PO. Sometimes the discounts are applicable on basic price and in some cases it is applicable on the price after some charges/taxes. This is not feasible in the current configuration, as we are unable to overrule the pricing conditions and the order of computation of discounts/taxes.
In some cases, we get an adhoc discount of an absolute value, which is not feasible to enter in the PO.
The excise modvat received from some traders is in absolute value and not in percentage. There is no provision to record the same as well.
Please let me know a feasible solution for this, as the charges, taxes and discounts vary from order to order and we would like to have the flexibility to define them physically in the order in which they are applicable (both in terms of percentage and absolute value).
There are cases where we would like to enter the percentage and the amount on which that rate needs to be applied. SAP's pricing condition automatically computes this. We need a solution for this as well.
Thanks in advance.
Shaji Varghese

Hi Shaji,
I would advise you to do this step by step. If you want to design the complete priciing procedure for ll cases immediately , you have to be experienced in pricing.
E.g. in your case : start with the complete manual solution ( and add automation afterwards if possible/desirable )
In the most basic scenario, you need something like
-Base price
-Discounts % Before
-Discounts Value
-Discount % After
-Tax1 base
-Tax1 %
-Tax1 value ( calculated )
-Tax2 base
-Tax2 %
-Tax2 value ( calculated )
-Total tax ( calculated )
In you create manual price conditons for all ( except tax value ), this should very fairly straightforward.
If you need a base for the % discount that is not available in the above, you add a condition type ( statistical ) and manually input the base specificially for the discount.
As I said, if it works, you can start to add more automation where possible ( e.g. determine a default for the tax bases and only update manually when necessary ). To do this create a price condition record that is always found by the system ( e.g. with value 0 ), but mark it as manual input takes priority. Thne use a condition base value formula to default the condition type. If you change it anyway, you changed value will be used
( this also has the advantage that the confition type 'appears' immediatly on the screen and the user only needs to fill, instead of adding the condition type itself also manually )
SAP pricing is VERY flexible and the same requirement can be implemented in many ways. It really depends on the complete picture to choose,
rgds
Dirk

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

I need output type NEU automaticaly for create purchase order document type

Dear Experts,
I need output type NEU automaticaly for create purchase order document type NB
when transaction code MN04, I am doing the following:
(1) I selected the third option Purchasing Output determination: Document type
(2) I selected the output type NEU.
(3) In condition records in document type , i have chosen NB.
(4) In name its automatically coming as Purchase requisition
Please suggest how Purchase Order NB will come

Hi,
Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
Now try to creating Purchase Order & you will have default message type NEU.
Regards,
Biju K

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

Rebate Condition Type cannot be reflected in sales order?

Hi Guru:
It seemed to be a issue? I set up the rebate agreement and ran the vbof successfully regarding this condition type rebate,and the retroactive billing also can view its rebate condition type as well as the accruals,and I believe the rebate settlement had been run too,credit memo to customer will be aslo routed to accounting side for sure,but I failed to see the rebate condition type and accrual value in the sales order based upon the retroactive all billings,please advise what I should do,thanks.

Hi Klaas,
If I remember well, in the standard price determination there is a conditional formula that only shows rebate conditions in the invoice, therefore you should not see rebate conditions in the sales order.
That is standard functionality.
For a Customer I took out the formula condition in the pricing so he could actually see the rebate condition in the sales order, the reason was to had access to this information before end of month invoicing. The problem is that in case of changes in rebate agreement or in case of retrospective agreements the rebate condition is only updated in the invoice, not in the sales order.
Best Regards,
Franck

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!

Create additional field in sales order item and copy to purchase order item

Dear SAP Gurus,
I am hoping that someone could help me by providing me with how to implement the following 2 requirements in the SD order and in the purchase order.
1. I am wanting to add a custom field to the SD sales order item copying a value from the vendor customer master.
2. I then want to add a custom field to the purchase order item and copy the value from my custom field in 1. to this new custom field..
Can you please advise how I would go about implementing the above requirements? I am assuming that there are exits to allow me to implement these 2 requirements.
Many thanks
Henry

Hi,
For the first requirement you can use the USEREXIT_MOVE_FIELD_TO_VBAP in report MV45AFZZ.
For the second, as I think that you will create a RFQ you can try to use the enhancement MEREQ001.
Regards,
Eduardo

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

Similar Messages

Maybe you are looking for