List of out of Tolerance (Price Variance) Invoices.

Hi Gurus,
Please tell me How to get the list of Out of Tolerance (Price Varience) invoices posted for a particular Period. ex ( 1st march to 31 st march).

Have you tried running transaction MRBR and filtering on the price blocking indicator?

Similar Messages

Lockbox issue - Payments out of tolerance should go "on account"

In FLB2, when I process customer payment advices that are out of tolerance for the invoice they are paying, the doocument is cleared, a residual item is created and the payment advice is applied. Is there a way to have the payment advice be put on account instead? (my users want to have specific information in the resiudal item record so want to manually create it during post-processing in FLB1).

Did you find the solution for this Marilyn?
I am having the same issue where if the program finds the invoice, regardless of the amount, it post and clear leaving the difference on the account.
Odd thing is it wasn't doing this a month ago? We have had a lof ot configuration changes and I am going through those but we can't understand what would impact this?
Can you share? Was your issue resolved?
Thanks!

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 PM

Hello,
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

Post an LIV invoice when it is out of tolerance

I need to understand how to post an LIV invoice when it is out of tolerance e.g. BD Small difference or PP. Once the clark parks the invoice and passes the invoice to supervisor, how does the supervisor posts the document? Where does the additional (amount higher than tolerance) amount go?
PO $100/ BD tolerance $10 but the invoice is for $115- where does the amount $5 get posted?
Need help.
Thanks in advance
Raj

Hello, Raj,
ad BD "Form small differences automatically"
-- if the the document ballance is within the limit, the difference is posted to transaction key DIF;
-- if the the document ballance out of the limit, you cannot post the invoice;
ad PP "Price variance"
-- if is is for stock material, wit avr. price and quantity on stocks, it revaluates the actual stocks, i.e. transaction key BSX;
-- if the material is with standard price, or there is no or not enough quantity on stocks, the difference is posted to transaction key PRD;
Hope you'll find it helpfull.
Kind Regards
TomT

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 Regards

Hi,
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

Invoice price variance

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
Anusha

I 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
Idit

Hi,
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

Asset PO Price Variance posting w/out asset account assignmt to wrong acct

We're bringing up fixed assets and are struggling with the account assignment behind PO Invoice receipt (MIRO) and price differences. At the moment, the PO is A account assigned and has the standard SAP settings except that the GR is valuated and the account assignment indicator is single instead of multiple. When we process MIRO, if there's a price difference, it hits the table 30 account assignment for the DIF trxn key.
We have 2 issues.
1. The account behind DIF is used for normal merchandise purchasing which isn't account assigned and doesn't reflect the GL account for the asset class.
2. The asset number is not being passed to the price variance posting (this could be a result of the GL account config since our normal merchandise purchasing doesn't carry a WBS).
We have an additional wrinkle in that we do a shadow posting to a WBS element as well as the asset number in MIRO. It seems to work fine so long as we don't have a price variance.
From reading documentation, it appears the price variance should be posting to the asset so we appear to have mis-configured something. I'm hoping it's not the valuated GR as we have a business requirement to show the value of the item when we receive it. In any case, we can't figure out what we're missing. Any assistance would be greatly appreciated.
thanks for your time and help.
Christie
Message was edited by:
Christie Monacos

Triplicate thread :-)
Getting error wrong number or type of parameters for EAM_PROCESS_WO_PUB
wrong number or types of arguments in call to 'PROCESS_MASTER_CHILD_WO'

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,

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,
Ale

HI
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

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
Sarabjeet

Hi,
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

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

Invoice Verification tolerance price varience

Hi All,
I have set Invoice verification tolerance key PP upper limit 5 % and value 5 in customizing.
I have also set message M8082 and M8083 as error message in customizing.
My requirement is to limit user from posting invoice above 5 % of GRN Amount.
The message customizing is working fine for value (M8082) however I cannot get message M8083 for % of invoice amount tolerance.
I want message M8083 to be triggered at invoice verification which is not happening.

Hi,
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
Please confirm your PO should have following check on condition control tab
and maintain the Tolerance key PS for upper and lower % limits, system first go through Val. check and then % tolerance limit check,
then you will get the message M8083
Sohaib Mahmood wrote:
My requirement is to limit user from posting invoice above 5 % of GRN Amount.
The message customizing is working fine for value (M8082) however I cannot get message M8083 for % of invoice amount tolerance.
I want message M8083 to be triggered at invoice verification which is not happening.
if you want to limit the user from posting the invoice by 5% tolerance, then maintain PP tolerance key,
you will get the message M8082 this will solve your purpose,
If your business demand for estimated price variance then maintain PS tolerance key you will get the message M8083
Thanks
Message was edited by: k j

Invoice Price Variance Report

Hi,
When the IPV report is run for a particular month , I find a variance value of -759 against an account. But when I look in Payables entries for this account, I find an additional -1329 , in addition to -759 and when I drill down these are identified as Invoice Price Variance. Why isn't the report picking up this entry ? For these entry lines the source is "Cost Management". Please provide me with some pointers to this.
Thanks,
Meenakshi

hi
thanks for your reply. assume that PO total is 150. invoice is created of 100. in this case should i see an amount in Invoice Price Variance? im not seeing any change in Invoice Price Variance. for me what happens here is Transaction Amount - Accounted is shown -50 as its still to create an invoice of amount 50 which is in fact the accrual balance. pls give me a feedback on this. i want to produce a scenario which will make the invoice price variance more or less than 0.
thanks
Lisan

Invoice Block due to price variance

Dear Friends,
In invoice verification I have configured invoice block for price variance (PP).
I have mentioned upper limit as 5%.
PO---100
GRN---100
Invoice---120
I have made this as warning message. I want this should not be open for payment before releasing in MRBR. After posting the document in MIRO it shows that invoice is blocked for payment. The payment bock indicator in payment tab in MIRO shows as "R"--Invoice verificatin.
But system allows this document for payment to be done both in f-58 & f-53.
So please tell me how to stop payment to be done before releasing it in MRBR.
Regards
R Panda

Hi
I think you may be missing some settings in FI, thats the reason it is allowing to pay the invoice whcih are blocked for payment.
Please check with your FI consultant
Thanks & Regards
Kishore

List of out of Tolerance (Price Variance) Invoices.

Similar Messages

Maybe you are looking for