Should I change the pricing procedure in SD ?

Hhello
we are running sales orders with a certain pricing procedure now for a long time. There are a lot of change requests for this pricing procedure, including structural changes like new sums and changes of positioning of a conditon type within the procedure. Should I change the existing pricing procedure to meet the new requirements or should I create a new procedure with a complete new structure, sums etc ?
Please advice. What are possible problems, which can occure in one or the other method.
Best regards and thanks for your help
Rauno

Hi Rauno,
You should definitly copy the current pricing procedure and make your changes to the copy.
The only disadvantage is that you can't mix old and new flows into e.g. the same billing document ( = pricing procedure is split criterium ).
But the BIG advantage is that all your old flows will not get inconsistent 100% guaranteed ( when you 'look' at them, or do e.g. VA02 on an old flow etc..)
rgds
Dirk

Similar Messages

  • How to find the pricing procedure?

    Hi,
         in the sales order modification(VA02), if there is any change in a field, i have changed the pricing procedure.
    i have done my coding in MV45AFZB and FORM USEREXIT_NEW_PRICING_VBAP CHANGING NEW_PRICING.
    Now my requirement is, when u user saves the document, i need to find whether the pricing procedure is changed. if yes, then i have to update all the deliveries for sales order with some values from Ztable.
    please tel me how to check whether the pricing procedure is changed?
    Reward points wil be awarded.
    Thanks in advance,
    Regards,
    Niyaz

    Hi,
    Look at the below link, this may helps you
    http://www.sap-img.com/sap-sd/creating-new-pricing-procedure.htm
    Regards
    Sudheer

  • Replacing  of the pricing procedure by a different pricing procedure .

    Hi
    We are process of changing the pricing procedure of the particular sales  process.
    In case of old open sales order after changing pricing procedure if i update it in VA02 mode then also ...it is not picking the current sales order ...
    Again in case of sales order where deivery has been done ...for them while creating billing ...it is taking current pricing procedure so that there is a mismatch of sales order amount and billing amount .
    Again while creating return order w r t old sales order ...it is taking current pricing procedure in return order instead of taking the original one ....
    Pls advice how to rectify this problem .
    Thanks in Advance
    Regards
    Mrinal

    Dear Lakshmipati,
    I told I am  in process of changing pricing procedure .
    Currently normal pricing procedure is configured in the system. Now business wants to change it in list price pricing procedure ( i.e base price with tax pricing procedure ) . And new pricing procedure has some extra automatic discount value also .
    My question was
    1) There is no change in open sales order ....IT is OK
    2) But for sales order where already delivery has been done then after changing pricing procedure it is taking new pricing procedure so that ..sales value and billing amounts are getting different . How to restrict this .?
    3)For return order also ...it is taking new pricing procedure ... How to restrict the same ?
    Regards
    MKC

  • How to Change Contract pricing Procedure

    Is there a way after the contract has been created to change the pricing procedure it uses. I know you can do this in the sales order.
    Will reward any help.
    Thanks,
    Richard

    Hi
    Pricing procedure is determined from the customer master(customer pricing group in the sales area tab) + document pricing procedure in the order type + sales area
    So if you want to change the contract pricing procedure, change the document pricing procedure in the contract type you are using.
    And make sure there is a combination maintained for the new document pricing procedure in IMG to determine the pricing procedure in the contract.
    Regards
    Sreekar M

  • Excise duty in the Pricing Procedure for Local Purchase / Importation

    Hi,
    I'd like to know how to set up the pricing procedure for the purchase of an IS Oil Material; for local purchase and importation, especially with regards to the excise duty posting.
    Local purchase:  the vendor will bill us inclusive of the ED tax he previously paid, so the tax is just passed on to us..  My receiving location has ED paid status. In the PO item, we need to see this price (inclusive of tax) in the net price field.
    Importation:  the vendor only bills us the cost of the material.  When we received the fuel, we paid ED tax to local tax authorities.
    I know that both in these scenarios, the system has to determine the excise duty.
    My questions are (1) how do you set up the excise duty condition type  in the pricing procedure(or do they have to be maintained in the pricing procedure?) ?   and (2)  how do you set up this condition type in the config?
    Thank you and hoping for your immediate feedback.
    zccr

    Hi,
    You can use same pricing procedure
    put 4 in subtotal in pricing procedure against the Discounr or freight cond
    and in taxinn
    BASb ALTCBV 362 and for jmop 363
    But this will work only if same  discount or freight value is in IV as that given in PO
    if freing value changes in IV then its a problem
    This is SAP bug, and SAP workes in that way only, freight value should be same in PO and IV
    other solution
    in taxinn create tax code like v8 vat 4% for 003 tax clasification
    in ftxp create tax code V8 desc vat 4%
    in fv11 for jvrd put 4
    and at the time of IV put this tax code for freight amount
    and for regular material value V1 tax code
    this will work only if u have used acess seq MWST instead of JTAX pr JST1
    hope this helps
    Vipin

  • Change the Pricing Type during billing

    We are facing an issue with the rebate conditions which needs to be resolved asap..
    User has created a credit memo request in VA01.
    Credit memo request is created for the change in the Price.
    (Note: Order reason for such specific credit memo requests is ZXX (e.g.))
    Due to price change rebate accruals value is also reduced in proportion to the reduced price.
    The rebate accruals should not be reduced in this case, since there is no material return and rebate condition is quantity based.
    As a solution to this u2013
    We created a new routine AAA and assigned to the rebate condition types in Pricing procedure.
    This routine will function when order reason entered in the Credit memo request is ZXX.
    Therefore all the rebate condition types (assigned with routine AAA in Pricing) will get deactivated in Order Conditions tab.
    This is working correctly in creating credit memo (VA01).
    The issue is u2013
    When the credit memo is created in VF01, these rebate condition types are again activated and accruals are posted.
    This should not happen. Pricing from the CM request (VA01) should get copied in Credit memo (VF01) completely. The same issue
    with VF02..
    Please  suggest a user exit in which the pricing type can be changed during billing..Tried coding in the form
    USEREXIT_PRICING_PREPARE_TKOMP in RV60AFZZ by changing the Pricing Type KNPRS..But didnt work out..
    Is there any way to meet this requirement. I have checked the user exit RV61AFZA having two forms:
    FORM USEREXIT_PRICING_RULE &
    FORM USEREXIT_PRICING_COPY.
    I would be interested to know how this can be  coded to meet the requirement. Coding displayed will be of great help to
    implement.
    Any pointers / solutions to the issue will be highly appreciated..
    Moderator message - Please do not offer points or rewards
    Edited by: Rob Burbank on Jul 29, 2010 12:34 PM

    Hello Sean
    1) Firstly I don't think the Credit Memo for this case or any case in your situation should be relevant to rebate.  That's becasue your rebate is tied to quantity.  So you should deactivate rebate processing for that Billing Doc type. T Code OVB0. That should close the issue.
    2) Pricing type 'D' in copy control from sales to Billing documents should ensure that Pricing from the CM request (VA01) gets copied in Credit memo (VF01) completely. Why do you need user exits for that? T code VTFA.
    3) If you need to change pricing type selectively for some conditions, then you should configure the condition type with condition category X,Y or Z ( Customer Reserve) and then use USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA to ensure that those conditions are copied (or otherwise) from source. But I don't think you need this.

  • Run out of step numbers in the Pricing Procedure

    Hello gurus,
    Has anyone come across the following situation:  Within the pricing procedure I want to insert a new condition type but there are no 'free' numbers available within the procedure steps to enable me to do this 
    e.g:  These are the steps in the Pricing Procedure
    Step     Cntr     Ctype     Description
    290     0     ZLTS     Type1
    293     0     ZLTD     Type 2
    296     0     ZDIF     Type 3
    297     0     ZLEX     Type 4
    299     0          Net Value Before Tax
    300     0     MWST     Type 5
    302     0     ZWR2     Type 6
    303     0     ZWR3     Type 7
    My new condition type should be applied on the Net Value Before Tax and before VAT (MWST) but there is no available step number i.e Net Value Before tax = step 299 and MWST = 300.   i.e new condition type should go in between 299 and 300.   Any ideas of how to get around this?
    Many thanks in advance....

    hi,
    you can shfit 299 0 Net Value Before Tax to 298, but you need to check all the alternative calculation types if any susbsequent condition is making us of this step in their calculations. We, use the step numbers(STUNNR) in our alternative calculation types, so if you change their number or sequence you will disturb the calcuation of other pricing conditions.
    so please evaluate from that angle.
    regards
    sadhu kishore

  • Impact of changing secondary pricing procedure

    Hi All
    I have a pricing procedure ZIMPOR having desired condition types. ZIMPOR is having condition type PB00 for gross price and is assigned RM0002 as secondary pricing procedure. I have changed secondary pricing procedure RM0002 assigned to condition type PB00 with ZIMPOR.
    What will be the impact of this change?
    Thanks
    Manoj Gupta

    Assuming the Names are not going to change, and everyone is using the names, then there should be no issues with this change. 

  • Rebate fixed amount condition in the pricing procedure

    Hi SD Gurus,
    i'm using rebate fixed amount conditions (Lum sum).
    The situation from a business point o f view is the following: i pay the customer 1000$ once he made something.
    This kind of condition is not relevant for accruals since they have to be built manually (manual accrual). As a consequence i'm note sure if this condition shoul be put in the pricing procedure used for invoices. In the other and for sure this condition should be inserted in the pricing procedure for manual accrual/credit note.
    What is your point of view!!
    Thanks
    C

    if you are going to use Rebate, then there is no need to add condition type in standard pricing procedure, if you have designed your pricing procedure, include condition types for rebates as in standard pricing procedure.
    This condition type is linked to Rebate type.
    I think you first try the scenario in IDES and then do the same settings as per yoru requirement.
    If you want step-by-step procedure for rebates will help you
    Please refere the thread
    rebate documentation
    Regards
    Jitesh

  • Conditions mutually exclusive in the Pricing Procedure

    Hello,
    I want to define two conditions in the pricing procedure, but I don't want them to be determined at the same time in the billing document. One of them has an access sequence and it isn't always determined, and the other one doesn't have access sequence and is always determined, but I want that the last to be active only when the first one isn't. Is there any way to do this without developing a condition to put it in the requirement field?
    Thank you,
    Silvia

    Try to use the Condition Exclusion For Groups Of Conditions in the pricing customizing.
    Create 2 groups, one assigned to the first condition and the other to the second, then assign the exclusion procedure to the you pricing schema.
    The exclusion procedure should be D, that means:
    Exclusive procedure: If a condition type from the first group exists
    in the document, all conditions types that are found in the second
    group are set to inactive.
    Pls. reward points if helpful
    Regards
    Roberto

  • Step number in the pricing procedure

    Hi experts,
    Pls advise the reasons. How to solve them without changing the step number?
    Q1: As long as HM00 is the first step number in the pricing procedure, the value of HM00 cannot be distributed among items.
    Example:
    Pricing procedure:
    step no.         conditon type
    10                      HM00 (statistical)
    30                      NETW (ERL)
    Sales order (HM00 = $100):
    item 1     NETW = 0
    item 2     NETW = $100
    Q2: When putting a conditon type between PR00 & subtotal in the pricing procedure, such as VPRS, the value of subtotal cannot be the same as PR00.
    Example of sales order:
    PR00 (unit price) = $19.95 per 10kg
    VPRS (internal price) = $10 per 1kg
    subtotal = $2 per 1kg
    Request: PR00 = subtotal = $19.95 per 10kg

    hello, cathy.
    i do not have access to my references now, but please allow me to advance a general concept.
    in SAP standard, HM00 is a group condition, and fixed value.  the distribution of this value is controlled by certain logic.  as in other header condition types, distribution of this amount can be based on either the value or quantity contribution of the different sales order items. 
    what serves as the basis for distribution of HM00, i do not recall but i will get back to you on this... or perhaps another consultant can give it sooner.
    as to your second issue, i will try to understand your situation better.  but generally VPRS is statitical and not meant to come between PR00 and the sub-total.  VPRS has a different logic compared to the other condition types, and is intended to return a statistical presentation of profit margin in the condition tabs.  if fact, in pricing procedure RVAA01 you will notice that VPRS is grouped with the other statistical condition types just before the profit margin.
    regards.

  • Explain the Pricing Procedure

    Hi Friends
    Explain how the pricing is determined for an item, starting from the sales order
    Discuss the full cycle also make a mention  on  the Condition type controls, and Maintain pricing procedure controls.
    Kindly explain it with an example.
    Thanks

    Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
    An Overview of Determination & Configuration of Pricing Procedure is as follows:
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
    Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

  • Configuring the pricing procedure

    Hi Experts,
    My requiremnt is,
    1. configure the price inclusive of sales tax             = X(Gross Price)
    2.calculate the vat of 4% in that                               = X*(104/100)=y(tax amount of 4%).
    3.Net price which is exclusive of tax                       =X-Y=z(net price).
    This is the scenario of the pricing procedure,.
    can u help me how to configure the pricing procedure as per this scenario.
    Gross price which has to be entered ,while  creating the sale order. From that vat 4% output tax which has to be calculated and finally give  the net price excluding the tax amount..
    I dono on what basis i should select my condition tables.I knw only the basic procedure of pricing .
    pls help me urgently.
    Regards,
    Divya.

    Hi divya,
    This may be helpful for u..
    15     0     ZPR0     FACT PRICE STD DOM               
    200     0     JEXP     IN: A/R BED %               
    405     0          Copy of base value     15       
    410     0     JEXT     IN A/R BED total     15       
    420     0          BED + AED + SED+CESS     200     202
    422     0     ZECP     IN A/R % ECess     410     419
    426     0          BED + AED + SED+ CESS     420       
    428     0          copy of Base Value     420       
    430     0          BASIC + ED + ECESS     10       
    440     0     JA1X     A/R Secondary&Hr ECS     424     429
    445     0          BASIC + ED + ECESS+HSCess     420       
                        430     440
    550     0     ZIVP     IN A/R VAT Payable     445     
    600     0          Base + ED + ST     445     560
    810     0          Net Value     600     
    Regards,
    Dippy

  • What is the meaning of this column in the pricing  procedure?

    Dear Gurus,
    What is the meaning of this column in the pricing procedure?
    thanks..

    subtotal field : Subtotal field is used to pass the value to some other field in PO .
    for ex: using value 9 you pass the value to field komp-brtwr. so that this can be used in  any other routine in the pricing procedure.
    requirement field: if there is a scenario that condition type should come in pricing on some condition like vendor country is india. in that case use create the requirment and attached this requirement.in this requirment you put logic and set the sy-subrc value 4 or 0.

  • About tax in the pricing procedure

    Hi Gurus,
    I need your help. Our client says that the tax was incorrectly calculated from the start of SAP application.
    Before SAP Application, their tax is computed as follows based on the Pricing procedure used:
    19% on Freight
    6% on Value of goods
    But now this is how tax is incorrectly calculated:
    6% on net value of goods
    I need your help on how I will solve this issue. This tax calculation should only be applied to sales to domestic Intercompany customer.

    Hi,
    Can you pls explain little more clearly with example in the pre and post SAP scenarios.
    Kind Regards
    Chakradhar

Maybe you are looking for