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 <b>Environment -> Define Attributes of System Messages.</b>
Activities
Maintain the tolerance limits for each tolerance key per company code
Regards
Biswajit

Similar Messages

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

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

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

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:
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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).
u2022     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.
u2022     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.
u2022     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).
u2022     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).
u2022     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.
u2022     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

1) "Powered by Jive Software" ....
2) 我看看有没有机会通过什么渠道反映这个问题..

GR tolerance Limits

Hi,
We would like to set the GR Tolerance Limits in the Configuration level.
In Transaction Code OMC0, if we set the tolerance limits for B1 and B2 how does the system works during Goods Receipt.
Thanks
Ravi

Hi,
GR tolerance limits are as follows:
B1 - Order qty variance (GR) error message.
B2 - Order qty variance (GR) warning message.
The GR tolerance is totally depends on the tolerance limits maintains against each tolerance key (B1 & B2)
Thanks,
AMIT

Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hai
for quantity tolerence limit u can do it while creating P O in item details-->delivery tab.
for date go to SPRO-->mm>purchasing->material master> define purchase value key>in that st.del.time var here it wil compare the dates and shows how much deviation is occuring for GR date
configure messages in SPRO-->mm>environment data--> define attributes of system messages
hope it may help u
regards
chandrasekhar

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

GR Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hi,
GR tolerance limits can be set based on the quantity only .It is configuration settings .
MM-->Inventory Management-->Inventory Management and physical Inventory --->set tolerance limit/
Following are the standard settings:
B1 ( order price quantity variance with error message): 50 %
B2 (order price quantity variance with warning): 20 %
VP (variance from moving average price) 25 %
In case of dates, the tolerance limit settings based on delivery date can be achived by using user exists or create a Z t.code goods receipt copying standard one & write a code to apply your logic while you do the GR.
Thanks,
AMIT

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

No tolerance limits maintained in controlling area 5555, profile 000001

Hi,
While Doing internal order budget i am getting the below error.Kindly help me in fixing that error.
No tolerance limits maintained in controlling area 5555, profile 000001
Thanks
Kishore

Hi Kishore FICO,
Menu path to maintain tolerance limit for internal order:
SPRO > Controlling > Internal Orders > Budgeting and Availability Control > Define Tolerance Limit for Availability Control...
regards,
ng chong chuan

Bapi incoming invoice not checking the tolerance keys

Hi,
I am using bapi BAPI_INCOMINGINVOICE_CREATE to post an invoice.Does it cover the tolerance check.
If it doesnt check all the tolerance keys lthen is there any other function module which can be used?
Any one ??Plz help.

Hi,
put a break-point in these fm´s:
FI_TOLERANCES_CHECK
MRM_TOLERANCE_CHECK
and execute the bapi.
Best regards.

Tolerance limits for vendors

Hi,
Can any of you suggest me how to overcum the below issue
Tolerance limits need to be maintained for the tolerance key PP for company code xxxx
VSK

Path OMR6
maintain following for your company code
0001     SAP A.G.     AN     Amount for item without order reference
0001     SAP A.G.     AP     Amount for item with order reference
0001     SAP A.G.     BD     Form small differences automatically
0001     SAP A.G.     BR     Percentage OPUn variance (IR before GR)
0001     SAP A.G.     BW     Percentage OPUn variance (GR before IR)
0001     SAP A.G.     DQ     Exceed amount: quantity variance
0001     SAP A.G.     KW     Var. from condition value
0001     SAP A.G.     PP     Price variance
0001     SAP A.G.     PS     Price variance: estimated price
0001     SAP A.G.     ST     Date variance (value x days)
0001     SAP A.G.     VP     Moving average price variance
Best Regards
Ashish Jain

Ignore Tolerance limits for Subsequent docs.

Dear All,
Is there any possibility exists to avoid PP tolerance key check ignore for only in case of SUBSEQUENT DEBIT/CREDIT.
The tolerance limits sets in PP working fine for INVOICE, but this check i dont want to be considered in case of SUBSEQUENT documents. SUBSEQUENT DEBIT can be done any amount without restricting the limits for PO or tolerances.
Thank you in advance.
Regards,
Syed Hussain.

Hi,
I would try this:
1. Configure alternative vendor tolerance limit for my company code.
2. Impelment badi: MRM_TOLERANCE_GROUP. Here, according to SAP documentation, you can change vendor tolerance key during invoice entry based on your on logic.
For the documentation of this badi go to IMG help for: 'IMG -> Materials Management -> Logistics Invoice Verification -> Maintain Customer Exits and Business Add-Ins -> Maintain Business Add-Ins for Invoice Verification' and then for badi MRM_TOLERANCE_GROUP.
Hope, it helps.
Regards,
w.

Maintain tolerance limits in the Tolerance key

Similar Messages

Maybe you are looking for