Issue in SD Pricing

Hi all,
I have created a pricing procedure. Everi condition is being calculated fine but the net value displayed is zero. Please update that why this is happening?
Please respond early.
Many Thanks
AI.

Here is the procedure.
10     0     ZPR0     Cement Basic Rate                     X          2               ERL
30     0     ZFED     FED - Cement                     X          2               ZED
50     0     ZCDI     Cement Discount               
70     0     ZMW1     Cement Discount Tax     50             X
90     0          Duty Paid Value     10     30     X     1
110     0     ZCI     Discount Negative     70             X
130     0          Discount/S.Tax Exclusive Value     90     110     X     2
150     0     ZMWS     Sales Tax - Cement     130             X          10               MWS
170     0          Net Value     130     150     X     3     2
180     0                                                                  A
190     0          Cement Basic Rate     10       
210     0          Cement Discount     110       
230     0     ZSED     SED - Cement     190     210     X
250     0     ZCCL     CCCL Material Rebate                               24               ERB     ERU
270     0     ZCOM     CCCL Mat comm rebate                     S          24               ERB     ERU
290     0     ZFRT     Freight - Cement                     X
Pricing on sales order is coming like:
     ZPR0     Cement Basic Rate     5,766.00      PKR     1     TON     5,766.00      PKR                                        567     TO     625     TON
     ZFED                              700.00      PKR     1     TON     700.00      PKR                                        567     TO     625     TON
     ZCDI     Cement Discount     164.00-     PKR     1     TON     164.00-     PKR                                        567     TO     625     TON
     ZMW1                              86.000-     %                    141.04      PKR                                        0             0
          Duty Paid Value     6,466.00      PKR     1     TON     6,466.00      PKR                                        567     TO     625     TON
     ZCI                              100.000-     %                    141.04-     PKR                                        0             0
          Discount/S.Tax Exclu     6,324.96      PKR     1     TON     6,324.96      PKR                                        567     TO     625     TON
     ZMWS     Sales Tax - Cement     16.000      %                    1,011.99      PKR                                        0             0
          Net Value     7,336.95      PKR     1     TON     7,336.95      PKR                                        567     TO     625     TON
                                   1,011.99      PKR     1     TON     1,011.99      PKR                                        567     TO     625     TON
          Cement Basic Rate     5,766.00      PKR     1     TON     5,766.00      PKR                                        567     TO     625     TON
          Cement Discount     141.04-     PKR     1     TON     141.04-     PKR                                        567     TO     625     TON
     ZSED                              1.000      %                    56.25      PKR                                        0             0
     ZFRT     Freight - Cement     560.00      PKR     1     TON     560.00      PKR                                        567     TO     625     TON               
Please update that what is the issue.

Similar Messages

  • Issue in Oracle Pricing - Creating a new pricelist line

    Hi All,
    We have an issue in Oracle Pricing.
    In a price list we have an existing line with some product precedence value, start date as not null and end date as null.
    Now through our PL/SQL code (using the API qp_price_list_pub.process_price_list) we are creating a new line with the same item, what happens is a new line is created and the existing line is end dated with the new line's start_date-1, but the precedence of the existing line is made null.
    We are unable to understand, is this a standard functionality and if not then what might be done to retain the previous line's precedence value.
    Any help in this would be of great help.
    Regards,
    Shruti

    Hi All,
    Can anyone please help me with the above issue....its getting critical for our client.
    Regards,
    Shruti

  • Issue in making pricing call

    Hi,
    In a price list we have multiple prices based on if the item is under a given model or on it's own.
    With this setup in place we are trying to make a pricing request with apps.qp_preq_pub.price_request but always getting the price of an item when it is on it's own.
    I am passing the attributes to API, could anyone help me correct these:
    ---- Control Record
    p_control_rec.pricing_event    :='LINE';
    p_control_rec.calculate_flag    := 'Y';
    p_control_rec.simulation_flag    := 'N';
    p_control_rec.rounding_flag    := 'Q';
    p_control_rec.manual_discount_flag    := 'Y';
    p_control_rec.request_type_code    := 'ASO';
    p_control_rec.temp_table_insert_flag    := 'Y';
        ---- Line Records ---------
    line_rec.request_type_code    :='ASO';
    line_rec.line_id    :=  v_quote_line_id; -- Quote_line_id
    line_rec.line_index    :='1';
    line_rec.line_type_code    :='LINE';
    line_rec.pricing_effective_date    := SYSDATE;
    line_rec.active_date_first    := SYSDATE;
    line_rec.active_date_second    := SYSDATE;
    line_rec.active_date_first_type    := 'NO TYPE';
    line_rec.active_date_second_type    :='NO TYPE';
    line_rec.line_uom_code    := v_uom;
    line_rec.currency_code    := v_us_curr_code;
    line_rec.price_flag    := 'Y';
    p_line_tbl(1)    := line_rec;
        ---- Line Attribute Record
    line_attr_rec.line_index:= 1;
    line_attr_rec.pricing_context:='ITEM';
    line_attr_rec.pricing_attribute:='PRICING_ATTRIBUTE3';
    line_attr_rec.pricing_attr_value_from:='ALL';
    line_attr_rec.validated_flag:='Y';
    p_line_attr_tbl(1)     := line_attr_rec;
    line_attr_rec.line_index    := 1;
    line_attr_rec.pricing_context    :='ITEM';
    line_attr_rec.pricing_attribute    :='PRICING_ATTRIBUTE1';
    line_attr_rec.pricing_attr_value_from    :=v_item_id;
    line_attr_rec.validated_flag    :='Y';
    p_line_attr_tbl(2)    := line_attr_rec;
        line_attr_rec.line_index    := 1;
    line_attr_rec.pricing_context    :='PRICING ATTRIBUTE';
    line_attr_rec.pricing_attribute    :='PRICING_ATTRIBUTE3';
    line_attr_rec.pricing_attr_value_from    :=v_item_id;
    line_attr_rec.validated_flag    :='Y';
    p_line_attr_tbl(3)    := line_attr_rec;
        line_attr_rec.line_index    := 1;
    line_attr_rec.pricing_context    :='PRICING ATTRIBUTE';
    line_attr_rec.pricing_attribute    :='PRICING_ATTRIBUTE2';
    line_attr_rec.pricing_attr_value_from    := ip_operating_unit;
    line_attr_rec.validated_flag    :='Y';
    p_line_attr_tbl(4)    := line_attr_rec;
    line_attr_rec.line_index    := 1;
    line_attr_rec.pricing_context    :='MODEL_ID';
    line_attr_rec.pricing_attribute    :='PRICING_ATTRIBUTE4';
    line_attr_rec.pricing_attr_value_from    := v_config_model_id;
    line_attr_rec.validated_flag    :='Y';
    p_line_attr_tbl(4)    := line_attr_rec;
        ---- Qualifier Attribute Record
    qual_rec.line_index    := 1;
    qual_rec.qualifier_context    :='MODLIST';
    qual_rec.qualifier_attribute    :='QUALIFIER_ATTRIBUTE4';
    qual_rec.qualifier_attr_value_from    := v_us_price_id;
    qual_rec.comparison_operator_code    := '=';
    qual_rec.validated_flag    :='Y';
    p_qual_tbl(1)    := qual_rec;
        apps.qp_preq_pub.price_request (p_line_tbl, p_qual_tbl, p_line_attr_tbl, p_line_detail_tbl, p_line_detail_qual_tbl, p_line_detail_attr_tbl, p_related_lines_tbl, p_control_rec, x_line_tbl, x_line_qual, x_line_attr_tbl, x_line_detail_tbl, x_line_detail_qual_tbl, x_line_detail_attr_tbl, x_related_lines_tbl, x_return_status, x_return_status_text);
    Thanks
    Sai

    Hi,
    Got your issue now.
    There is no problem with your service configuration. Changes required at server level. Let me explain this
    Instantiation is happening because of transactional & retries configuration, but when you are using reply action in error handler you are actually completing the transaction by sending reply. The error I suspect is to be effect of redelivery-limit=1.
    eg in xbusResources-jms.xml in your domain config
    <queue name="wlsb.internal.transport.task.queue.file">
    <sub-deployment-name>wlsbJMSServer</sub-deployment-name>
    <delivery-failure-params>
    <redelivery-limit>1</redelivery-limit>
    </delivery-failure-params>
    <jndi-name>wlsb.internal.transport.task.queue.file</jndi-name>
    </queue>
    Follow the below steps
    On Weblogic Admin Console go to
    Services > Messaging > JMS Modules
    See if you can find a module called "jmsResources"
    In jmsResources configuration check for ... wlsb.internal.transport.task.queue.file
    There go to Delivery Failure tab. The Redelivery Limit must be 1 there.
    Change it to 0.
    Thanks,
    Durga
    - It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).

  • Issue in MM Pricing

    Hi all,
    I have an issue to discuss. When we procure a material, there are 3 types of costs:
    - that belongs to vendor like price, discount, salex tax, etc
    - some other conditions that does not belong to vendor but have effect on material cost like insurance charges, lc opening charges, bank charges etc etc
    - some other conditions that do not have impact on material cost but pay to different vendors like labour charges.
    Please tell that which conditions should come on PO and how can we differentiate among these conditions and when the financial impact of these conditions will appear?
    Many Thanks.
    Best Regards,
    AI.

    hi,
    Yes. Change the calculation with accrual settings which identifies various types of G/L Accounts with the aid of Account key.
    by
    Prabhu
    Edited by: Prabhu Narayanan on Sep 1, 2009 1:11 PM

  • Issue regarding condition pricing date as system date for some condition types in sales order

    Hi
    I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
    Regards
    prashant

    Hi
    When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
    After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
    Regards
    PK
    Sales order header change mode VA02
    Here pricing date VBKD-PRSDT = 04.06.2016
    Item change mode
    I have added new line item 150 on 14.06.2014
    Changed the condition pricing date to 14.06.2014 & saved
    After saving I have gone to Va02 screen of line item 150
    & there I have gone to condition pricing date field from item condition tab
    for JEX2 condition type but still here condition pricing date is showing as
    04.06.2014 as below.
    Condition pricing date
    My requirement is like this
    For some particular conditions like JEX2  condition pricing date will take as system
    date instead sales order creation date when I will add a new item 150 on
    14.06.2014.but for other conditions it will show as order creation date for the
    same line item 150 .

  • Issue with the Access Sequence related to Pricing

    Hi Gurus,
    I have one issue related to Pricing. I have an access sequence ZPCD which has Table "A558" assigned to it.
    Table A558 has fields
      5  Sales Org
    10  Distribution channel
    20  Division
    25  Customer.
    But the issue is here.....in the access sequence ZPCD the field "20  Division" got deleted some how.
    but i checked the table A558, it has "Division" in it.
    So, summary is Table A558 has field Division, but the access sequence ZPCD is missing field Division in Access table A558.
    Table 518 contains 585 condition record entries entries in Production system.
    So question is how will i add Division back to the Access sequence Table A558.
    Waiting for your expert advise and comments
    Thank you

    Dear Anitha
    If I am correct, in access sequence, at field level, there is no deletion option available and hence, I am surprised how this could be possible.
    Anyway, you can try in development server as follows:-
    Go to V/07, select ZPCD, block the table 558 and delete.  Save the data.  Now try to reassign the same table and see how it works.
    thanks
    G. Lakshmipathi

  • Intercompany Pricing issue

    I have an issue with intercompany pricing.  I need to redetermine the pricing (reprice the billing document) on a user exit; at least I believe so.  What we are doing is as follows:
    We need to change the sales org, distribution channel, and sales group, on the billing document, in order to distribute commissions properly.  We then have a pricing condition setup but we get the following message (message number 108) when we view the pricing conditions of the saved billing document:
    "Condition record exists, but has not been set"
    What does this mean and/or how do we solve it?  I assume it just means that I have to manually reprice it after I change the fields.
    Regards,
    Davis

    Thanks for your reply
    Yes I followed the same process first intercompany invoice and then standard invoice.
    but got pricing error in intercompany invoice and also the pricing procedure is picked up accurately only the values are not appearing.
    The condition records are also maintained properly for billing date.
    Thanks,
    Deepak

  • Having Peformance issues Advance Pricing Form

    we are in R12 .12.1.3.
    We have 2 envs.
    Having issuewith QPXPRFOR.fmx
    One env we do not have performance issue while in other we have issue in loading pricing attributes.

    we are in R12 .12.1.3.
    We have 2 envs.
    Having issuewith QPXPRFOR.fmx
    One env we do not have performance issue while in other we have issue in loading pricing attributes.

  • Issue with BAPI CONTRACT CREATE while uploading pricing conditions

    Hi Experts
                        I am using BAPI CONTRACT CREATE to create Purchase Contract ME31K
    I am facing the issue while passing pricing conditions  Could you please help me regarding this
    Could you please help me along with this what are the values has to pass
    Thanks
    Vijay Kumar Reddy

    Hi Experts
                        I am using BAPI CONTRACT CREATE to create Purchase Contract ME31K
    I am facing the issue while passing pricing conditions  Could you please help me regarding this
          gs_oucondition-item_no = w_data-evrtp.  
          gs_oucondition-serial_id = '1'.     
          gs_oucondition-cond_count = '01'.     
          gs_oucondition-cond_type = w_data-cond1.     
          MOVE w_data-amnt1 TO gs_oucondition-cond_value.     
          gs_oucondition-currency  = w_data-curr1.     
          gs_oucondition-numerator   = '1'.     
          gs_oucondition-denominator = '1'.     
          gs_oucondition-change_id   = 'I'.     
          APPEND gs_oucondition TO gt_oucondition.     
          CLEAR gs_oucondition.
          gs_ouconditionx-item_no = w_data-evrtp.     
          gs_ouconditionx-serial_id = '1'.
          gs_ouconditionx-cond_count = '01'.     
          gs_ouconditionx-item_nox = c_x.     
          gs_ouconditionx-serial_idx = c_x.     
          gs_ouconditionx-cond_countx = c_x.     
          gs_ouconditionx-cond_type = c_x.     
          gs_ouconditionx-cond_value = c_x.     
          gs_ouconditionx-currency  = c_x.     
          gs_ouconditionx-numerator   = c_x.     
          gs_ouconditionx-denominator = c_x.     
          APPEND gs_ouconditionx TO gt_ouconditionx.     
          CLEAR gs_ouconditionx.
    Could you please help me along with this what are the values has to pass.
    these are the parameters passing to the condition structure while executing bapi i am getting error like enter quantity conversion.
    but with the same data i am able to create contract using SE37 by directly executing the Function module.
    and if i have net price in my excel sheet also i am able to create contract using my program.
    the only problem with pricing conditions alternatively there will be no net price..
    Please really it will be a challenging question....
    Thanks
    Vijay Kumar Reddy

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

  • Credit note is having different pricing procedure

    Hi All,
    We have an issue with the Pricing procedure determination.
    While creating Return order, we are creating with reference to standard Invoice.
    Document pricing procedure in the Standard Invoice and Return order are different.
    We maintained different pricing procedure for Return order. But system is copying the Pricing procedure from Invoice into the Return order.
    We are creating Return credit note with reference to Return Delivery.
    Here in the Credit note, Pricing procedure is different, that is actually what we maintained in OVKK.
    But in VTFL, Pricing source field is maintained as "Order" only.
    Does this setting not enough to copy the pricing procedure from the Return Sales order.
    We need the same Pricing procedure what is available in the Return order to be copied into the Return credit note.
    Advice me what standard settings to be done to achieve this.
    Regards,
    Rajesh Lingadurai

    Dear Manoranjan,
    Thanks for the reponse.
    Return order part is clear to me. As per standard, system is copying the Pricing procedure from the Invoice.
    But I am not clear about Return Credit memo i.e. Billing part.
    As I explained above, I believe the Pricing procedure will be redetermined in the Billing only when the Document Pricing Procedure in the Billing is different from the Sales document type.
    But in my case, Document pricing procedure is same in Sales document type and Billing document type, but why system is redetermining the Pricing procedure in the billing level.
    As per our requirement, system has to copy the Pricing Procedure and Condition values whatever is determined in Return order level into Invoice level.
    Is it possible to copy the entire pricing from Sales order into Billing even if it is Delivery related billing.
    I hope it is clear now.
    Regards,
    Raja Durai

  • How can we revise the pricing both at header and item level of sales order?

    Dear All,
      Now there's one issue of the pricing to me. i want to revise the pricing both at header and item level of sales order. but after i finished the cutomize and tested it, it's more different as i thought. i found that the pricing can revise at the one side only,for example, if i revise the pricing at item level and it's grey and can't be revised at the header. on the other hand, it's the same result what's happened at item.
      So, in my opinion, we can't revise the pricing both at header and item, right? if not, please give me more advices and teach me how to solve the problem. thanks a lot.

    Dear Lakshmipathi,
      Thanks a lot for your kindly and useful answer for me and I learn more for the pricing technology.
      I didn't notice the way that you reminded ago therefore I also saw the button at the condition tab. And your suggestion makes me know more.
      And I had tested the way that you said, I met with a question. Below is my opinion for my testing.
      I had created one SO and the pricing was $10, then I revised the pricing from 10 to 15 by VK11. It can't be updated automatically at SO and I must update it manually by clicking the "Update" button. This is OK for my testing, but I have another question to disturb you for the use of "Active" button. When I click the button and nothing is responsed, it's quite different what you said. So, please give more detail for the Active button. Thanks a lot.

  • Pricing Related Question?

    *Hi Gurus,*
    *I have an issue related to pricing.that is as follows..*
    *A freight condition is there.that needs to be determined with first invoice and not for the other invoices.*
    *Ex:i have sales order with four items.This conditoin determined in the sales order.Now i am doing invoice for two items.*
    *In this the condition needs to be determined for first invoice(two items),not for other invoces.*
    Please provide solution as early is possible.
    Thanks in Advance
    Ash
    Edited by: dasariashok on Sep 27, 2011 11:03 AM

    Hi,
    I hope it is possible for the condition type KF00 (FREIGHT) check the field Condition update at master data section in V/06.
    and in condition record VK11 for that condition maintaine condition values,double click on condition line and at additional data icon you specify max no.of sale orders 01,at limits of pricing tab and maintaine max condition base value for each and max condition value.save the record
    Ex:
    max condition base value(quantity) 2 EA
    max condition value 200 inr (2 EA x 100)
    and create order you will get condition value for 2 EA max.
    i did not tried it let you do it and check.
    Thank you.

  • Pricing data not geting picked in business orders

    Hi All,
    I am facing an absurd issue related to pricing. I have maintained all settings for orders, pricing, sales area, item categories etc.
    Yet when i try to create an order and enter the product, the pricing does not get picked?
    I tried alot but dono what is going wrong.
    If anyone can help, that would be great....
    Nicol

    Nicol,
    Going by your words that you have maintained all the settings, I wont challenge that.
    However I would like you to check one specific setting in item categories.
    In item category customization, check settings for pricing relevance. Make the relevant setting.
    Just a thought though. Hope this helps.
    Julius

  • Pricing condition value mismatch:

    I have an issue on, how pricing value is getting determined.
    Our client wants to dictate the price at each level. For example,
    if 100 EA = 234.77 EUR and if customer orders 125 EA system should calcuate the value in the following way.
    First it will convert the value to one unit price which is 2.3477 and round the value to two decimal. Now value would be 2.35
    Now this one multiplied by the quantity will be the price for the customer. So price = 2.35*125 = EUR 293.75.
    In order, under condition tab we have four Columns
    1. Conditino type 2. Name 3. Amount, 6.Condition value.
    Under komv-kbetr we are pulling EUR 2.35. but under KBETR, value is not 2.35Qty = 293.75, but instead it's 125234.77/100 = 293.46
    Because in Kbetr the value is rounded, where as in Kwetr the final amount (293.46) is being calculated before rounding the condition value. ( No rounding of 234.77/100 to 2.35).
    Any clue what to do on Kwert so that it will match with Kbetr.
    Thanks,

    Hi,
    In my opinion, logically what SAP is calculating is correct.
    If you round-off, before doing the calculation as 2.35, then for 100 EA it would be 235.00 EUR which is incorrect pricing.
    Per SAP calculation, 293.46/125 = 2.3476, which almost equals to 234.77/100 = 2.3477.
    So it looks at one hand, you are trying to charg more if the customer buys more quantity. (by applying 2.35 EUR per 1 EACH).
    So inform your customer that the pricing is correct.
    If you want to round to 2.35, then in transaction VK12 itself, you can change the pricing record as 2.35 EUR per 1 EA.
    Regards,

Maybe you are looking for