Delivery Tolerance limits
Dear all,
1.In case of stock item,we maintain delevary tolarance limits in Materia master (Purchse value key),where these values picks up at the time of creation of PO for that material.
2.In case of non-stockable items/services(Item category D, account assignment catogory K ),Where from,these default values for Over delivery tolerance limit,Unlimited check box,come from? During PO creation,by default (over delivery tol limit as 0% and Unlimited as checked)values are comming.If i want to change these default values, where to go and change?
Please suggest the way.
Hi,
Tolerence limit will pick from either contract or from Info record.
IF you mantain any one or both then.
1st priority from contract will pick the tol. limit.
then Info record.
SAM
Similar Messages
-
ME54N Release strategy question over delivery tolerance limits
I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
Can someone give me some insight into this ? Thanks.Hi Siva:
You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
Good luck
Z.T -
Tolerance Limits with Date and quantity
Hi Experts,
We would like to set the GR Tolerance Limits with Date and qty.
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 .Go to SPRO - Material Managemetn - LIV - Invoice Block - Set Tolerence limit.
USe company code and maintain a value for ST
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. -
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-mmHi
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 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 -
Tolerance limits at Schedule line level in PO
Hi
How to make tolerance limits at schedule line level in PO, (not at item level)
Thanks
RajuHI Raju,
In PO Delivery schedule qty tolerance is not possible.
PO delivery line itemwise tolerance only possible and also we have freezed tolerance in the line items.
Based on line item qty, We have delivery schedule given and not exceed line item qty.
Hope, you are clear.
K.Rajendran -
Dear All,
How to set the under and over delivery tolerances for MIGO.
When we create the GR wrt to PO how w can set the tolerance limits for stock and non-stock and free text items.
Please adviseAdding to replies,
In P.O item level,You can set under delivery or Over delivery tolerance % manually,based on it you can do Goods receipt.
By default you can set under & over delivery tolerance value in info record also.
For example:
For stock items, for example
If you do p.o for 100 nos,and you define under delivery tolerance of 5%,you can do goods receipt for 95 nos,
automatically p.o is closed(Delivery completed indicator is ticked)
Similarly for over delivery tolerance of 5%,you can do goods receipt for 105 nos. -
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 RegdsHi 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... -
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 - X1) "Powered by Jive Software" ....
2) 我看看有没有机会通过什么渠道反映这个问题.. -
Under /Over Delivery Tolerance with Sales Contract
Hello All,
Overview: In our current environment we are creating Sales Contracts, then a Subsequent order from the Sales contract. We change the Sales order quantity to desired amount for the time of delivery which the customer is requesting. Also in customer master (XD02) we have delivery tolerance setup for under and over.
Question: Since we have tolerance setup for the customer. At delivery time, we picked less from what the sales order originally had and complete the whole process to billing. Does the remaining quantity go back to the sales contract? Sales order is still showing "Being Processed" Or is not possible to do that with delivery tolerance setup and Sales Contracts?
Scenario 1: XD02 - Tol. Over/Under set as 5%. Unchecked box "Complete Delivery", "Partial del. Set to "Blank" and Max Partial to "9" for Customer
Created Sales Contract for quantity 500 Tons--> Created Subsequent Sales order for 25 Tons.
Delivery: Picked 22 Ton's. Recieved Message" Underdelivery tolerance of 5.0% has been exceeded".
Completed shipment and billing.
Sales order shows "being processed" and remaining qty did not go back to original Sales Contract.
Scenario 2: XD02 - Tol. Over/Under set as 5%. Checked box "Complete Delivery", "Partial del. Set to "B" and Max Partial to "1".
Created Sales Contract for quantity 500 Tons--> Created Subsequent Sales order for 25 Tons.
Delivery: Picked 22 Ton's. Recieved Message" Underdelivery tolerance of 5.0% has been exceeded". Acc. To the partial dlv. Agreement, no subsequent delivery can take place
Completed shipment and billing.
Sales order shows "Completed", but the remaining quantity did not go back to the original Sales Contract.
Is possible to have the remaining quantity to go back to the Sales Contract without going back to the Sales order and change the quantity to what was shipped. Can this be done via configuration?
Can anyone please shed some light on this.
Thank you all,
NavHi
Can this be done via configuration?
To my knowledge...definitely NO. It is not possible through configurations.
Regarding the two scenarios...you are delivering quantity less than the lower tollerance. It should not happen and if your business process demands it....there is no meaning of maintaining the tollerance limits for the customer. Since the message is a warning message, you are ignoring it and proceeding with the delivery. This message should be an error message and delivery should not be allowed when the tollerance limits are crossed.
Thanks,
Ravi -
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 -
Set up Tolerance Limits with Date and quantity for GR
Hi Experts,
We would like to set the GR Tolerance Limits with Date and qty.
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,
You can do one thing...
Activate the SLED check...
BY this when the date goes earlier or late from the expected date, then system show you the messages like:
1. Earliest delivery date is DD.MM.YY..
2. Expected delivery date was DD.MM.YY...
In std sap system, the second message is already error message...so when get late delivery then it'll not be possible to maintain the GR...
For the qty varinace, activate the quantity variance either via over/under delievery tolerances..or
Via SPRO settings...
SPRO >> MM >> LIV >> Invoice block >> check for qty tolerances and make the settings as per your requirement...
Regards
Priyanka.P -
How to default Over&under delivery tolerances into Replishement delivery ??
Hi
How to default the Over delivery and under delivery tolerances in to the replishement delivery created against the STO which has those tolerance values ??
And i should be able to do Goods receipt(GR) with over delivery quantity within the limits against the replishement delivery(I do not want to do GR against STO)
Thanks
Maruthi RamHi Jurgen,
Thanks for the link you provided.
But can't we control the overdelivery tolerance just like the under delivery for a specific combination of plants in the STO configuration.
Cheers
Maruthi.
Edited by: MARUTHI RAM on Mar 18, 2009 7:37 PM -
Over and Under Delivery Tolerance Defaults
Hi !
Is there a way to provide a default Over and Under Delivery Tolerance % at Company Code or Purchising Org level?
If yes, please let me know what the menu path is to make that setting.
Our tolerance for Over delivery is 10% standard across the board and we would rather not have to enter it separately in every Purchasing Info Record.
I understand that I could use Purch Val Keys, but we are trying to avoid that as well.
Appreciate the help!
Thanks,
Anisha.Hi anisha,
Try using this way.
SPRO-MM-PURCHASING--PURCHASE ORDER--SET TOLERANCE LIMITS FOR PRICE VARIANCE
Here u can finalize the upper and lower limits as 5%. the PO shall automatically pick up the same.
Using Purchase value keys is preferred in u r case.
SPRO- MM - PURCHASING - MATERIAL MASTER - DEFINE PURCHASING VALUE KEYS - NEW ENTRIES Define a purchasing value key which has over and under delivery tolerance as 10% in GR/IR controls
and assign this purchasing value key in the material master to which you want to allow 10% variation.
Hope this helps.
Regards,
Nani. -
Over delivery tolerance report
Hi,
I have given over delivery tolerance in PO for qty.
So while making GRN,upto tolerance,the quantity will be accepted.
Is there any report available to see the difference between the PO and GR done for PO's which has Tolerance limits?
Regardshi,
There is no seperate report for over and under del tolerance. you can create a quick qurey using SQVI and use PO table EKKO and EKPO to get ther report.
Hope this helps
Thanks,
Suresh
Maybe you are looking for
-
My iPod Touch 4th Gen won't charge?
Well I've had my iPod Touch 4th Gen since it came out it will be 2 years old in October. Yesterday I charged my iPod while listening to music. I took it of when it was charged and used a little it became half dead so I put it on my charger. I realize
-
How do I change the size of ikons and the background in Firefox??
See above
-
Mac airplay to apple tv, there is only voice,no video..
mac airplay to apple tv, there is only voice,no video..
-
HT1918 why do i see contact itunes support when i'm opening an acount on my iphone or computer?
when i'm trying to open an acount on my iphone or computer it wont open and i see the message ( PLEASE CONTACT ITUNES SUPPORT TO COMPLET THIS TRANSACTION )?? please help me to have my acount thank you
-
Purchasing Music lags...... And lags......
Hi, I use the shopping cart feature in iTunes. But I use it more for a wishlist type thing. So instead of clicking the Buy All button in the Shopping Cart, I just do them individually. But when I try to buy them, after I click buy, a warning comes up