Price determination process for contract

Hi experts,
I need to affect a new calculation schema to the header of the contract.
How can I do this please ? Could you please give me steps to do this ?
What procedure I need to change to manage new condition for the header of a contract ?
Thanks in advance.

Hi,
Yes, I  have created a new procedure "Condition Supplement Header" based on the RM0001 schema. I put my new condition type (Discount % on Gross) but I do not know how to affect this new schema to the header of the contract.
Thanks for your help

Similar Messages

  • Using formula in price determination process for PO

    Hi, dear experts,
    I would like to define some conditions types for purchasing orders that allow me to calculate an insurance amount using the formula:
                 Insurance = [CF)((C+F)10%)]T
         Where: C is the Gross price, F is the Freight and T is a factor that the user has to input
    For that, I define a condition type for gross price, for the freight and for the T value
    How can I have to define a condition type to do this operation?
    On the other hand, the freight is a percentage of the gross price, but for this operation I need the amount, how can I make reference to this amount? (Result of gross price * freight (%))
    Also, there is a link where can I find information regarding the price determination process?
    Thanks in advance,
    Mairo.

    Hi,
    You can store (surely you have them in data) the data for C and F in values that you can config in pricing procedure in the field 'SubTo'. After, you can obtain the amount with a formula VOFM and set it in M/08 in field 'AltCTy'. You can check this links to know how to do it:
    http://saptechsolutions.com/pdf/InsideVOFM.pdf
    http://saptechsolutions.com/pdf/VOFMFormulaRoutines.pdf (althouth it's for SD, pricing procedure in SD (tcode V/08) and in MM (M/08) are the same.
    I hope this helps you.
    Regards,
    Eduardo

  • How the Purchase Price determination process works in sap-mm?

    Hi,
    Can anybody tell in detail or have step by step document on  Purchase Price determination process?
    Thanks,
    Pradip

    Hi,
    You can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
    For the above individually you have to configure Pricing Procedure and the following steps are:
    SPRO->MM->Purchasing->Conditions->Define Price determination process
    1. Define Condition Table:
    2.Define Access Sequence,
    3.Define Condition Type,
    4.Define Calculating Schema,
    5.Assign Calculation Schema, Access Sequence and Condition Type,
    6.Define Schema Group Of Vendor,
    7. Define Schema Group Of Purchasing Organization,
    8.Assign Schema Group Of Vendor to Purchasing Organization,
    9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
    10. Assign Vendor to Schema Group of Vendor (XK02)
    11.Maintain Condition record (MEK1)
    after above steps, you can go for create PO in ME21N.
    In the case of Import PO, you have to activate Import PO.
    SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents -
    Regards,
    Biju K

  • Condition Types in Price Determination Process

    Hi
    Can any one explain me about in Detail about the VARIOUS TABS that  work in the CONDITION TYPE  of PRICE DETERMINATION PROCESS
    Thanks & Regards,
    Senmani.

    hi
    hi
    control data 1 :
    Condition Class is a grouping that lets you control each condition type differently.
    For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
    Condition category (examples: tax, freight, price, cost)
    A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
    Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
    Calculation type
    Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
    The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
    Rounding rule
    The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
    Example
    In the standard rounding rule '_', values are rounded off according to business standards:
    10.454 -> 10.45 DEM
    10.455 -> 10.46 DEM
    In rounding rule 'A', values are always rounded up:
    10.459 -> 10.46 DEM
    10.451 -> 10.46 DEM
    In rounding rule 'B', values are always rounded down:
    1045.9 -> 1045 LIT
    1045.1 -> 1045 LIT
    In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
    Structure condition
    controls whether the condition type should be a duplicated condition or a cumulated condition.
    This control is only helpful when you use bill of materials or configurable materials.
    Aduplicated condition is duplicated into all assigned items.
    A cumulated condition contains the net value of all assigned items.
    control data 2 :
    promotions
    Specifies that the condition type in question is only valid for Promotions.
    Use
    Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
    Accrual (e.g. Freight)
    Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
    Use
    If you mark this indicator, the condition appears in the document as a statistical condition.
    Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
    Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
    Solution: For this reason more indicators are being set up in 4.0 for the condition type:
    'Variant condition' (KVARC)
    'Internal costing condition' (KFKIV)
    The characteristic values O and I for the condition category must no longer be used.
    For more information, see the note 93426.
    inv.list condi
    Condition for invoice list
    Marks the condition type as relevant for internal costing.
    Quantity conversion
    This field controls the quantity conversion during determination of the condition basis.
    The field is only relevant for calculation rule 'C' (quantity- dependent.
    It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
    Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
    Rounding errors can occur during quantity conversion.
    Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
    Condition for inter-company billing
    Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
    Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
    Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
    Scale :
    Scale basis indicator
    Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
    Checking rule for scale rates
    Indicates whether the scale rates must be entered in ascending or descending order.
    Scale Type
    Indicator that controls the validity of the scale value or percentage:
    From a certain quantity or value (base scale)
    Up to a certain quantity or value (to-scale)
    Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
    Formula for scale base value
    Formula for determining the scale base value.
    Use
    You can use this formula to specify calculation methods that are not provided in the standard system.
    reward points if helpful
    thanks and regards
    ravikant dewangan

  • IS-U: Separate dunning processes for contracts after move out?

    Hi all,
    we are working with IS-U (water, wastewater etc.). After a move-out has been created, the dunning process changes for the whole contract account (VK), as defined in the Customizing area.
    The problem is - if only one contract out of 2 or 3 has to be ended, the dunning process changes for all of them and not only for the one that really has ended. This leads to wrong letters to the customers and a high amount of complaints.
    I found out that there is a new table entry VKKVKP-UMZMAHNV, but as far as I could find out, this changes the dunning process only for a whole VK, too.
    Does anyone of you have had similar problems and could give me a hint?
    Best Regards,
    Stefanie

    Hi Stefanie,
    You can use FM ISU_S_CONTRACT_CHANGE for the purpose to update the Dunning Procedure at contract level using BOR Object MOVEOUTDOC.
    Thanks,
    Amlan

  • In Price determination process,how to correct Net values ?

    In me23n, how can I correct Net value inclusive of tax & final price ?
    Netvalue inclusive of tax = basic + NAVD(deductible) + NAVS(non deductible)
    When I go to me23n screen, when I click on invoice tab the screen contains basic price ,deductible tax and non deductibe tax.
    Invoice tab
    JSTD A/P Service tax ded        12.000 %         5,148.00            
    JSTE     A/P Ed Cess ST ded        2.000 %         102.96            
    JSTH     A/P SEd Cess ST ded   1.000 %          51.48          
    Total deductible tax(NAVD) is 5302.44
    but when I go to condition tab
    NAVD     Deductible Tax       6,266.49      INR     
    because NAVD calculated incorrectly,hence netvalue inclusive of tax is calculating wrong values.
    How can I correct NAVD?
    Regards,
    Rachel
    Edited by: Rachel on Oct 14, 2008 8:41 AM

    Hi,
    You can check in the Pricing Calculation Schema.The addition and subtractions steps are done there. check the step numbers given are correct.
    For that, in Vendor AMster Purchasing view check the schema assigned and go to  Customisation for MMPurchasing-Conditions----Define calculation Procedure. assignment of Calculation schema to schema....
    Hope this will help.
    Regards,
    Smitha

  • How to set the price activation process for Purchasing Promotion

    Dear All,
    In solution we have 2 types of Promotion = Sales and Purchasing.
    Is Sales part you are creating benefit conditions (discount, fixed price, free good etc. ) and it will not be active while you are not activating it.
    Whenever pricing condition for Purchasing created in wak2 transaction, condition is active as of indicated date. No activation possibility.
    I'm trying to figure our the opportunity how to set up the configuration, so when I'm creating condition, it will be in planing status, as long as i did not press the activation button.
    Any ideas, suggestions, appreciated.
    Best regards,
    Liza

    Hi;
    Please make a search at metalinks as "The following input contained illegal input value, please re-enter your input or contact the system administrator", There are more than 6 notes mention this error message
    Regard
    Helios

  • Error: Transaction cannot be posted due to errors in price determination

    Hi,
    I am facing below error when i try to post GR for a SA. I checked out all the configurations, these worked on GR for PO but not on SA.
    I have seen other posts which recommend to view OSS note 447374 and 446831. I am not sure where to find these and how to use these notes.
    Please help!.
    Thanks
    Ramya

    Here you go
    Transaction cannot be posted due to errors in price determination
    Message no. ME573
    Diagnosis
    The error marked with 'X' occurred during the price determination process for purchasing document 201 00010:
    [ ] Net price is 0.
    [ ] Net price is negative.
    and/or there are no valid conditions or the duration of the
    contract has ended.
    [ ] Effective value is negative.
    [X] Mandatory condition missing.
    [ ] Negative delivery costs.
    [ ] Delivery costs have been recorded although invoice
    receipts are not defined for the item.
    [ ] Error during quantity conversion
    [ ] Error during currency translation
    [ ] Field overflow
    [ ] A condition involving delivery costs exists without a
    transaction/event key.
    [ ]Error during maint. of delivery costs in master conditions
                  Delivery cost conditions in different validity  periodsnot identical
    System Response
    The transaction cannot be posted without successful price determination.
    Procedure
    Check the purchasing document and the associated conditions:
    Display purchase order
    Display scheduling agreement
    If the problem cannot be resolved in this way, contact your system administrator.
    The latter can check the Customizing settings for price determination in Purchasing under Conditions -> Define Price Determination Process
    When the foregoing steps have been carried out, try posting the transaction again.

  • Transaction cannot be posted due to errors in price determination

    Hi
    when I made the receipt of goods by MIGO the system to me gives me the following message blocking:
    " Transaction cannot be posted due to errors in price determination
       Message no. ME573 "
    Thainks in advance

    Hello
    Please refer the message long text and just check based on the suggestions given :
    Short Text
    Transaction cannot be posted due to errors in price determination
    Diagnosis
    The error marked with 'X' occurred during the price determination process for purchasing document  :
    [ ] Net price is 0.
    [ ] Net price is negative.
               and/or there are no valid conditions or the duration of the contract has ended.
    [ ] Effective value is negative.
    [ ] Mandatory condition missing.
    [ ] Negative delivery costs.
    [ ] Delivery costs have been recorded although invoice receipts are not defined for the item.
    [ ] Error during quantity conversion
    [ ] Error during currency translation
    [ ] Field overflow
    [ ] A condition involving delivery costs exists without a transaction/event key.
    [ ]Error during maint. of delivery costs in master conditions
                  Delivery cost conditions in different validity  periods not identical
    System Response
    The transaction cannot be posted without successful price determination.
    Procedure
    Check the purchasing document and the associated conditions:
    Display purchase order
    Display scheduling agreement
    If the problem cannot be resolved in this way, contact your system administrator.
    The latter can check the Customizing settings for price determination in Purchasing under Conditions .
    warm regards
    Ramakrishna

  • Price conditions available in contract (MM)

    Hi,
    I created a new price condition and it is not available in tha match code in contract (ME32K).
    How can I customize which condition are available in the contract ? Does it depend on the category of the condition ???
    Thank you for your help,
    Laetitia

    Dear Laetitia,
    a) Please check if this condition type "Manual Pricing" set as allow
    b)Please check if you have include this condition type in your pricing procedure.
    Transaction SPRO:
    MM->Purchasing
    ->condition
    -> Define Price Determination Process
    -> Define calculation schemas
    Regards,
    ian, Wong Loke Foong

  • Purchase order price determination

    Hi Gurus.
    Please help on below Inquiries
    In Purchase order, how is the net price determined?
    Is it from the agreement? the info record? RFQ? Is there a sequence for this?
    If there is, where is this configured?
    Thanks!

    Hi,
    Purchase order price determination takes place with help of  Access Sequences and Schema Group of Vendor.
    You can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
    For the above individually you have to configure Pricing Procedure and the following steps are:
    SPRO->MM->Purchasing->Conditions->Define Price determination process
    1. Define Condition Table:
    2.Define Access Sequence,
    3.Define Condition Type,
    4.Define Calculating Schema,
    5.Assign Calculation Schema, Access Sequence and Condition Type,
    6.Define Schema Group Of Vendor,
    7. Define Schema Group Of Purchasing Organization,
    8.Assign Schema Group Of Vendor to Purchasing Organization,
    9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
    10. Assign Vendor to Schema Group of Vendor (XK02)
    11.Maintain Condition record (MEK1)
    after above steps, you can go for create PO in ME21N.
    In the case of Import PO, you have to activate Import PO.
    SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents ->>>>>>
    Regards,
    Biju K

  • Price determination as per delivery date

    Hi All,
    I have created a PO in which the PO is picking up the dalivery date as the current date. when i change the delivery date as some other date there is a message saying Delivery date changed (new price determination process may be necessary).. I worked with my ABAP guy and solved this problem and now the PO is not picking the current date.
    Now, the user wants me to configure how to determine the Price for different delvery dates.
    That is if i change the delivery date to some other how to check if the PO is picking the price determined by that delivery date.
    I checked the info record and the validity date is 12/31/9999. and this is the message iam getting
    Delivery date changed (new price determination process may be necessary)
    Message no. 06484
    Diagnosis
    If the price determination date is the delivery date and other conditions are valid on the new delivery date than those that are valid on the old one, the price is no longer valid.
    Procedure
    If this is the case, and you wish to see the price that is valid as at the delivery date, carry out a new price determination process.
    And u said to define on the basis of which Date of Price Determination system should select the price. where can i define the price determination for delivery date. This is the first time iam working on such issue of price determination.
    Thanks,
    Sameer

    Dear Sameer
    There is no relevance of pricing date with delivery date.  For information,  while creating sale order in VA01 after giving your sales area and execute, there is a field "Pricing Date" in Sales tab and the date will flow into this field by default the date on which you are creating sale order. 
    So irrespective of your delivery, your invoice pricing will be effective based on this field.  Unless you change the date here, your pricing condition will not change, if you have a different pricing in VK11.  Of course, you can also change the pricing date at item level for which click on "Goto -- Item -- Sales A".
    thanks
    G. Lakshmipathi

  • Error in the price determination procedure in the Delivey NL

    Hi Gurus,
    I'm working in a project and the customer wants the delivery note with value. Then I have activated the Price determination procedure for the delivery NL ( deliveries to transport material between plants ) and the determination doesn't work correctly, The conditions doesn't appears but if you push "analisys" and you check the conditions PR02 and MWST,  the condtions record are determined but not printed in the document.
    It print the following message:This message tells you that the condition record exists, but has not been set in the document...
    Some ideas?? thanks in advance for your help
    Francisco Javier Fernandez

    Hello,
    Solved, in the customizing, you need check if the price determination procedure for the item category NLN is active, how?? spro>sales>basic functions>pricing>pricing control>define pricing by itgem category.
    Check if your item category NLN have "x" Active price determination procedure.
    Is nothing related with the reference to a PO, or copy rules...
    Best regards,
    Francisco Javier Fernandez

  • How to activate NF Metal Processing for SD?

    Hi,
    how can we activate NF Metal Processing for SD??
    (We have a demo ECC 6.0 and EHP)
    Thanks

    hi
    Purpose
    This scenario includes three sub-scenarios which cover procurement non ferrous material for the warehouse, sales of non ferrous material with two pricing strategies, one is weight dependent and the other one is not weight dependent.
    Function List
    The following functions are provided to support the Non Ferrous Metal Processing building block:
    Sub-scenario 1: Purchasing Non-Ferrous Processing (Weight-Dependent)
    Purchasing order creation
    Goods movement
    Invoice verification
    Sub-scenario 2: Non-Ferrous Processing (Non Weight-Dependent)
    Initial stock
    Sales order creation
    History of coverage
    Delivery processing
    Goods issue
    NF rate maintenance
    Billing
    Sub-scenario 3: Non-Ferrous Processing (Weight-Dependent)
    Initial stock
    Sales order creation
    Delivery processing
    Goods issue
    Billing
    Key Points
    Supports various rate determination processes for NF metals traded on stock/metal exchanges using the condition technique.
    NF metal coverage is an agreement to invoice a customer for a specific NF metal quantity within a specific period at a specific rate. It also contains coverage used history.
    BB:
    http://help.sap.com/bp_metalsv1600/Metals_DE/html/M87_EN_DE.htm

  • Price determination 2 and S -- No material selected for CKMLCP

    Dear all,
    We have a case here that raw materials have price determination 2V, semi-finished and finished goods are 2S.
    The MM period is now 2011/07.  We tried to run CKMLCP for 2011/06 and system reponded "C+114 list contains no items".
    I have searched forum and SAP OSS.  What I found is CKMLCP will not process for 2V.  How about 2S?  Should I change all the settings to 3S instead?
    Please let me know if you have faced the same issue before and how you solved it.
    Thanks~
    Best regards,
    Sharon Chen

    Hi,
    The materials 2S (price determination 2, price control S)
    will NOT be selected for the actual price determination in CKMLCP.
    In Material Ledger you may use materials with price determination 2,
    price control V or materials with price determination 3,
    price control S. In the first case (2V), actual price will be calculated
    after each material movement, while in the second case (3S), actual
    price will be calculated with the cockpit (CKMLCP) at the end of the
    period. Only in this case, price differences are rolled-up to finished
    materials when multi-level price determination is run.
    Regarding to your problem with transaction CKMM, please keep in mind
    that CKMM was created to maintain the Price determination control field and
    not the price control only. The reason is a design issue.
    If you want to change the material from 2S to 2V you can overcome the
    change in two steps:
    1- change 2S to 3S and
    2- afterwards 3S to 2V
    or you can also use transaction MM02 to change the price control from
    S to V.
    Please check the notes about transaction CKMM which provide very useful information:
    703604     CKMM: When to change price determination '2' to '3'
    384553     Data inconsistencies after CKMM
    Best regards,
    MLM

Maybe you are looking for