MIRO lower tolerance limits check

Hi All,
In order to check the lower limit of Invoices I've implemented the BAPI MRM_PAYMENT_TERMS and collected all SAP standard message M8 specific 084 and 085.
The problem is that SAP standard doesn't call any messages in case of subseq debit/credit values are out of the tolerances limit range.
Do you know a way how I can retrieve the message in case of Subseq Debit/Credit?
Your answer we'll be highly appreciated.
Thanks.
Andrei

Please check whether exit MM08R002 is of any use to your business procedure..here you can through some customized message if the business purpose is not meet.
Regards,
Indranil

Similar Messages

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

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) 我看看有没有机会通过什么渠道反映这个问题..

Want to do changes in lower tolerance check in MIRO

Currently miro doesn't work for lower tolerance limit properly.In case of high tolerance limit whenever
limit is exceed traffic light becomes yellow and the message is displayed and posting is not
allowed.This functionality doesn't take place in case of lower tolerance limt.To do this
i need a customer/user exit.Pl tell which one should be used.

check according to your requirement
Enhancement
LMR1M001                                User exits in Logistics Invoice Verification
LMR1M002                                Account grouping for GR/IR account maintenance
LMR1M003                                Number assignment in Logistics Invoice Verification
LMR1M004                                Logistics Invoice Verification: item text for follow-on docs
LMR1M005                                Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006                                Logistics Invoice Verification: Process XML Invoice
MRMH0001                                Logistics Invoice Verification: ERS procedure
MRMH0002                                Logistics Invoice Verification: EDI inbound
MRMH0003                                Logistics Invoice Verification: Revaluation/RAP
MRMN0001                                Message output and creation: Logistics Invoice Verification
LMR1MF0L
LMR1MF0T
LMR1MF1T
LMR1MF1U
LMR1MF26
LMR1MF3L
LMR1MF3M
Business Add-in
INVOICE_UPDATE                          Business Add-In: Logistics Invoice Verification

Block Payment in MIRO for Lower Tolerance Limit

when we are posting MIRO Transaction
how can we block payment invoice in MIRO Tcode for the Lower Tolerance Limit
As the standard functionality is working for Upper Tolerance Limit, in the same way user needs to
block invoice for Lower Tolerance limit
Thanks

Hi Ganesh,
below is the user exit where you can check the tolarance and put the Block according to the your requirment.
User Exit name - MM08R002 -User exit for tolerance checks
in the above user exit you have to use the below Function exit.
1) EXIT_SAPLMRMC_001
2) EXIT_SAPLMRMP_001
we implemented the above user exit to put the payment block based on the checks.
You can find the documentation of the above exit in the system.
Thanks
Naresh

User exit for lower tolerance check and block of invoices

Hi,
Is there any user exits or ways to block invoices for their lower limits. Presently, for upper tolerance limits, the invoice is blocked, but for lower tolerance limit only a warning message is displayed.
Regards,
Arun Mohan

Hi,
I have the similar problem.
Did you find solution?
Best regards.

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

Tolerance limits & Number ranges

1. What is tolerance limits ? Why we need to use it ? What are the steps to configure tolerance limits ?
2. What is number ranges ? How to create number ranges ?

Hi,
IN PO tollerence limit:
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.
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.
MIRO Tolerence limit: OMR6
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.
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.
SAM

Tolerance limits on PO

Dear All,
I need to place tolerance limits on PO quantity. e.g 5 percent of the PO quantity is allowed to GRN.
how can i do that,
Thanks

Hi
The SPRO setting under Inventory Management > Good Receipt > Set tolerance key
this is at company code level. if you set this, then each and every MIGO will pass through the limit
this may have an impact on inventory inflation if MIGO is on higher side, especiallyfor A class items.
Better to set tolerence key at various level mentioned by one of Gurus so that only the particular combination will pass through the tolerance Limit. and on the other hand you will controlled inventory.
in spite of this client insist at Company code level then proceed with SPRO setting
Also check the message setting if you want to give Error message if it is exceeding the tolerence Limit.

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

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

Purchase Order History Tolerance Limits

Good Morning,
I am hoping someone can clarify this for me. Within MM_EKKO archiving object a reason why you can not archive is "The last purchase order history transaction for an item is outside the tolerance limit". When SAP says Tolerance Limits for this item what are they referring to? Is it Residence Time or is it the C MM-PUR Reorg. Sched. Agrmnt Extra configuration?
Our current settings are as follows:
Residence Time = 2500 days
C MM-PUR Reorg. Sched. Agrmnt Extra = Validty Period is expired for more than day. No other settings are active.
Thanks in advance.

GR for movement type '101'. IR via tcode MIRO.IR happens first before GR only in case where friegth charges are paid to a third party.

MIRO lower tolerance limits check

Similar Messages

Maybe you are looking for