Tolerance for Price change

Hi,
Can we set tolerance for price change for particular material or groups of materials.
say i dont want my material price to hit by more than 10% when using average price.

Hi Ravi,
SPRO - MM - Purchasing - Purchase Order - Set Tolerance Limit for Price Change
Using the Above path, you can change the Tolerance limits for price at Company code level.
Regards,
Ashok

Similar Messages

  • Threshold value for price changes

    hello,
    We are trying to change the price for material and getting error Threshold value for price changes was exceeded
    msg no is CKPRCH 032
    Being Sd guy I'm not able to understand where we need to check and what changes to be done
    Please guide
    Regards
    Vishal Jajoo

    Dear friend
    For that u check the following path
    spro>> material management>> logistics invoice verification>>invoice block>>> stochastic block
    please check here for your plant your activated, if you activated then this error will appear
    regards
    Pramod

  • Tolerance for price confirmation

    1.The tolerance for price confirmation is not restrictive enough for confirmation control key one particulatr KEY.Where to upadte  it to allow only 10% tolerance

    Hi
    Maintain the config in
    SPRO-> IMG-> MM -> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
    Here you can miantain the tolernace limits for key PE: Price variance: purchasing
    Thanks & Regards
    Kishore

  • How to set default value for Price Change Indicator in Purchase order

    Hi,
    While creating the service purchase order with item category "D" the price change indicator in the services tab of the purchase order is getting checked by default. I want to uncheck this by default.Where can we set the default property for this.
    Thanks in Advance!
    Surya

    My plsql parameter is p_arr which is of "TYPE vc2_255_arr IS TABLE OF VARCHAR2(255) INDEX BY BINARY_INTEGER"You need to declare it in a package specification and initialize in the package body:
    SQL> create or replace package pmp_lib
    as
       type vc2_255_arr is table of varchar2 (255)
                              index by binary_integer;
       vc2_255_arr_default   vc2_255_arr;
    end pmp_lib;
    Package created.
    SQL> create or replace package body pmp_lib
    as
    begin
       vc2_255_arr_default (1) := 'abc';
       vc2_255_arr_default (2) := 'def';
    end pmp_lib;
    Package body created.
    SQL> declare
       arr   pmp_lib.vc2_255_arr := pmp_lib.vc2_255_arr_default;
    begin
       for i in 1 .. arr.count
       loop
          dbms_output.put_line (arr (i));
       end loop;
    end;
    abc
    def
    PL/SQL procedure successfully completed.so in your case it would probably be sth like (assuming pmp_lib is a package):
    <%@ plsql parameter="p_arr" type="PMP_LIB.VC2_255_ARR" default = "PMP_LIB.vc2_255_arr_default" %>

  • No accounting document created (?) for price change MR21

    Dear All,
    I'm facing a strange issue:
    1. I changed the price of a material (MAP price control) in MR21.
    2. After price change, on the Accounting view of material master both MAP shows the new value both stock value shows the proper value. So, it is OK.
    3. When I want to check the document flow and I go to transaction CKMPCD, SAP doesn't show the belonging FI/CO documents when I click on 'Accounting Documents' button (error message: C+652)
    4. If I check whether accounting document exists in FB03 I can find no accounting documents.
    What might be the explanation for this? Why no accounting document has been created (the price change was big enough)?
    (both qty & value update is set for material type for the valuation area and there's no problem in case of price change for materials with SP)
    Thanks,
    Csaba

    MB5L checks if values updated in MM and values updated thanks to FI document on G/L account are the same,
    hep.sap.com
    "Check if there are data inconsistencies in valuation between the Financial Accounting (FI) and Materials Management (MM) components. To do so, start the List of Stock Values: Balances (report RM07MBS, transaction code MB5L) for the last period of the fiscal year. Enter a company code on the initial screen and set the Totals only indicator. If the report finds differences, inform SAP using the SAPNet - R/3 Frontend (formerly OSS). You can continue processing your year end closing while SAP clears up the data inconsistencies. The creation of the balance sheet is the only thing that has to wait until after the inconsistencies are removed. "
    Of course you can run this report in your case for current date.
    If there are no inconsistency - it means that FI should be generated - check in FB03 all FI document created by you, please.
    If you find no FI document create OSS message - FI account updated without FI document during MR21 price change.
    Andrzej

  • BAPI for Price Change using Transaction VK12

    Hi All..
    Can any one help in locating a BAPI for making price changes using transaction VK12.
    Rgds

    try RV_CONDITION_MAINTENANCE

  • 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

  • Order Testing for Price changes

    Is there a easy way to enter and test the orders instead of entering them online for pricing changes?

    Not sure, but for sure they are going to take their own time based on priorities :)
    I would really be happy if this is given in 1year.

  • How can i get the pulish data for Price change?

    From the rpm-1205-og.pdf document, the RegularPriceChangePublishBatch Batch can formats and stages output of regular price change price events.
    but I can't get data from rpm_price_publish_stage table after I run the batch.
    if I want generate data into rpm_price_publish_stage, how can I do?
    Please help me. thanks.
    Daniel

    Message was edited by:
    user616568

  • Document number for price change

    Good day!
    Is there a separate t-code such that i could view the generated document number from MR21? The number series starts with 3. (e.g., 3000000001)
    Thank you!

    Hi,
    Use t code CKMPCSEARCH & select the matl numbers & execute u will find a list in that u select a doc number & view details ur requirment will bo solved
    Pandari

  • MM:Price Change did not Carry forward from previous to current period

    Hi Gurus,
    Client has Reported that the Weighted Average Cost (WAC) was automatically  reset to Zero in a particular Period and didn’t carry over from the previous period , The initial analysis was done and it was found that there is a configuration for “Price Change in Previous Period and not in current Period” which has to be maintained for the company code
    The question is whether this configuration (“Price Change in Previous Period and not in current Period”) impacts both the Standard Price and
    WAC or does this impacts only Standard price
    Any pointers will be helpful, Will also Award Points
    Regards

    Hi Gurus,
    Client has Reported that the Weighted Average Cost (WAC) was automatically  reset to Zero in a particular Period and didn’t carry over from the previous period , The initial analysis was done and it was found that there is a configuration for “Price Change in Previous Period and not in current Period” which has to be maintained for the company code
    The question is whether this configuration (“Price Change in Previous Period and not in current Period”) impacts both the Standard Price and
    WAC or does this impacts only Standard price
    Any pointers will be helpful, Will also Award Points
    Regards

  • GL accounts in Price change

    Hi
    I have posted price change document and now analyzing which GL accounts are hit.
    Its bit strange but GL accounts which are hit are not defined in OBYC.
    I am not able to understand which GL are picked by the system and from where are they picked if not defined in OBYC.
    Regards
    Sharabh

    Hi
    In OBYC check transaction UMB - Gain/Loss from revaluation , the account for price changes triggers from this transaction key, check the G/L account assigned to the Valuation class..
    When a price change occurs the Postings are if material value is being decreased then
    Credit - Invenotry account
    Debit - Gain/ Loss account
    & for increase in material price the reversal postings happen.
    Thanks & Regards
    Kishore

  • Material Price change mr21

    Hai
    Any body can explain material price changing procedure. step by step how to we do this.
    My client ask to me change material price for costing run month end.
    Regards,
    Basha.

    Hai
    I have to change material price,  can any body tell me what is procedure for price change
    step by step with transaction codes tell me.
    I read some information in this tell tc ckmprp, ckme, and mr21  what is difference between this tc s and also ck24
    can any body tell step by step how i follow ( what is TCs for this )
    I am new for this material change so tell me step by step how i follow
    Edited by: Shaik Jani Basha on Sep 28, 2011 2:17 PM

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

Maybe you are looking for