MM invoice - limits of tolerance

Hello!!
Anyone know how to set tolerance limits of the total invoice value ? I know that i can do to the total value of each item, but for the full amount of the invoice i don´t know how to do?
thanks for your attention,
André

thanks for your answers
Mr. MM  :
may not make sense, but a client asked me if I could find something about this, because she wanted to do this... so, if you can help me will be fantastic :P , If there is no way to do the same I appreciate your help!
Srinivasa :
Already tried that transaction but does not have that option , thanks for the help!
best regards,
André

Similar Messages

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

  • MIRO- INVOICE BLOCK-Set tolerance limit

    Dear All,
    We configure tolerance limits for each tolerance key in IMG-Invoice block>set tolerance limits.
    What is meaning of absolute upper and lower limit in tolerance key. And how it is different from upper and lower limits
    I have read the details of each and every tolerance key for example –AN, AP, BD, BR, BW, DQ, DW, KW, LA, LD, PP, PS, ST, VP   from sap help, but I am not able to understand properly and remember.
    Especially DQ- (the line that is Underlined and in bold letters)
    If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
    If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
    The system compares the outcome with the absolute upper and lower limits defined.
    <u><b><i>This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.</i></b></u>
    You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
    The system also carries out a quantity variance check for planned delivery costs.
    Can anybody spare time to explain me in the laymen language ALL these keys so that I can remember and get the meaning of these keys.
    thanks in advance
    regards

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

  • Maintain Tolerance limits for  tolerance key B1

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

    Any Help?

  • 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

  • Invoice verification item tolerance

    HI experts
    I actived the invoice verification item tolerance check function.and set the upper limit 1000EUR.
    then I created a po with price 1500eur. after goods receipt, I did invoice verification by referring
    the po.system generated a document successfully. but seems system didn't check the item
    tolerance. can anyone give some suggestion? thank you!

    hi,
    You need to do two things:
    1. Activate item amount check
    2. Set item amount check....
    Item amount check can't be taken into consideration when you go for vendor specific tolerance...because it works for total based acceptance ..but willnot work for the item wise amount check...
    Have you properly activated the amount check in the SPRO settings or not...DO check it properly...
    Regards
    Priyanka.P
    Additional info:
    Also check the below link to check whether you have done settings properly or not...
    [Item amount check|http://help.sap.com/saphelp_47x200/HELPDATA/EN/a8/b99f58452b11d189430000e829fbbd/frameset.htm]

  • 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

  • Invoice with PP tolerance key

    Hi experts
    I have PP tolerance key set for 10%
    My PO for a service item for toal val 10000 INR
    I have created a Service receipt (SR) for 1000 IN\R
    Then i have intitated MIRO for same SR for partial amount 400 INR
    Also second MIRO for another 400 INR
    What would be the influce of tolerance key PP, when my next invoice is processed in MIRO?
    Warm regards
    ramSiva

    Hi,
    PP tolerence key is Price Varience key and used in case of price varience there is no relation with partial IV with PP
    PP-The system determines by how much each invoice item varies from the product of quantity invoiced * order price
    Please explain what you are trying to achieve
    Thanks
    Diwakar

  • Invoice with PP tolerance: pecular behaviour

    Hi experts
    I have PP tolerance key set for absolute value 50INR
    My PO for a toal val 1000 INR and service receipt for total 1000 INR
    First invoice entered for 500INR. No block and worked fine.
    Second invoice attempted for 551INR. No block experienced. This is not correct.
    Could get invoice blocked at 1051 only, But it should work at 551. Can anybody give clue why this is always checking at total Service receipt amount and not considering partial invoices so far created.
    Warm regards
    ramSiva

    Hi,
    Set message as Error no more SES possible more then PO value for Message no. SE 363 in following path:
    SPRO---> Material Management->External Services Management->Define Attributes of System Messages
    Also set message in  t.code: OMRM & Maintain the following messages( For restriction of  invoice verification more then PO quantities)
    A.  M8 -081 Quantities invoiced greater than goods receipt quantity as ERROR ( maintain GR-based IV in the PO item level )
    B. M8 -087( item without GR ) - Invoice quantity greater than PO quantity as ERROR & save.
    Also maintain the messages M8 -081 & M8 -087 as ERROR in OBMSG t.code & save.
    Regards,
    Biju K

  • R/3 - SRM [ Limits and Tolerances questions ]

    Hi
    I was wondering if anyone out there could help provide any helpful info in relation to any of my questions below.
    1) PM order requirement against an operation for service, requirement (pur. req.) created in MM, requirement sent to SRM, PO created in SRM and copied back to R/3.
    Q. Overfulfillment tolerance - Should this be calculated into the Total
    Value of the Operation or Activity so that the GOA (approvel) is granted on this
    amount?
    2) Overall vs. Expected Value - Should GOA (approval) be granted on the Overall
    Limit instead of the Expected Value?
    3) Overfulfillment Tolerance - should this appear on the SRM PO?  Should
    it be used to calculate the total value of the PO so that GCA (approvel)_is granted
    on this amount?
    4) Should a Buyer be able to revise the SRM PO without the change also
    being made to the R/3 PR?  If not, should there be validations in SRM to
    prevent the Buyer from doing this?
    I really appreciate any help anyone out there can provide.
    Many Thanks,
    Paul

    Hi,
    Register the queues via t.code sxmb_adm where u have an option manage ques.
    Once you register the queues, they default activated.
    If u want to manually unlock then u need to go to transaction SMQR,SMQ1,SMQ2 for queue management. There u have to select the queue and activated all entries.
    SMQ1 u2013 qRFC Monitor for the outbound queue You use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually.
    SMQ2 u2013 qRFC Monitor for the inbound queue. You use this transaction to monitor the status of the LUWs in the outbound queue.
    U may schedule the report RSQOWKEX (Outbound Queues) and RSQIWKEX (Inbound Queues) to restart the queues automatically.
    To Cancel the messages from MONI with the Status Scheduled for Outbound Process
    Schedule the Report RSXMB_CHECK_MSG_QUEUE
    SAP_BC_XMB_DELETE
    Reward points if help ful.
    Regards,
    Pradeep A.
    Edited by: Pradeep Amisagadda on May 21, 2008 6:59 AM

  • 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

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

Maybe you are looking for

  • Where do I need to fix this?

    The assignment was: Create a non-GUI based Java application that calculates weekly pay for an employee. The application should display text that requests the user input the name of the employee, the hourly rate, and the number of hours worked for tha

  • Error :-The requested resource does not exist while opening the adobe form

    hello Experts, We are in Portal implementation face with ECC6 EHP4 and Portal EHP1 We have developed adobe  form using HCM forms and processes and done the required configuration in SPRO When we are trying to open the form from ESS we are getting bel

  • Burned cd's problem

    Hey everyone. I got a very strange problem - When I insert a burned cd (with data on it), tiger deals with it as I insert a blank cd. (The "Blank cd" massage appears, - - what do I want to do with this cd...) What do I have to do? Thanks Dror

  • How can find what are the customers are created in my earlier version.

    Hi all,I am trying to find out how can I check the  what are the customers are created in my earlier version of sap (i.e 4.7B) My client  Upgrade d the 5.0 in 2007. Now my client asking, list of WDs which are created in the 4.7B.

  • Prt availability.while creating production order

    while creating production order. system checking PRT availabilty if PRT is not there system throws warning msg PRT: Item: 0010  Material TESTPRT1 plant BP01 is not available. Message no. CF301 Diagnosis You are attempting to use a PRT. However, the c