Invoice error---- ""Maintain Tolerance Limits" - unknown solution "

Hi Gurus,
When Invice is posting error is coming " Maintain tolerance Limits". Could you please explain where I need to check the tolerances and where I need to maintain limits of these concern..
Regards,
Subbu

hi,
I think you have assigned the tolerance group to the material master which is configured inside SPRO...
SPRO >> MM >> LIV >> Incoming invoice >> define vendor specific tolerances..
Due to this when you make the invoice, system ask for the toleance limits, so that system can calculate overdelivery and under delivery tolerance and if the invoice posted above or below based on this the system will provide the message...
So, do enter the tolerance limits in the invoice and then save the invoice...
If the invoice is out of tolerance system will show you a message and post the document as BLOCKED...
After this you need to release the doc from MRBR..
Regards
Priyanka.P

Similar Messages

Maintain tolerance limits for tolerance key PE (CoCode S001)

Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopal

Hi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages

Maintain tolerance limits for tolerance key PE

Hi,
How can I correct the error below?
"Maintain tolerance limits for tolerance key PE"
Thanks

REFER BELOW SDN POST
Re: TOLERANCE KEY ERROR DURING MIGO
MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT ASSIGNMENT -
> Please follow this link --> SPRO -> MM-> Purchasing --> Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for Tolerance keys PE and SE. Just copy them from std co. code.
Message was edited by:
SHESAGIRI.G

Maintain tolerance limits in the Tolerance key

Hi,
Could any one help me how to maintain these Tolerance limits in the Tolerance key. This is an error I receive while creating a PO.
Best Regards,
Sridhar.k

What is the Error Mesaage no you are getting??
Solution is as Follows
Set Tolerance Limits for Price Variance
In this step, you define the tolerance limits for price variances.
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
Activities
Maintain the tolerance limits for each tolerance key per company code
Regards
Biswajit

Maintain Tolerance limits for tolerance key B1

Hi,
When We tried to reverse a 'reversal' document using MBST but the system does not let me a throws up the following message no. M8125...
"maintaintolerance limits for tolerance key B1 (CoCode 5000)".
I checked configuration in OMc0, we have lower limit 10 % anf Higher limit 10% and BOTH 'check limit'.
Still I donot where is the problem?
Can somebody throw smoe light on this issue? Please....

Any Help?

Simple error... Unknown solution...?

Alright well this is a simple error and when i got it i thought alright well that's simple enough to fix.
But wow wth, it won't fix. Lol.
This is the error:
Exception in thread "main" java.lang.NoClassDefFoundError: server (wrong name: n
et/stanyer/server)
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(Unknown Source)
        at java.security.SecureClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$000(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClassInternal(Unknown Source)
Press any key to continue . . .At first, you think "wth, obviously you are directing it to the wrong class name..." but i'm not ;S
This is the directory of the run file; C:\Documents and Settings\Administrator\Desktop\stanyer_new
This is the location of the class file "server"; C:\Documents and Settings\Administrator\Desktop\stanyer_new\bin\net\stanyer\server.class
And this is my run.bat file;
@echo off
title Stanyer's 503 (server)
cd bin/net/stanyer/
java -Xmx1024m server 43594
pauseWhat on earth am i doing wrong? Thanks.
Edited by: Ryan_Stanyer on Aug 9, 2008 1:25 PM

Works..
But errrrr;
Exception in thread "main" java.lang.NoSuchMethodError: main
Press any key to continue . . .However:
* @author Stanyer
* The main class of the server, contains the method main(String[] args)
* which is the first method called and the entire server is started from
* that method, so any important variables that need to be set can be set
* from within that method.
package net.stanyer;
import net.stanyer.misc.*;
import java.io.*;
import java.net.*;
import java.text.*;
import java.util.*;
public class server implements Runnable {
     protected misc _misc = new misc();
     protected ServerSocket main_socket;
     protected boolean server_active = true;
     protected int port;
     public server() {
     public void main(String[] args) {
          port = _misc.parse_int(args[0]);
     public void run() {
          try {
               main_socket = new ServerSocket(port);
               _misc.cmd_log("Server was opened on port: "+port+".");
          } catch(Exception _ex) {
               server_active = false;
               _misc.cmd_log("Server was unable to start: port may already be in use?");
}There is a main method.. Lol?

Tolerance limits in the invoice creation

Hi,
I am not able to create invoice using BAPI function module.
I am getting the error 'Maintain tolerance limits for tolerance key BD (Company Code 1007)'.
What are the tolerance limits and How can I maintain these.
Can anyone please help me to solve this problem.
Thanks in advance.
Regards,
Eswar

Dear Eswar,
For invoices without reference to a PO or those with reference to PO,in customizing for Material Management under
Logistic Invoice verification: Invoicing Block: Set tolerance limit, You can set diffrence tolerance limit for each company code.
If you enter an item with a large amount it make sense to often block this invoice in order to check.For this for each co. code
Path: SPRO : LIV : Invoice Block: Item amount check :Activate item amount check.
In addition to above
Path: SPRO : LIV : Invoice Block: Item amount check :Set item amount check.
I hope this will help you.If so reward points
Vivek Maitra

Tolerance Limits - Error message: SV033

Hi Guys,
I am trying to add a new entry on the below transaction:
IMG - Material Managment - Logistics Invoice Verification - Invoice Block - Set Tolerance Limits
But I got the error message: SV033 - "Specify the key within the work area".
Does anyone know how can I procede in this case?
Thanks
Daniel

That's a pretty odd message. Are you getting it when you enter the TCode? Upon saving? I'd check OSS and create a ticket if you can't find anything.

Tolerance limits in Invoice Varification

Hi All
In Std SAP how to set the tolerance limits for Invoice Varification.
On what are all different parameters can i set these tolerence limits ?
That is in MIRO we do enter different values at Header level( Amout in basic data & Unplanned delivery cost) and at item level (Amount in PO reference, G/L a/c ,Material tabs)
Is it possible to set the toleremce limits for each of the above said values?
Pls advise..
With Regds

Hi BSA
U can set tolerance limit in customization for following
Amount for item without order reference
Amount for item with order reference
Form small differences automatically
Percentage OPUn variance (IR before GR)
Percentage OPUn variance (GR before IR)
Exceed amount: quantity variance
Quantity variance when GR qty = zero
Var. from condition value
Amount of blanket purchase order
Blanket PO time limit exceeded
Price variance
Price variance: estimated price
Date variance (value x days)
Moving average price variance
Path
Spro>MM>LIV>Invoice Block>Set Tolerance Limits
Vishal...

Tolerance limits for PO,MIGO..etc..?

Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mm

Hi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices 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:
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.
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.
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.
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.
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.
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.
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.
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).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
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.
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).
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).
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.
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.
Thanks & Regards
Kishore

Tolerance limits for contract

Hi all,
   Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
      it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendra

Hi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
        Ramesh

Tolerance Limits PP

Dear All,
I have maintained tolerance limits in material master as 5% for both over and under tolerance....But the problem is even if i maintain the production order as below or over 5% still its is accepting the production order n allowing to do confirmation and goods receipts....I want to stop this....Please suggest..
Regards,
Pawan Shetty

Pawan,
??? You want a warning every time there is a confirmation for a quantity less than the underdelivery tolerance? That means almost every confirmation will give the user a warning. Does that really make any sense?
Underdelivery tolerance setting only produces a warning when you are setting the final confirmation for the operation.
Normally during confirmations for an order, most of the confirmations will be for substantially less than the goal quantity. Only the final few confirmations bring the total confirmed quantity to something 'close' to the goal quantity.
Best Regards,
DB49

Triggering of price block for lower tolerance limits

Hi.....
I have defined tolerances for invoice verification using tolerance key PP (path: spro --> Material Management --> Logistics Invoice Verification --> Invoice Block --> Set Tolerance Limits). Our system is correctly blocking invoices when it comes to upper limits. However, when I post an invoice outside the lower limits, system is giving me a warning but it is not blocking the invoice. It simple posts the invoice despite the difference.
Where in customizing can you define that exceeding lower limits, also should lead to a block?
Kind regards
Jacob

Hi Jacob,
in SAP standard the Invoice is only blocked if it is above the upper limit. If it is below the lower limit it will only issue a warning message:
In SAP Library: MM-Invoice with Variances-Tolerances you will also find the following explanation:
".. If the variance is outside the tolerance limit, the system displays this in a warning message. If you do not adjust your entries, you can still post the invoice. If, however, the upper tolerance limit is exceeded, the system automatically blocks the invoice for payment."
Usually you can be fine with the lower payments, it is the Vendor who should be afraid but If you anyway need to have that block I think the only way is to develop.
Let me know if useful.
cheers, MM

MIRO- INVOICE BLOCK-Set tolerance limit

Dear All,
We configure tolerance limits for each tolerance key in IMG-Invoice block>set tolerance limits.
What is meaning of absolute upper and lower limit in tolerance key. And how it is different from upper and lower limits
I have read the details of each and every tolerance key for example AN, AP, BD, BR, BW, DQ, DW, KW, LA, LD, PP, PS, ST, VP from sap help, but I am not able to understand properly and remember.
Especially DQ- (the line that is Underlined and in bold letters)
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.
Can anybody spare time to explain me in the laymen language ALL these keys so that I can remember and get the meaning of these keys.
thanks in advance
regards

Please use the Posting Key BD, with no limits there by restricting any value differences

Logistics Invoice verification MM - tolerances for lower limits and Credits

Hello,
My end-user is wondering why the system does not re-act/block on the lower limits of the price tolerance.
I have checked several SAP document and found:
1. Blocking Invoices
If a tolerance limit is exceeded, you receive a system message. You can post the invoice in the
system, but it is automatically blocked for payment if an upper tolerance limit is exceeded.
So for the lower tolerance limit there is no block only a warning.
2. Posting Credit Memos
The system does not check if your entries in the columns Amount and Quantity correspond to
the purchase order price or the invoice price.
So there is never a message or block for Credit Memos.
3. Subsequent Debits/Credits
If you want the system to carry out a price check for a subsequent debit, it compares the
value invoiced to date plus the value of the subsequent debit with the expected value based
on the purchase order. The system takes tolerance limits into account when carrying out the
price check. If a price variance exceeds one of the upper tolerance limits, the subsequent
debit is blocked for payment.
So only a check for subsequent Debit , not for Credit.
The examples my end-user has are the following.
1. Blocking Invoices
If the Invoice price is too low, the purchaser should be informed, he has to check what is wrong in the purchase order.
Maybe the price unit was filled in incorrectly or ...
Example:
a. Standard price is 100 Eur per 1 PC
b. Purchase price is 1000 Eur per 1 PC
Purchaser has made mistake it should have been 100 per 1 PC.
I checked and the Purchaser gets an info msg 06207 Effective price is 102.00 EUR, material price is 100.00 EUR,
but he can ignore this message.
c. Invoice price is 500 Eur per 1 PC
This invoice price is actually too high compared with the standard price but because of the high Purchase price no blocking occurs.
In this case we would like the system to also block the Invoice for payment.
2. Posting Credit Memos
Purchase order has a price of 1765 Eur.
We received goods and an Invoice for 1765 Eur.
We have returned the goods to the Vendor and we post a Credit Memo of 1048 Eur.
We receive no warning and the Credit Memo is not blocked for payment
The system should warn us that the Credit Memo has a too low value and we would prefer that the system blocks the Invoice.
3. Subsequent Debits/Credits
The Subsequent Credit can be seen as an Invoice price too low and therefore we would like it to be handled the same, see 1.
Can you please give us your opinion.
Is there a possibility to change the standard behavior of the system ?

Hello,
The limit check values have already been set up for key tolerance PP -upper and lower limit in OMR6 tcode.
Unfortunately when we are creating an invoice with a lower value than the expected value on the PO, it doesn't trigger the invoice block.
From what I've read on the forum SAP proposed as a solution the use of enhancement MM08R002-User exit for tolerance checks=> fm EXIT_SAPLKONT_002- Customer Exit: Change Tolerance Check, but in our system the check for upper limit is performed inside the fm MRM_AMOUNT_CHECK=>
fm MRM_TOLERANCE_CHECK
Überschreitung der Toleranzgrenze -
IF I_AKT_WERT > I_VERGLEICHSWERT.
... Betrag -
    IF T169G-XW2JA NE SPACE.
      DIFF_P = I_AKT_WERT - I_VERGLEICHSWERT.
      IF DIFF_P > WERT2.
        E_BETRAG = WERT2.
        E_RETURNCODE = 1.
        E_SPERRGRUND = 'X'.
      ENDIF.
    ENDIF.
Could you please advise me how you have implemented the check on lower limit tolerance?(eventually a sample of coding)
Thanks,
Andrei J.

Invoice error---- ""Maintain Tolerance Limits" - unknown solution "

Similar Messages

Maybe you are looking for