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

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

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 advise

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

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

Check for available downloads does not work HELP

I had previously bought about 100 songs on my laptop, but we encountered a problem were my wireless network would not work. The support at HP wouldn't help us out unless we did a system restore first, so i lost all my stuff.
when i installed itunes again after the restore, it gave me one song from the check for available downloads option, and it says all available purchases have been located. Also, when i try to download a song I already had before it recognizes that I already downloaded it and tells me to use the check for available downloads button, which obviously is not helping me.
anyone else have this problem? I dont really wanna be out a hundred bucks...

and * is wrong with you guys!
The only people who participate here are we your fellow users, so please don't yell at us.
your making music even more expensive! $1.29 for a song i could get for free! *?!
It's the record companies who are controlling the pricing. They forced Apple to accept having more popular songs be more expensive as the price for allowing Apple to remove the copy protection. Rant at the record companies, little good though that will do.
Look for a folder called "Downloads" in your iTunes Music folder. If there is such a folder, look for files that would be the partial download and delete those, so that the download starts over from the beginning. Then try again using the "Check for Available Downloads" command under the iTunes Store menu.
If that doesn't work, contact the iTunes Store customer support department through the form at the bottom of their web page and explain the problem to them.
Hope this helps. Next time, though, it would be better if you started your own topic rather than tagging onto someone else's thread.

"Include when checking for new mail" option not working

Hi,
I have 2 email accounts set up on mail, but I only want 1 of them to pull down mail (the other will only be used for sending). For the account I don't want to get mail I deselect the box "include when checking for new mail".
However, Mail still pulls down messages from that account. When I put in the correct server settings for the incoming, it pulls all of my mail (in this case gmail), and when I put in bad settings (as a way of avoiding getting the mail) I get an annoying error message.
Does anyone know of a way to make that function of Mail work?

Hi feuerstein.
How have you set up the Gmail account in Mail (POP, IMAP), and under which circumstances does Mail check for new mail on that account? More info, please.
BTW, Mail doesn’t automatically check when launched every account if Include when automatically checking for new mail has been turned OFF. That happens with IMAP accounts only (and only if they’re “online”), not with POP accounts, but it isn’t clear at all whether that’s what you’re talking about...

Check for updates in LR5 not working.

When i try to check for updates in LR5 help, it show me the veriosn check is unsuccessful & stated that my line is not connected but my internet is working. Please assist my issues, thank you.

Had the same issue and complained about it in this forum.
The only way to fix it was to uninstall and reinstall LR, but it only worked after repeating this several (!!!) times.

Compliance Checker for Vsphere 5.5 Not working /connecting

I am trying to run the Compliance Checker for VSphere 5.5 woth no luck.
I run the program from the Vcenter server and get nothing.
I have run from a pc and gotten "cannot connect"
I have tried every possible username and PW combination we have.
Any help would be greatly appreciated

This is the error I receive,
Error connecting to host service instance (IP Address xxxxxxxxxxx; User ID: [email protected])
Also I can log into the vsphere server at the console using root but cannot login using the vsphere client using root
it tells me root does not have permission. Not sure if this may have be some of the issue with the compliance checker
or a function of Vcenter 5.5.

Check for updates (apps) does not work any more

In iTunes when I click the "Check for Updates" nothing happens. But, I can download update using my iPhone as usual.
In iTunes I can still buy new APPs, access the store, buy music, TV shows as usual.
Any suggestion,
MS

Im also having the same issue. I called Apple they refer me to do an uninstall of all ituns apps which I did by following the link they that he had emailed me ( http://support.apple.com/kb/HT1923) which i did anden when the still I got the issue has not been resolve I even went thru unistalling it and deleting all of the windows registerys and reinstall and still no fix.
it seems like they dont know the cause or have a fix, does anyone has any ideas

PO Tolerance Limit for Price Variance

All,
For the key PE I have set Upper Limit for Percentage Check Limit to 0.01%. At what point is the tolerance limit check? Is it at PO creation or some other point?
Thanks,
Sean

The related error message appears at the time of PO creation. It will prevent you from creating the PO with a price that is ourside the allowed tolerance value
PE tolerance limits defines the allowed variation in price between the PO price and that of material price stored in the material master as standard price. The standard price is the output of the standard costing process

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

Tolerance limits for Price Variation

Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
Sathya

Hi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal

Lower Tolerance Checking for PM Key

Hi,
For our business process we accept every incoming quantity change made by the vendor in the purchase order response. We accept quantity increments as well as quantity descents. In order to prevent the POR from having to be approved/accepted by the responsible purchaser, we also need a lower limit to customize the same.
Therefore the question is, why is the lower limit input field missing in the PM key? When going through the help file of this customizing transaction we can read the following:
PM: Quantity variance (converted to currency amount)
If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
As you see above, it is clearly stated that u201CThe system compares this sum with the defined upper and lower limitsu201D. So according to SAP help, lower limit comparison should be possible.
In order for this to work we need the lower limit input fields.
---> Is there any other way to establish the above ?
Thanks and regards,
Aline

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

Auto To working for one material and not working for other material

Hi,
Hope everybody is doing fine.
I have configured the auto TO. Its working fine for one material and not working for the other material. I checked the material master and wm 1,2 views have the same fileds / values. What could be wrong?
I didn't setup the back ground processing job. Is that is affecting it?
thanks for any help.
regrads,
KHAN

Thnaks,
You are right but then what could be wrong? Its working for one material and not working for otehr material? Any clue?
Appreciate your time charlie

Valuation Basis for Different Payment (BWGRL) not working in 2010

Hi
We have a commission wagetype which we entered in IT 2010 in Number/Unit field.
Since we don't have premium id available, we used "Valuation Basis for Different Payment (BWGRL)" to enter the RATE.
This RATE is not working during our payroll run, however when we are using the wagetype with premium ID it is working fine.
My question is- What could be the reason that the Valuation Basis for different payment is not working ?
I checked the wagetype in V_512W_B table and it has the following configuration-
Current wage type
Valuation Basis = BLANK
Statement/WT = BLANK
%Rate = 100
1st derived wage type
Valuation Basis = BLANK
Statement/WT = BLANK
%Rate = BLANK
2nd derived wage type
Valuation Basis = BLANK
Statement/WT = BLANK
%Rate = BLANK
Would appreciate if the the fix could be provided.
Saurabh Garg

Hello,
I think in your case for commision wagetype you need to modify rule $930 to process the override rate from Infotype 2010 BWGRL field in case you are using the US standard schema.
The valuation basis table V_512W_D and rule $930 together will determine the valuation basis.
The default valuation basis comes from table V_512W_D.In case you want to override the valuation basis rate defined in this table,you need to maintain override rate in It2010 and accordingly have the logic defined in rule $930 for that particular wagetype .
Following is the sample rule definition for a similar scenario.
****(commision wagetype)
NUM= ANZHL Set
RTE= BWGRL Set
RTE?0      Comparison
      MULTI NRA Multipl.amt/no/rate
      SETIN X=NX Set variable split
      ADDWT *    OT   Output table
    =
      VALBS0     Eval.0.WT in 512W
      MULTI NRA Multipl.amt/no/rate
      SETIN X=NX Set variable split
      ADDWT *    OT   Output table
Regards,
Malathi V.

Tolerance Check for Price Variance is not working

Similar Messages

Maybe you are looking for