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

Similar Messages

Maintain tolerance limits in the Tolerance key

Hi,
Could any one help me how to maintain these Tolerance limits in the Tolerance key. This is an error I receive while creating a PO.
Best Regards,
Sridhar.k

What is the Error Mesaage no you are getting??
Solution is as Follows
Set Tolerance Limits for Price Variance
In this step, you define the tolerance limits for price variances.
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options <b>Environment -> Define Attributes of System Messages.</b>
Activities
Maintain the tolerance limits for each tolerance key per company code
Regards
Biswajit

IR during the invoice creation moment - TAXBRA

Gentlemen, good afternoon,
We are using the TAXBRA. IS necessary to make the IR is retained in the issuance of the note. Along with the FI consultant we did this parameter did not work. The ISS has the same characteristics (retained in the issuance of the note) worked properly.
We created the category, assign a code, we associate the category for the company and IRW6 condition, we record in VK11 for this condition, we fixed J_1BTXWITH in aliquots and associate with the master data.
Another important detail, the value of IR tb is not being transferred to the bill, although we have configured it in SD Tax Values option.
As the accumulation of SAP note made no mention of IR in the issuance of the note, just in
payment, I wonder if anyone has gone through this problem before and what is the procedure to be adopted?
Thanks!
Fábio Justo

Hi Everyone
Thanks a lot for your responses.
As time was running out the only option was to delete the line item with "0" qty and value (item cat. tatx) at the table level. Once deleted there was no problem in creating excise invoice using tcode "JIIIN" wrt commercial invoice.
Though this is not SAP recommended best business practice, this option had to be taken or else we would not have been able to open the MM posting periods (mmpv) for the next month without closing all the entries for the previous month.
And if we do not open the mm posting periods we cannot goods issue for the next month.
Thanks & regards
satish

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 Value tolerances based on the Purchase Order type..

Hi Gurus,
Can anyone please tell me if there is a way to assign the variance (tolerance limit) to the Invoice document based on the Purchase Order? What I want to do is that when the Invoice is posted in the system, the system should be able to check the document type of the Purchase Order and then based on that the tolerance limits should be applied on the Invoice. for example PO document type NB- tolerance for Invoice plus/ minus 10%, Document type FO- tolerance limit plus/minus 5%.
I know we can do it based on the Vendor but we use the same vendors for a number of purposed ( a number of PO types)hence can use that.
Thanks in advance
Anoop

Hi,
Check on it:-
Purchase Order Tolerance
http://wiki.sdn.sap.com/wiki/display/ERPSCM/MM-IV-LIV-CRESetTolerancesforIncoming+Invoice
pherasath

How to Debug the Driver Pgm and Smartform while Invoice Creation(VF01)

Hello All,
I've configured the Driver Pgm and Smart Form in NACE for the output type RD00. I would like to debug the Driver Pgm and Smartform while creation of invoice using VF01. I've set the break points in the Driver Pgm and Smart form, but its not taking me to there while creating an Invoice using VF01.
Once the Invoice created, If I go thru the VF02/VF03 to see the output, I'm able to debug.
Please help me to debug the Driver Program and Smartform during the Invoice Creation.
I've configured the following objects in NACE:
Program ZDRIVER_PGM_INVOICE_SMARTFORM
Form Routine ENTRY
PDF/Smartform Form ZINVOICE(Smartform)
Thanks in Advance!
Anil S.

Moderator message - Welcome to SCN.
But please read Please read "The Forum Rules of Engagement" before posting! HOT NEWS!! and How to post code in SCN, and some things NOT to do... before posting. In particular, asking the same question multiple times is not allowed.
Thread locked
Rob

Pricing date for the tax condition type should be invoice creation date

HI Folks,
As per the current design taxes conditions are determining based on the Service rendered date which is similar to the GI date and pricing type is G in copy control .
New requirement is taxes should calculate based on the Invoice creation date in the invoice.in order to acheive the solution i have customized the tax related condition type functionality "pricing date" as KOMP-ERDAT but still system calcualting the taxes based on the service rendered date and same also writing in the invoice also.
pLease help me out what need to be configured here to acheive the solution.
Regards,
Ram.

Hello XYZ,
As you said the tax is calculated in Taxware system, i think taxware system is configured to calculate the taxes based on the "service rendered date". That is the reason why even you have changed the pricing date to be billing date for condition type XR1 taxware is not behaving as you expected.
You have two options.
1. Invocie creation date/ blling date is available in the structure "TAX_CAL_ITEM_IN00".If it is available in the structure ask the Taxware team to make changes in their system to consider that field value instead of the service rendered date.
2. Alternatively you can over write the filed which contains the service rendered date value with the value of billing date. This way no changes required in Taxware system. You can do that in cusotmer exit "EXIT_SAPLFYTX_USER_001" include ZXFYTU03 .
Based on my exeperince i think the consistant approach would be going with option 1 . Please revert if you need furhter information on the same
Thanks,
Srini
Edited by: srini vasarao on Jul 14, 2011 12:02 PM

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

Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hai
for quantity tolerence limit u can do it while creating P O in item details-->delivery tab.
for date go to SPRO-->mm>purchasing->material master> define purchase value key>in that st.del.time var here it wil compare the dates and shows how much deviation is occuring for GR date
configure messages in SPRO-->mm>environment data--> define attributes of system messages
hope it may help u
regards
chandrasekhar

Regarding invoice Creation

Hi All-
Please help with the below situation.
sales order is created.
There are two line items exist in sales order.
line item 20 is a sub item for lineitem 10.
Lie item 10 item category is "ZABC"
Line item 20 item category is :ZCBA"
when we check the item category details in config by going T code VOV7 ,
Item category ZABC has Billing Plan type (Periodic Billing).
and Billing relavance indiacator is "I"( Orfder relevant billing -Biiling Plan)
For Item category ZCBA billing plan was not set.
Billing relevance set as "B"(relevant for order related billing :status according to order quantity)
Both line items are not relevant for delivery as it was set in the respective item categories.
So when i create a billing by going to VF01 (order reference) , Invoice got split in two invoices.
Now the requirement is to create a single invoice.
I have checked in copy control routines but not found any thing related to spliiting the invoice with some selection criteria.
can any one tell me how to identify that why the invoice got split ??
Thanks in advance.

Please check the copy control routines from sales order to invoices. there might be some programming present in the routines that makes it do this. Also checking the invoice creation log helps to determine the reason behind the split.

GR Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hi,
GR tolerance limits can be set based on the quantity only .It is configuration settings .
MM-->Inventory Management-->Inventory Management and physical Inventory --->set tolerance limit/
Following are the standard settings:
B1 ( order price quantity variance with error message): 50 %
B2 (order price quantity variance with warning): 20 %
VP (variance from moving average price) 25 %
In case of dates, the tolerance limit settings based on delivery date can be achived by using user exists or create a Z t.code goods receipt copying standard one & write a code to apply your logic while you do the GR.
Thanks,
AMIT

GR tolerance Limits

Hi,
We would like to set the GR Tolerance Limits in the Configuration level.
In Transaction Code OMC0, if we set the tolerance limits for B1 and B2 how does the system works during Goods Receipt.
Thanks
Ravi

Hi,
GR tolerance limits are as follows:
B1 - Order qty variance (GR) error message.
B2 - Order qty variance (GR) warning message.
The GR tolerance is totally depends on the tolerance limits maintains against each tolerance key (B1 & B2)
Thanks,
AMIT

PO Collaboration : Invoice Creation Type field

Hello,
The Invoice Creation Type field in the SNC Web UI is always "Invoice Creation not allowed" irrespective of the settings to the Master Data / Transaction Data.
Given below are the settings I ve maintained
ECC System:
PO -> Item Details -> Invoice Tab:
Inv. Receipt Indicator - Checked
GR-Bsd IV - Checked / Unchecked
SNC System:
Vaildation Checks - Tried both these settings:
1. PO_INVOICE_CREATION - Active
    PO_INVOICE_DATA_ASSIGN - Active
    PO_INVOICE_RELATED_TO_PO_OR_ASN - Inactive
2. PO_INVOICE_CREATION - Inactive
    PO_INVOICE_DATA_ASSIGN - Active
    PO_INVOICE_RELATED_TO_PO_OR_ASN - Active
Infact, I am not able to see the Invoice tab itself in the PO details screen in SNC Web UI.
Note : I am using the Orders.Orders05 Idoc for sending the PO from ECC to SNC system.

Hi Bharath
Your settings are fine
Please do the following checks
If you use IDocs of type ORDERS.ORDER05, SAP SNC can instead read the data for these fields from a reference document, such as a contract, that has previously been transferred via the Core Interface (CIF).
In your PO you would have referenced a contract/agreement, Please check whether it is CIFed or not
Also before CIFING do implement these notes
1053121 & 828912
Now when you send the ORDERS idoc, The RON xml reads this data and puts in structure
<FollowUpInvoice>
<RequirementCode>01</RequirementCode>
<GoodsReceiptBasedInvoiceIndicator>TRUE</GoodsReceiptBasedInvoiceIndicator>
<CustomerSelfBillingIndicator>FALSE</CustomerSelfBillingIndicator>
<ProductTaxationCharacteristicsCode>V1</ProductTaxationCharacteristicsCode>
</FollowUpInvoice>
Irrespective, whether you create invoice for ASN or PO, the tab should be visible as Nikhil rightly mentioned
In SAP SNC , Controlling Invoice Creation for POs is done by FollowUpRequirementCode as mentioned above
Now since you are using ORDERS, you need to check you SA or Contract in Item Details Tab
the following fields need to be checked "IR" in both cases and In Header Details Field "Invoicing Party"
Also during creation of PO, make sure you dont check Unlimited Overdelivery in item delivery tab and even in your reference document.
Now after implementing above two notes reCIF and try creating PO, It will work
Please do mention whether you are able to see the above structure in your RON xml in SCM side and what details???
Best Regards
Vinod

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

Invoice verification tolerance limits

Hi
what are tolerance limits in invoice verification
thanks

Hi
Find below the tolerance keys for invoice
AN
AP
BD
BR
BW
DQ
DW
KW
PP
PS
ST
VP

Tolerance limits in the invoice creation

Similar Messages

Maybe you are looking for