Tolerance for AP Checks

Hi All,
Where can I go to set tolerance for vendor check payments?
Eg: If I am paying a vendor a check for $1, I want the system to put a tolerance around that and prevent me from paying a check worth that small an amount.
Thanks,
Deki

Hi
Go to FBZP, select the button Paying Company Codes you will see the field Minimum amount for outgoing payments

Similar Messages

Customer Tolerance for all open item selected in an incoming payment.

Hi Experts
I have set a tolerance of 5 $ in OBA3 to be written off to Bad Debts account. This settings are working fine when an incoming payment is entered in F-28.
My requirement is, in F-28 I enter the Document Date, Posting Date, Company Code, Currency, REF, Doc.Header Text in the document header & enter the Bank Account, Amount and Text, then instead of entering the customer account in open item selection, I selet the process open items and Select the Reference as the selection criteria and enter a list of references (for clearing a Batch of open items for different customers).
Standard tolerance functionality will check if the complete incoming document meets the specified tolerance limits set in OBA3. But I want the tolerance of 5 $ specified to be applied for all the open items selected to be cleared with the incoming payment.
I understand that tolerance will be applied when the amount entered and amount of the open items (total) is within the specified tolerance.
But is there any option which will check if each of the open item selected for processing short of 5 $ and then write off to the bad debt account specified in OBXL.
Do we have any user exit, or BADi or can we use any of the BTE functionality to achieve this.
Kindly give your valuable inputs..
Thanks in Advance.
KIM Khan.

Kim,
Did you get answer to this question? If so can you please share with me?
Thanks

Vendor Evaluation - Underdelivery Tolerance for Qty. reliability Criteria

Hi experts.
When using Underdelivery tolerance in a PO, the Evalation criteria Qty. reliability is not taking into account this tolerance and give a vendor a score based on the requested qty.
It doesn't make any sense to me, since I'm allowing the vendor to deliver up to this tolerance.
Please advice.
Thanks.

Hi,
When calculating score for quantity reliability, the Minimum delivery quantity % mentioned in customizing (Txn OMGL) is only taken into account, so that if the delivered quantity is below this then the score for the vendor will not be calculated.
The underdelivery tolerance is not checked. This is the standard functionality.
Best Regards,
Arminda Jack

Tolerance for LIV

I have a question with reference to following tolerances:
1- Tolerance key "PE" set at upper limit of 10%
2- Vendor specific tolerance set @ Auto accept + diff $ 5
                                                   Absolute upper limit $ 50
                                                   % upper limit 2%
Invoice block-
3- Small diff key "BD" $25
4- Price variance Absolute upper limit $ 5
                           % upper limit 5%
How will these tolerances work- the order? what comes first? which key supersedes the other and in what order?
In short I am trying to figure out is that the system looks at all of these 4 keys at the same time or does it look at any other way?
need help- is there any specific documentation I should look at?
Thanks
Raj

Hello
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 BW 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.
Regards

Set tolerance for Invoice confirmation

Dear Experts,
We are using SRM 550 , Classic Scenario
When we make the invoice verification process it allowed only the order price,
When I change the price to lower value we got Error Message :
Average price too low: below tolerance limit of 0.00 and ILS (Item 1)
I saw in IMG that the following errors message are set by Item
PRICE TOLERANCE     BBP_IV     069
PRICE TOLERANCE     BBP_IV     071
Now we would like to set the Upper and Lower tolerance for the Invoice ,
we set in IMG:
spro > SRM > Enterprise Buyer > Cross application basic settings > set tolerance checks.
We have set a new Tolerance Group- new entry ( it was empty)
But Tolerance Key we can not find the one for the Invoice
We have only this keys:
CF     Document Tolerances for GR
DA     VALUE OVERRUN
DQ     OVERRUN QTY IN CURRENCY AMT
LA     AMOUNT BLANKET PURCHASE ORDER
LD     TIME OVERRUN BLANKET PO
PM     OVERRUN QTY IN CRCY AMT (PO)
PP     PRICE DEVIATION
PR     PRICE VARIANCE (PO)
PZ     TIME OVERRUN (PO)
TX     TAXES (INV)
Which one is for the Invoice Verification tolerances?
Please advise where and how can we set it ?
Regards,
Moshe

Hi
PP is the tolerance key required by you.
PP: Price variance (value variance from expected value)
You only use this tolerance for invoice entry.
The variance from the expected value is checked here, based on the preceding document (purchase order price or confirmation value).
The system determines by how much each invoice item varies from the product of quantity invoiced multiplied by the order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
PR is for deviations while creating Confirmations.
Make sure you enter the tolerance key in vendor master too.
Regards
Virender Singh

Tolerances for User Id

Hi guys,
We have assigned tolerances for the MICs. For in-process inspection and final inspection (03 & 04) the production people will release and do GR. The tolerance values are not being assigned in results recording for their user ids in the production system.
If I do the same process with my user id they are assigned perfectly. I need information of the authorization objects that need to be assigned for the user ids for this problem. Please advise.
Thanks
Ram

The best method I would suggest is take screenshot by typing /NSU53 in QA32 screen for the user IDs where tolerance values are not appearing. That will give you the list of missing authorization objects if any.
Another possibility is that, check the variant setting. May possible that the tolerance column is placed at last and because of which it is not visible.
Best Regards,
Anand Rao

LIV tolerance for price variance from PO to LIV

Hi Friends,
I am finding difficulty in setting up the tolerance key for price variance from PO value to invoice value. Suppose if PO price is $100 then system should allow upto $105 with out blocking means with percentage of 5%. If it exceeds 5% system should block the invoice.
Please suggest the tolerance key to use and if any other settings required.
Thanks...
Best Regards

Hi,
Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
===================
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:
    o   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.
    o   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.
    o   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.
    o   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.
    o   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.
o   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.
o   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.
o   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).
o   LA: Amount of blanket purchase order
        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.
    o   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).
    o   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).
    o   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.
    o   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
===============================================
Best Regards,
Siva

Open sales order value for credit check need to be changed (S066)

Hi all,
I need to change open sales order value which is already there in S066 table.
Previously we had used open order value for credit check. Open order values are already updated in the S066 table.
Now we dont want to consider open order value for credit check (which is already included in the credit exposure field in FD32).
When we create sales order system is taking old open order value for credit. Now i have changed not to update open order value for credit check. Now its not updating open order value. But my issue is how to change existing or (previous) open order value for credit?
Can i change S066 table data directly to '0'. Is it advisable to chage open order value directly from this table?
Please advise me.
Regards,
Babu
Edited by: babs on May 19, 2010 4:26 PM

Hi Babs,
If you doesn't want to reflect the open order value in the structure for this order value ,If the order is not processed kindly delete the line items and the order. Then save the document. Then try to see the structure S066.. This will be modified.
If you want to modify the value then follow the below process.
Otherwise delete the line item in the order and change the pricing date and the document date. Re enter the line item again so that it will take it up the new changes.
I hope it will help.
Regards,
SK

Incoming orders in COPA not working if Sales Order blocked for Credit Check

Hi all,
We need to build a report showing all incoming sales order by entry date and/or change date (change of values or quantities later on). COPA allows to do this, but the problem is that COPA line item table is only updated if the sales order is released from credit check (VKM3). I am looking for a solution to be able to record sales orders in COPA even if they are still blocked for credit check. By doing that we will be able to report all sales orders entered from COPA and provide basis for commissions calculation to the business.
I have investigated possible COPA enhancements like COPA0005 but it doesn't seem to be used at the time of sales order save.
Thanks.

Hello ,
Thanks for the reply
As you said , the credit check in the service order is information message "Credit check (maximum percentage for ope
exceeded)" .
If you enter and come out this message then one more message will come , i.e., "The business transaction can not be carried out" detail message - System status CNOK is active (ORD XXXXXXX).
with the above message , system will not allow to do the Service order release.
In this particular case , we have done the VKM1 for the sales order to unblock the order from credit check . But again system is checking the credit check at service order (created w.r.t sales order) . we are not able to control this .
we also suggested the solution to the customer , saying removal of credit check for service orders . But customer requires credit check to happen at both the documents.

Txn for cancelled checks

Hi Friends,
Can u please suggest me the Txn used for cancelled checks in SAP .
Thanks n Regards,
S.Agarwal.

Hi
LI05     Inventory History for Storage Bin
LM55     Print Storage Bin Labels
LP22     Replenishm. Planning for Fixed Bins
LS04     Display Empty Storage Bins
LS05     Generate Storage Bins
LS06     Block Storage Bins
LS08     Block Storage Bins by Aisle
LS10     Generate Storage Bins
LS25     Display Quants per Storage Bin
LSET_BIN_COORDINATES     Maintain Storage Bins by selection
LT343XYZ     Copy Storage Bin Definition Rules
LT343XYZA     Maintain Bins by Definition Rule
LX01     List of Empty Storage Bins
LX03     Bin Status Report
LX05     Block Bins in Bl.Storage w.Time Lim.
LX15     Selection of Bins for Annual Invent.
LX16     Selection of Bins for Continuous Inv
LX40     Material Situation Prod. Storage Bin
LX41     Bin Status Report WM/PP Interface
LX45     Verification Field in Storage Bin
rwd if useful
rgds
BV

How to use multiple languages at the same time for spell checking?

I use two different languages all the time and words are mostly so different (English and Finnish) that I could have spell checking on for both languages at the same time.
Now it seem to allow to select only one language at the time and I have to switch back and fort zillion of times per day.

Thanks for the quick answer.
The Dictionary Switcher doesn't seem to work with Finnish language, it doesn't detect it at all to be one of the choices although in the Firefox context menu Languages -> Finnish/Finland is shown.
Also, if it would work, I would need to get rid of multiple EN_* langauges. I just need EN_UK or EN_US, not all 22 different EN_*.
One option would be to create a custom dictionary, which would have words from both languages. The next task is then to find out how to make this kind of custom ENFI-dictionary, which would have words from both English and Finnish languages.
Finnish may be a some kind of special case for spell checking anyway, because the support is in its separate plugin:
http://voikko.sourceforge.net/

Why can't I use my Mac Book pro for cashing checks like every one else uses their iPhone and iPad? I am a grandmother and in the past 4 years I have purchased 4 MacBook Pros and 1 iPad for my children and grand children.

I would like to be able to use my MaBook Pro for cashing checks lie the I phone and I pad. Why isn't this feature included?

This has nothing to do with Apple. As BobTheFisherman indicated, your bank needs to create an App for the Mac to do this. These types of applications tend to be limited to mobile devices as they are a bit easier to maneuver for taking photos.

Trying to spell check email, I get this: "This language is no longer available for spell checking.

Firefox does automatically check my emails like it does when I use Word Perfect. When I select spell check, I get this message: "This language is no longer available for spell checking. Please check another in the spelling options box."
When I click on the spelling options box, I get the same message. I have never changed any settings as regards to spell checking

Which language is selected if you check that via the right-click context menu > Languages in a text area?
Is that dictionary still installed and enabled?
* [[Troubleshooting extensions and themes]]
See also:
* http://kb.mozillazine.org/Spell_checking
* http://kb.mozillazine.org/Dictionaries
* [[Using the spell checker]]
You can look here for dictionaries:
* https://addons.mozilla.org/firefox/language-tools/

Change due date in receivables for credit check

Hi Sappers!!
Scenario: When SAP performs a credit check for a customer we need that pending receivables
(open items) for this customer which have a concrete payment method, don't use due date
for calculation, instead we want to use invoice date for carrying out the credit check
calculation.
Is that posible? Is there any user-exit where we can change this date to be used during
credit check control for documents which fulfill this requirement?
We don't want to change permanently the due date for this kind of documents, we only need to take another date into account when performing credit control.
Thanks so much in advance & best regards

Thanks so much for your quickly answer.
Creating a new payment term is not a valid solution because, we don't want to change any date in the financial document. We just only need to use another data only for credit check. Here you have a concrete example:
Invoice created with invoice date 01/12/2009
Payment method confirming 90 days.
Base line calculated: 01/03/2010
If we create a new sales order, this open item will not be considered exceeded because due date is still in the future.
We want to consider it as exceeded and the due date would be 01/12/2009 but only for credit check. This "new" due date must not be stored anywhere.
Thanks so much once again & best regards

Can any body tell me the transaction for budget check in SRM ?

HI,
Experts,
As i want to check the budget of a business partner / customer i am new to that can u please tell me basic information about budget check and pass the Standard transaction for budget check.
Thanks in advance,
Shabeer Ahmed

Hi    Dinesh,
Thanks for your reply and can u send me the Budget check standard transaction and related tables and how he going to check his budget.
According to me:
1    In which table Amount is maintained for BP
2   How we have check the budget.
Do u have any document related to this please forward it to me.

Tolerance for AP Checks

Similar Messages

Maybe you are looking for