BAPI for Pricing condition record  to transaction MEk1

Hi Experts,
I am facing problem to find out the BAPI or function module  to create the condition record for transaction MEK1.Please let me know asap.
Richard.

You can use BAPI_PRICES_CONDITIONS .
See the thread.
BAPI_PRICES_CONDITIONS

Similar Messages

  • BAPI for Pricing & Conditions

    1. what is the use of Function     Module "BAPI_PRICES_CONDITIONS"? what value we have to pass to BAPI BAPI_PRICES_CONDITIONS"?
    2. Which function Module will use to Extract the Pricing & conditions Details (from SD) ?
    3. Can anyone help me how to extract the Pricing & conditions Details (from SD) ?
    Thanks

    you can use KONV table to get pricing condition(KSCHL) and pricing value(KBETR), for this we require sales order no(VBELN) and item no(POSNR).

  • T code for maintaing condition record in MM pricing

    Hiii ..MM GURUS...
    Can anyone let me know the transaction code for maintaing condition records for condition types in MM pricing .
    Regards
    SARFRAZ..

    MEK1 with appropritate key combination

  • Is there a  BAPI to create IS-Oil (formula) MM Pricing condition records

    Hi,
    Is there a standard BAPI to create IS-Oil (formula) MM Pricing condition records, which would include the maintaining of the formula?
    Regards
    Kasi

    no BAPI exists

  • BAPI  to create IS-Oil (formula) MM Pricing condition records

    Hi,
    Is there a standard BAPI  to create IS-Oil (formula) MM Pricing condition records, which would include the maintaining of the formula?
    Regards
    Kasi

    no BAPI exists

  • Transaction used for maintaining condition record for contract

    Hi All,
    In one of the issue user is not able to print contract,we have noticed that default printer is set for user.I need to check what condition record is maintained for user.
    Can anyone let me know what is the transaction used for maintaining condition record for contract output.
    Regards,
    Dharmesh

    Hi
    MN01 Create Message: RFQ
    MN04 Create Message: PO
    MN07 Create Message: Outline Agreement
    MN10 Create Message: Schd. Agmt. Schedul
    MN13 Create Message: Service Entry Sheet
    MN21 Create Condition: Inventory Mgmt
    MN24 Create Message: Shipping Notif.
    MN27 Create message: rough goods receipt
    MN10 / MN11 - Scheduling Agreement Delivery Schedule
    Vijay

  • How to Maintain the Pricing Condition Records in CRM

    Hi
    I am new to the CRM
    How to maintain the pricing condition records in crm for the particular condition type?
    as we do in SD(VK11)
    Thanks

    Hi Binu,
    First of all, you could maintain pricing conditions in the following places:
    1. In General Condition Maintenance (GCM)
    2. At the product maintenance level
    3. At the 'Price agreement' tab of Contracts
    4. As manual conditions during order processing at item level
    Now, if you want to maintain conditions using GCM, you first have to maintain a condition maintenance group in the customizing where in you can assign condition table and condition type for different counter values. I am assuming that you have done this activity successfully.
    When you run the transaction '/SAPCND/GCM', for application 'CRM', your condition maintenance group name and context 'GCM', you will be initially taken to a screen where in you'll have an item area which would be blank and then condition fields would be displayed in a tree on the left.
    Here, select the field 'Condition type' and click on icon 'Select records'. You would get a dialog prompting you to enter condition type. Here you can specifiy the condition type for which you want to maintain/view condition records.
    If no condition records are available, item area would be left blank. Here, you can choose a condition type using the standard F4 help. Depending on condition types that are assigned to condition maintenance group, different condition types would be displayed in the F4-help using which you can maintain condition records.
    Hope this helps.
    Regards,
    Pavithra
    **PS: Please reward points if this helps.

  • FM for creating Condition Records

    Is there FM for creating Condition Records for output type like transaction VV11 (Create Output - Condition Records: Sales)

    Hi there,
    FM for condition records? Why do you want to think of a FM for creating conditon records?
    Condition records is a master data that has to be manually created as per the business requirement.
    But what we can do is that if the data ia existing in an external legacy system, we can migrate that into SAP through a BAPI / BDC or LSMW depending on the volume of data.
    But in other cases condition records are manually created in SAP system.
    If at all you have a function module to create condition records, how would you ensure that it feeds correct data into the condition records? What key combination would the system take & what data would you want the FM to upload?
    How will you monitor what data is uploaded,.
    Regards,
    Sivanand

  • Maintain Excise defaults for pricing condition in TAXINN procedure

    Hi all,
    I post this message as I'm customizing CIN part for creation and calculation of excise invoice. I have read lot of post but i'm a bit confused about right procedure to adopt. I try to explain:
    I'm doing a stardard sales flow (sales order -> delivery -> commercial invoice -> excise invoice) and the only method I have found to flow excise values in excise invoice is to insert pricing conditions in India -> Basic settings -> Determination of excise duty -> Maintain excise defaults for TAXINN procedure.
    In this table I have insert pricing conditions I use in my SD pricing schemas (in this case I use a copy of JINFAC). I have insert pricing conditions corresponding to BED % and BED total, and also CESS % and total and S&HCESS % and total.
    If I remove pricing condition from this table, corresponing value in excise invoice, when I create it, become 0.
    My dubt is if is correct to populate with table to flow excise values in excise invoice. I ask it as I have read differents approach and differents customizing settings applied in similar situations. In particular, I have found documentation in which, for TAXINN procedure, is recommended to leave blank "excise defaults" (with exception of CVD condition). What is the right method to use?
    There is one right procedure or, as it seems reading posts, someone have to do his "proper CIN customizing" based on results that have to obtain?
    Thanks in advance for any contribute that can help to clarify this situation.
    Regards
    Gianpaolo

    Hi all,
    I think to have found solution to my dubt.
    If I use "condition based Excise determination" I have to insert records with pricing schema (if is a copy of standard J* schema, like ZINFAC that is a copy of JINFAC) and excise pricing conditions in the transaction below:
    India -> Basic settings -> Determination of excise duty -> Condition-based Excise determination -> Classify condition type
    To determine value in excise invoice seems that program check before table in transaction described before. If in this table don't find records for pricing schema-excise pricing condition the program check also table in transaction below:
    India -> Basic settings -> Determination of excise duty -> Maintain excise defaults
    If during this second check find excise pricing conditions insert, can determine equally the values of excise in excise invoice.
    This is the result of my checks. I hope this could be useful for other people with similar problem.

  • Function module to change the value for pricing condition type

    Hello experts,
    I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
    I used many function modules but none are working.
    Please kindly suggest a function module that will change the value for a condition type .
    I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
    Thank you.
    CLEAR PRCD_COND.
         SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                              KSCHL = COND_TY.
      IF SY-SUBRC = 0.
    *    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
    *    CLEAR L_COND_CHG-KBETR.
        L_COND_CHG-STUNR = PRCD_COND-STUNR.
        L_COND_CHG-KBETR = COND_PRC.
    *    L_COND_CHG-KSCHL = COND_TY.
        INSERT L_COND_CHG INTO TABLE T_COND_CHG.
    L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
    L_ITEM_GUID = WA_ORDERADM_I-GUID.
    INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
    INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
        CALL FUNCTION 'CRM_ORDER_READ'
         EXPORTING
           IT_HEADER_GUID                    = HEAD_GUID
           IT_ITEM_GUID                      = ITEM_GUID
         IMPORTING
           ET_ORDERADM_H                     = LT_ORDERADM_H
           ET_ORDERADM_I                     = LT_ORDERADM_I
           ET_PRIDOC                         = IT_PRIDOC_RD
           ET_DOC_FLOW                       = T_DOC_FLOW
    *     CHANGING
    *       CV_LOG_HANDLE                     =
    *     EXCEPTIONS
    *       DOCUMENT_NOT_FOUND                = 1
    *       ERROR_OCCURRED                    = 2
    *       DOCUMENT_LOCKED                   = 3
    *       NO_CHANGE_AUTHORITY               = 4
    *       NO_DISPLAY_AUTHORITY              = 5
    *       NO_CHANGE_ALLOWED                 = 6
    *       OTHERS                            = 7
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
    INSERT L_PRI_COND INTO TABLE PRI_COND.
    LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
    L_PRIDOC_CHG-PRIC_COND = PRI_COND.
    L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
    L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
    INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
    ENDLOOP.
    LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
    MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
    INSERT L_HEADER INTO TABLE HEADER.
    ENDLOOP.
    LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
    MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
    INSERT L_ITEM INTO TABLE ITEM.
    ENDLOOP.
    L_FIELD-FIELDNAME = 'STUNR'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_FIELD-FIELDNAME = 'KBETR'.
    L_FIELD-CHANGEABLE = 'X'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_INPUT-FIELD_NAMES = FIELD.
    L_INPUT-REF_KIND = 'E'.
    L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
    L_INPUT-OBJECTNAME = 'PRIDOC'.
    INSERT L_INPUT INTO TABLE INPUT.
        CALL FUNCTION 'CRM_ORDER_MAINTAIN'
         EXPORTING
           IT_PRIDOC                     = PRIDOC_CHG
         IMPORTING
           ET_EXCEPTION                  = EXCEPT
         CHANGING
           CT_INPUT_FIELDS               = INPUT.
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    REFRESH EXCEPT.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        IT_OBJECTS_TO_SAVE         = HEAD_GUID
    *   IV_UPDATE_TASK_LOCAL       = FALSE
    *   IV_SAVE_FRAME_LOG          = FALSE
    *   IV_NO_BDOC_SEND            = FALSE
    *   IT_ACTIVE_SWITCH           =
    IMPORTING
       ET_SAVED_OBJECTS           = SAVED
       ET_EXCEPTION               = EXCEPT
       ET_OBJECTS_NOT_SAVED       = UNSAVED
    * CHANGING
    *   CV_LOG_HANDLE              =
    * EXCEPTIONS
    *   DOCUMENT_NOT_SAVED         = 1
    *   OTHERS                     = 2
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    COMMIT WORK AND WAIT.

    Hi,,
    To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
    Alternatively u can use this function module.
    CRM_STATUS_DATA_SAVE_DB
    BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
    Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

  • Pricing condition record text maintenance in multiple language

    Hi friends,
    While maintaining condition record by VK31 transaction, there are options for multiple language selection. but after saving it appears only in English. Please let me know whether we can maintain text in multiple languages for a pricing condition record?
    Regards
    Manish
    9741178072

    HI Manish,
    You need to maintain the translations for the condition types in SPRO.
    The path is SPRO - Sales and Distribution - Basic Functions - Pricing - Pricing condition types - Maintain Condition types.
    Then selecting the particular condition type GOTO- Translations, you need to maintain the translation in the particular language as desired.
    Thanks
    Ani

  • Bulk Pricing condition record upload

    can any body help out for , Is there any transaction code  for uploading the pricing condition record in BUlk.
    Ex: 1000 condition records upload for condition type PR00..
    Ragards

    Dear Ramesh,
                           This you can do by creating an LSMW,one of the mass upload tool.
    Regards,
    AKD
    Edited by: Ashish Dikshit on Sep 19, 2009 9:31 AM

  • Loading program for pricing conditions

    Hi,
    Can anyone guide me in writing the code for Loading Condition records in Vk11, either BAPI or BDC.
    <<removed by moderator>>
    Thank you

    Hi
    check this code
      loop at it_werks into wa_werks.
        clear v_index.
        perform bdc_dynpro      using 'SAPMV13A' '0100'.
        perform bdc_field       using 'BDC_CURSOR'
                                      'RV13A-KSCHL'.
        perform bdc_field       using 'BDC_OKCODE'
                                      '/00'.
        perform bdc_field       using 'RV13A-KSCHL'
                                      'ZPUP'.
        perform bdc_dynpro      using 'SAPMV13A' '1911'.
        perform bdc_field       using 'BDC_OKCODE'
                                      '/00'.
        perform bdc_field       using 'KOMG-WERKS'
                                       wa_werks-werks.
        v_index = 1.
        loop at it_bdcdata into wa_bdcdata where werks = wa_werks-werks.
          if v_index > 15.
            perform bdc_dynpro      using 'SAPMV13A' '1911'.
            perform bdc_field using 'BDC_OKCODE' '=P+'.
            v_index = 2.
          endif.
          clear v_string.
          concatenate 'KOMG-MATNR(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-matnr.
          clear v_string.
          concatenate 'KONP-KBETR(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-kbetr.
          clear v_string.
          concatenate 'KONP-KONWA(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-konwa.
          clear v_string.
          concatenate 'KONP-KPEIN(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-kpein.
          clear v_string.
          concatenate 'RV13A-DATAB(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-datab.
          clear v_string.
          concatenate 'RV13A-DATBI(' v_index ')' into v_string.
          perform bdc_field       using  v_string
                                         wa_bdcdata-datbi.
          clear v_string.
          v_index = v_index + 1.
        endloop.
        perform bdc_field       using 'BDC_OKCODE'
                                    '=SICH'.
        perform bdc_transaction using 'VK11'.
      endloop.
    form bdc_field using fnam type bdcdata-fnam
                         fval type any.
      if fval <> ''.
        clear wa_bdc.
        wa_bdc-fnam = fnam.
        wa_bdc-fval = fval.
        append wa_bdc to it_bdc.
      endif.
    endform.                    "BDC_FIELD
    form bdc_transaction using tcode type c.
    REFRESH it_messtab.
      call transaction tcode using it_bdc
                       mode  c_ctumode
                       update c_cupdate.
      commit work and wait.
      refresh it_bdc[].
    endform.                    "bdc_transaction
    redards
    Rao

  • Pricing condition record

    Hi All,
    There is a problem with the invoice condition records.In our case invoices are actually created via Idocs.
    Usually the condition record type is sent in the Idoc and the corresponding condn. type comes in the invoice.But in one case,the Idocs do not have a particular condition record type present in the data segment ,yet the invoice when created has the condition type in it.
    Does any one have  a idea if the condition type gets picked from any master table or is there any other way it  appears in the invoice.
    As far as the program that creates the Idocs,It picks the condition records from a Z table and fills in the Idocs.
    Thanks for your help!
    Regards,
    Gowthami SK

    Hi Sam,
    the preceding document is the sales order.
    the scenario is like the sales order gets created through Idocs (msg type:VLCCPO),the pricing condition record is filled in the Idoc ( KSCHL) and it appears in the invoice.
    But in a particular case,there is no condition type in the Idoc  ,yet the condition type appears in the invoice.
    Is it possible that any standard pricing condition has been defined???
    Regards,
    Gowthami SK.

  • Changing the Sequence of the Access Sequence for Pricing Condition Type

    Hi Friends,
    We have an access sequence to determine the pricing. We have 8 key combinations for the same.
    Customer/Plant/Material/Batch
    Sales Org/ Dist Ch/ Cust Region/Plant/Material/ Batch
    Price List Type/Currency/Plant/Material/ batch
    Plant/Material/ Batch
    1st 4 is with batch. and 2nd 4 is without batch.  At the time of implementation ie., before 8 years the 1st 4 key combinations were used.  But now based on the business need we are not using the 1st 4 key combination rather we are using the 2nd 4 which is without batch.
    My question is that can we change the access sequence so that while the system fetches the price it need not go through the entire ( 91,02,401 ) records.
    If this is possible then
             Will there by any impact during viewing of past data?

    Hi,
    There are two options.
    1)Change the validity dates for those condition records to earlier date.
    2)Usually the sytem checks from top to bottom.If it finds the record in first table then it will return that value and stop searching.
    As your not required things are on the top,remove the condition records for them using VK12 T.Code.And maintain the records for what condition tables you are required.
    Regards,
    Krishna.

Maybe you are looking for