Issue in Pricing Exclusion

Dear Team,
I have a issue with Condition exclusion, We have created the condition exclusion and assigned to pricing procedure,but when we are trying to enter the condition type in the sales document net value is showing '0', Zero, please help me how solve this issue.
Thanks & Regards,
MK.

Dear Murali,
Please cross check the configurations done with the below link.
http://www.sap-img.com/sap-sd/how-to-use-condition-exclusion-type-in-so.htm
Check whether any configuration is missing.
Revert back after that.
Thanks & Regards,
Hegal K Charles

Similar Messages

  • I have an issue with pricing condition ZPRO (basic price )

    Hello gurus
    I have an issue with pricing condition ZPRO (basic price ).
    users created a sales order, and the basic price ZPRO which is mannual is added twice ,now i want to put a check so that condition tpye zpro is not accepted twice by the system. please let me know how can i restrict  system from accepting condition type zpro  twice during sales order.
    regds
    Edited by: sapuser09 on Jul 26, 2011 8:44 AM

    Hi,
    Solution for this is very simple. Don't make any changes to the sales order user exit. Use condition exclusion  for the condition type.
    Do customization in the following path of IMG
    Sales and distribution---- > Basic Functions--- > Pricing--
    > Condition exclusion -- > Condition exclusion for groups of conditions
    First  In Define condition exclusion groups you have to define condition exclusion group (ZXXX)
    Then  in Assign condition types to the exclusion groups you have to assign condition type to the exclusion group (ZXXX   ZPRO)
    Then in Maintain Condition exclusion for pricing procedures select the pricing procedure where you have the problem and click Exclusion box present in Dialog structure box
    You will be faced with Change view exclusion overview screen Click new entries
    You will be faced with New entries overview of added entries screen.
    Take serial no as 10 Condition exclusion procedure  as B (Best condition with in condition type) In the exclusion group1 add the exclusion group ZXXX.
    Save it and create order.
    In the order pricing you will again observe that ZPRO appearing twice but only one will be active.
    Changing user exit for this issue is not at all required and it must be only the last resort Try replicating the issue in your sand box system. As I had mentioned it will be picked twice but only one will be active.
    Hope this helps.
    Edited by: mokirala tilak on Aug 10, 2011 10:19 AM

  • Issue in Pricing Formulae

    Hi Sap gurus,
    I am facing one issue in pricing. I am getting this error in my effective pricing condition.
    "Inactive via formulae of incorrect". Can any body please give me some lights on the issue?
    Thanks.
              chetali

    Hi Chetali,
    As per your error mssage I came to know that this is related to some routine issue which is assigned to that 'effective pricing condition'
              So, Please check the settings related to the requirement ,alternative calculation type and alternative condition base value routines of that condition type.
    Also check the logic involed in the routines with the ABAPer help.
    I hope it will help you
    Regards,
    Murali.

  • Issue on Pricing

    HI SAP Gurus,
    Could any one help me out with an Issue on Pricing
    The need is
    Our company sells consumer goods through our website store. We introduced a coupon system. The coupn system is that if u r a coupn member (means employees of the organisation) and if u put ur coupon no then the customer will be entitled for a discount of fixed Percentage.
    How i put the values of coupn in pricing procedure,
    Could any one help me out in this procedure
    Thanks in advance
    EDIE
    Edited by: Edie Edie on Jan 8, 2008 11:24 PM

    hi warwick,
    we r not using condition records, so no acess sequence, we r manualy updating the conditions value in  the pricing.
    Is there any way to create  a service material and put in the item level of Sales  order with the name coupn, so 2 items in  sales order, 1 is the main item and 2nd the coupon
    1st item we put the price, 2nd item we put the percent discount for coupons, because we dont want to see this coupon discount in first item pricing
    thanks in advance
    Edie

  • Issue with Pricing in Invoice.

    Hi,
    I have one condition ZIST in my pricing. Whenever I create the invoice manually through VF01, all the items are showing up proper values of ZIST, however header is not showing the proper value (Header is showing the value which is suppose to be at the header minus correction value with respect to rounding off). But when I click on ACTIVATE button on the header pricing screen, system updates the correct value of ZIST.
    If I dont click on activate button then Invoice gets saved with wrong ZIST value at the header.
    I dont know how should I tackle this issue, Do I need to write a code somewhere to carru out the pricing again to update the right value of ZIST.
    Edited by: sanjay kulkarni on Sep 22, 2009 4:00 AM

    Thanks for ur response.
    Actually in my case netwr value is correct and all the line items are also in good shape, problem is only with header level pricing, that too only one condition is showing wrong value and that needs ACTIVATE to click to get updated with correct value.
    In my case its very diffucult to replicate the senario and the one example we have for testing is a huge invoice. Also my pricing procedure has many routines hooked to diffrent condition tyeps. Hence it would be tedious job to debug and see each and every routine from the pricing.
    Still, I would try to do it. But I would appreciate if you can let me know what did your developer do wrong in the routines so that I would also concentrate on the same line.

  • Issue during pricing in invoice

    Hello everyone,
    I have a question regarding pricing during invoicing.
    We have a tax condition type used to calculate VAT on free goods sale. As we want tax to be computed based on 'sales order reason' entered during sales order, i created a new condition table with one of the fields as 'order reason' AUGRU assigned from structure KOMV. This table is assigned to existing access sequence and the tax based on order reason is correctly picked up during the order creation.
    But this tax condition is missed during the billing creation. The copy control settings are set such that tax conditions are redetermined during billing. Hence the system is trying to redetermine the tax based on order reason. As it is failing to find the order reason during billing, the retrieval of condition record is failing.
    I guess the issue is because the order reason is maintained at header level in order but at item level in invoice. In the field catalog of access seq, as i assigned AUGRU to header structure KOMV, the system is failing to find the order reason during invoice as its maintained at item level. I tried to assign AUGRU to item structure KOMP but that field is not available in KOMP.
    Please let me know how to get around the problem.
    Thanks,
    Kits008

    I have a full cycle testing.
    Now, I understand where is problem occurred.
    For sales order pricing, the order reason can pass to KOMK from order header and can be used in pricing determination procedure.
    But for billing document, the order reason in "VBRP-AUGRU_AUFT", if you carry out a new pricing , then the system caused a problem like the post.
    I suggest you implement the user exit (USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ))
    If you have further problem, please reply the post.
    Flex Yang
    FI/CO, MM, SD Certificated

  • Issue in Pricing

    Hi All,
    We have an issue is we have created a credit memo with ref to the invoice, and Discount condition type has the value in the credit memo request. While creating the Creditmemo invoice Discount condition type is missing in the invoice means it was not copied from Creditmemo request (CR ) to Creditmemo (G2). Kindly advice what could be the issue? How to fix .
    Thanks in advance..
    regards,
    SK

    Hi Lakshmipathy,
    Thanks for the reply.  As per your i have checked the same but VOV8 and VOFA is having the same doc pri procedure. In VOKK Pricing procedure is assigned as ZSN0007. This one the one which was picked in the Credit note ( G2 ).
    But Credit memo request ( CR ) created with reference to invoice, So the pricing procedure  ZSN0002 from the invoice also copied in to the credit memo request. So Mismatch pricing procedures between Credit memo request and the Credit note.
    First Question is if you try to create a Credit memo request with ref to Invoice F2, Will it copy the pricing procedure also? Basically we have differet pricing procedures for the  std sales and the Credit/Debit memos.
    Kindly advice how to solve the issue...
    Regards,
    SK

  • Issue in pricing routine

    Hi,
    I have an issue while writing code in the pricing routine. while calculating KBETR if the value is 1.035 it is rounding off to 1.04.
    Since KBETR has only two decimals it is rounding-off but client wants 1.035 only.
    Please help me.
    Regards,
    Anvesh Gummadapu.

    Hi Anvesh,
    Table for decimal decimal places in currency is TCURX .
    If ur currency does not supports 3 decimal places then may be u need to create a Z version of that currecny with 3 decimal places.
    Please check SAP documentaion [Special Output Formats |http://help.sap.com/saphelp_470/helpdata/en/9f/dba1ef35c111d1829f0000e829fbfe/content.htm]   & 
    [Defining Currencies|http://help.sap.com/saphelp_40b/helpdata/en/08/51410a43b511d182b30000e829fbfe/frameset.htm]

  • Currency Issue at Pricing Level

    Hi.......Please help me to slove this issue which I am facing at the time of creating Sales order, in pricing part I m getting massage---"Euro Customizing not maintained." I can run the pricing in Sales order but currency is in EURO and INR both. How can I convert all EURO currency to INR.

    Dear Arindam,
    Contact your FI-Personnel.
    Best Regards,
    Amit
    Note: Just for Information-sake:
    T. Code: OB08 - Maintain exchange rate between Euro and INR
    T. Code: EWFC
    Click Rado-Button: Confirm Euro Currency Customizing, and Execute (F8).

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

  • Price Rounding Issue - AFS  Pricing

    Hello Friends,
    We are facing an issue in sales order pricing & its subsequent effect in invoice. We use AFS pricing, where different grid sizes have its basic price.
    We have a basic price condition which come thru a master record, and this can be overridden by a manual price condition.
    When such manual condition is entered, it applies to all the quantity of the line item irrespective of the number of grid sizes.
    So suppose I had 6 grid sizes in the line item (which also results into 6 schedule lines) list price will be shown across all the grid sizes, see DOC1
    But when I enter a manual price EUR 7, it applies to the total quantity that is 6. So the net value in this case will be EUR 7, See DOC2
    By calculation, 7/6 = 1.166666666666667
    So when now I create the invoice, the value gets rounded for all the grid sizes & it becomes 1.17
    Here when system calculate the net value it will sum up 1.17, six times & the resultant net value is EUR 7.02, see DOC3
    As a result most of the time there is difference between the order value & the invoice value.
    Please suggest what action should be taken.
    Regards,
    Dhananjay Borate

    Dear Dhananjay Borate,
    You can avoid this issue working this the following options:
    Every Condition Type, in the "Control Data Box 1" have the option to apply a "Rouding Rule" with three different options:
    Empty.
                         In the standard rounding rule '_', values are rounded off according to business standards: 
                             10.454 -> 10.45 DEM
                             10.455 -> 10.46 DEM
    "A"
                        In rounding rule 'A', values are always rounded up:
                            10.459 -> 10.46 DEM
                            10.451 -> 10.46 DEM
    "B"
                       In rounding rule 'B', values are always rounded down:
                          1045.9 -> 1045 LIT
                          1045.1 -> 1045 LIT
    Also you can use,  in the "Gruop Condition ",  the Rounding difference comparison.
             Indicator that controls whether rounding difference is settled for group conditions with a group key routine. If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
    Use the Conditons Types:
    PDIF - Diff.value (own)
    DIFF - Rounding Offwith the Conditions that apply to your needs. The standard gives this ones as examples:  [Requirement: Routine 13 - Rounding as perT001R], [Condition Formula 16] and [Basis Type 4]
    Regards,
    Johnattan.

  • Rounding issue in pricing

    HI,
    system is showing different condition values(condition type PNTP) in sales order and Invoice..
    Eg.  material cost in Material master is 16.59 $ per 1000 PCS
    here our ordering quantity is 10,000 pcs
    in sales order it is taking amount as 16.59 per 1000 pcs and for 10,000 condition value is  165.90 $
    but in invoice it is taking amount as 0.02 per 1 pc ( rounding the 16.59 to 1 pc  i.e 16.59/1000 = 0.01659 = 0.02) and hence for 10,000 qunatity it is showing condition value as 0.02*10,000 = 200 $
    here i am getting around 30$ different.. can you please help me in solving this issue...
    are there any SAP notes available for this?
    thanks,
    sudhir

    Hi,
    Go to VK11 and save the condition record as 0.01659 for your condition type.
    Or save the condition record as 16.59 per 1000.
    Then go to V/08 and select your pricing procedure.
    Over there remove the rounding of the condition type.
    Also go to V/06 select your condition type and go to detail.
    Over there just remove the rounding rule.
    Now try to create the sales order and check the pricing.
    One question do you want rounding should be done in the last of the pricing?
    Regards
    Raj.
    Edited by: Raj Aryan Malhotra on Jul 16, 2009 1:25 PM

  • Rounding Issue with Pricing Conditions

    Currently we have in place a pricing hierchery that consists of two pricing conditions.  ZP for base price and ZD for a +-differential.  Both conditions begin with 00.  ZP00. ZP01, ZP03, ZP04.  If a ZP01 exists it overrides a ZP00.  If a ZP03 exists it overrides ZP00,ZP01, etc.  So basically the higher the number means it overrides anything underneath it.  The ZD conditions are setup exactly the same way.  I am currently running into a round issue.  We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places.  SAP is treating the calculation for the ZP and ZD as two separate calculations.  It rounds each of them and then combines for a total price.  So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755  which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74.  However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685.  This multiplied times the quantity 3,999 = $9,071.731 which is correct.  But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT.  I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better?  Or if there was a preferred method?

    Currently we have in place a pricing hierchery that consists of two pricing conditions.  ZP for base price and ZD for a +-differential.  Both conditions begin with 00.  ZP00. ZP01, ZP03, ZP04.  If a ZP01 exists it overrides a ZP00.  If a ZP03 exists it overrides ZP00,ZP01, etc.  So basically the higher the number means it overrides anything underneath it.  The ZD conditions are setup exactly the same way.  I am currently running into a round issue.  We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places.  SAP is treating the calculation for the ZP and ZD as two separate calculations.  It rounds each of them and then combines for a total price.  So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755  which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74.  However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685.  This multiplied times the quantity 3,999 = $9,071.731 which is correct.  But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT.  I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better?  Or if there was a preferred method?

  • Issue in Pricing Report Creation - V/LA

    Dear All,
    I have created a new pricing report in V/LA.
    Details:
    3 condition tables in the pricing configuration.
    1-SO / DC / Customer / Sales district / Material
    2-SO / DC / Customer / Material
    3-SO / DC / Material
    During report creation I select only "Material" field from the field selection screen & proceed with "AND" option.
    From Table selection screen, I select all those 3 condition tables.
    Now at executing of this report (In V/LD), I enter only "Customer" field (say customer 1000) in the selection criteria. (because I want to see all condition records exists for that customer 1000?
    When I execute the report it shows below 3 sections.
    1-SO / DC / Customer / Sales district / Material - All condition records exists for that customer/Sales District combination
    2-SO / DC / Customer / Material - All All condition records exists for that customer
    3-SO / DC / Material - All condition records maintained for Material level.
    But as per my selection criteria, system should show only 1 & 2 sections.
    How can I omit appearing sections 3 in my pricing report. ( Because I want to see condition records relevant to that customer only)
    Highly appreciate all your suggestions !!
    Thanks in advance !
    Edited by: Anupa Wijesinghe on Sep 24, 2009 8:32 AM
    Edited by: Anupa Wijesinghe on Sep 24, 2009 8:33 AM

    Dear Matthew,
    As per suggestion, I have to create 2 reports for the above requirement.
    1- with only Customer tables to see customer level prices. (For this I have to add only below 2 tables)
                          - SO / DC / Customer / Sales district / Material
                          - SO / DC / Customer / Material
    2- Other report to see material level prices. For that I have add all 3 tables.
                          - SO / DC / Customer / Sales district / Material
                          - SO / DC / Customer / Material
                          - SO / DC / Material
    So with this when user want to see price by customer, he has to select FIRST report & when he want to select price by Material, he has to select SECOND Report.
    It's not very user friendly, But yes, I can suggest it as a solution.
    Thanks for your reply ! 
    Really helpful !

  • Condition type decimal point issue in pricing

    Hi
    I have a import pricing Procedure as shown
    The condition types JEDB and JSED were calculated on 0.16 EUR,
    Like JEDB 2% of 0.16EUR= 0.0032
    and JSED 1% of 0.16EUR= 0.0016
    it is taking the first two digits of the value, ie 0.00 only
    Please confirm how to come with the corrected values,
    Thanks,

    Yes it is intended for TM but you can do the manual changes as recommended in the note and for technical coding, you can copy that logic.  Else, have a look at this note:-
    Note 38881 - Pricing with different decimal places
    G. Lakshmipathi

Maybe you are looking for