Estimated price

Hi
In some cases Our company uses an estimated price as base price for allsubsequent activities. Generally this estimated price is adjusted with the final price at the end of the season or a predefined time period. Here SAP is required  to do a reconciliation, this reconciliation can be either a credit or a debit. To ensure that the final u201Cactualu201D price is correctly calculated either a debit note or a credit note will be issued.
How to do settings in pricing procedure. and how to do reconcilliation with condition type
Regars

First of all you need to create two condition types for Expected Price and Final Price. Expected price would be used in transactions but final price is to be used f aor comparing. For example - Suppose Expected price is maintained at Rs. 100 on 10.10.2001 and you sell on 01.01.2010 with expected price 100.
Now on 31.03.2010 you derive the final price. You need to maintain this value in a new condition type (may be for customer/material combination) with period 01.01.2010 to 31.03.2010.
Now, a Z-Table needs to be be developed to compare the two prices on the invoice date. i.e. the program will run on the last day of the period (e.g. 31.03.2010) for each and every invoice created during the period. It will check the basic price of the invoice and the final price maintained in the condition rec. for that invoice date.
Then based on this report Price Difference Credit/ Debit memos can be created either manually or automatically as background job th. BDC. You need to create pricing procedure for the credit/debit memo - which will calculate differential taxes,etc. for the differential price. It is good to create one credit/debit memo per original invoice.
Hope this helps. Let me know if this works.
Thanks

Similar Messages

  • I dropped my iPhone 4s and the back cracked and it now will not turn on. I was wondering if anyone could give me an estimated price to fix it. Thanks. And I do have insurance on it with best buy. I'm with Verizon so I don't know what way would be cheaper

    I dropped my iPhone 4s and the back cracked and it now will not turn on. I was wondering if anyone could give me an estimated price to fix it. And I do have insurance on it with best buy. I'm on Verizon's phone plan so I don't know if it would be cheaper to have it fixed with Best Buy or Verizon. I cracked my iPod a little bit ago and got a refurbished one for free with the insurance on it but I don't now if it would be different because it is a phone. I don't know really anything about this stuff so any information that could possibly help me is greatly appreciated. Thanks.

    That's only for the iPhone 5. On the 4 and 4S, they can repair the back glass in store for $30. They will not replace the display on a 4 or 4S. They must replace the entire phone. Replacing the display on them requires disassembling the entire phone, which they will not do in store.

  • Estimated price and Actual price for purchased Materials

    Hi Experts
    Please advice for the below scenario:
    We don't know the Exact price of a Material (Externally purchased) while raising the PO, so we enter an Estimated price in PO and send it to vendor.
    While doing GR, We should identify the Material which was entered estimated price by some warning or information message.
    Then we will go and edit the PO with Actual price, after that GR will be done.
    Any idea how to achieve this requirement?
    Thanks in advance.
    Regards
    Bala

    There are no facilities in SAP at all as per your requirement.
    You can only achieve this via development. You have to use something different for those material in PO. And at the time of MIGO, the enhancement (by using any exit or badi) will check the field or field value in PO and system will show the warning / information at the time of GR.
    You may also create new field in PO/EKPO.
    Suppose for those material you have entered the value X and blank for the normal material.
    Then system will check the field at the time of goods receipt. If system will find the value X, then system will show the information / warning message.
    If system finds the blank value for the field, then system will not show the message.

  • Exit to populate Estimated Price (EKPO-SCHPR) while posting PO from ME21N

    Hi All,
    While posting PO from ME21N, I need to populate EKPO-SCHPR based on condition records. Can any one please provide me some exit or BADI.
    Thanks
    Subhankar

    Not got the answer. I am closing the thread..

  • Use of SAP PS for new product price estimation

    Hello Experts
        My organization is not using SAP PS but we have a process of estimating price before launching new product without creating Material Master in SAP. Is it possible to use SAP PS for price simulation process?
    Thanks
    Ankit

    Hi,
    We can use Adhoc cost estimate using easy cost planning in sap.
    Thanking you
    Vengaiah Chowdary

  • How to block the printing of a price on a Purchase Order

    Prices are often negotiated towards the end of the month in our business, but to keep our costing as accurate as possible we wish to include an estimated price in the PO record but not transmit it, in order to avoid sharing our estimate with the supplier.  Can we set up master data to block these prices on all orders, say for a vendor and material?
    Many thanks for any ideas
    Paul

    Paul,
    In the pricing schema there is a print indicator.  IF, and that's a GIGANTIC IF, the ABAP coder or form developer did their coding correctly, this is all you need.  Otherwise you will have to make code changes to the form and possibly to the print program.
    Unfortunately my guess is that you will have to make the code changes.  Unless your ABAP coder was truly experienced, rather than so many of them who claim to be, I seriously doubt that the form or print program were coded to use the standard SAP functionality.  My experience has been that about 9 out of 10 times you will have to adjust the print program or the form, or both.
    Good luck...
    Bill

  • Change in PO Price after goods receipts and goods issue

    Dear All,
    Happy Holidays!! Wishing you a happy and fun-filled holiday season.
    I would appreciate your input of the issue at hand. I support MM users in and Oil & Gas downstream company.
    Issue
    Purchase Orders are created using price estimates. The price of oil products fluctuates and we usually cannot get the exact price at the point of creation of the PO.
    We use Moving Average Price (MAP) for stock valuation and so the price & quantity in the PO affects the moving average price.
    We use price estimates to create the PO but when we receive the final price for the oil products from the Supplier, most times there is a significant difference between the estimated price and the final price. Usually, at this point, we have completed all goods receipts and goods issues against the PO and are unable to make changes.
    We have an issue posting the invoice because the invoice value is significantly higher than the PO value. We also have an issue with the moving average price because it is understated as a result of this.
    To reiterate, this is a summary of the issue:
    At the point if PO creation ; Quantity = 10, 000 MT Price = $650
    Later when final price is available; Quantity = 10, 000 MT Price = $715
    Any advise on how to treat this issue, please? Your assistance will be truly appreciated.
    Thanks

    Hi All
    For my client I have to map the similar requirement for material price which is subject to more than 15% fluctuation. The actual invoice price is having quite a huge difference.
    Below are my limitations within which need to give a solution.
    PO is subject to release strategy and Material is delivered over a longer duration of time. Hence there is problem to de-Release the PO everytime price is changed.
    Since differnce is so huge, the same can not be settled during the MIRO.
    Down Payments has to be posted hence PO has to be created with estimated base price.
    Please suggest me suitable alternative options which will require no changes in PO and the price change also can be accomodated during the MIRO for  Multiple goods receipts.

  • Price difference between the requisition and the order

    Hi All,
    There is new functionality in ERP6 that checks the difference in price price between the requisition and the order. The configuration is under Purchase Requisition -> Tolerance Limits -> Define Tolerance Keys. This is very useful functionality when the requistion item is approved at an estimated price, but a purchasing group needs to change the $ value it will block the Purchase Order.
    I have this configuration menu available in SPRO in one of my systems (IDES), however on a newly installed ERP6 system we are missing this menu path in SPRO.
    Does anyone know why this menu path in SPRO is missing on some systems...

    Thanks Henry,
    I've done some digging and the tables that store these config settings are part of US Federal Governement addons.
    Looks like all the (non government) sites that need it aren't able to have it. Great shame really as this would be very useful to communicate with the requestor whena  price difference occurs.

  • Contracts and Vendor Price

    Hi ,
      I have an issue today from user.Having not worked on contracts much,I am quite confused what to do.My user has a requirement like below
    We create a Contract type YKM2. (With an estimated
    price)
    From the Requirement we create a Purchase order.
    We don't get the price from the Vendor until the goods are recieved on the plant.
    Then we change the price on the contract.
    As it is today, the Call-offs are made before we have change the price on the contract, and we would like that no Call-offs are to be made until we remove the block
    Is there any chance we could do this in standarad with any T.C or do i have to ask any technical guy.I will award full points for valid answer
    Edited by: aram ust on Jan 24, 2008 5:13 PM
    Edited by: aram ust on Jan 25, 2008 4:16 AM

    I think if you re-title your subject to "Very Very Very Very Urgent" you may get a better reply.
    Or perhaps read the rules of engagement, which do NOT allow the use of Urgent in the the subject line, then re-title your subject line to be something relevant of the details of your actual question.
    Aram, sorry if you are new and this sounds harsh, it just happens alot, and if the subject line shows some idea of what the question relates too, folks can better sift through the list.
    I suggest no one answer this until the subject title is appropriately renamed, otherwise we just perpetuate folks to continue th practice

  • Changing Cost Estimation ( ML activated)

    Hi All,
    We have ML activated  and we have Price Control as "S" for all  ROH, HALB & FERT Materials.
    The intention was to have one Cost Estimation per year and  difference to be posted to variance.
    The Material Valuation Strategy is
    1. Valuation Price from User Exit
    2. Price from Info Record
    3.MAP
    4.Planned Price 1
    Now our issue, in June 2011 we have executed cost estimation for some new materials(say one Material ABC - Cost estimation must be $12000 but it is updated as $19000 due to wrong price maintenance)  with wrong price and made  goods movement.
    Now when we want to correct the cost estimation by executing a new cost estimation( i.e. we want to overwrite the $19000 by $12000 for the ABC material) by this month( July 2011), but the system is picking the same old cost estimation price (old cost estimation price as $ 19000).
    Can you suggest, how we can overwrite the existing cost estimation.
    Do suggest.
    Regards,
    Rex

    Hi All
    Costing valuation follows the priority you have define. If this is taking 19000 maybe this value is coming from the first option (user exit).
    I suggest you to change the priority to take price from  planned price 1. Go to OKKN and change the priority for Valuation variant.
    ...or you have to assure there is no prices from priority from 1 to 3.
    Regards.

  • Price from Requisition to PO

    Hi,
    when I create a Purchase Order Requistion (POR) I have to indicate a price. Is it possible to copy this price automatically into the Purcahse Order (PO) when I create the PO? You, know, whit ME21N I take the POR and I move it into the basket. Material code, cost centre, description and so on will be copied from the POR into the PO but not the price (I think because the price you indicate in the POR is an estimated price). Is there something in Customizing where I can set up that the price in POR is copied in PO?
    Thanks.
    FT

    Hi Fabio,
    What Antony mentioned about consumables is true.
    However, for material purchases there is another way to do it. Please follow the steps below.
    1) SPRO --> MM --> Purchasing --> Authorization Management --> Define Function Authorizations for Buyers
    2) Maintain 01 function authorization or copy it to create a new one
    3) Under General Parameters, Check Adopt PO Price.
    4) If you would like PO to have reference objects as mandatory, uncheck W/o Reference Optional. This means that when you are creating a purchase Order, you must refer it to another document, for example PR.
    5) Go to each buyers ID by SU01 --> Parameter. Enter EFB and enter the 2 codes that you defined in Step 2.
    6) Log out then log back in
    Now with that ID, when you create PR, under valuation tab, you have a new drop down button asking whether you would like to adopt the price in PO.
    Hope this helps.

  • Price varaince

    Hi
    How do i get price varaince in material master.
    Tell any std t.code is there
    Rgds
    Srini

    hi,
    >You can also set special tolerances if the price in the >purchase order is flagged as an estimated price.
    Regards
    Priyanka.P

  • 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

  • Moving Average Price for non stock material

    Hi All,
    We are looking at loading a large number of material masters for items that will not be stocked - i.e. an account assignment will always be provided during purchasing.
    When we load these materials - what should the moving average price on the accounting tab be set to? If we put an estimated price in - then when we purchase we will get a warning if the variance between the purchase price and the moving average price is too great. And then when the material changes in price (in lets say a year because the vendor has increased prices by 10%) we can no longer update the moving average price.
    What is the best practice in this scenario?
    Kind Regards,

    non stock material (standard material type NLAG) does in general not have accounting views, hence it has no fields for moving average prices.
    however it can be customized to have an accounting view, we did it too. This  servers the requisition process, with accounting view the price defaults to the requisition. without accouting view, the valuation price needs to be entered manually by a user in the requisition.
    The MAP gets only updated if the stock is posted to inventory, which will never be the case for non-stock material, because of this you should always be able to change the MAP directly in the material master with MM02, or if not possible in MM02 with MR21.

  • Invoice Verification tolerance price varience

    Hi All,
    I have set Invoice verification tolerance key PP upper limit 5 % and value 5 in customizing.
    I have also set message M8082 and M8083 as error message in customizing.
    My requirement is to limit user from posting invoice above 5 % of GRN Amount.
    The message customizing is working fine for value (M8082) however I cannot get message M8083 for % of invoice amount tolerance.
    I want message M8083 to be triggered at invoice verification which is not happening.

    Hi,
    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
    Please confirm your PO should have following check on condition control tab
    and maintain the Tolerance key PS for upper and lower % limits, system first go through Val. check and then % tolerance limit check,
    then you will get the message M8083
    Sohaib Mahmood wrote:
    My requirement is to limit user from posting invoice above 5 % of GRN Amount.
    The message customizing is working fine for value (M8082) however I cannot get message M8083 for % of invoice amount tolerance.
    I want message M8083 to be triggered at invoice verification which is not happening.
    if you want to limit the user from posting the invoice by 5% tolerance, then maintain PP tolerance key,
    you will get the message M8082 this will solve your purpose,
    If your business demand for estimated price variance then maintain PS tolerance key you will get the message M8083
    Thanks
    Message was edited by: k j

Maybe you are looking for

  • Movie Clips with one Frame

    If I have SWF's that I am using for UI elements in a game, and in these SWF's there are layers with Movie Clips and these clips have only one frame in them - do I need to explicitly put a stop() in there for optimal performance? I'm curious if these

  • Oracle 8i Lite - SQLPlus 8.0 Connect

    I am running Windows 98 and Oracle8i Lite. I have been trying to launch SQLPlus 8.0 from Oracle 8i Lite. I typed SCOTT for a username and TIGER for a password, but I could not figure out what I am supposed to type for the HOST STRING. I researched th

  • Exception to contract coverage times - Service Contracts.

    Service contracts are allowed to have exceptions to coverage hours. This is defined in the "Exception Coverage" section of Lines -> Effectivities tab. When I query for the coverages attached to the contract in the form, I see the exception coverage,

  • SAP SRM - ERP INTEGRATION

    Hello, we are designing application architecture. Our landscape is: - ECC 6.0 - SRM 5.0 - XI 7.0 We are thinking of using <b>XI as middleware even for those scenario in which in not required</b> (es. Contract Managament): In particular every time we

  • New itouch: FaceTime won't let me sign in!

    I just got a new itouch for Christmas, and I absolutely cannot get FaceTime to work. I have tried everything. Everytime I try to sign in, it says that my password is wrong. I know that it is correct, because I checked it on other apps. I went ahead a