SAP Pricing Routine For EDi1 & EDI2 Condition Types Not Triggered

Hi All,
We have implemented customer expected price functionality by incorporating EDI1 and EDI2 condition types in the pricing procedure.
Also, I have copied standard routine 8 and made new routines and assigned to EDI1 and EDI2 in calculation type.
The routines are getting triggered correctly for standard items which is pricing relevant.
But for BOM Header item , these routines are not getting triggered at all. Actually the pricing relevant check is present inside the routine and it should go till that point. But these routines are NOT getting triggered at all for BOM Header.
Please advise.

Hi,
Which level do you have the pricing? at BOM header or at sub item level?
Regards
Murali

Similar Messages

  • Pricing date for the tax condition type should be invoice creation date

    HI Folks,
    As per the current design taxes conditions are determining based on the Service rendered date which is similar to the GI date and pricing type is G in copy control .
    New requirement is taxes should calculate based on the Invoice creation date in the invoice.in order to acheive the solution i have customized the tax related condition type functionality "pricing date" as KOMP-ERDAT but still system calcualting the taxes based on the service rendered date and same also writing in the invoice also.
    pLease help me out what need to be configured here to acheive the solution.
    Regards,
    Ram.

    Hello XYZ,
    As you said the tax is calculated in Taxware system, i think taxware system is configured to calculate the taxes based on the "service rendered date". That is the reason why even you have changed the pricing date to be billing date for condition type XR1 taxware is not behaving as you expected.
      You have two options.
    1. Invocie creation date/ blling date is available in the structure "TAX_CAL_ITEM_IN00".If it is available in the structure ask the Taxware team to make changes in their system to consider that field value instead of the service rendered date.
    2. Alternatively you can over write the filed which contains the service rendered date value with the value of billing date. This way no changes required in Taxware system. You can do that in cusotmer exit  "EXIT_SAPLFYTX_USER_001" include ZXFYTU03 .
       Based on my exeperince i think the consistant approach would be going with option 1 . Please revert if you need furhter information on the same
    Thanks,
    Srini
    Edited by: srini vasarao on Jul 14, 2011 12:02 PM

  • Sales order Pricing for a particular condition type

    Hi Folks,
    I have a requirement that when i change the Shipping condition(VBAK-VSBED) in the Sales order  The Pricing should be triggered and the price should be re-determined only for a particular condition type (ZFM1) . This condition type represents Freight charges.
    I am trying to use user exit USEREXIT_NEW_PRICING_VBAP(include MV45AFZB) in the below fashion but the price is getting
    re-determine for all the condition types. I have even tried by passing NEW_PRICING = 'H' but we have multiple condition types for freight and price would get re-determined for all these condition types. I want the price should get refreshed only for condition type ZFM1.
    FORM USEREXIT_NEW_PRICING_VBAP CHANGING NEW_PRICING.
       IF VBAK-VSBED NE *VBAK-VSBED
          New_Pricing = 'B'.
       ENDIF.
    ENDFORM..
    So, do we have any function module which i can use to refresh only a specific condition type.
    <Priority normalized by moderator>
    Edited by: Vinod Kumar on Nov 3, 2011 1:35 PM

    Hi
    It's hardcoded. Go to include FV45PF0P_PREISFINDUNG and you can see when the userexit is called and how the report call other subroutine:
              perform userexit_new_pricing_vbap(sapmv45a)
                      changing da_pricing.
              if not da_pricing is initial.
                 if da_pricing ne function_new_pricing.
                    perform preisfindung using da_pricing.
                 endif.
              endif.
    In subroutine PREISFINDUNG is called the FM 'PRICING' with the value for DA_PRICING for CALCULATION_TYPE.
    Regards
    Eduardo

  • How to set required for group of condition type in the same condition class

    Hello,
              we have a group of condition type with the same condition class B, the last one have been set, and all of others will be inactive.
    but we don't set any required for all the condition types in pricing control, so if user don't set any of them, the sales order or billing is still saved. that is a risk.How can i fix it? Thanks.
    Sophie

    Hello,
      incompletion log is not available in invoices.
    You have different options:
    - activate a validation in FI when the Billing document is released into accounting,  so that te release into accounting is not allowed if the invoice amount is zero;
    - define a subtotal in the pricing procedure as sum of the pricing conditions of your group, then develop a custom routine to be assigned in the formula "CalType" (field T683S-KOFRM) where an error should be raised if the amount of the subtotal is zero (use as an example formula 48);
    Best regards,
    Andrea

  • VA00 condition type not getting determined for the returns order

    Hi All,
    I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
    When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
    Note:VA00 condition type is getting deleted from the  internal table tkomv[].
    If any one came across  this scenario can you please help me.
    Request your valuable inputs

    Hi,
    Please check the copy control setting in VTAA.
    Maintain the pricing type as "D" at item category level for the respective document type .
    Hope this will resolve your issue.
    Regards,
    Krishna O

  • Excise condition types not appearing in the Delivery document pricing

    Hi,
    This is a scenario of sales from an Exciseable Plant.
    The client has pricing requirement at delivery document.
    I have configured the pricing at Delivery document, but the Excise condition type (JEXP) does not appear.
    We are maintaine ED values at control code level and control code field is not availabe in LIPS, i tried adding the field in LIPS structure but still the ED condition type does not appear as program is not identifying the control code field in delivery.
    Can you please let me know the solution for bringing Excise condition type in the Delivery document pricing procedure.
    Regards
    Venkat

    Changed the Condition Category from 'F' to 'L'.

  • Condition type not appearing in Pricing report

    Hello all,
    There are 2 condition types
    ZR00 - condclass B, calc type C, item condition, with acc seq Sales Area/Material and
    ZQA2 - condclass A, calc type C, item condition, with acc seq Sales Area/Customer/Material.
    I have maintained condition records for both & created a pricing report with field name Condition type for which position is Page Header of Pricing report.
    However when i fire this report condtype ZR00 appears but ZQA2 does not. Please advise.
    Thanks
    -Dinesh

    Hi Dinesh
    In the condition table , maintain the key combination of sales area/Customer grp /customer/material and then generate the report. Then you may  get the output  . But make sure you have maintained the customer group in CMR also.
    But it is better to reduce the key combination you have maintained , because there are many feilds which are involved, may be that could be the reason you were not getting output.
    Regards
    Srinath

  • V-41 tcode error :Table 304 is not defined for use with condition type PR00

    Hi All,
    I am trying to create a BDC using the transaction V-41. 
    The first screen has fields:
    ConditionType and Table, where I have to fill values ZPM1 and 800 respectively.
    But as soon as I enter the tcode v-41 and say enter, the above mentioned fields are already having the  values 'PR00' and ' 304'. Normally if you take an example fo t-code VA02, all fields are blank.
    Then an error message  is displayed:
    Table 304 is not defined for use with condition type PR00
    This behaviour is not allowing me to use the BDC feature.
    Please advise me on why this is happening. What are the possible solutions I can use to clear these values programmatically?
    Can anything be done via customizing?
    Regards,
    Namita.

    Dear ILHAN ,
    Well the problem you are facing is having the following solution:
    Table 304 is not defined for use with condition type PR00
    Message no. VK024
    Diagnosis
    The selected condition type does not fit in the condition table, that is the basis for the condition record. Alternatively the selected condition type is not included in the condition types that were selected on the selection screen or that are defined in the variant of the standard selection report.
    Procedure
    Úse F4 help to choose a valid condition type.
    If this does not give you the required condition type, check in Customizing for condition types and the related access sequences.
    In the condition maintenance also check Customizing for the selection report (pricing report), that you have selected in the navigation tree, using the standard condition table as a reference.
    I hope this helps.
    It has worked for me.
    I gave it a try and what I am getting using the transaction V-41 is create Price condition (PR00) : Fast Entry.
    Please award points if you find it useful.
    Regards,
    Rakesh

  • Pricing Condition Type - Not visible to the customer

    Dear All,
    What all the config need to set up in the pricing procuder for a condition type to ensure customer did not wish to see the value for the particular condition type on the invoice. However it should have the ability to value in the condition type automatically post to the correct accounts at the time of invoicing.
    Thanks in advance.
    Victor

    Hi victor
    If nobody should change the condition type at billing level or sales order level also  means then go to V/06 and set the field  Manual Entries - D .
    Secondly, in VTFL change the pricing  type to C or D then changing the condition type manually is not possible
    Regards
    Srinath

  • Pricing Error- Condition type not found.

    Hi Gurus,
    I have a issue with pricing.
    Scenario :
    For a pricing procedure i have 3 condition types ;
    For example :
    ZXED, ZXE1 & ZXE2.
    Of these ZXED is Manual, Mandatory & Statistical in nature.
    ZXE1 & ZXE2 are Manual.
    When i create a sales order my pricing procedure is getting determined correctly.
    The issue comes in when i try to key in the values at the item level condition in the sales order:
    If i see the options(F4) available for me to select the condition types i get have see only one condition type i.e ZXE1. but esentially i should get to see all the 3 condition types as an choice of code(condition type).
    Can any one help me to find out the possible reason why i get to have only one condition type for selection.
    Your suggestion is highly appreciable.
    Rgd
    VIVEK.

    Hi,
    1. Understand onething that a particular condition type if maintained "mandatory" in the pricing procedure then you will have to create the condition record for it using transaction code <b>"VK11"</b>. If it is manual then you can give the rate directly in the sales order after selecting it. Since you have maintained <b>"manual", "mandatory" & "statistical"</b> for the condition type <b>"ZXED"</b> at the same time that is why the system is giving you the error <b>"Pricing error" Mandatory condition ZXED is missing."</b>
    2. Also you want the system to show you all threee condition types <b>"ZXED', "ZXE1", "ZXE2"</b> to choose manually as per your requirement. Do one thing go to transaction code <b>"V/06"</b> - select the required condition type say <b>"ZXED"</b> - double click on it - in the <b>"changes which can be made"</b> section you will see a field for <b>"Manual entries"</b> - in this select <b>"no limitations"</b> and save the <b>condition type</b>. Similarly do it for the other 2 condition types and save it.
    <b>I tell you</b> you must have maintained there <b>"D-not possible to process manually"</b>. If this is maintained then the system will never show you the condition type to choose from the condition type list in the sales order.
    Note: You have maintained for <b>"ZXED"</b> manual/mandatory/statistical. Now as it is mandatory also you have to maintain the condition record for it in <b>"VK11"</b>. Now if you change the rate of this condition type in the sales order then when you will create the invoice in <b>"VF01"</b> the system will show that value only which has been maintained using <b>"VK11"</b> because in billing also the system fetches the condition record from <b>VK11</b> for the mandatory conditions.
    Hope this clarifies and solves your doubt.
    Reward points if solution helps.
    Regards,
    Allabaqsh G. Patil

  • We look now for a suitable condition type "deposit for loaned packaging"

    Hi,
            Following is my client reuirement,
        We buy a lot of raw materials in loaned packaging (drums or IBC). The
    vendors are invoicing the packaging as an extra item on their invoice.
    Weeks or months later when we return the packaging to them we get a
    credit note.
    We look now for a suitable condition type "deposit for loaned packaging"
    which refers to account 631010 and we can use in the purchase order.
    Can you create such a type ?
    Please any one tell me whether it is possible? If yes, then which way?
    Regards,

    Hi Ajinkya1788 ,
    you can use a condition like FRB1 with a provision account key for your 631010
    or set up a valuation class to determine that account.
    You might want to check empties management documentation in help.sap.com
    best regards,
    Edgar

  • HM00 -Condition type not present in pricing procedure.

    I have included HM00 as manual condition type in pricing procedure attached to the sales order through prcing procedure detrmination. But in sales order when I am entering the value manually for HM00, the error is "HM00 -Condition type not present in pricing procedure", but actually it is present in pricing procedure.
    Any idea how to fix thie problem ?

    Hi Sunil,
    Just check in V/08 > <b>YOUR</b> pricing procedure and see if HM00 is included in it or not.
    Hope this will definitely solve your issue
    Reward suitably
    Regards
    SD

  • Differentiating of pricing schema for each purchasing document type

    Dear colleagues,
    This topic could be discussed before but I need to clarify some points.
    We would like to differentiate pricing schema per purchasing document types (e.g. AA and ZZ). These purchasing documents are not like domestic and import types.
    There some condition(s) where purchasing document type AA should not be able to maintain whereas ZZ should be able to.
    In this case shall use one unique pricing schema for both purchasing document types if so how can I hide some conditions for document type AA or if I use separate pricing schema how can I set different pricing schemas for different purchasing document types because both document types have same purchasing organization, vendor etc. 
    Regards
    Metin

    Hi,
    Why to have two different schema groups! Is procurement process is completely different, so use to have!
    (have thought of separate condition types for each Calculation Schema)
    Based on Schema Group Of Vendor in the vendor master, the PO for vendor with respective Schema Group Of Vendor will populate the assigned condition typesu2019. Follow path:
    SPRO->MM->Purchasing->Conditions->Define Price determination process ->Define Schema Determination
    Under segment:
    Determine Calculation Schema for Standard Purchase Orders
    Here you can assign Schema Group Purchasing Organization, Schema Group of Vendor and Calculation Schema
    Under segment:
    Determine Schema for Stock Transport Orders
    Here you can assign Schema Group Purchasing Organization, PO document type and Calculation Schema
    Regards,
    Biju K

  • Which Access sequence will use for sales tax condition type for TAXINN

    hi.,
    which Access sequence will use for sales tax condition type for TAXINN procedure.pls give one example (Access sequence) and give fields.
    Because i couldnot create the condition record,the system not accepted for tax indicator.
    Regards.,
    lakshmanan

    We also got the same problem with our client and escalated it to SAP.
    they advised to use the access sequence <b>JIND</b> which consists of condition tables in the order given below
    <b><u><i>Step    Condn Table</i></u> 
    10            354
    20            355
    30            40</b>
    Attach this to your condition types.
    Rewards if it helps.
    Regards,
    Anbu

  • RM06ENP0 - SAP SURGERY REPORT for geting valid condition price in CONTRACT

    Hello All
    Has any one run this report RM06ENP0  everyday in the SAP ECC system ?.
    any one experienced difficulty ?challenges?
    is this report is mandatory to obtain correct and valid price from the condition?...
    Muthu

    Hi
    Please clarify my doubts, which are given at ***
    It will be better if you create Pricing Report for the necessary condition table of your access sequence
    M_LA - Create Condition List
    M_LB - Change Condition List
    M_LC - Display Condition List
    M_LD - Execute Condition List
    In M_LA, in initial screen, enter Pricing Report Code(*** I am not getting the pricing report code in the drop down, if i want to create them how can I create)
    and description and press enter,
    here select "MATNR" (Material) and then Press enter,
    here select the condition table for which you have maintained the condition record and Press enter,
    here set the positions of the fields and save the report and then execute in M_LD and from here you can download details to Excel file.
    Your help is appreciable
    Thanks and Regards
    KVK

Maybe you are looking for