F-48 exceed amount

Hi expert
I am making advance payment through f-48, when i am putting the amount 110 ( 100 + 10) net price + tax, the system is through a error, amount exceed.
regard
Nabil

Solve by own

Similar Messages

Budget Exceeded but no Error message Assign more than allocated

Hi Gurus,
I am stuck in a situation where the Error Message BP603 while creating a PO for a wbs at level 2.
IN cj30 , i found out that Budget = 69500000 and assigned = 69950772
if i create a PO OF even .30 (thirty paisa) the budget exceeded amount = 450772.35, which is actually the diffrecene betweenn assigned and Budgeted values.
Now we are not able to raise any PO
Below is tolerance limit
please key in your valuable inputs.
Regards
Rohit

Hi Rohit,
In Budget report, Assigned value = Actual + Commitment
If your assigned value is great than Budget, then you will get Budget exceeded error when you try to do any further posting against specific WBS element.
So, you will need to supplement Budget to cover shortfall.
You can also refer following SAP note which shows how assigned value is calculated.
178837 - Availability control: Incorrect assigned value?
There are lot of threads already discussed in this forum for error message you are mentioning.
Please search them.
Regards
Tushar

Ran system restore and now my Adobe Acrobat license has exceeded its limit

I tried restoring computer due to a corrupt install and it removed Adobe Acrobat, since the system restore did not work, I re-installed the OS, patched and then installed Adobe Acrobat XI Professional, entered my license and it comes up with exceeded amounts of use for this license. Would just like to get the license reactivated. Any help would be appreciated. I tried calling in and Adobe is closed on the weekends, tried chat but nobody has come online in quite sometime so now trying the forums since they are 24/7.
Thank you -
Jake

You will need to talk to Adobe, not users on the forums, because only Adobe can reactivate something on their end. I would imagine that staffing levels increase during the work week.

Miro to be booked @ purchase order amount.

Dear All,
I had a query related to MIRO-when we book MIRO on a purchase order , we can only book as per the quantity in GR.Is there a way that i can control the amount while booking the MIRO i.e tolerance +- 15000/- or smaller amount.right now i can manually change the value and book excess amount or can i control that any point the MIRO value should not exceed the purchase order value.
Need your help on this.
Thanks,
Priya

Hi,
Maintain tolerance limits as ZERO in OMR6 t.code for the tolerance key PP ( for Price variance) & DQ ( Exceed amount: quantity variance)
Also you can set message as ERROR in OMRM t.code for messages M8 -081 {Quantities invoiced greater than goods receipt & maintain GR-based IV in the PO item level} & M8 -087 {( Invoice quantity greater than PO quantity) is for material without GR only}
NOTE:
If message setting not work, you can set ERROR message for M8 -081 & M8 -087 in OBMSG t.code.
Regards,
Biju K

IR Value exceed GR value

Hi xpert,
how to block IV from processing IR if the item value exceed GR item value.

Hi,
SPRO --> MM --> logistic invoice verification --> invoice Block --> Set tolerance limit
Now u can set tolerance for a compnay code
BR     Percentage OPUn variance (IR before GR)
BW     Percentage OPUn variance (GR before IR)
DQ     Exceed amount: quantity variance
DW     Quantity variance when GR qty = zero
here in BR and BD, you can define upper limit or lower limit.
Regards,
Pardeep malik

Error while submitting the Invoice

Hello Everyone,
We are using SRM 5.0 with Extended classic scenario.
I am having a problem while submitting the Invoice.
I keep getting errors saying I need to enter a quantity for a line item that has already been billed in full. When I enter a quantity I then get new error messages telling me I've exceeded amount for that line item.
Please help me in this.
Thanks & Regards,
Khushbu.

Hi,
This is typically a process issue. There are a few things I think you can do...
a. If the invoice has reached customer already (bcoz it was raised in the month of May), then, as you now cannot cancel as there has been a lot of wrong entries, you an create a credit memo either from SD side or from FI side so that the customer a/c is balanced and it will not show any AR balance.
b. Raise a debit memo request against the right customer and invoice it.
I think you have to work with your Finance people to be in concurrence before you take up he above process.
Thanks
Mukund S

Tolerance limits for vendors

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

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

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

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

Hi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore

Tolerance limits 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...

Withholding tax not captured for a single Vendor during Invoice

Dear SAP Gurus,
Withholding tax is not captured during MIRO for a particular Vendor. The Vendor Master has been assigned with the relative tax codes. Program RFWT0010 has been run. Tax Types have been
checked. Error message was changed to Warning in OBA5. Message 7Q321 Withholding tax
amount exceeds amount in Vendor line item 001. Relative SAP notes referred. Withholding tax
type at the time of payment Central Invoice & I ppmt checked. OBC4 reconciliation account
G067 field status group checked for taxes - optional. Please give solution.
Thanks and regards,
Sadashivan

Hi,
Check with the minimum amount of the withholding tax code.
Check accumulation activated or not.
If you are using portary dependencies check the base withholding tax code given.
While defining the withholding tax code check the posting indicator and check withholding tax formula is activated or not. if it is active then check the amount given in withholding tax code formulas.
Still problem continue revert back.
Regards,
Sankar

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

Firefox, as default browser, opens Outlook 2010 hyperlinks very slowly, but other browser open, the links, at normal speed, whats going on?

Running Windows 7, 64-bit, with Firefox 19.0 as default browser. When opening hyperlinks in Outlook 2010, Firefox takes an exceeding amount of time to open the link. All other browsers, when set as default, open links at normal rate. Have tried clearing the cache and cookies and this fixes the problem temporarily. Help!

If you have Firefox closed while opening a hyperlink then it may take some time. It will also take some time if you are opening it for the first time since the boot up of your computer. Add-ons may also cause startup issues - please see below for troubleshooting.
'''Try the Firefox Safe Mode''' to see how it works there. The Safe Mode is a troubleshooting mode, which disables most add-ons.''
''(If you're not using it, switch to the Default theme.)''
* You can open the Firefox 4.0+ Safe Mode by holding the '''Shift''' key when you use the Firefox desktop or Start menu shortcut.
* Or use the Help menu item and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
''Don't select anything right now, just use "'Start in Safe Mode"''
''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut (without the Shift key) to open it again.''
'''''If it is good in the Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one.
Please follow the [[Troubleshooting extensions and themes]] article for that.
''When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.''

Exchange rate calculated wrong

Hi All,
We have a case where Our Cash allocation Team has cleared the items on the attachment on the customer account 1418029 in SAP PRE. The clearing document is 16000167. As per the credit controller s advise they needed to clear the item and leave exceed amount of 15731.44 EUR. They used T-code F-32 and they made the part allocation in EUR.
As it shows the exceed amount was left there indeed. It is 15,731.44 EUR. FX rate 1.41401 which should give 22,244.41 USD in loc curr and not as it shows in customer account (39,454.25 USD). Can you pls advise what has happened as it caused serious problems in the last month end reporting.
The clearing doc has another clearing document i.e 16000194 in which for the particular effective exchange rate it is showing 2.50799.but if u check inside the document they have given exchange rate as 1.41401.From where the effective exc rate is picking.
can anybody help on this?
Thanks
Aniswa

Customer account shows the amount as per the posting date exchange rate.
But in F-32, F-44 & F-03 clearing screens will show the amount as per the exchange rate of clearing date which is different to posting date. This is normal behaviour only.
While clearing system automatically creates the realized loss/gain line items automatically.
Rgds
Murali. N

EDI-IDOC: want to generate Reference Specifications for Bank Details field

Hi Guru,
We are running to the situation that we use EDI with China vendor (using China bank account). The bank account for China has greater than 18 characters which is the maximum limit for bank account field. Based on note 96624, we are suggested to maintain the exceeding amount into the "Reference Specifications for Bank Details" field. However, when I run the payment on F110, IDOC do not generate the reference field.
How can the bank reference field be included in the IDOC?
Thanks,
Song

Hi Auro,
You use use EDI_DC-SNDSAD field, currently this field is used no where.
If you not sure where to see double control record and click address info tab
you can use either field receiver or sender.
For testing use WE19 transaction and pass your paymethod to following field
and then inform to EDI Mapper that your sending paymethod in this field.
For them this field is very easy to grab.
Let me know if you any concern.
Thanks,
Narayan

DQ tolerance key

I have maintained the DQ tolerance key in CUSTOMIZING in the foll path : Materials management ----> Logistics Invoice verification -----> Invoice Block ------> Set Tolerance limits.
For DQ, I have set 30 INR as the upper limit ( absolute value )
Documentation for the following tolerance key:
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 cost
My scenario :
Order Qty = 10 kg
Order Price = 20 INR per 1 KG.
GR Quantity = 5 kg
Invoiced Quantity = 3 KG
Next time MIRO has to be done for remaining 2 KG. But suppose we do invoice verification for 3 Nos. ie We are performing MIRO for 1 number more than what has actually been received
So, according to the above calculation,
system will calculate = 20 * (3 – ( 5 – 3 ) )= 20 * 1 = 20 INR. This 20 INR is less than the 30 INR maintained in Customizing. But I am still getting the error message " Quantity invoiced greater than goods receipt Quantity". Why is this so ? Can somebody provide some light into the issue ?

Hi all ;
If your customizing is correct , there might be other control like ABAP or anything else ..
Please check oss notes :
835073 - Enhancement of the tolerance checks
1853166 - Quantity too high, tolerance limit exceeded
786810 - MM IV: Tolerance check when you enter invoices
102350 - Incorrect tolerance check for small amounts
496357 - MRBR: Percentage check with quantity variance
1372102 - IMG documentation: Set Tolerance Limits
Also, you can benefit from document M8 messages for incoming invoices with tolerances .
Regards.
M.Ozgur Unal

F-48 exceed amount

Similar Messages

Maybe you are looking for