Fixing Price of Condition type

Hi All,
When i try to change quantity in delivery condition type related to travel expense must make as fixed irrespective of changed quantity.Where this has to check.
Please help......

The Activity Price calculation depends on the planning you do for the activity. If you planned for 12 periods and the planning data is different for each period, running Plan Activity Calculation will calculate a different plan rate for the activity for each period. This can be done using KSPI and it does not matter whether you run this at the start of the 12 month period or somewhere in betwen - if the planning data stays the same, the system will calculate the same price irrespective of when you run this.
If you wish to calculate the Actual Activity rate each period, that may certainly differ each period depending on the consumption of activity, the actual costs etc. For this you HAVE to run the Actual Activity Price calculation each month using KSII. You have no option. Infact, not running the Actual Activity price calculation will result in no price update of your activity (which will inturn affect Material Ledger or Actual Cost, if active).
Hope this helps.
Cheers.

Similar Messages

How to change condition type of Markdown price?

Dear Expert,
When I active markdown price, the system create price with condition type VKP0 (same as article regular retail price). Now I want system create price with other condition type, for example ZXXX.
Could you give any help or tips? Thank you very much!!
Robin Hu

Xiaowei Hu
You solved the problem?
Tks
Filipe Borges

Selecting the best Price for a condition type but only for some customers

Hi All,
I have this situation where we have condition type ZPPR (COPY OF PR00) with 5-6 Condtion tables.
in Access sequence for ZPPR, we have Exclusion Indicator set for all the conditiona tables so if first price is found, it doesn't search for others.
Now I have a requirement that we should search for all the condition records and choose the lowest price. But this should happen for only a certain type of customers and not for everybody.
Spefically we have:
1. Contract Price
2. Plant/Material price
Normally, if contract price is found, it doesn't look for Plant/Mat price but we want to offer our customers(some of them) an option where they could choose the lower of the two price. We set both the prices every day based on some inputs.
Regards,
Luke
Edited by: Lukesh Singla on Dec 21, 2011 8:49 PM

Hi Luke,
We have multiple option for this implementation:
Option 1: If possible based on access sequence. Not sure if this is suitable considering you mentioned that ZPPR has 5-6 access sequence.
1) Store Contract price in condition type ZPPR and store Plant / Material Price in new condition type say, ZPPX.
2) Have separate pricing procedure and determine them based on customer type. In first pricing process XXXX01, configure Condition exclusion with the setting that ZPPX should be deactivated if ZPPR is present, condition exclusion procedure D (exclusive) . In second pricing procedure XXXX02, configure condition exclusion with the setting that compare ZPPX and ZPPR and activate best condition type for the customer by using condition exclusion procedure C (Best condition between two exclusion groups ).
Option 2:
1) Copy ZPPR and its access sequence to a new condition type and access sequence say ZPPX without checking exclusion indicator in the access sequence. In the condition type control for condition type ZPPX >> Master data section >> Reference Condition type = ZPPR so that master data records need not be duplicated.
2a) Assign the current procedure to the set of customers which should get the first price. Create a new procedure with condition type ZPPX instead of ZPPR keeping other parameters similar and assign the new procedure to other set of customers who should get the best price.
OR
2b) if 2a is difficult in terms of future maintenance, add condition type ZPPX in the same procedure and create 2 new pricing requirement validating the customer segments and assign them to respective condition type in procedure ZPPR and ZPPX.
3) Maintain condition exclusion for condition type ZPPX with B ( Best condition within Condition type).
Hopefully it helps. Let me know if you need any other help in implementation of the solution.
Regards,
Naveen Aggarwal

Condition Type NAVS not determined for Goods PO

Hi all,
I am working on SRM 5.0 and R/3 4.6C.The problem im facing is for the tax condition determination for PO for Goods type which replicated from SRM to PO .
In case of Service PO,the conditions are determined correctly and can be seen in the PO print out.However In case of a goods PO,if i goto conditions tab in ME23N for the PO,the conditions (NAVs) are not determined as well as they cant be seen in PO print .
The config on R/3 side is Correct as in case of manual PO(PO created directly in R/3),the conditions are determined correctly.
Now when i debuuged the BAPi "BAPi_PO_CREATe1",i observed the following:
If i chnage the field PO_PRICE in the table POITEM to "1",then conditions are determined corretcly for the PO.However by dfault,the value for this field comes to "2".
This field is nothing but indicator of the price i.e. 1 for Gross and 2 for Net.
Can anybody explain me the link between this price and condition types determined in PO.
Thanks.

Check out SAP Note 580225 - Purchasing BAPIs: Conditions and pricing
Hope it helps

Restrict referance of pricing and condition type from latest PO.

Hi Experts,
I am creating Purchase order and at the time of creation of purchase order system is copying prices and condition types from latest PO.
Which is not desirable to our business process, when I dig out I found out that in standard SAP system
The system looks at pricing in the hierarchy order as below:
u2022     Contracts/scheduling agreement
u2022     Condition records
u2022     Info Records
u2022     Last purchase document
So can some one help me with information how to restrict system to follow this referance of pricing.
I want to enter price as well as condition type manualy every time user create a purchasing document.
Also i want to know can it be restricted specificaly for few document type.
Thanks
Best Regards
Ritesh

Hi sir
can we try this
Use the user parameter EVO to indicate that no price adoption from last Purchase Order must take place:
IMG: MM -> Purchasing -> Environment data -> Default values for Buyers
-> Setting for Default values.
Select or setup a default value and on the "price adoption" tab you may choose how copying of conditions from last purchase order must behave. Select "Do not copy".
Then assign this default value to the user, using the EVO parameter.
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/price-to-flow-from-info-record-at-plant-level-813066]
[Re: new info record with same details as archive one.;
check following notes it may helfull
569885 About Info Record Update indicator (EKPO-SPINF)
13127 Update in info record from PO, quotation, contract
430543 FAQ: Purchasing info record
675523
456691
Regards
Kailas ugale

Condition types EDI1 & EDI2

How are Condition types EDI1 & EDI2 used?

dear venkat
EDI1 AND EDI2 (Customer expected price):
In normal business process, business charges certain price for particular material but customer expects certain price. Customer expected price can be entered manually or through EDI (Electronic Data Interchange). Someone in the business may accept or reject customer expected price. So that system has to block the billing document by considering sales document as a incomplete one so that the document can be released by using transaction code V.25 by accepting or rejecting customer expecting price.
Condition type EDI 1 is used to compare the net price for each item whereas condition type EDI2 is used to compare the overall item value (net price * quantity)
For EDI1, calculation is = 8; for EDI2, calculation is = 8 make it as a manual/statistical.
In V/08, include EDI1 and EDI2 as last steps.
Go to VA01, raise the sales order
Go to item condition screen, now include EDI1 as 40/- and EDI2 as 40/-
Raise delivery and invoice. System block invoice
Now go to V.25 and click on release and now raise the invoice
The customer expected price is differ from the automatically determined price or value by more than the maximum difference allowed then the system will look this order as incomplete when it is saved .
The blocked sales order should be released by concern person through work list traction code: V.25
     logistics
     S d
     sales
     Information. System
     Work listV.25 release customer expected price.
Select the sales order click on release, save and exit.
rewards pls
siva

Sum of Condition types

Hi,
I have two condtions 1. for cost and 2. other for markup
cost and markup are statastical condtiions. tehre is an other condition which is sum of cost and markup. when i am creating the sales order the condition is added at KWETR and not KBETR. Users would like to see the price per unit. what am i missing.
eg: cost is
order qauntity 10
Pricing
VPRS 10 EA 100
Markup1 ea 10
Selling price 11 x 10 =110
But 11 is coming as zero and only 110 is appearing.
Thanks,

Kindly check whether the New Condition Type ( Sum of Cost and Markup ) in the Pricing Procedure has the Step number of Cost Price & Markup Condition Type in From & To Column.
Best Regards,
Ankur

Condition types from SRM to backend

Hi All,
When accepted bid (complex prices with condition types) is converted to PO, in backend PO is created with net price only. Is there a way to move the condition types also to backend. Can we use any Badi in this case?
Thanks in advance.
Will reward full points for the reply.
Venu

Hi
Either you need to maintain the Condition types locally in SRM system by maintaining Z tables and then create your own logic for pricing in SRM. I guess, this will be much more complex activity.
I know there is some issues, but, Anyways, you have to go for this approach.
You need to go for custom fields and then get the data passed back over to R/3 PO using any of the BADIs
BBP_CREATE_PO_BACK / BBP_TARGET_OBJECTS / BBP_TARGET_OBJTYPE / BBP_CREATE_PO_NEW
in SE18 Transaction.
Refer OSS note - 672960 and 485891 for creating customer fields.
Also, incase this don't suits your requiremnents, Please raise an OSS message with SAP.
Regards
- Atul

Condition type EDI1 in PO: Condition ignored (requirement 053 not fulfilled)

Hi,
I am trying to change price in condition type EDI1 of a line item, but I am getting following error:
PO has AB confirmation and GR also has been done. Still getting this error. Please suggest how to rectify this.
Thanks and Regards,
D. Krishna Bharadwaj.

Hi,
The condition types EDI1 and EDI2 are used when the vendor send the price change and is accepted automatically. Refer the note: 456127 - FAQ: Electronic Data Interchange (EDI) in purchasing Question number 14.
Regards,
AKPT

Is there a way to fix the exchange rate of PO item condition type ?

Hello all,
We have an agreed selling price in RMB from the supplier and the export rate(RMB to USD) is given by them according to delivery date. But we pay in USD.   Thus PO header is USD and using M rate but PO price condition type in PO item is RMB -> then convert to USD and sum up into gross price. We want to control the way RMB is converted to USD in the item level.
e.g. PO order currency is USD, PO header exchange rate is a fixed rate input by user
        (hedge rate USD -> Local company currency)
PO item 1      agreed PO price is 100 RMB -> PO item condition's rate is 100 RMB per pc
                     -> export rate RMB to USD fixed at 8 -> 100 / 8 USD
PO item 2      agreed PO price is 200 RMB -> PO item condition's rate is 200 RMB per pc
                      at export rate -> 200 / 8 USD
Total PO value in USD = 300 RMB / 8      (we don't want it to convert 300 RMB using M rate)
Appreciate if anyone has a solution for this similar case.

KiltedTim wrote:
The only way to do so and preserve your warranty is a replacement from Apple. US$199 without AppleCare+, US$49 with. If it doesn't affect the functionality, though, they may not give you that option.
It's not that big of a deal. I'm just seeing if anyone knows how to bend it back straight from experience or imagination.

Price was not picking from the Condition type for Item Category 'P' in PO

Hi Experts,
I Created one condition type based on Material and WBS which price was fixed based on this
I used the Purchase Order having Item Category P or Q Price should pick from the condition type where I mapped the WBS Element and Material.
The Net price was not picking from the Condition type Record. Why? What should be the Problem?
Whether my logic is correct or not?

The Scenario: I want to fix the Material price base on each WBS Element for a Project. For each WBS Element the Price will be various for same material.
Please help on this.
Thanks
Muthukumar

Hi,
In standard configuration you cannot set item delivery date as a pricing data.
Maybe you shoud look at SAP enchancement - in dedicated structures you can pass additional item data (structure KOKMP).
IMG link:
Materials Management -> Purchasing -> Conditions -> Define Price Determination Process -> System Enhancements
hope it helps.
regards,
wojciech

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Condition type fix value

hi all
i want to make one condition type in which i want to feed one fix amount.....
suppose PO is of 100 quanity
and that condition is having value 100 Rs.
and if i am doin GR of 10 then i want that condition value 100 instead of 10....
means for every partial GR i need this value as 100....
how to maintain condition type in this case???
Anin

Hi Jazz
Firstly in GR u'll not get a value field..
Can you be more specific
Regards
Jagadish

Two prices for one material in sales order according condition type

Hi,
I configure the condition type according to following condition record:
Plant/ Sales Organization/ Distribution channel/ Material / Customer
(because system should calculate two prices for one material in two plants)
In the sales order screen, when user firstly select material , quantity, plant , system calculate the related price correctly but if user select the material and quantity and enter and after that select the plant, system will show the error message in pricing procedure and to have a price for material, user should update the price in the price condition in sales order.
It is so difficult for user to update one by one, because there are several sales orders which need to update.
Is it any way to solve this problem?
Thanks,

> In the sales order screen, when user firstly select material , quantity, plant , system calculate the related price correctly but if user select the material and quantity and enter and after that select the plant, system will show the error message in pricing
Hi,
Why to let the user press Enter button before entering plant value Obviously, system will give error, because it doesnt get all the required value based on which you have maintained condition records.
Ask the user to enter all the value at item level otherwise you will have go for the option that you are doing currently.
It is said prevention is better than cure
Hope you get some inputs
regards,
Sagar

Determination of Base price condition type depending on Item Category

Dear All,
The requirement I have is as stated below:
There are two materials A and B that are individually sellable materials. But during a specific time period the company decides to give a scheme where in Material B is given as free when a particular quantity of material A is purchased. Irrespective of the scheme, material B can also be individually purchased during the scheme period.
Now in the former scenario where material B goes free with material A in the same order, the base price of material B should not go to revenue G/L but to a different G/L called Scheme G/L. To counter this scheme G/l there is another counter G/L into which 100% discount on base price to material B goes.
In the latter case, if material B is sold individually, then the base price should go to Revenue G/L and not scheme G/L and the 100% discount is not applicable.
Can you please guide me on how to configure this.
The approach I have taken is as follows:
The condition types for base price are ZBPR and ZBP1(reference condition type of ZBPR)
Item Categories to be considered: ZTAN and ZTNN (for material B going as free during the scheme)
The requirement is such that, whenever the item category for a particular material is ZTAN, the condition type to be picked must be ZBPR while the condition type ZBP1 must be deactivated.
Similarly, if the item category for the line item is ZTNN, then the condition type to be picked must be ZBP1 and the condition type ZBPR must be deactivated

Dear All,
I have fulfilled this by doing rev acct determination in vkoa using item category and moving it up the order. Also I used a requirement in v/08 for 100% discount on free material.
This has resolved my issue and i am now closing this thread.
Thanks and Regards,
Rohan
Edited by: Lakshmipathi on Apr 2, 2011 10:53 AM
Since you have arrived at a solution, please change the status of the thread to "Answered"

Fixing Price of Condition type

Similar Messages

Maybe you are looking for