Tolerance Limit for Price Variance (Purchase Order)

Hello,
Business Case :
Final users require a specific tolerance limit rate for Price variance in Freight services POs.
We have a current rate set up at Company level
--> standard customizing (MM / Purchasing / Purchase order / Set tolerance limit for Price variance)
Do you know any way to set up diffferent tolerance limit depending on the purchasing flow ? Vendor level for example ?
thanks for your time.
regards,

Thanks for your reply.
What do you mean by "syestem look for noramal quantity variance from info record" ?
P.I.R only conatins under and over delivery tolerance, but nothing related to price variance between GR and Invoice.
I'm looking for a customizing in order to have a Tolerance limit for Price variance at another level than Company.
At vendor level for example ?
Do you confirm there is no standard customizing ?
Any user exit available ?
thanks
regards

Similar Messages

  • Tolerance Limit for quantity in Purchase Order

    How can i set tolerance limits for amounts and quantities for purchase orders?
    Please respond,
    Best Regards,
    AI.

    Hi,
    Please tell me that where I have to do settings according to my requirements,
    either in
    SPRO->Materials ManagementPurchasingPurchase Order--Set Tolerance Limits for Price Variance
    or
    SPRO->Materials ManagementInventory Management and Physical InventoryGoods Receipt--Set Tolerance Limits ??
    Best Regards,
    AI.

  • PO Tolerance Limit for Price Variance

    All,
    For the key PE I have set Upper Limit for Percentage Check Limit to 0.01%.  At what point is the tolerance limit check?  Is it at PO creation or some other point?
    Thanks,
    Sean

    The related error message appears at the time of PO creation. It will prevent you from creating the PO with a price that is ourside the allowed tolerance value
    PE tolerance limits defines the allowed variation in price between the PO price and that of material price stored in the material master as standard price. The standard price is the output of the standard costing process

  • Set Tolerance Limits for Price Variance when PO-based Purch.Requisition

    We must garanty that Price from Purch.Requisition will be the same at PO.
    IF some variance occur a error messag must be sent to user and PO could not be saved.
    I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
    Reading the help of customizing it mean the system consists what we need..
    I have created tolerance limit NB, and set limits for all checks as 0,01.
    When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
    The help mention that after create tolerance limit we must set this tolerance by document type..but I didn’t find this field at customzing
    Does anyone can help me ?
    See the help on customizing below…
    Set Tolerance Limits for Price Variance
    In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
    You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
    When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
    Note
    You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
    To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
    Requirements
    The tolerance key must be defined in step Define Tolerance Key.
    Activities
    1. Define tolerance limits for each tolerance key.
    2. Define the tolerance key in step Define Document Types.
    Thx  and best regards,
    Ale

    HI
    SET   TOLERANCE  LIMITS  FOR PURCHASE  REQUISITION  UNDER THE  DEFINE  DOCUMENTS   FOR PR
    AFTER  SETTING  TOLERANCE  LIMITS  WHILE  CREATING  PURCHASE  U  WILL   GET  BASED ON  TOLERANCE  LIMITS  THERE   FOUR   WAYS  TO  SET  TOLERANCE  LITS 
    1
    ABSOLUTE VALUE
    2
    PERCANTAGE
    3
    TOTAL  PO  VALUE
    4
    QUANITY  BASED  PRICE  PER  UNIT
    OK  BYE

  • Set Tolerance Limits for Price Variance for PR missing from SPRO

    I'm looking into setting up tolerance limits for price variance at the PR level. But when i navigate here:
    SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance
    I'm not seeing that available in SPRO. It's available for PO's but not PR's. We want to be able to set tolerances on the PR to be applied to the PO for non stock items (material master). Please advise

    Hi,
       There is no standard configuration option to set the tolerance limit at PR level. You may set the tolerance limit for PO and control the price change. If you want the same functionality at PR level, then you have to go for development. Please check whether the BAdI: ME_PROCESS_REQ_CUST can fulfill your requirement. You may set the tolerance limit in OLME - PO - Set Tolerance Limits for Price Variance itself and write the logic in the BAdI to check the price variance in PR based on the same configuration (table T169G and similar).
       You may check the similar thread: PR VS PO Price Tolerance
    Regards,
    AKPT

  • Tolerance limit for Components in Process Order

    Dear Friends,
    As we can provide underdelivery / overdelivery tolerance for GR of process order, likewise is it possible to provide tolerance for BOM components in process order?
    The requirement is like that confirmation should be allowed with GI done within + / - 5 % of BOM qty in process order. Is it possible to cater this requirement with any exit / BAdi?
    Kindly help with your valuable inputs.
    Thanks in advance.
    Regards,
    Tejas

    Dear,
    Thanks for your prompt reply. Actually I have been already working on this exit only.But me & my technical fellow are stuck up for build logic for tolerance limit. It is working to restrict confirmation till GI has been done. But we are unable to give provision of tolerance limit for GI with this exit.
    Can you pls share more details about writing logic for it?
    Regards,
    Tejas

  • Tolerance Check for Price Variance is not working

    Hello,
    In SRM 5.0 IMS we have configured a tolerance group with tolerance Key ‘PP’ to allow Price Variance while Invoice entry.
    We have assigned this tolerance group to the user via attribute “TOG” in the organizational structure (Transaction Code: PPOMA_BBP)
    The user to whom this tolerance group is assigned is logged on into the system and created an invoice in the system with the higher amount as compare to the PO. This difference of price is very well within the tolerance limit configured in the system, but still it gives the following errors:
    •     Average price too high: Tolerance limit of 0.00 and USD exceeded  (Item 1)
    •     Value too high (tolerance limit of 0.00 and USD exceeded)  (Item 1)
    It’s not checking the tolerance limit assigned to the user through tolerance group.
    But the same works when we assign this to vendor group, but this we don't want.
    We want the system to check the tolerance group assigned to the user.
    Please suggest the solution to reslove the above errors.
    Thanks
    Sarabjeet

    Hi,
    Priority of tolerances is  PO tolerance limit,  TOG tolerance grp. for User, TOG tolerance grp. for Vendor (if user not logged on). Even absolute tolerance limit always has priority over percentage limit.
    In your case, you need to check PO tolerance first then TOG for user.
    regards,
    rahul

  • Tolerance limit for GI against production order

    HI
    Is there any standard functionality of having tolerance limits at Goods issue level - against the production order?
    Just like GR.
    or can we make this functionality using any Exits?
    -ashok

    Dear,
    Rstriction of excess goods issue against production order is not possible in standard setting.
    For achiving this you have to go for User exit.
    The logic should be
    In MIGO check mvt. type 261
    Pass the order through table RESB and select all the components with quantity.
    Capture the header material of order and use this as input along with the order creation date, plant and BOM application to explode function module CS_BOM_EXPLOSION.
    This will give you the BOM components which were valid at the time of order creation.
    Now compare these BOM components with the components from RESB with quantity.
    Here conditions will come in picture
    If quantity is exactly matching then GI will be possible
    or if you want to keep tolerance limit say for 10% then accordingly you can map the condition.
    Regards,
    R.Brahmankar

  • LIV tolerance for price variance from PO to LIV

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

    Hi,
    Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
    ===================
    Set Tolerance Limits
        In this step, you specify the tolerance limits for each tolerance key
        for each company code.
        When processing an invoice, the R/3 System checks each item for
        variances between the invoice and the purchase order or goods receipt.
        The different types of variances are defined in tolerance keys.
        The system uses the following tolerance keys to check for variances:
        o   AN: Amount for item without order reference
            If you activate the item amount check, the system checks every line
            item in an invoice with no order reference against the absolute
            upper limit defined.
        o   AP: Amount for item with order reference
            If you activate the item amount check, the system checks specific
            line items in an invoice with order reference against the absolute
            upper limit defined. Which invoice items are checked depends on how
            you configure the item amount check.
        o   BD: Form small differences automatically
            The system checks the balance of the invoice against the absolute
            upper limit defined. If the upper limit is not exceeded, the system
            automatically creates a posting line called Expense/Income from
            Small Differences, making the balance zero and allowing the system
            to post the document.
        o   BR: Percentage OPUn variance (IR before GR)
            The system calculates the percentage variance between the following
            ratios: quantity invoiced in order price quantity units : quantity
            invoiced in order units and quantity ordered in order price quantity
            units : quantity ordered in order units. The system compares the
            variance with the upper and lower percentage tolerance limits.
        o   BW: Percentage OPUn variance (GR before IR)
            The system calculates the percentage variance between the following
            ratios: quantity invoiced in order price quantity units: quantity
            invoiced in order units and goods receipt quantity in order price
            quantity units : goods receipt quantity in order units. The system
        compares the variance with the upper and lower percentage limits
        defined.
    o   DQ: Exceed amount: quantity variance
        If a goods receipt has been defined for an order item and a goods
        receipt has already been posted, the system multiplies the net order
        price by (quantity invoiced - (total quantity delivered - total
        quantity invoiced)).
        If no goods receipt has been defined, the system multiplies the net
        order price by (quantity invoiced - (quantity ordered - total
        quantity invoiced)).
        The system compares the outcome with the absolute upper and lower
        limits defined.
        This allows relatively high quantity variances for invoice items for
        small amounts, but only small quantity variances for invoice items
        for larger amounts.
        You can also configure percentage limits for the quantity variance
        check. In this case, the system calculates the percentage variance
        from the expected quantity, irrespective of the order price, and
        compares the outcome with the percentage limits configured.
        The system also carries out a quantity variance check for planned
        delivery costs.
    o   DW: Quantity variance when GR quantity = zero
        If a goods receipt is defined for an order item but none has as yet
        been posted, the system multiplies the net order price by (quantity
        invoiced + total quantity invoiced so far).
        The system then compares the outcome with the absolute upper
        tolerance limit defined.
        If you have not maintained tolerance key DW for your company code,
        the system blocks an invoice for which no goods receipt has been
        posted yet. If you want to prevent this block, then set the
        tolerance limits for your company code for tolerance key DW to Do
        not check.
    o   KW: Variance from condition value
        The system calculates the amount by which each delivery costs item
        varies from the product of quantity invoiced * planned delivery
        costs/ planned quantity. It compares the variance with the upper and
        lower limits defined (absolute limits and percentage limits).
    o   LA: Amount of blanket purchase order
            The system determines the number of days by which the invoice is
            outside the planned time interval. If the posting date of the
            invoice is before the validity period, the system calculates the
            number of days between the posting date and the start of the
            validity period. If the posting date of the invoice is after the
            validity period, the system calculates the number of days between
            the posting date and the end of the validity period. The system
            compares the number of days with the with the absolute upper limit
            defined.
        o   PP: Price variance
            The system determines by how much each invoice item varies from the
            product of quantity invoiced * order price. It then compares the
            variance with the upper and lower limits defined (absolute limits
            and percentage limits).
            When posting a subsequent debit/credit, the system first checks if a
            price check has been defined for subsequent debits/credits. If so,
            the system calculates the difference between (value of subsequent
            debit/credit + value invoiced so far) / quantity invoiced so far *
            quantity to be debited/credited and the product of the quantity to
            be debited/credited * order price and compares this with the upper
            and lower tolerance limits (absolute limits and percentage limits).
        o   PS: Price variance: estimated price
            If the price in an order item is marked as an estimated price, for
            this item, the system calculates the difference between the invoice
            value and the product of quantity invoiced * order price and
            compares the variance with the upper and lower tolerance limits
            defined (absolute limits and percentage limits).
            When posting a subsequent debit/credit, the system first checks
            whether a price check has been defined for subsequent
            debits/credits, If so, the system calculates the difference between
            (value of subsequent debit/credit + value invoiced so far) /
            quantity invoiced so far * quantity to be debited/credited and the
            product quantity to be debited/credited * order price. It then
            compares the variance with the upper and lower tolerance limits
            defined (absolute limits and percentage limits).
        o   ST: Date variance (value x days)
            The system calculates for each item the product of amount *
            (scheduled delivery date - date invoice entered) and compares this
            product with the absolute upper limit defined. This allows
            relatively high schedule variances for invoice items for small
            amounts, but only small schedule variances for invoice items for
            large amounts.
        o   VP: Moving average price variance
            When a stock posting line is created as a result of an invoice item,
            the system calculates the new moving average price that results from
            the posting. It compares the percentage variance of the new moving
            average price to the old price using the percentage tolerance limits
            defined.
        Variances are allowed within predefined tolerance limits. If a variance
        exceeds a tolerance limit, however, the system issues a message
        informing the user. If an upper limit (except with BD and VP) is
        exceeded, the invoice is blocked for payment when you post it. You must
        then release the invoice in a separate step. If the tolerance limit for
        BD is breached, the system cannot post the invoice.
        Note that if you set all limits for a tolerance key to Do not check, the
        system does not check that tolerance limit. Therefore any variance would
        be accepted. This does not make sense particularly in the case of the
        tolerance key Form small differences automatically.
        Activities
        Configure the tolerance limits for the individual tolerance keys.
                     Lower limit             Upper limit
                     Absolute    Percentage  Absolute    Percentage
         AN          -           -           X           -
         AP          -           -           X           -
         BD          X           -           X           -
         BR          -           X           -           X
         BW          -           X           -           X
         DQ          -           -           X           -
         DW          -           -           X           -
         KW          X           X           X           X
         LA          -           -           X           X
         LD          X           -           X           -
         PP          X           X           X           X
         PS          X           X           X           X
         ST          -           -           X           -
         VP          -           X           -           X
    ===============================================
    Best Regards,
    Siva

  • Tolerance limits for Price Variation

    Dear All,
    I have set the Following in Customizing.
    In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order --------->  Set tolerance limits for price Variance.
    In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the  Percentage field ( Upper limit ).
    Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
    Note : 120 INR = 100 + (20%)(100) = 120 INR.
    Regards
    Sathya

    Hi Sathyanarayana Rao V N
    You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
    Regards.
    M.Ozgur Unal

  • Tolerance limit for STO orders

    HI
    I want to set the tolerance limit for under delivery and over delivery qty tolerance. Where can we set the tolerance limits for stock transfer orders from plant to plant ?

    Please check OSS notes:
    Note 1093582 - FAQ: Delivery complete indicator ELIKZ
    5. Question
    In which cases does the system automatically set ELIKZ in stock transport orders?
    Answer
    ELIKZ will be set at the goods receipt stage automatically, if the GI = GR quantity. This behaviour applies to intra-company stock transport orders and cross-company stock transport orders. See note 196280.
    With stock transport orders the 'delivery completed' indicator is only relevant when there is no stock in transit The tolerance quantities from the purchase order are not taken into account.(see note 34737).
    It is possible to modify the standard to allow to set the "delivery completed" indicator for cross-company stock transport orders. This modification is contained in note 167795.

  • Tolerance Limit for Quotations.

    Hello all,
    Is it possible to set a tolerance limit for Quotations, such that the prices of quotes adopted to Purchase Order cannot be changed over a specific limit.
    Thanks

    Limits are nothing but Target value in quotation. It is the max value.
    But you want to fix the value in PO, So that no one can change.
    you can very well adopt the Version management & Release in PO, for that you can fix the limit & save the PO. If anyone change new version get triggered & document get dereleased.

  • To add Net price in Purchase order

    Hi,
    I have a sceneria where i need to add net price against line item which was marked as free in purchase order (Net price is 0). Subsequently material was deliverd from vendor and GI also was done. Goods receipt is also completed. This material batch number is consumed for custmer sales orders subsequently. There is 0 quantity available for this material in the plant. Now the user wants to change the net price to 2 for the line item. To change net price in purchase order, we tried to cancel GR material document.But we get an error that 'Deficit of unrestricted use' for the batch number.
    Can any one give us solution for changing the net price in purchase order?
    Regards,

    Hello,
    the only chance to add a PO price is to unflag the free flag in ME22N.  This is only possible when quantity received for the PO is zero. Therfore you must reverse the quantity received by doing a dummy receipt for the batch, reverse the GR for PO, you change the flag, set a price, redo GR for the PO, reverse the dummy receipt.
    Hope this helps, regards
    Michael

  • Can anyone give me user exit name for create/update purchase order partners

    Hello guys
      Can anyone gives me user exit name for create/update purchase order partners?
      Requirement is to insert/update partner when SC flag is checked while creating/updating purchase order (ME22N / ME21N)  by using user exit.

    hi,
    check these exits.
    Transaction Code - ME21N                    Create Purchase Order
    Enhancement/ Business Add-in            Description
    Enhancement
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number

  • Purchase Requisition - Adopt requisition price in purchase order

    Hello all,
    In Purchase Requisition there is the field BPUEB (Adopt requisition price in purchase order) that is used to transfer the valuation price from the PR to the PO.
    The field's values are :
    0. Do not adopt
    1. As gross price
    2. As net price
    The default value is "Do not adopt".
    How can I change the default value to "As gross price" ?
    Thanks,
    Isaac

    Hi,
    you can control this via the user parameter EVO.
    the various combinations can be configured in SPRO
    Material management > Purchasing > Environement data > Define default values for buyers
    Choose an entry (or create a new one)
    Go to the price adoption tab and set the "always copy" option and flag the "manual becomes gross price".
    Allocate this code to the EVO parameter on the user profile settings.
    Steve B

Maybe you are looking for

  • The field SAKNR search help doesn't work?

    Dear Expert, My dialog program used a table field data element call SAKNR , and i set the search help in the layout screen of my table control. the search help works but after i double click it but the value didn't show up in the field. don't know wh

  • Import DNG preference not working

    I have set the import extension as dng to auto import as dng from a Canon 40D. Doesn't happen and after I import I have to convert the raw to dng. Is there anything I need to do in addition to setting the preference? Jay Gould

  • Hi OLAP Help Needed

    Hi, I have to create a cube to work with BI Beans. But i am unable to do so. I want to use only cwm2 for some specific reasons. I am using oracle 10g. Given Below is my database structure TABLE : dw_all_counties Name Null? Type COUNTY_CODE NOT NULL N

  • Procure KIT with Purchase order but 15 different materials - how?

    Hi SAP MM Guru's, I have a requirement There are 15 different mateirals which are maintained in Material master seperately with different numbers but all will have to be procured from one vendor same time and issue is each material is consumed on the

  • Leopard + Numpy + Scipy: Path Issues Remain

    +This post has been cross-posted on the pythonmac-sig mailing list.+ I've been reading about the python path issues with Leopard and have tried the different methods outlined for addressing this problem with no good result. Currently I am using a com