Error: No Pricing procedure(Sales Order)

Dear All,
I am getting a error saying, "No pricing procedure determined while I am trying to generate a Sales Order in SAP SD. Need Help.
Thanks and regards,
Sunil S

Hi,
It looks you need to assign the pricing procedure to the sales document type.
Go to SPRO-> Sales and distribution -> Basic functions -> Pricing -> Pricing control -> Define and assign pricing procedure.
Go through all the steps like define and assign customer and document pricing procedures, and define the pricing procedure determination.
Hope this helps

Similar Messages

  • Condition rounding error in pricing of sales order

    Hi all,
    I have a problem on rounding of condition type MWST in a sales order.
    I have the PR00 condition evaluated with 6,50 euro for 1 piece; on this price should be applied condition type MWST with a percentage of 10%.
    The result should be 0,65 euro but the system shows (and calculates) 0,64 euro for MWST.
    How can I solve this rounding problem?
    Thanks in advance for your helpful answers.
    Alessandra

    Hi,
    Check if you are using VOFM subroutines in your pricing procedure (V/08) or in the condition type (V/06) for rounding rules.
    Check too this notes and related notes in them (surely, they will help you)
    Note 80183 - Rounding
    Note 315792 - Group conditions of the same amount on item
    Note 166952 - Rounding when distributing header conditions
    Note 517829 - Source code f new dstrbtn rule 'roundng diffrnce comparison'
    I hope this helps you
    Regards,
    Eduardo

  • Re-Pricing on sales order

    Hello All,
    How can I redetermine pricing for a change in item partner. The user exit USEREXIT_NEW_PRICING_VBAP or USEREXIT_NEW_PRICING_VBKD does not have visibility to VBPA table...
    Thanks,
    Sunny.

    But, the exception to that is the service render date should be of w.r.t. new tax values
    & this will be determine from delivery doc date.
    case1. could you please elaborate the above point?
    why delivery doc date shall determine the tax value? is it not the pricing date and the validity period of the condition type in the condition record that determine the values?
    Business scenario with different pricing procedures - sales order & billing doc.
    this "concept" (of diff pps) is still not clear.
    1. From a business process perspective, why shall I tell my customer, via my sales order that the price = 100EUR and bill him another price, e.g. = 90EUR?
    moreover, if finally i want to give my customer at a reduced price, then i would tell him this upfront (during the creation of s.o.) as this is to my advantage.
    2. "Gross Price, Taxes, Discount, Rebate, Freight, Frieght related Insurance charges, Handling charges, etc." All these condition types I can have in one pp and then with requirements; e.g. in the case of Rebate condition types requirement =24,25; in standard functionality; activate or deactivate when required. Thus why do I need 2 pps, as you have suggested in this example?
    other examples are welcome!
    many thanks, in advance!

  • Price error - In creation of sales order

    Dear ALl,
    When i am trying to create a sales order with the t -code VA01 and enter a material i get a warning saying
    "000010:: Enter Pricing".This happens only for one customer ,for other customer with the same material there is no warning.
    Can some one guide as to what is missing for this customer.
    Thanks in advance,
    Swati

    Hi,
    You have to maintain the CONDITION RECORDS for the MWST condition type in the transaction code VK11
    Alternatively  you can also do some configration to make the MWST as Optional
    In the Pricing procedure V/08 uncheck the  MANDATORY and check the Manual option which will not display the Error.
    During the Sales order processing you can enter the MWST price as some percentage.
    Please do the above and revert back if you need any other details
    thanks,
    santosh

  • Error while saving the Sales Order

    Hi experts,
        i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
    Thanks.

    I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
    You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
    Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
    If you see what they are, you can check to see what the usages represent.   Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc.   In our system, we only have A entries.
    What are the usages for the 521 entries?  Do they relate to Free Goods/Pricing???
    Does the table KOTN521 exist in the ABAP Dictionary?
    Answering these questions may get you closer to the answer.
    Can you compare the values in these entries to what you have in different SIDs?
    Is this problem happening in Production, or is it still in a development or Quality Assurance client?
    If it is still in development or Q, then it may be that a recent customization change was made.
    Compare the entries across your systems, if possible.
    Good luck
    Brian

  • Back Calculation in Pricing for Sales Order.

    Hello friends,
    Please help me out with this below mentioned problem in the Pricing for Sales order.
    I am creating a Contract with Customer and Plant from the same Region (State), while creating the subsequent Sale order I want to use the plant of some other Region which is different from the contract. In this case the pricing will change as there will be different Taxes (%) that would be applicable for different Region.
    Now the requirement is that we want to use the Final Selling price which is calculated in the contract, therefore by keeping the Selling Price Fixed we have to backtrack and calculate new pricing accordingly.
    An example for the same is explained below:
    When Both Customer and Plant are from same Region:
         Particulars                        %           Value
    A     Basic Value                                       100000
    B     ED                     10.30%           10300
         Sum total (A+B)                                 110300
    C     VAT                        5%            5515
         Sale Price (ABC)                                 115815
    When Customer and Plant are from different Regions:
         Particulars          %           Value
    D     Basic Value (A-B-C)                  92105
    C     ED                        10.30%            9487
         Sumtotal (A-B)                  101592
    B     VAT                          14%            14223
    A     Sale Price                                       115815
    Please reply with possible solutions.
    Thanks and Regards,
    Edited by: Lakshmipathi on Oct 4, 2011 5:41 PM
    Thread Locked - Reason Cross Posted

    Hi Nitin,
    Go through the bellow links you can resolve your problem.
    Re: Reverse Calculation in Pricing Procedure
    Reverse Pricing???

  • Activating Pricing for Sales Order in Retail

    Hi All/Vijay/KK,
    Please tell me how activate the pricing for sales order, actually in SD we do Pricing Determination, what has to be done for Retail pricing

    Hi,
    To do sales order pricing
    Goto IMG>Sales & Distribution>Basic Functions>Pricing>Pricing Control
    Either Follow Standard, condition type PR00
    or in case of Custom
    1. Use condition table 406 Site/article
    2. Define Access Sequences ZPR0
    Enter accesses:10 406 Site/article Exclusive x
    3. Define Condition Types (ZPR0 assign newly defined access sequence)
    4. Define And Assign Pricing Procedures (assign condition types ZPR0..etc. to it)
    Then maintain condition record , go to VK11 --> Enter your Z condition type (eg. ZPR0)., enter the amounts.
    Add the pricing procedure , to sales document type.
    For Retail Sales Pricing
    For Retail Sales Pricing based on Purchase pricing you can follow the following method:
    The retail price is always based on the purchase net/net price. This purchase net price is built up from the purchasing pricing elements or condition types defined to be included in the purchase net price. A planned mark-up is applied to the purchase net/net to calculate the proposed retail price. The planned mark-up can be set by merchandise category and for exceptions, more specifically by article.
    You can perform Two-step calculation for retail pricing, for example, for stores that are supplied by a distribution center (internal vendor). Calculating sales prices for the stores is based on the transfer price for distribution centers (preceding organizational unit).
    1. Set up Master Data (WB02) - Relevant Fields should be maintained
    2. Set up Article Master Data - Logistics DC and Store View (MM42)
    Relevant Fields should be maintained
    3. Maintain Mark up for DC(VK11) -Markup % at Distribution channel distribution chain level
    Mark ups maintained at two levels:
    For DC: At distribution chain level
    Condition type used: AUFS
    For Stores: At article level
    New condition type ZUFS created.
    4. Maintain Mark up for Stores (VK11) Markup % at Store distribution chain level
    5 Create Pricing Procedures (IMG) -Pricing Procedures created
    6. Carry out Price calculation for DC(VKP5) - Pricing Document created - DC Transfer price calculated
    7. Carry out Price calculation for Stores (VKP5) - Pricing Document created - Final Retail Price Calculated
    The final retail price that is calculated is stored in the condition type VKP0.
    Hope it helps,
    Regards,
    Anirban Roy

  • RunTime Error while saving a Sales Order

    Hi All,
    When i am saving a Sales Order, the system is throwing a Runtime Error.
    The ABAP Code in the Runtime Error screen as follows.
              select * from (t681-kotab) appending table <cond_tab>
                     up to 1 rows
                     where kappl  = se_kappl
                     and   kschl  = se_kschl
                     and   datbi >= se_date
                     and   datab <= se_date
                     and   (coding_tab).
    Till these days, there was no such error while saving a Sales Order.
    How to resolve this issue?
    Regards
    Pavan

    Hi,
    The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
    select * from (t681-kotab) appending table <cond_tab>
    up to 1 rows
    where kappl = se_kappl
    and kschl = se_kschl
    and datbi >= se_date
    and datab <= se_date
    and (coding_tab).
    The reason could be is someone has screwed up the entries in T681 table. Check that out.
    Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
    Let me know if you are still stuck up.
    If you can send me the ST22 dump of the run time error, i might be able to help you more  on this.
    Hope this helps.
    Thanks,
    Balaji

  • Error while creating the sales order with billing reference

    hi alll
    i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
    cheers
    shalsa007........

    Dear SAP SD 007
    I can confidently tell that an enhancement or an user exit has been applied in your scenario
    You have to check that
    Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
    Your people has solved the standard problem by enhancement
    Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
    Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
    To solve this only your people have used userexit
    Line items and qty greyed out means definately there is some enhancement or user exit applied
    You have to check that
    Regards
    Raja

  • Incompletion procedure -Sales order Item level.

    Hi
    I want to add the field "MATERIAL SALES TEXT" in Incompletion procedure -Sales order Item level.
    The Table that i need to enter in procedure is VBAP.
    But what should be the "Field Name" and  Screen for creating missing data?
    Plz Help....
    Regards
    Subhasish

    Field ARKTX refers to 'Description' of material in sales order and not to 'material item text'.
    'Material sales text' flows into sales order from the text you maintained in customer master record or Material master record.
    Of course, you could also maintain sales text at sales order stage also.
    Incompletion process inspects specific fields in order to see if data has been maintained in these fields. Should data not be maintained in these specified fields, the system is told how to respond, that is, whether or not to give a warning message and to what extent does it allow further processing of the document.
    Material sales text is not a field.
    So, you cannot add material sales text at incompletion procedure.
    Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

  • Configuration Validation error when booking an Sales Order.

    Hi,
    Getting an error when booking an sales order ie; "Configuration Validation error".
    We are upgrading from 11.5.8 to 12.1.1 and this issue is critical. Please provide your valuable suggestion and advice.
    Thanks in advance,
    Asif

    It seems you use configurator. Is this happening in production or in some test instance?
    If it is a test instance, when was it cloned from prod? Did you clone the configurator instance at the same time?
    1) You should publish the configurator model from the configurator developer to this new instance.
    2) Also, it is possible that the selections made during order entry earlier are not valid anymore due to ECO/BOM changes or due to configurator rule changes. Open the configuration, make any selections if necessary and then click ok.
    This will repopulate the order lines then you should be able to book the order.
    Hope this helps
    Sandeep Gandhi
    Independent Techno-functional Consultant

  • Error as Deficit in Sales Order stock in VL02N

    Hi Experts,
    We have a problem while doing PGI in VL02N we are getting below mentioned error as                       Deficit in Sales Order stock. We have analyzed and found that although GR for PO is done, the Customer stock for Sales is not getting updated .we has referred in the same in MD04 also.  So while doing PGI the error "Deficit in Sales Order stock" is displayed.
    Please guide us to proceed further on this issue.
    Cheers,
    Kumar.S

    Hi Kumar
    Deficit in Sales Order stock. during PGI
    The reason is in MMBE there is no sales order stocks reserved against your sales order number
    We have analyzed and found that although GR for PO is done, the Customer stock for Sales
    is not getting updated .we have referred in the same in MD04 also.
    I beleive that you are  doing individual purchase order As soon as you save the sales order system will trigger a PR and MM will convert the PR to PO and GR is made against the PO and after the receipt of stocks you will create the delivery for your sales order
    If this is the process you are doing then your sales order item category should be TAB with special stock indicator E marked
    Check this
    whether you have marked E in item category TAB in VOV7
    and make sure GR is made as a sales order stocks against this PO
    In standard it will be managed as a sales order stock and Item cate group of the material in MMR should be BANC
    Or if you are creating the sales order with  item category  marked with special stock indicator E and if you  receive the material from vendor then receive it through MB1C with movement type 561 E
    This should solve your problem
    Create a fresh cycle and see and after making the suggested settings
    Regards
    Raja

  • User-exit for  carry out new pricing while sales order save automatically

    Hi all,
    I need to carry out new pricing while sales order save automatically. Please any one help me to finding proper user-exit to achieve my requirement.
    Thanking You.
    Moderator message: please search for available information.
    Edited by: Thomas Zloch on Jan 11, 2012 12:53 PM

    Pl help.

  • Sales document number based on pricing procedure ,sales area , customer pri

    Hi,
    where can i get saler document number based on pricing procedure ,sales area , customer pricing procedure and document pricing procedure.
    please tell me the table name.
    Thanks
    Edited by: pandu123 on Jun 16, 2011 8:22 PM

    I never heard of this requirement before, pulling sales document number based on pricing procedure based on customer pricing proc + document pricing procedure +sales area. These data are found in tables VBAK, T683,KNVV and TVAK. I dont think you can use ABAP query to join these table, check with an ABAP'er to develop a program for this requirement.
    Regards,

  • Error in Pricing Procedure Determination in Sales Order

    Hi All,
    I have created a Pricing Procedure and asiigned it with the SALES ORG, DIV, DISTR CHANL, CUSTOMER PRCDR and DOCUMENT PRCDR in SPRO.
    i have assigned the Cust Doc Prcd with the BP and the Docuemnt Prcdr with the respective transaction. And also created the Basic Price for product and Discount Price for Sold To Party via CONDITION MAINTENANCE.
    Still getting this error.
    Looking for the solution.
    Thanks,
    VS

    If you have check what RK suggested and is ok, then check also the customization of your transaction in spro>crm>transactions>basic settings>define transaction types.
    go to your transaction type and then in left panel select customazing header. there check if you have defined under pricing data the doc.pric.proc. (document pricing procedure)
    and also if you are not always using customer pricing procedure it is good to define in spro for determination of pricing procedure 1 determination rule which has filled only the folowing data:
    - sales organization
    - distribution channel
    - document pricing procedure (the one you defined on transaction - which I described above)
    - procedure
    and division (if you use the dummy one) and customer pricing procedure leave empty. this way the procedure will be determined even if it's not found from customer sales data
    And also be aware that once the error message for determination of pricing procedure appears it can't be removed so don't try the determination with already corrupted transaction.

Maybe you are looking for