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

Similar Messages

  • 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

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

  • Invooice block for price variance

    Hi
    I require a block for the invoice for value more than PO value by 2Rupees. I have done the Tolerance key cuustomizing for PP (Price variance) by mainaining the upper limit as 2 Rupees and have checked the limits. I expected the system to block the invoice for value more than PO value by 2 rupees, but system blocks even for value more than 10 or 20 paise. Please clarify and guide what needs to be done.
    I also beleive system does not blocks invoice for the above tolerance for extra duties and taxes and unplanned costs. Pl brief.
    Regards
    Arvind

    hi
    u have given tolerence for PP     Price variance
    u check following
    BD     Form small differences automatically
    KW     Var. from condition value
    VP     Moving average price variance
    for the above keys make the option as do not chck and then try
    regards
    KI

  • Line Item For Price Variance

    Hi,
    What non FI datasource in RSA5 can i find the line item for Price Variance?
    Thanks

    Hi Sam,
    I think 0CO_OM_CCA_9 will word best for me.
    what does it mean by:  Actual Costs Using Delta Extraction ?
    Also would the field REFBN Reference Dosument Number have the invoice number & the PO Number?
    Thanks

  • Set Tolerance Limits

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

    1) "Powered by Jive Software" ....
    2) 我看看有没有机会通过什么渠道反映这个问题..

  • 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

  • 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

  • Standard Report for Price Variance

    Dear Friends,
    Business is asking for the Price Varinace Report in standard SAP based on following criteriau2019s
    The requirement is to have a report which provide :
    ·         Purchase price variance u2013 PO V/s Invoice which is posted to General ledger.
    ·         By Vendor ( both third Party & Intercompany) with Vendor number and name.
    ·         By Material code & Material description and Material class
    ·         By Purchase order
    ·         For a given month or Year to date.
    ·         By GL code where the purchase price ( PO v/s invoice) is posted.
    Is there any standard report available for this in SAP or is it should be customised, if so is it complex...
    Please suggest me on the same
    Thank you for your promt reply
    Radhika Eluri

    Hi Santosh,
    I could not find the related reports for the same which i can show to the user.
    Could you please give me what are those reports available(Even they are not completed) so that i can provide the same to business.
    If they are not satisfied with them, then we will go for developemnt
    Thank you
    Radhika Eluri

  • Input Quantity Variance and Input Price Variance for Production Order

    Dear All
    I am running variance program KKS2 for calculating variance of production order. for Activity variances are coming under input price variance and input quantity varinace but for material the variances is now shown separately for quantity and price rather it is shown as variances total amount. Can someone help me in know why material quanitty variance and price variance not shown separately
    Regards

    How does input variance and output varia.nce will be calculated on the settlement of production order after TECO.
    VARIANCE CALCULATION DEPENDS ON CONFIGURATION IN THE FOLLOWING AREAS,
    1) VARIANCE VARIANT -  DETERMINES WHAT VAREIANCE CATEGORIES ARE CALCULATED, E.G MATERIAL PRICE , USAGE, LABOUR RATE , USAGE VARIANCE ETC..
    2) TARGET COST VERSIONS
    3) VALUATION VARIANT FOR WIP  AND SCRAP
    Can we check in KOB3 or COOIS.
    KOB3 -  YES
    COOIS -  CHECK IN COST REPORT

  • Variances accounts - for Price variances

    Hi,
    I have a problem with deciding how many Price variance Accounts I should create.
    There are 3 Production divisions and there are 3 types of PP orders.
    Each PP order can create Finished Goods or SemiFinished Goods.
    Should I create separate variance account for Finished Goods and separate variance account for Semi Finished Goods?
    How can I assign these variances account (for settlement) to an order type, if one order type can do both FG and SFG. Maybe the PP order types should be divided into FG and SFG - so that there would be 6 PP order types?
    What can you suggest me?
    Best wishes,
    Karol

    Hi Karol
    Create two production variance accounts for FG and SFG.  These should not be created as cost elements and should have PRD PRF as account determination.  You dont have to create as many variance accounts for each PP orde type
    Create one more variance account - called Variances in production as cost element. 
    Order crated for a material and depending on the material type and valuation class assigned to material, different accounts will be hit
    You assign PRD PRF for FG and SFG material valuation classes
    Hope the above clarifies. Please assign points

  • Invoice blocked for price variance or quantity variance

    Dear friends,
    In case if in the PO, either there is a price difference between GR and IR or a quantity difference between GR and IR, then does the invoice posted stays automatically in a "blocked" status??
    If not, then can we manually do some configuration to make this possible? The intention is that such invoices(with price variance or quantity variance) should remain in blocked status and should not be picked for payment in F110 run.
    Please advise asap.
    Rgds,
    Kunal Vichare.

    check this links
    http://www.sapfans.com/forums/viewtopic.php?f=6&t=324521
    http://www.sapfans.com/forums/viewtopic.php?f=6&t=336490

  • Set tolerance limits in invoice block

    We have the following tolerances:
                                                                                    Lower limit                                     Upper limit
                                                                                   Absolute     Percentage     Absolute     Percentage
    BD     Formación automátic.difer.pequeñas                                    0.05     
    BR     Desviación porcen.CPP (RF ant.a EM)                                                           5
    BW     Desviación porcen.CPP (EM ant.a RF)                                                          5
    DQ     Sobrepasar importe desviación cantidad               25     5
    KW     Desviación del valor condición                                                        25     5
    PP     Desviación del precio                                                           25     5
    PS     Desviación del precio estimado                                            300     10
    We would like to avoid this:
    1- User creates purchase order with price 1 u20AC por example
    2- Goods receipt is made with 1 u20AC
    3- User modifies purchase order´s price to 100 u20AC
    4- Invoice is stored with 100 u20AC.
    I would like to block invoices in which purchase price and invoice price
    are the same but goods receipt´s price is very-very different.
    How should I set the values? Which one?
    Thanks in advance.

    Hello,
    Set Tolerence limits for Invoice verification in OMR6 Tcode.
    If Invoice price is more than tolerence limit, then invoice will go to block.
    Regards
    Mahesh Naik.

  • Purchase Order - tolerance key SE for price variance

    Dear folks,
    In the purchase order config for tolerance limit, there is a setting for tolerance key SE.
    The SAP help defines that this limit is triggered with system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
    Can anyone advice me where do I specify which cash discount or what discounts will trigger this warning messages?
    Also, is it comparing the discount % against the % in the config or against the discount value from the PO price?
    Best Regards
    Junwen

    Dear Folks,
    To clarify, I meant how do I trigger this tolerance limit SE?
    Which discounts will trigger this limit?
    If I add new discounts or delivery conditions like Freight, will it be subjected to this check?
    This setting is set in the SPRO in Purchase Orders setting together with the tolerance key PE. PE will be triggered in the purchase order when the price in the PO is lower or higher than the tolerance limit when compared to the material price.
    Thus, I think SE will be triggered in the PO also, but how?
    Best Regards
    Junwen
    Edited by: Junwen Huang on Jun 11, 2008 10:12 AM

Maybe you are looking for

  • HT204053 multiple icloud accounts on one apple id

    I have my two boys connected to my Itunes account and Apple ID.  Is there a way that they can have their own icloud accounts so that everything on their phone is not mixed up with what is on my phone?

  • Lenovo S10-3T пароль BIOS

    Здравствуйте !Недавно откопал у себя старенький S10-3T - включил - ноут выдал ошибку CMOS Checksum Error - Defaults Loaded - при этом теперь при входе в BIOS запрашивается пароль, какой пароль - неизвестно, естественно зайти в него не получается, а н

  • Hide value from url

    This forum has been a greate help, I learned a lot by asking questions here. Have a customized query that generated a link icon to another page. The url pass the primary key along with some item values to the linked page. It works. My question is if

  • Lightroom 4 doesn't detect Photoshop Elements 9/10 for external editing

    Hi, I own Photoshop Elements 9 and recently decided to install trials of Lightroom 4 and Photoshop Elements 10.  For whatever reason, Lightroom doesn't detect Photoshop Elements 9 or 10 for external editing.  I need to make sure this functionality wo

  • Importing a class i made

    i have a silly question. let's say i've created a class called ClassOne.java and I want to create an instance of it in ClassTwo.java I've tried making a package and being able to access the first class but it keeps telling me that it cannot resolve s