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

Similar Messages

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.

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

Invoice block for lower invoices prices

In MIRO SAP blocks invoices for higher prices.
As SAP standard Invoices are not automatically blocked for price and quantiy differences exceeding lower tolerence.
Is it possible to do it for lower invoice prices.For lower price I want to make ZLSPR =R(Invoice Verification)

Hi,
I am not sure but I remember seeing the setting for lower limits on the same place where you set the higher limits.
Please have a look into the t.code: OMR6, if you haven't. Here, maybe, you need to check the type of the tolerance key used for your requirment.
Hope this helps,
Sumant.

Set blocking price for lower tolerance limit

Hello,
when we try to park or post a vendor invoice in MIRO or MIR7 transactions we need to set the blocking price (RSEG-SPGRP) when the lower tolererance limit is reached.
I have reviewed the OSS note 165589 but I think it is only for checking other tolerances different to the standard ones.
Do you know how can we do it?
Thank you in advance.
Best regards.

Hello Dëv,
yes, the check limits are set correctly. Indeed, the tolerances are working properly, but the standard doesn't set the field blocking price (RSEG-SPGRP) into "X" when the lower tolererance limit is reached because it is in favour of the customer company. However, my customer wants to avoid posting this invoices too. Hence, I need to set this fied to "X" in order to launch an approval workflow.
I thought that the OSS note could be usefull, but when I change this field in some of the user-exits detailed in the note, it is changed to blank later again.
Thank you for your quick answer.
Best regards.

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

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

Invoice Tolerance variance PP not working for lower limit

I am working in ECC 6.0 environment. I had configured tolerance variance PP to check MIRO value with GR Value. I had maintained upper and lower tolerance limits equal to 1000/- and had set messages M8082 and M8084 to error to stop invoice activity if invoice value is not within interval specified by tolerance variance.
I had posted a GRN with value 5000/-. Now, at time of MIRO ---
1) If i change MIRO value more than 6000/-, error message M8082 is there, which is correct.
2) But, if i decrease MIRO value by 500/- (which is within lower limit of variance), error message M8084 is there which should not be there until MIRO value will be reduced by more than 1000/-.
Kindly resolve this issue asap.

Hi !
Please note the following:
The system will check the lower tolerance limit but an invoice will
never be blocked if the LOWER limit is exceeded. The system will only
display a warning message. In the standard system invoices will only be
blocked if the UPPER limit is exceeded because normally one wants to
prevent to pay more than expected.
In SAP Library: MM-Invoice with Variances-Tolerances you will also
find the following explanation:
Variances are allowed within predefined tolerance limits. If a varianc
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 mus
then release the invoice in a separate step. If the tolerance limit fo
BD is exceeded, the system cannot post the invoice."
The system will check the lower limit but an invoice will never
be blocked if the lower limit is exceeded. The system will only
display a warning message. In the standard system invoices will only b
blocked if the upper limit is exceeded because normally one
wants to prevent to pay more than expected.
Best regards
Erika

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

Invoice block-for a PO with Invoicing plan

Hi Team,
The Invoice is blocked with Price block for a PO with Account assignment category Z (no GR cost centre) and with the Invoicing plan.
the Invoicing plan is a periodic with monthly invoice dates.
for ex: 31.01.09
28.02.09
01.03.09 and so on
but no Invoices were posted for the month of January and two invoices were posted in Feb.
the 1st Invoice is cleared and 2nd is blocked for Price.
please answer these questions.
1) The system should not have blocked the 2nd Invoice of Feb as no Invoice was posted for January?
2)Then if the system is not allowing two invoices in the same month eventhough the earlier month posting is not done.
the earlier month can be posted only with the Past date is it so?
Regards,
Adinath Raykar

y

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.

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

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

Triggering of price block for lower tolerance limits

Similar Messages

Maybe you are looking for