PO Price Variance Tolerance
Hi Experts,
Can we do "Set Tolerance Limits for Price Variance" by document type? I saw the standard config is by company code.
Thanks
John K.
hi,
what is your requirement. if you set "Set Tolerance Limits for Price Variance" here it is company code level not document type or PO level you can set if you require at company code level.you can set tolerance limit at PO level in delivery tab at item level.
Regards,
mukesh
Similar Messages
-
Set Tolerance Limits for Price Variance when PO-based Purch.Requisition
We must garanty that Price from Purch.Requisition will be the same at PO.
IF some variance occur a error messag must be sent to user and PO could not be saved.
I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
Reading the help of customizing it mean the system consists what we need..
I have created tolerance limit NB, and set limits for all checks as 0,01.
When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
The help mention that after create tolerance limit we must set this tolerance by document type..but I didnt find this field at customzing
Does anyone can help me ?
See the help on customizing below
Set Tolerance Limits for Price Variance
In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
Note
You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
Requirements
The tolerance key must be defined in step Define Tolerance Key.
Activities
1. Define tolerance limits for each tolerance key.
2. Define the tolerance key in step Define Document Types.
Thx and best regards,
AleHI
SET TOLERANCE LIMITS FOR PURCHASE REQUISITION UNDER THE DEFINE DOCUMENTS FOR PR
AFTER SETTING TOLERANCE LIMITS WHILE CREATING PURCHASE U WILL GET BASED ON TOLERANCE LIMITS THERE FOUR WAYS TO SET TOLERANCE LITS
1
ABSOLUTE VALUE
2
PERCANTAGE
3
TOTAL PO VALUE
4
QUANITY BASED PRICE PER UNIT
OK BYE -
Set Tolerance Limits for Price Variance for PR missing from SPRO
I'm looking into setting up tolerance limits for price variance at the PR level. But when i navigate here:
SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance
I'm not seeing that available in SPRO. It's available for PO's but not PR's. We want to be able to set tolerances on the PR to be applied to the PO for non stock items (material master). Please adviseHi,
There is no standard configuration option to set the tolerance limit at PR level. You may set the tolerance limit for PO and control the price change. If you want the same functionality at PR level, then you have to go for development. Please check whether the BAdI: ME_PROCESS_REQ_CUST can fulfill your requirement. You may set the tolerance limit in OLME - PO - Set Tolerance Limits for Price Variance itself and write the logic in the BAdI to check the price variance in PR based on the same configuration (table T169G and similar).
You may check the similar thread: PR VS PO Price Tolerance
Regards,
AKPT -
Price & Quantity Variance / Tolerance
Hi Experts,
read a few threads on IV, but not completely clear as there were many varied answers.
My question:
a) During IV, say my Invoice price is more than PO price (loss to company), in MIRO Invoice would be blocked.
Say my Invoice price is less than PO price (profit for company), in MIRO would the Invoice still be blocked?
b) what is upper and lower limit variance or tolerance?
Also require a brief example on tolerance limits.
Appreciate the explanation with an example, as I understand it better than definitions given.
Aditya.Hi,
Tolerence limit is 1. Price varience
2. Qty Varience
Price variance:
Lower limit: 1. % ( if you maintain the % , then will check the PO price > Invoice price variances if the value more then the % then it get blocked.
Upper limit: PO price < Invoice price variances if the value more then the % then it get blocked.
Absolute:
Lower value: You give the absolute value. if the diference from PO to IV more then that say PO value 100 & IV value -80..
your absolute value is 10 . then the invoice get blocked.
Upper value: You give the absolute value. if the diference from PO to IV more then that say PO value 100 & IV value 130..
your absolute value is 20 . then the invoice get blocked.
Hope ths willhelp
SAM -
Tolerance Check for Price Variance is not working
Hello,
In SRM 5.0 IMS we have configured a tolerance group with tolerance Key PP to allow Price Variance while Invoice entry.
We have assigned this tolerance group to the user via attribute TOG in the organizational structure (Transaction Code: PPOMA_BBP)
The user to whom this tolerance group is assigned is logged on into the system and created an invoice in the system with the higher amount as compare to the PO. This difference of price is very well within the tolerance limit configured in the system, but still it gives the following errors:
Average price too high: Tolerance limit of 0.00 and USD exceeded (Item 1)
Value too high (tolerance limit of 0.00 and USD exceeded) (Item 1)
Its not checking the tolerance limit assigned to the user through tolerance group.
But the same works when we assign this to vendor group, but this we don't want.
We want the system to check the tolerance group assigned to the user.
Please suggest the solution to reslove the above errors.
Thanks
SarabjeetHi,
Priority of tolerances is PO tolerance limit, TOG tolerance grp. for User, TOG tolerance grp. for Vendor (if user not logged on). Even absolute tolerance limit always has priority over percentage limit.
In your case, you need to check PO tolerance first then TOG for user.
regards,
rahul -
LIV tolerance for price variance from PO to LIV
Hi Friends,
I am finding difficulty in setting up the tolerance key for price variance from PO value to invoice value. Suppose if PO price is $100 then system should allow upto $105 with out blocking means with percentage of 5%. If it exceeds 5% system should block the invoice.
Please suggest the tolerance key to use and if any other settings required.
Thanks...
Best RegardsHi,
Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
===================
Set Tolerance Limits
In this step, you specify the tolerance limits for each tolerance key
for each company code.
When processing an invoice, the R/3 System checks each item for
variances between the invoice and the purchase order or goods receipt.
The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
o AN: Amount for item without order reference
If you activate the item amount check, the system checks every line
item in an invoice with no order reference against the absolute
upper limit defined.
o AP: Amount for item with order reference
If you activate the item amount check, the system checks specific
line items in an invoice with order reference against the absolute
upper limit defined. Which invoice items are checked depends on how
you configure the item amount check.
o BD: Form small differences automatically
The system checks the balance of the invoice against the absolute
upper limit defined. If the upper limit is not exceeded, the system
automatically creates a posting line called Expense/Income from
Small Differences, making the balance zero and allowing the system
to post the document.
o BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units : quantity
invoiced in order units and quantity ordered in order price quantity
units : quantity ordered in order units. The system compares the
variance with the upper and lower percentage tolerance limits.
o BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units: quantity
invoiced in order units and goods receipt quantity in order price
quantity units : goods receipt quantity in order units. The system
compares the variance with the upper and lower percentage limits
defined.
o DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods
receipt has already been posted, the system multiplies the net order
price by (quantity invoiced - (total quantity delivered - total
quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net
order price by (quantity invoiced - (quantity ordered - total
quantity invoiced)).
The system compares the outcome with the absolute upper and lower
limits defined.
This allows relatively high quantity variances for invoice items for
small amounts, but only small quantity variances for invoice items
for larger amounts.
You can also configure percentage limits for the quantity variance
check. In this case, the system calculates the percentage variance
from the expected quantity, irrespective of the order price, and
compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned
delivery costs.
o DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet
been posted, the system multiplies the net order price by (quantity
invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper
tolerance limit defined.
If you have not maintained tolerance key DW for your company code,
the system blocks an invoice for which no goods receipt has been
posted yet. If you want to prevent this block, then set the
tolerance limits for your company code for tolerance key DW to Do
not check.
o KW: Variance from condition value
The system calculates the amount by which each delivery costs item
varies from the product of quantity invoiced * planned delivery
costs/ planned quantity. It compares the variance with the upper and
lower limits defined (absolute limits and percentage limits).
o LA: Amount of blanket purchase order
The system determines the number of days by which the invoice is
outside the planned time interval. If the posting date of the
invoice is before the validity period, the system calculates the
number of days between the posting date and the start of the
validity period. If the posting date of the invoice is after the
validity period, the system calculates the number of days between
the posting date and the end of the validity period. The system
compares the number of days with the with the absolute upper limit
defined.
o PP: Price variance
The system determines by how much each invoice item varies from the
product of quantity invoiced * order price. It then compares the
variance with the upper and lower limits defined (absolute limits
and percentage limits).
When posting a subsequent debit/credit, the system first checks if a
price check has been defined for subsequent debits/credits. If so,
the system calculates the difference between (value of subsequent
debit/credit + value invoiced so far) / quantity invoiced so far *
quantity to be debited/credited and the product of the quantity to
be debited/credited * order price and compares this with the upper
and lower tolerance limits (absolute limits and percentage limits).
o PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for
this item, the system calculates the difference between the invoice
value and the product of quantity invoiced * order price and
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks
whether a price check has been defined for subsequent
debits/credits, If so, the system calculates the difference between
(value of subsequent debit/credit + value invoiced so far) /
quantity invoiced so far * quantity to be debited/credited and the
product quantity to be debited/credited * order price. It then
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
o ST: Date variance (value x days)
The system calculates for each item the product of amount *
(scheduled delivery date - date invoice entered) and compares this
product with the absolute upper limit defined. This allows
relatively high schedule variances for invoice items for small
amounts, but only small schedule variances for invoice items for
large amounts.
o VP: Moving average price variance
When a stock posting line is created as a result of an invoice item,
the system calculates the new moving average price that results from
the posting. It compares the percentage variance of the new moving
average price to the old price using the percentage tolerance limits
defined.
Variances are allowed within predefined tolerance limits. If a variance
exceeds a tolerance limit, however, the system issues a message
informing the user. If an upper limit (except with BD and VP) is
exceeded, the invoice is blocked for payment when you post it. You must
then release the invoice in a separate step. If the tolerance limit for
BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the
system does not check that tolerance limit. Therefore any variance would
be accepted. This does not make sense particularly in the case of the
tolerance key Form small differences automatically.
Activities
Configure the tolerance limits for the individual tolerance keys.
Lower limit Upper limit
Absolute Percentage Absolute Percentage
AN - - X -
AP - - X -
BD X - X -
BR - X - X
BW - X - X
DQ - - X -
DW - - X -
KW X X X X
LA - - X X
LD X - X -
PP X X X X
PS X X X X
ST - - X -
VP - X - X
===============================================
Best Regards,
Siva -
Tolerance Limit for Price Variance (Purchase Order)
Hello,
Business Case :
Final users require a specific tolerance limit rate for Price variance in Freight services POs.
We have a current rate set up at Company level
--> standard customizing (MM / Purchasing / Purchase order / Set tolerance limit for Price variance)
Do you know any way to set up diffferent tolerance limit depending on the purchasing flow ? Vendor level for example ?
thanks for your time.
regards,Thanks for your reply.
What do you mean by "syestem look for noramal quantity variance from info record" ?
P.I.R only conatins under and over delivery tolerance, but nothing related to price variance between GR and Invoice.
I'm looking for a customizing in order to have a Tolerance limit for Price variance at another level than Company.
At vendor level for example ?
Do you confirm there is no standard customizing ?
Any user exit available ?
thanks
regards -
Hi gurus,
Can anybody please let me know where to look for the settings for invoice price variance. The PO was created for material A for 26.01 USD for 1EA for 6EA. Therefore the GR amount is 156.06 USD (26.016). We received the invoice for 48.41 USD for 1 EA, therefore the total is 290.46 for 6EA (48.416). accounting have blocked the invoice. Where can we check in the system for the invoice tolerances so that it explains why the invoice is blocked. I also want to know whether the invoice was blocked manully or system atuomatically did it? Now how can accounting correct this anamoly?
Thanks
AnushaI guess your invoice has automatically been blocked for payment because either the upper absolute or the percentage limit has been exceeded by the amount specified in customizing for key PP
Go to OMR6, key PP and check the settings
Accounting can release the invoice for payment through Tcode MRBR
See following wikis for some additional information:
http://wiki.sdn.sap.com/wiki/display/ERPSCM/MM-IV-LIV-CRESetTolerancesforIncoming+Invoice
http://wiki.sdn.sap.com/wiki/display/ERPSCM/MM-IV-LIV-MRBRInvoiceReleaseinLIVTransactionMRBR
Regards
Sidi -
Moving average price variance in Invoice verification
Hello,
I set in sys that the moving average of price variance will be check in tolerance of x% (lower & upper limit) BUT the system ignore it , when I save an Invoice (MIRO) with price that change the moving average price for more than X% the invoice was saved with no W/E massage . I set all massages that seams to be relevant with E but nothing was happened .
What is the way to set the system that in Invoice verification stage it will check the moving average price variance and give an alert or will not let the invoice to be post ???
Best Regards
IditHi,
You can block Invoices using transaction code OMC0
(a) Use Tolerancy Key VP for your company code
(b) Fill-up Lower and Upper check tolerance limit %
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Bye,
Muralidhara -
PO Invoice ..blocked due to Price Variance
Hi
I would like to know that how we can create a PO invoice if Purchasing document already exists. I would like to craeate this invoice such a way that it should have the price variance. Also how this invoice gets blocked and when we can unblock this. What all Tables are updated during this whole process?
Also if any one could provide me documents on PO invoices where in the general business process is explained in layman's term then it would be a great help.
Thanks in advance,
Jigar Shah.Dear Jigar,
It purely depends on the tolerances configured. If the price difference is more than the tolerance configured, the invoice gets blocked. The blocked invoices are available in the table RBKP_BLOCKED.
There are two ways to remove the blocks, both using transaction MRBR
These are:
Manually, by indicating which block or blocks are to
be removed
Automatically, by running MRBR with the automatic
In order to get familiarise with MM related transactions, it is recommended to visit sites like the one given below. This is purely MM related query. I have tried to answer it and I am open to correction, if any.
http://www.sap-img.com/sap-mm.htm
Trust this helps much!
Cheers, -
Price variance workflow for blocked invoices in MM purchasing
Hi Gurus,
We are implementing price variance workflow for blocked invoices. We built a custom workflow to
take care of the routing requirement of the customer.
We also did necessary customization defining the tolerance limits for price variance. Before testing the workflow wanted to check events in SWEL and its is found that system doesn't raise any event for price/ quantity block and hence the workflow is not triggered at all.
Event trace active flag is set in SWELS. I am not able to figure out what we are missing.The invoice gets created correctly with the price/quantity blocks and blocked invoices are available when we see in Tcode 'MRBR'.
Any suggestion will be highly appreciated.
Edited by: srinivas bejjanki on Jan 29, 2009 10:34 PMHello,
So you are absolutely sure the event trace is on. If you try SWUE with some other event, you see the entry in SWEL, dated a few minutes ago, correct?
When you try SWUE with BUS2081.BlockedPrice does it give any message?
Does SWUE work with any other BUS2081 event?
regards
Rick Bakker
Hanabi Technology -
Price Variance not blocked for payment
Hi
it is about how to create a payment block "R" once the LIV has posted with the price variance beyound the limits set in the OMR6 under AN/AP/PP etc
this is in ECC.6.0
would be great that if any one of you can assit me to resove this
thanks
Suraj fernandoSet value limits for tolerance key 'PP' for reqd. company code.
-
Hi,
in trx OMEU there is an entry: PE "Price variance: purchasing"
What is the purpose ?
RegardsPE is the tolerance key for price variance checked during invoic verification. the setting is at company code level.
For example:
Price variance
Lower limit: 10%
Upper limit: 0.00%
If you have configured these settings, an invoice amount can be up to
10% below the value determined from the purchase order and the goods
receipt. The invoice amount must not exceed this value. -
Hello Experts,
I've maintained the tolerance limit as 30% for my company code and tolerance key 'PE'.
Even though I try to create a Purchase Order with the same effective price as the material price (no variance), still it gives me the following error:
"Effective price lower than material price (variance > 30.00 %) Message no. 06206"
However, I get this error only for Import vendors and not for Domestic vendors.
I'm using same currency (INR) in Purchase Order for Import vendor as for Domestic vendor.
I've debugged the code to find where exactly and why it throws that error but have been unsuccessful. When I reach METHOD pbo_finished, deep structure my_pushed_message already has the error message ID 06 and number 206 stored in it.
Seeking Experts' help!
BR//
Anishsince you are getting effective price lower than material price, your PO appears to be at a lower value. This may be since the total is not carried to the appropriate field. pl check whether Subtotal column is having S entry
if its an error, in attributes of system messages change to warning -
Invooice block for price variance
Hi
I require a block for the invoice for value more than PO value by 2Rupees. I have done the Tolerance key cuustomizing for PP (Price variance) by mainaining the upper limit as 2 Rupees and have checked the limits. I expected the system to block the invoice for value more than PO value by 2 rupees, but system blocks even for value more than 10 or 20 paise. Please clarify and guide what needs to be done.
I also beleive system does not blocks invoice for the above tolerance for extra duties and taxes and unplanned costs. Pl brief.
Regards
Arvindhi
u have given tolerence for PP Price variance
u check following
BD Form small differences automatically
KW Var. from condition value
VP Moving average price variance
for the above keys make the option as do not chck and then try
regards
KI
Maybe you are looking for
-
How can I get Verizon to block all outgoing messages on my email?
My email was apparently hacked, it is the main account that I have used for the past seven years and all of my bill notifications and important things come to this address. I have changed the password repeatedly, run several scans on my main compute
-
when i am executing GL line itemes for clearing account , purchase documen column is not getting updated . It does not contains any po number.
-
Copying a video from Youtube to use in Final Cut Pro
I have an old final cut pro that I us for charities and non-profits I think it is version 5.1.7. I have never had the money to upgrade and now I do not have any disk or material for the program, only what is on my system. Now the question. I have
-
Trouble setting up X with FreeBSD 7.1 on my Thinkpad T60 1951-FCG
Hi! I'm having some trouble setting up X on my Thinkpad T60 1951-FCG running FreeBSD 7.1. When I run whatever config, either the one I get from X -configure or one edited after my settings, all I get is a black screen. The screen is a tad bit lighte
-
Estimate Cost on Split Valuation Materials
Dear Experts, We have split valuation on MM for almost 2 years. But we have since then the following problem: We have this split valuations: For finished products (FERT) we have 01 and 02 for valuation types For semi-finished products (HALB) we have