Tolerance Types

I have like 12 Tolerance types..can any one explain them for me....
<u>TKy -- Description</u>
AN - -Amount for item without order reference
AP-- Amount for item with order reference
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
KW -- Var. from condition value
PS -- Price variance: estimated price
ST -- Date variance (value x days)
VP -- Moving average price variance
Can any one give some more details on it..as i have to assign the tolerance types....I know the description is given but i need some more details on this..Need help ASAP please....please

Hi
Please refer the following link , explained the each tolerence key functionality with examples.
http://help.sap.com/erp2005_ehp_02/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
Regards
Ramakrishna

Similar Messages

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

The Tolerance limit for type "1" not running in Av. Control

In my project I am unable to see the effect of Warning on budget even though Activation type 1 with tolerance limit "1" is activated for 50% of budget.
The actual cost are posted by MB1A against reservation to the activity and material reservations are created.
Although when the costs exceed more than 50% the system status shows BUDG ISBD AVAC for the said WBS.
System does give the error on reaching 100% level of cost i.e. no "3" tolerance limit is successfully running.
A reply /suggestions shall be appreciated.
Thanks
Rajeev

Hi,
We are also getting the same error message when posting from an external system.Could you please let me know if you were able to resolve it?

IMG , tolerance key assingment to Puchase requision document type

Hi Expert,
In ECC 6.0 there is option to create tolerance key in purchase requision configuration. If this tolerance key is assigned to the PR document type,while creating the PO, system issues a warning message if the PO net price is above the tolerance limit.
But in configuration there is no option to assign the tolerance key to the document type

Solved?????
I do not see it either?
Is it only working for the Public Sector Solution?
If yes it's a shame because it's a super functionality.
Thanks in advance,
Thomas

What is tolerance limit? for which type of GL accounts its required?

HI
what is tolerance limit? why it is being used? can any body give conceptual understanding? I would appreciate help?

Hi,
Tolerances are used if you want to define, for example:
- the maximum document amount the employee is authorized to post
- the maximum amount the employee can enter as a line item in a customer or vendor account
- the maximum cash discount percentage the employee can grant in a line item
- the maximum acceptable tolerance for payment differences for the employee.
Also, there are tolerances for difference postings used to (for customers, for example):
- Tolerances up to which differences in payment are posted automatically to expense or revenue accounts when clearing open items
- The handling of the terms of payment for residual items, if they are to be posted during clearing
Regards,
Eli

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

BOM in Scheduling agreement (Type LZ)

HI
I am using scheduling agreement (Type LZ) for maintaining my sales plan for a period of 4 months. (1st one month - daily & subsequent months as weekly requirements). Ii would create delivery and invoices for each supply.
Pricing previously was based on the finished product (basic price for product was available). SO there was no problem.
<u>New requirement:</u>
finished Product above - is made up of components. Now, price should be derived from components. For this I have enabled SD Bom for my finish product.
But the problem is when i use the Finish product code in scheduling agreement type LZ, the BOM doesn't explode (it explodes in other scheduling agreement types, say LP)
Clarification:
1. Is it possible to calculate price of the higher level material by summing up the components' price?, with out BOM explosion
2. Is BOM explosion possible in scheduling agreement with delivery schedule (LZ).
Note:
1. Necessary settings for item category & BOM master already in place.
2. BOM is exploding in sales order and other sheduling types, except doc type LZ.

If it is maintained as error message, it does not allow me to maintain delivery schedule more than target quantity of 100 EA. Also the overdelivery tolerance is maintained as 20 %, so it should allow me to maintain delivery schedule of 120 EA, but it does not allow me to maintain greater than target quantity of 100 EA. Please let me know your comments.

Can I "BATCH"/"Change All" Values of an Event Type in Logic 8

NOTE: This is my first leap into Logic, so please be gentle and tolerant of my lack of knowledge. I have been using Garageband since v1 and am know on '09 with all the Jam Packs.
I recently got Logic 8 for my G5 Quad to edit MIDI Files (mostly commercially produced files) and refine my GB projects.
Sometimes the MIDI programmers use variable volume (Control 7) instead of expression (control 11) to add swells to instruments, which makes it difficult to balance the instrument levels in logic/garageband as software instruments do not have the same level balance a standard MIDI values.
I can manually edit each volume event and change it to expression, but this is very time consuming, especially for instruments like a pedal steel that may have thousands of volume events in the track.
What I am hoping is that I can select a range of events between bars (highlighting everything in the range) and be able to change only the Control 7 events to Control 11 events without changing any other type of event.
Is this possible in Logic 8? If not, might there be another utility that I can use that will do this?
I suppose, if no other option is available, I could adjust the generator's volume, but that isn't as convenient or interactive as being able to use track volume to set a master level and use expression to control swells.
Any help or suggestions would be greatly appreciated.
TIA

Brilliant!!
How did you find the command? It is NOT listed in the Keyboard commands.
Also, would you know how to change the velocities in a similar fashion? i.e. A guitar track may have velocities exceeding 120, which with the Steel String Acoustic Guitar, results in a slide to the target note. I would like to change ALL velocities over 120 to 115, or reduce values over 120 by 8 to reduce them below 120.
The find similar/exact seems to go after the note values and does not consider velocity.
Many years ago, I used a PC app called Power Tracks (part of Band-in-the-Box suite) and I could define a range of values and reduce them by amount or percentage. Very light weight (resource wise), but extremely power app.
TIA

Dynamically assigning aggregation type in a matrix table

I have a matrix table that will produce multiple summary columns. These columns should not all use Sum in the Totals row at the bottom. Some will any of these to be determined at runtime: Sum, Avg, Count, Min, Max. I have a column in the
underlying dataset that will tell me which aggregation type to use and now I need some logic in the summary cell to use the correct aggregation type. I tried different variation of this:
=IIF(Fields!AgType = "Sum",   Sum(Fields!VI_Impact.Value), … next IIF statement….
And here’s the full line
=IIF(Fields!AgType = "Sum",   Sum(Fields!VI_Impact.Value), IIF(Fields!AgType = "Avg",   Avg(Fields!VI_Impact.Value), IIF(Fields!AgType = "Cnt",   Count(Fields!VI_Impact.Value), IIF(Fields!AgType
= "Min",   Min(Fields!VI_Impact.Value), IIF(Fields!AgType = "Max",   Max(Fields!VI_Impact.Value), 0)))))
I also replaced the zero at the end with another sum statement as a default if nothing else is used.
Just to keep it real simple for proof of concept, I used:
=IIF(Fields!AgType = "Sum",   Sum(Fields!VI_Impact.Value), Sum(Fields!VI_Impact.Value))
But the report gets the error:
The Value expression for the textrun ‘VI_Impact.Paragraphs[0].TextRuns[0]’ contains an error: [BC30311] Value of type ‘Microsoft.ReportingServies.ReportProcessing.ReportObjectModel.field’ Cannot be converted to ‘String’
Any idea how I can make this work?

Thanks Jason. I've put an sql script below that will create a test table and populate it with test data. I also attached an rdl file so after you run the script and load the report, all you need to do is update the report's data source
to the correct database and you will see exactly what I'm trying to do.
This report table creates a maxtrix with 4 SUM columns to the right. as you will see in the data, the column headers are named by "VA", and column "AgType" shows how the column should be aggregated. Once you run the report
and look at the data it should be easy to understand.
Thanks for any help you can offer.
DESCRIPTION: Schema Synchronization Script for Object(s) \r\n
tables:
[dbo].[zzzRptValueImpactListing]
AUTHOR: [Insert Author Name]
DATE: 11/19/2014 5:17:57 PM
LEGAL: 2013[Insert Company Name]
SET NOEXEC OFF
SET ANSI_WARNINGS ON
SET XACT_ABORT ON
SET IMPLICIT_TRANSACTIONS OFF
SET ARITHABORT ON
SET NOCOUNT ON
SET QUOTED_IDENTIFIER ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
GO
USE [VME_KP]
GO
BEGIN TRAN
GO
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
GO
IF @@ERROR<>0 OR @@TRANCOUNT=0 BEGIN IF @@TRANCOUNT>0 ROLLBACK SET NOEXEC ON END
GO
-- Create Table [dbo].[zzzRptValueImpactListing]
Print 'Create Table [dbo].[zzzRptValueImpactListing]'
GO
CREATE TABLE [dbo].[zzzRptValueImpactListing] (
[Id_Number] [int] NULL,
[Id_Name] [nvarchar](4000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[VA] [nvarchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[VI_Impact] [decimal](18, 3) NULL,
[Id_Assignees] [nvarchar](500) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[AgType] [nvarchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[Pj_Id] [uniqueidentifier] NOT NULL
GO
IF @@ERROR<>0 OR @@TRANCOUNT=0 BEGIN IF @@TRANCOUNT>0 ROLLBACK SET NOEXEC ON END
GO
ALTER TABLE [dbo].[zzzRptValueImpactListing] SET (LOCK_ESCALATION = TABLE)
GO
IF @@ERROR<>0 OR @@TRANCOUNT=0 BEGIN IF @@TRANCOUNT>0 ROLLBACK SET NOEXEC ON END
GO
IF @@TRANCOUNT>0
COMMIT
SET NOEXEC OFF
DESCRIPTION: Synchronization Script for Object(s)
Tables:
[dbo].[zzzRptValueImpactListing]
AUTHOR: [Insert author name]
DATE: 11/19/2014 5:50:25 PM
LEGAL: 2014 [Insert company name]
SET NOEXEC OFF
SET ANSI_WARNINGS ON
SET XACT_ABORT ON
SET IMPLICIT_TRANSACTIONS OFF
SET ARITHABORT ON
SET NOCOUNT ON
SET QUOTED_IDENTIFIER ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
GO
BEGIN TRAN
-- =======================================================
-- Synchronization Script for Table: [dbo].[zzzRptValueImpactListing]
-- =======================================================
Print 'Synchronization Script for Table: [dbo].[zzzRptValueImpactListing]'
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (5, N'Change from double tape to liquid glue', N'Prod Cost', CONVERT([decimal](18, 3),-0.050), N'Philipp Bart
Steve Stewart', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (7, N'Position of NTC out of contact area', N'Complexity', CONVERT([decimal](18, 3),-170.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (7, N'Position of NTC out of contact area', N'Mrk Conf', CONVERT([decimal](18, 3),8.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (8, N'Change type of patches', N'Mrk Conf', CONVERT([decimal](18, 3),7.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (9, N'Reduce winding turns for harness', N'Mrk Conf', CONVERT([decimal](18, 3),8.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (9, N'Reduce winding turns for harness', N'Relblty', CONVERT([decimal](18, 3),1.500), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (11, N'Use fix sizes of carrier material rolls', N'Prod Cost', CONVERT([decimal](18, 3),-0.310), N'Marc Pauwels', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (11, N'Use fix sizes of carrier material rolls', N'Prod Cost', CONVERT([decimal](18, 3),-0.310), N'Marc Pauwels', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (12, N'Cold pressing process for laying or needle technology', N'Prod Cost', CONVERT([decimal](18, 3),0.080), N'George Padvorac', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (12, N'Cold pressing process for laying or needle technology', N'Relblty', CONVERT([decimal](18, 3),0.500), N'George Padvorac', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (13, N'Liquid cold gluing instead of hot processing', N'Complexity', CONVERT([decimal](18, 3),-100.000), N'Philipp Blattert', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (13, N'Liquid cold gluing instead of hot processing', N'Mrk Conf', CONVERT([decimal](18, 3),8.000), N'Philipp Blattert', N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (14, N'Confidential', N'Prod Cost', CONVERT([decimal](18, 3),-0.020), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (16, N'Decrease positioning tolerances to reduce distance between parts', N'Complexity', CONVERT([decimal](18, 3),-40.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (16, N'Decrease positioning tolerances to reduce distance between parts', N'Prod Cost', CONVERT([decimal](18, 3),-0.060), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (17, N'Control and reduce amount of thermoactive glue', N'Prod Cost', CONVERT([decimal](18, 3),-0.030), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Complexity', CONVERT([decimal](18, 3),-50.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Complexity', CONVERT([decimal](18, 3),-50.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Mrk Conf', CONVERT([decimal](18, 3),6.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Mrk Conf', CONVERT([decimal](18, 3),6.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Prod Cost', CONVERT([decimal](18, 3),-0.040), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (18, N'Pull off force harness: reduce spec', N'Prod Cost', CONVERT([decimal](18, 3),-0.040), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (23, N'Simplify and stabilize contact process', N'Mrk Conf', CONVERT([decimal](18, 3),6.000), NULL, N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (23, N'Simplify and stabilize contact process', N'Prod Cost', CONVERT([decimal](18, 3),-0.320), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (23, N'Simplify and stabilize contact process', N'Relblty', CONVERT([decimal](18, 3),1.500), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (24, N'Decrease positioning tolerances to reduce distance between parts', N'Prod Cost', CONVERT([decimal](18, 3),-0.210), N'Mark Powel
Philipp Bart', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (25, N'Separate extension of carrier material, than assembly by gluing', N'Complexity', CONVERT([decimal](18, 3),-20.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (25, N'Separate extension of carrier material, than assembly by gluing', N'Prod Cost', CONVERT([decimal](18, 3),-0.230), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (26, N'Use higher emission foam/fleece where possible', N'Mrk Conf', CONVERT([decimal](18, 3),7.000), N'Craig Squires
Stacy Johnson', N'Avg', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (27, N'Reduce material variance fleece: width, composites, glue or not,', N'Complexity', CONVERT([decimal](18, 3),-5.000), N'Stacy Johnson', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (28, N'Confidential', N'Relblty', CONVERT([decimal](18, 3),4.000), NULL, N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (29, N'Reduce material variance tape: width, composites', N'Complexity', CONVERT([decimal](18, 3),-3.000), N'Steve Stewart', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (29, N'Reduce material variance tape: width, composites', N'Prod Cost', CONVERT([decimal](18, 3),-0.350), N'Steve Stewart', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
INSERT INTO [dbo].[zzzRptValueImpactListing] ([Id_Number], [Id_Name], [VA], [VI_Impact], [Id_Assignees], [AgType], [Pj_Id]) VALUES (29, N'Reduce material variance tape: width, composites', N'Relblty', CONVERT([decimal](18, 3),3.000), N'Steve Stewart', N'Sum', '47c9efba-f25e-4ffe-be66-5c5e7f3a3e18')
GO
-- TRANSACTION HANDLING
IF @@ERROR<>0 OR @@TRANCOUNT=0 BEGIN IF @@TRANCOUNT>0 ROLLBACK SET NOEXEC ON END
GO
IF @@TRANCOUNT>0
COMMIT
SET NOEXEC OFF
GO
Here's the code for the rdl file:
<?xml version="1.0" encoding="utf-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<Body>
<ReportItems>
<Tablix Name="matrix1">
<TablixCorner>
<TablixCornerRows>
<TablixCornerRow>
<TablixCornerCell>
<CellContents>
<Textbox Name="textbox3">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>#</Value>
<Style>
<FontWeight>Bold</FontWeight>
<Color>#054974</Color>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Center</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>textbox3</rd:DefaultName>
<ToolTip>Idea Number</ToolTip>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>Solid</Style>
</Border>
<BackgroundColor>#fafafa</BackgroundColor>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixCornerCell>
<TablixCornerCell>
<CellContents>
<Textbox Name="Textbox13">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>Idea</Value>
<Style>
<FontWeight>Bold</FontWeight>
<Color>#054974</Color>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Left</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Textbox13</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>Solid</Style>
</Border>
<BackgroundColor>#fafafa</BackgroundColor>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixCornerCell>
<TablixCornerCell>
<CellContents>
<Textbox Name="Textbox1">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>Assignees</Value>
<Style>
<FontWeight>Bold</FontWeight>
<Color>#054974</Color>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Left</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Textbox1</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>Solid</Style>
</Border>
<BackgroundColor>#fafafa</BackgroundColor>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixCornerCell>
</TablixCornerRow>
</TablixCornerRows>
</TablixCorner>
<TablixBody>
<TablixColumns>
<TablixColumn>
<Width>0.95in</Width>
</TablixColumn>
</TablixColumns>
<TablixRows>
<TablixRow>
<Height>0.3in</Height>
<TablixCells>
<TablixCell>
<CellContents>
<Textbox Name="textbox2">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Sum(Fields!VI_Impact.Value)</Value>
<Style>
<Format>#,###.###</Format>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Right</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>textbox2</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<TopBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</TopBorder>
<BottomBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</BottomBorder>
<LeftBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</LeftBorder>
<RightBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</RightBorder>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>4pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
<DataElementOutput>Output</DataElementOutput>
</TablixCell>
</TablixCells>
</TablixRow>
<TablixRow>
<Height>0.25in</Height>
<TablixCells>
<TablixCell>
<CellContents>
<Textbox Name="VI_Impact">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Sum(Fields!VI_Impact.Value)</Value>
<Style>
<FontWeight>Bold</FontWeight>
<Format>#,###.###</Format>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Right</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>VI_Impact</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<TopBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</TopBorder>
<BottomBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</BottomBorder>
<LeftBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</LeftBorder>
<RightBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</RightBorder>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>4pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
<DataElementOutput>Output</DataElementOutput>
</TablixCell>
</TablixCells>
</TablixRow>
</TablixRows>
</TablixBody>
<TablixColumnHierarchy>
<TablixMembers>
<TablixMember>
<Group Name="matrix1_VA">
<GroupExpressions>
<GroupExpression>=Fields!VA.Value</GroupExpression>
</GroupExpressions>
</Group>
<SortExpressions>
<SortExpression>
<Value>=Fields!VA.Value</Value>
</SortExpression>
</SortExpressions>
<TablixHeader>
<Size>0.3in</Size>
<CellContents>
<Textbox Name="VA">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Fields!VA.Value</Value>
<Style>
<FontWeight>Bold</FontWeight>
<Color>#054974</Color>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Right</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>VA</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>Solid</Style>
</Border>
<BackgroundColor>WhiteSmoke</BackgroundColor>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>4pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
<DataElementOutput>Output</DataElementOutput>
<KeepTogether>true</KeepTogether>
</TablixMember>
</TablixMembers>
</TablixColumnHierarchy>
<TablixRowHierarchy>
<TablixMembers>
<TablixMember>
<Group Name="Id_Pj_Id">
<GroupExpressions>
<GroupExpression>=Fields!Pj_Id.Value</GroupExpression>
</GroupExpressions>
</Group>
<SortExpressions>
<SortExpression>
<Value>=Fields!Id_Number.Value</Value>
</SortExpression>
</SortExpressions>
<TablixMembers>
<TablixMember>
<Group Name="matrix1_Id_Number">
<GroupExpressions>
<GroupExpression>=Fields!Id_Number.Value</GroupExpression>
</GroupExpressions>
</Group>
<SortExpressions>
<SortExpression>
<Value>=Fields!Id_Number.Value</Value>
</SortExpression>
</SortExpressions>
<TablixHeader>
<Size>0.4in</Size>
<CellContents>
<Textbox Name="Id_Number">
<CanGrow>true</CanGrow>
<CanShrink>true</CanShrink>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Fields!Id_Number.Value</Value>
<Style />
</TextRun>
</TextRuns>
<Style>
<TextAlign>Center</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Id_Number</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>Solid</Style>
</Border>
<BottomBorder>
<Color>LightGrey</Color>
</BottomBorder>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
<TablixMembers>
<TablixMember>
<Group Name="matrix1_Id_Name">
<GroupExpressions>
<GroupExpression>=Fields!Id_Name.Value</GroupExpression>
</GroupExpressions>
</Group>
<SortExpressions>
<SortExpression>
<Value>=Fields!Id_Name.Value</Value>
</SortExpression>
</SortExpressions>
<TablixHeader>
<Size>4.81979in</Size>
<CellContents>
<Textbox Name="Id_Name">
<CanGrow>true</CanGrow>
<CanShrink>true</CanShrink>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Fields!Id_Name.Value</Value>
<Style />
</TextRun>
</TextRuns>
<Style />
</Paragraph>
</Paragraphs>
<rd:DefaultName>Id_Name</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<TopBorder>
<Style>Solid</Style>
</TopBorder>
<BottomBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</BottomBorder>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
<TablixMembers>
<TablixMember>
<TablixHeader>
<Size>1.33333in</Size>
<CellContents>
<Textbox Name="Id_Assignees">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>=Fields!Id_Assignees.Value</Value>
<Style />
</TextRun>
</TextRuns>
<Style />
</Paragraph>
</Paragraphs>
<rd:DefaultName>Id_Assignees</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<TopBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</TopBorder>
<BottomBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</BottomBorder>
<LeftBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</LeftBorder>
<RightBorder>
<Color>LightGrey</Color>
<Style>Solid</Style>
</RightBorder>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
</TablixMember>
</TablixMembers>
<DataElementOutput>Output</DataElementOutput>
<KeepTogether>true</KeepTogether>
</TablixMember>
</TablixMembers>
<DataElementOutput>Output</DataElementOutput>
</TablixMember>
<TablixMember>
<TablixHeader>
<Size>0.4in</Size>
<CellContents>
<Textbox Name="Textbox35">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value />
<Style />
</TextRun>
</TextRuns>
<Style>
<TextAlign>Center</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Textbox35</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
<PaddingBottom>2pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
<TablixMembers>
<TablixMember>
<TablixHeader>
<Size>4.81979in</Size>
<CellContents>
<Textbox Name="Textbox36">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value />
<Style>
<FontWeight>Bold</FontWeight>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Right</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Textbox36</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>4pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
<TablixMembers>
<TablixMember>
<TablixHeader>
<Size>1.33333in</Size>
<CellContents>
<Textbox Name="Textbox6">
<CanGrow>true</CanGrow>
<KeepTogether>true</KeepTogether>
<Paragraphs>
<Paragraph>
<TextRuns>
<TextRun>
<Value>Totals</Value>
<Style>
<FontWeight>Bold</FontWeight>
</Style>
</TextRun>
</TextRuns>
<Style>
<TextAlign>Right</TextAlign>
</Style>
</Paragraph>
</Paragraphs>
<rd:DefaultName>Textbox6</rd:DefaultName>
<Style>
<Border>
<Color>LightGrey</Color>
<Style>None</Style>
</Border>
<VerticalAlign>Middle</VerticalAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingRight>4pt</PaddingRight>
<PaddingTop>3pt</PaddingTop>
<PaddingBottom>3pt</PaddingBottom>
</Style>
</Textbox>
</CellContents>
</TablixHeader>
</TablixMember>
</TablixMembers>
</TablixMember>
</TablixMembers>
<KeepWithGroup>Before</KeepWithGroup>
</TablixMember>
</TablixMembers>
</TablixMember>
</TablixMembers>
</TablixRowHierarchy>
<RepeatColumnHeaders>true</RepeatColumnHeaders>
<RepeatRowHeaders>true</RepeatRowHeaders>
<DataSetName>DataSet1</DataSetName>
<Top>0.30375in</Top>
<Height>0.85in</Height>
<Width>7.50312in</Width>
<Style />
</Tablix>
</ReportItems>
<Height>1.845in</Height>
<Style />
</Body>
<Width>8.42925in</Width>
<Page>
<PageHeight>8.5in</PageHeight>
<PageWidth>14in</PageWidth>
<LeftMargin>0.25in</LeftMargin>
<RightMargin>0.25in</RightMargin>
<TopMargin>0.25in</TopMargin>
<BottomMargin>0.25in</BottomMargin>
<Style />
</Page>
<AutoRefresh>0</AutoRefresh>
<DataSources>
<DataSource Name="VEMasterDataSource">
<DataSourceReference>VEMasterDataSource</DataSourceReference>
<rd:SecurityType>None</rd:SecurityType>
<rd:DataSourceID>c76f7aa3-8f20-4495-a1bf-0b7a2ede98e3</rd:DataSourceID>
</DataSource>
</DataSources>
<DataSets>
<DataSet Name="DataSet1">
<Query>
<DataSourceName>VEMasterDataSource</DataSourceName>
<CommandText>select * from zzzRptValueImpactListing</CommandText>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
</Query>
<Fields>
<Field Name="Id_Number">
<DataField>Id_Number</DataField>
<rd:TypeName>System.Int32</rd:TypeName>
</Field>
<Field Name="Id_Name">
<DataField>Id_Name</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="VA">
<DataField>VA</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="VI_Impact">
<DataField>VI_Impact</DataField>
<rd:TypeName>System.Decimal</rd:TypeName>
</Field>
<Field Name="Id_Assignees">
<DataField>Id_Assignees</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="AgType">
<DataField>AgType</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Pj_Id">
<DataField>Pj_Id</DataField>
<rd:TypeName>System.Guid</rd:TypeName>
</Field>
</Fields>
</DataSet>
</DataSets>
<Language>en-US</Language>
<ConsumeContainerWhitespace>true</ConsumeContainerWhitespace>
<rd:ReportUnitType>Inch</rd:ReportUnitType>
<rd:ReportID>86e382ea-6e9e-46b0-a5c1-7bf67abfdcf5</rd:ReportID>
</Report>

Error while doing MIRO-Overflow for arithmetical operation (type P) in prog

Hi ,
I am getting the error while doing the MIRO as below-
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          20.05.2009 10:07:03
Short text
     Overflow during the arithmetical operation (type P) in program "SAPLMRMC".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMRMC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
      caught in
     procedure "MRM_AMOUNT_QUANTITY_PROPOSE" "(FUNCTION)", nor was it propagated by
      a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
Please let me know how can this be removed.

Hi,
There can be some problem with tolerances set in the customizing.
In my case, I was getting this error because of delivery date variance. The difference between delivery date maintained in PO and invoice date was huge and hence the multiplication of price of PO and difference of delivery date was huge and that was the reason for error.
Similarly in your case also, there will be some tolerance limit problem.
Please check your tolerance limits set in customizing.
Regards,
Mihir Popat

PR tolerance key

Dear All
Where can I assign the PR tolerance Keys to the Document types, pl explain how the system will give error message in PO if price is exceeds than PR tolerance Price. what are all the configuration settings required
Regards
Ramesh B

Hi
In standard SAP it may not be activated. You need to use public sector management. You can see it in below customization.
spro>public sector management->Functions for US federal government->integration->Materials management------> document to document tolerence.
Here you can assign PR document type and tolerance.
Regards
Antony

Tolerance limits for contract

Hi all,
   Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
      it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendra

Hi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
        Ramesh

Tolerance limits & Number ranges

1. What is tolerance limits ? Why we need to use it ? What are the steps to configure tolerance limits ?
2. What is number ranges ? How to create number ranges ?

Hi,
IN PO tollerence limit:
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.
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.
MIRO Tolerence limit: OMR6
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.
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.
SAM

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 Purchase Requisition and Purchase Order

Hi there
I see there is some new functionality in ERP6 to control the price difference between the requisition and the order. According to the documentation one needs to set up a tolerance key and then set the tolerance limits for price price variance. Thereafter one needs to set the tolerance key on the document type. I have looked in the document type and I can't seem to find any place in the config to set up or assign the tolerance key to it. Has anyone tried this and how would I assign the tolerance key to the document type?
Thanks
Vinesh

Aroop thanks for your reply.
My scenario is not the same as in 3rd party processing. In fact my scenario is make to order and even repairs of other companies machinery. Now what we are trying to achieve is lets say in the repair or in production of the customers machinery or service, MM needs to make a purchase for a part or tool etc. That in itself has a price. Meaning our purchase mm dept has to pay the vendor for the purchase made and in return we need to charge our customer for that purchase. So we would like for the price of the purchase order come in our sales order condition type as a surcharge.
We were able to fetch the price of the production order automatically thru condition type EK02.
We would like to do the same from purchase order.

Tolerance Types

Similar Messages

Maybe you are looking for