BAPI or FM for Condition Pricing

Hi All
I need to develop a report that shows all the condition pricing (SD).
It is necessary to show the same fields of the pricing screen (VA03) -  it would be a kind of simulation.
I would like some function that gives me a report similar to the screen of pricing condition - transaction VA03 - SD module.
I am trying to use the BAPI  BAPI_SALESORDER_SIMULATE, but I am  getting only the aliquots of the taxes.
I am using 4.7.
Could you please advise?
Thanks in advance.
João Gaia

Hi,
Bapi for creating Pricing conditions is BAPI_PRICES_CONDITIONS.
In this u need to pass value to the below parameters:
bapicondhd-table_no
operation
applicatio
cond_type
or
It seems the RV_CONDITION* function modules only supports to change or create a new price condition by copying an existing one.
else use
BDC.
I think, It helpful to you.

Similar Messages

  • BAPI/BADI/FM for condition deletion (MEK2/VK12)

    Does any guy know any BAPI/BADI/FM to DELETE purchase/sales condition record as T-code MEK2/VK12?

    Hi Leo ,
    u cannt delete any Condition Record , but what u can do is " U can tick the Condition item record for deletion ".
    to do so :
    1.U have to get the Access Seq of that Condition , and get the condition number of that ConditionItem  i.e check tables like A0*.
    2.Then u have to make use of FM
    SD_SALES_CONDITION_MAINTAIN
    Regards
    Prabhu

  • Bapi or FM for uploading the condition records

    HI,
    i wanted know that is there any way to uplaod the condition records to sap by using any BAPI or FM or any standard program.
    this is urgent.
    thankx in advance
    regards,
    hpp

    Hi,
    Use the BAPI BAPI_PRICES_CONDITIONS to load the pricing conditions..
    Check this link for a sample code..
    Re: Sample code for  BAPI_PRICES_CONDITIONS
    Thanks,
    Naren

  • How to change exchange rate type for specific pricing condition type

    Hello every one,
    I have a requirement for billing ie VF01.
    currently  all the exchange rate are being calculated with exchange rate type 'M' by default.
    but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
    Please any body can help me with the exit and code which i can use.
    I have checked exits SDVFX008.
    but how to change exchange rate with type 'E' only for two conditions.
    as changing exchange rate at document header will change exchange rate for all condition type.

    You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
    Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
    Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
    Link to refer for selective runtime analysis - Runtime Analysis for VOFM
    Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally  we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

  • How to extract values from pricing procedure for conditions in CRM Billing?

    I have a number of conditions in the pricing procedure in CRM Billing that I would like to extract to SAP BW. How can this be done?
    Is there a standard extractor for CRM Billing similar to the SD Billing extractor "Extraction of SD Billing Conditions" (2LIS_13_VDKON)?
    If there is no standard extractor, is there another way to extract the conditions and the related values?
    I am using the standard CRM Billing Extractor 0BEA_CRMB already, so maybe an append could solve my problem. How can this be done? In what CRM-tables can I find the values from pricing procedure for conditions in CRM Billing?

    you may want to post that last question in a CRM forum... in ECC it would be table KONV

  • Pricing limits for condition type PR00

    Hi,
    I have got a scenario at hand, where i have to assign tolarence limits to all the conditions types in the pricing procedure. i have maintained limits in Transaction OVB2 except Base price condition type i.e. PR00. the problem i am facing is, we have got some where around 1,500 material and 3,200 customers and the price variation between the material is large(3000-150000). The main purpose of maintaining limits is to reduce the risk when entered manually. Please do consider the general business implications while replying.
    eg: new pricing procedures, condition records for base price etc makes a hafty job, so can you please suggest me any other means to have a tolerence limit to condition type PR00(PR00 is used as base price for all pricing procedures).
    Thank you, Have a nice day at work.
    with regards
    RVS Prasad

    Hi venkata siva
    As you are having around 1500 materials in your business . That means you need to maintain condition records for all these materials. While maintaining condition records only  , in VK11 for PR00 condition type , maintain upper limit and lower limit in additional data  . Then there should not be an problem
    Another way of maintaining pricing at upper limit and lower limit is in OVB2.
    Regards
    Srinath

  • Requirements not fullfilled for Condition type - Pricing Procedure

    When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

    Hi Sunil,
         Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is,  once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of  ABAP'er regarding this requirement if it is customized requirement.
    We should know the purpose of requirement in condition type.
    Venkat.

  • Condition types for import pricing

    hi,
         the conditions types for import pricing procedure are not appearing.
    please suggest all the notes from where i can take reference and create the condition types for import process.
    please also suggest what are they?
    with regards

    Hi anitha,
    In case of import purchase. u have to configure the conditions in pricing procedure.  The condition types are as follows:
    1)jcdb               basic customs
    2)jcv1               CVD
    3) jec1               ECS on CVD
    4)jed1              cess on customs
    5) j1cv                secess on cvd
    6) jsdb               secess on customs
    Go to the master note no 1032295 for recent budget changes.
    award points if found useful
    chintu

  • 2-dimensional scale for a pricing condition

    Hi,
    Need your Expertise please. We would like to implement 2-dimensional scale for a pricing condition.
    We have found a decision as use Reference condition type (RefAppl 'F').
    It works but we can't define Condition base value for the determination of value according quantity of item.
    Could you advise the decision... ?
    Thanks,
    Andrew

    Hi there,
    The base value can be set only for the maim condition type and not for the reference condition type.
    thanks
    Shanker

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

  • When we clicked on Update for new pricing,condition type is repeated twice

    Hi Friends,
    For new pricing,I clicked on the Update pushbuttion in the conditions tab of sales order,Condition type is repeated twice .So value is increased.I checked in the pricing  analysis,it is showing only once.
    I searched all threads and I tried all the possibilities.
    I checked exclusive indicator,it is correctly checked.
    Condition type manual entries selected as B automatic as priority
    Item condition check box is checked only.
    Mandatory check box is selected in the Pricing procedure for that condition type.
    Anything i missed out .
    Please suggest me how to go.
    Thanks in advance.
    Rgds....VM
    Edited by: vm on Nov 2, 2011 5:55 PM
    Edited by: vm on Nov 2, 2011 5:56 PM

    Condition type is repeated twice
    Ensure that the pricing condition is not maintained for multiple combinations in VK11
    G. Lakshmipathi

  • Bapi to create a condition record

    hi,
    is there any standard bapi for creating ,changing and deleting a pricing record using VK11,VK12.
    any other function module will solve the problem.

    Hi Ajith,
       You can use <b>IDOC approach</b> also for doing teh same solution. Yo get Create/Change/ Delete Option as per indicator passed:
    Refer Code below.
    *&      Form  map_idoc_structure
          Map E1KOMG, E1KONH, E1KONP segment fields
    FORM map_idoc_structure
                  USING fp_condition_table TYPE kotabnr
                        fp_rate            TYPE z_cs_cpp_rate
                        fp_condition_type  TYPE kschl
                        fp_rate_type       TYPE z_cs_file_type.
    *-- Local Data Declaration
      DATA: lw_e1komg TYPE e1komg, "Filter seg. with separated condition key
            lw_e1konh TYPE e1konh, "Data from condition header
            lw_e1konp TYPE e1konp, "Conditions Items
            lv_delete TYPE konp-loevm_ko. " Delete Indicator
    *-- IDoc data internal table
      DATA: i_idoc_data TYPE TABLE OF edidd
                        INITIAL SIZE 0
                        WITH HEADER LINE.
      CLEAR: lw_e1komg,
             lw_e1konh,
             lw_e1konp,
             lv_delete,
             v_segnum,
             w_e1komg,
             v_rate_type.
      REFRESH i_idoc_data.
      v_rate_type = fp_rate_type.
      PERFORM conversion_alpha_input
          USING w_crp_data-kunnr CHANGING w_crp_data-kunnr.
      PERFORM conversion_matn1_input
         USING w_crp_data-matnr CHANGING w_crp_data-matnr.
    E1KOMG: Filter segment with separated condition key
      i_idoc_data-segnam  = 'E1KOMG'.
      lw_e1komg-kvewe     =  c_usage_cond_tab.
      lw_e1komg-kotabnr   =  fp_condition_table.
      lw_e1komg-kappl     =  c_cond_type.
      lw_e1komg-kschl     =  fp_condition_type.
    CONCATENATE p_vkorg p_vtweg p_spart p_hienr p_matnr
      CONCATENATE w_crp_data-vkorg w_crp_data-vtweg
                  w_crp_data-kunnr w_crp_data-matnr
                  INTO lw_e1komg-vakey.
      lw_e1komg-vakey_long = lw_e1komg-vakey.
      lw_e1komg-vkorg      = w_crp_data-vkorg.
      lw_e1komg-vtweg      = w_crp_data-vtweg.
      lw_e1komg-spart      = w_crp_data-spart.
      lw_e1komg-kunnr      = w_crp_data-kunnr.
      lw_e1komg-matnr      = w_crp_data-matnr.
      i_idoc_data-sdata = lw_e1komg.
      APPEND i_idoc_data TO i_idoc_data.
    Segment E1KONH - condition header
      i_idoc_data-segnam  = 'E1KONH'.
      lw_e1konh-datab     = w_crp_data-datab.
      lw_e1konh-datbi     = w_crp_data-datbi.
      lw_e1konh-knuma_pi  = v_promotion.
      lw_e1konh-knuma_ag  = v_sales_deal.
      i_idoc_data-sdata = lw_e1konh.
      APPEND i_idoc_data TO i_idoc_data.
      IF fm_process_type EQ c_pt_dep.
        lv_delete = c_x.              " Deletion Indicator
      ENDIF.
    Segment E1KONP - condition items
      i_idoc_data-segnam = 'E1KONP'.
      lw_e1konp-kschl     = fp_condition_type.
      lw_e1konp-kbetr     = fp_rate.
      lw_e1konp-konwa     = w_crp_data-waers.
      lw_e1konp-kpein     = v_cond_pric.
      lw_e1konp-kmein     = v_cond_unit.
      lw_e1konp-knuma_pi  = v_promotion.
      lw_e1konp-knuma_ag  = v_sales_deal.
      lw_e1konp-loevm_ko  = lv_delete.
      i_idoc_data-sdata = lw_e1konp.
      APPEND i_idoc_data TO i_idoc_data.
    *-- Post Idoc for Creating Pricing Condition
      PERFORM post_idoc
             TABLES i_idoc_data.
    ENDFORM.                    " map_idoc_structure
    *&      Form  post_idoc TABLES i_idoc_data.
          Post Idoc for Creating Pricing Condition
    FORM post_idoc
              TABLES i_idoc_data STRUCTURE edidd.
    *-- Local data declaration
      DATA: lv_komg         LIKE komg,         " Condition Structures
            lv_subrc        LIKE sy-subrc,     " Sy-subrc
            lw_messages     TYPE rsuvm_msg,    " Message Description
            lw_idoc_status  TYPE bdidocstat.   " ALE IDoc status
      DATA: idoc_contrl                        " IDoc Control data
                LIKE edidc OCCURS 1 WITH HEADER LINE.
    *-- Initialize Internal Tables
      CLEAR:  t_konh,
              t_konp,
              t_konm,
              t_konw,
              i_idoc_status,
              t_kona.
      REFRESH: t_konh,
               t_konp,
               t_konm,
               t_konw,
               i_idoc_status,
               t_kona,
               i_messages.
    This code is taken from IDOC_INPUT_COND_A
      PERFORM fill_appl_structures(saplvkoi)
                      TABLES i_idoc_data
                             t_konh
                             t_konp
                             t_konm
                             t_konw
                             i_idoc_status
                             t_kona
                       USING lv_komg
                             lv_subrc
                             idoc_contrl-docnum
                             idoc_contrl-mestyp.
      IF lv_subrc = 0.
    This code is taken from IDOC_INPUT_COND_A
        PERFORM idoc_in_datenbank(saplvkoi)
                  TABLES idoc_contrl
                         t_konh
                         t_konp
                         t_konm
                         t_konw
                         i_idoc_status
                         t_kona
                  USING  lv_komg
                         lv_subrc
                         idoc_contrl-docnum.
        IF lv_subrc = 0.
          COMMIT WORK AND WAIT.
        Endif.
    Reward points if this Helps.
    Manish
    Message was edited by: Manish Kumar

  • Requirements are not fulfilled for condition EDI1

    Hi Gurus,
    We are trying to add (EDI1 confirmed qty) in the PO item conditions.
    We are using the standard PO schema which has these condition type. It has no access sequence attached to it and hence it is a manual entry.
    If we try to add that condition type in the PO it throws me the following error :
    "Requirements are not fulfilled for condition EDI1
    Message no. V1215"
    Kindly let me know what I have to maintain at the earliest.
    Best Regards,
    Ravi.

    You incorrectly filling item information with condition value. All quotation related pricing need to pass QUOTATION_CONDITIONS_IN table paramete of BAPI.
    Try it and the problem get solved.
    Cheers
    Nilesh Shete

  • Vk11 condition pricing upload

    Hi
    can anybody say any scenario about condition pricing upload (vk11 transaction) using bdc

    It is not advicable to create BDC for transactions like VK11, MEK1 ... which we use to create condition records. The reason is for each condition type, the options we see might vary when ever there is change in access sequences and their precedence. So if we create BDC, our program needs to modified everytime there is change in the access sequences and condition tables.
    I would recommed you to either use the program that i have provided or use some BAPI's to upload/change condition records.
    As you are saying, you have the data in your internal table. Download the data to a file in the format RV14BTCI needs and SUBMIT the program.
    For understanding on the structure for this program, use transaction SXDB.
    Use BAPI Function module - BAPI_PRICES_CONDITIONS
    Reward Points if it is useful
    Thanks
    Seshu

  • Problem in conditions pricing updation using BAPI_PO_CREATE1

    hi,
        I am creating PO using BAPI_PO_CREATE1 however when i am passing the data to the bapi for conditions at item level the price value is not changing and throwing error as ( NET PRICE FOR ITEM 00010 adopted from last document ) so for all the items its throwing the same information and when i am chekin the PO the value is not the changing. and while creating the PO manually also the net price is coming automatically and we need to backspace the value and re enter the new value. So wht should i do in order to input the data into the PO.
    Thanks in advance

    Thanks

Maybe you are looking for