CREATE PRICING CONDITIONS

Can anybody please let me know the file format for Pricing Conditions in LSMW for direct input program.

Sorry for the confusion,
Here is the business process:
Sales Order>Delivery>Billing Document>(Customer complains that they have been over charged)>Custom RK Document Created in VA01 with reference to Billing Document>......
I am trying to automate to creation of the custom RK document.
I have been able to do so successfully using the code I posted above, however, I came across an issue. If the original sales order had discounts applied, when I was creating my Custom RK Document, it wasn't picking up the discounts and therefore we would be giving the customer back more than they were owed.
However, after a number of days of working on this issue I figured out the problem. The discounts that were being applied on the original sales order were as a result of a TPM Trade Promotion, the only way those discounts would be applied to my new document is if I passed in the trade promotion GUID into the ls_sales_items_in-campaign field. I found this value using this code
    SELECT SINGLE campaign
      FROM cmpb_asgn
      INTO ls_sales_items_in-campaign
      WHERE vbeln = lt_icr-vbeln_o
      AND posnr = lt_icr-posnr_o.
Thank you for your interest and advice. I hope this proves useful to someone in the future.

Similar Messages

Create pricing condition with default value in processing process field

hi all,
when i maintain the pricing conditions with vk11 or vk31, i want the price maintained is set default as blocked (the processing status field-KBSTAT). can it be done? i am using 4.6c.

You should try to use transaction variant
<i>Transaction variants simplify transaction flow by:
Inserting default values in fields
Changing the ready for input status of fields
Hiding various screen elements and menu functions, or even entire screens
Adjusting table control settings
When you create a transaction variant, you run through the transaction in a special mode. In this mode, you decide which elements you no longer need in your transaction and which values should be inserted where. If you choose to hide an entire screen, the system will no longer display that screen in the transaction and will proceed on to the next screen in the series. You can also adjust table control settings and determine the width of columns and the order in which you want them displayed. In tab strips, you can suppress tabs that you no longer need by setting them to invisible.
You may also create as many variants for a transaction as you desire. One of these variants can be defined as a standard variant. This variant is then valid across all clients. You may also assign different variants to specific users.
This is done using Variant Transactions. Variant transactions are then places in those users user menus instead of the standard transaction. </i>
To use this : Tools -> Accelerated SAP -> Personalization (transaction SHD0)
Regards

Create pricing condition with BAPI_PRICES_CONDITIONS

Hello,
I am trying to create a new pricing condition for a material using BAPI_PRICES_CONDITIONS, but unsucsessfuly.
Has anyone tried to do that?
Looks like BAPI is not generating a condition number.
Regards,
Eglese

Hi Eglese
Check these threads,
BAPI_PRICES_CONDITIONS
Problem with BAPI_PRICES_CONDITIONS
cheers
Sameer

Create pricing condition using BAPI_CUSTOMERQUOTATION_CHANGE

Hi ,
I have a requirement to update quotation pricing data is condition exists i.e if pricing is already exists , if pricing is not exists it has to create a new pricing condition with the given information .
I am able to update the information using BAPI_CUSTOMERQUOTATION_CHANGE if pricing condition exists ,if pricing condition not existing its not working as expected.
Please guide me..
code i have written
*Conditions
      lt_conditions_in-itm_number = it_quot-posnr.
      lt_conditions_in-cond_type = c_zill.
      lt_conditions_in-cond_value = it_quot-kbetr.
      lt_conditions_inx-cond_count = 1.
      APPEND lt_conditions_in.
      lt_conditions_inx-itm_number = it_quot-posnr.
      lt_conditions_inx-cond_type = c_zill.
      lt_conditions_inx-updateflag = c_u.
      lt_conditions_inx-cond_value = c_x.
      APPEND lt_conditions_inx.
Thanks in advance,
Srinivas.

Hello Srinivas,
Use BAPI_QUOTATION_CREATEFROMDATA in the create scenario. Before calling the BAPI check if the quotation exists. If yes, use BAPI_CUSTOMERQUOTATION_CHANGE.
Regards,
Ajith

Problem in Creating Pricing Condition Table...

Friends,
I am creating a condition table.
i selected perticular fields (S.org, D.ch, Div, So-to-Party,Mat)
When i click on Generate Icon
I Got error message:
Customer Object VKOS A505 cannot be assigned to package

Hello,
Which is the number you have given for your table?
The best way is to search for the table which is having most of these fields and copy that table to a new table. When you create table give a table number after 900 and copy from another table. After this you can add/delete the fields and generate the table.
Prase

Module function to create and read pricing condition

Hello,
I am looking for an easy function module that enable us to get the pricing condition record ?
(As transaction for example VK13)
And I am looking for a function module to create pricing condition ?
(As transaction XK15 or at least VK11)
Thanks in advance,
Maxime

for creating try BAPI_FTR_CONDITION_CREATE (no experience with this one..)
for reading use Function SD_COND_ACCESS
consider more than one Condition Table may be involved via AccSeq for your KSCHL.
Fill KOMK and KOMP accordingly for all Tables of AccSeq for the KSCHL
Cheers
carsten
example:
*& Report ZCAWA_CONDR
TESTREPORT
Konditionen lesen via Zugriffsfolge des eingegebenen KSCHL
C.Wagener, 11.02.2009
REPORT zcawa_condr.
PARAMETERS:
p_kappl TYPE kappl DEFAULT 'V',
p_kschl TYPE kschl DEFAULT 'ZGRA',
p_vkorg type vkorg default '0100',
p_vtweg type vtweg default '00',
p_datum TYPE sydatum default sy-datum,
p_mlfb type YYBCEZNDR default '6MD90001AA'.
DATA: ls_komk TYPE komk.
DATA: ls_komp TYPE komp.
DATA: ls_konp TYPE konp.
DATA: lt_t682i TYPE TABLE OF t682i WITH HEADER LINE .
DATA: ls_koprt TYPE koprt.
DATA: lt_conditions TYPE TABLE OF a000 WITH HEADER LINE.
DATA: ls_sdprothead TYPE sdprothead.
ls_komk-prsdt       = p_datum.
ls_komk-vkorg       = p_vkorg.
ls_komk-vtweg       = p_vtweg.
ls_komp-zzyybcezndr = p_mlfb.
Tabellen der Zugriffsolge zur Konditionsart ermitteln
SELECT * FROM t682i AS a
JOIN t685 AS b ON
akvewe EQ bkvewe AND
akappl EQ bkappl AND
akozgf EQ bkozgf
INTO CORRESPONDING FIELDS OF TABLE lt_t682i
WHERE b~kvewe EQ 'A'
AND b~kappl EQ p_kappl
AND b~kschl EQ p_kschl.
pro ZugFolgen-Tab-Eintrag FuBa aufrufen
LOOP AT lt_t682i.
CALL FUNCTION 'SD_COND_ACCESS'
    EXPORTING
      application          = p_kappl
      condition_type       = p_kschl
      date                 = p_datum
      header_comm_area     = ls_komk
      position_comm_area   = ls_komp
      t682i_i              = lt_t682i
      koprt_i              = ls_koprt
    TABLES
      condition_records    = lt_conditions
    EXCEPTIONS
      field_is_initial     = 1
      not_read_unqualified = 2
      read_but_not_found   = 3
      read_but_blocked     = 4
      t682z_missing        = 5
      t681v_missing        = 6
      t681z_missing        = 7
      mva_error            = 8
      OTHERS               = 9.
und raus, wenn Treffer
READ TABLE lt_conditions INDEX 1.
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM konp INTO ls_konp
    WHERE knumh EQ lt_conditions-knumh.
    IF sy-subrc EQ 0.
      IF ls_konp-konwa EQ '%'.
        ls_konp-kbetr = ls_konp-kbetr / 10.
      ENDIF.
      WRITE ls_konp-kbetr.
      EXIT.
    ENDIF.
ENDIF.
ENDLOOP.

Creation of Customized field for Pricing Condition tables

Hi Friends
I have a requirement to create a Pricing condition table with Customized field starts with 'Z' and
Field length should be more than 80.
After creating New Customized Field, system is not allowing to create Pricing Condition table and giving error 'Too Many fields selected (larger than 100 bytes)'.
Could you please advice how to over come this error and Maximum field to create Pricing condition table .
Thanks
Ravi

Hi there,
Table & table attributes are defined by the ABAPers. Not by finctional consultants.
You need to have an access key to define new tables & access sequence.
Check with your ABAPer. He will be able to help you with that.
Regards,
Sivanand

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

Can idoc COND_A04 be used to update/delete existing pricing conditions?

Hi all,
I am designing an interface from an external pricing system to SAP, and am currently looking at the COND_A04 idoc as a mechanism to load the prices into SAP. In testing I've found that this idoc creates pricing conditions very nicely, but I'm wondering if the idoc can also be used to change existing pricing conditons or mark existing pricing conditions for deletion. Has anyone ever done this with COND_A04?
I tried deleting an existing condition by populating E1KONH-KNUMH with the condtion record number of the existing condition, and populating E1KONP-LOEVM_KO (deletion indicator) with an 'X'. Instead of marking the existing condition with the deletion flag, what this did was create a new condition record (same validity period and price) that is marked for deletion. While functionally this does in fact delete the price (the previous condition is 'overlapped' by the new condition and therefore ignored going forward), it doesn't seem like a clean solution and the resulting change history is very confusing.
Are there are fields on the idoc that can be set to perform a true change or deletion, vs. simply creating a new condition record??? Any ideas will be most appreciated!
Thanks,
Allison

There could be numerous reasons for the IDoc failure because the message that you are getting is too generic. Btw, Is this the only message you get, check if there are more than 1 status 51 in your IDoc to get some more information.
Also see the longtext of the message by double clicking on the status message, probably you will get a more comprehensive reason for the failure.
If nothing of the above helps, try to see the message number and class and see where it is used in the posting program and put a break point at the spot where this message is triggered.
regards,
Advait

Pricing condition not updating

Hi All,
When using 'BAPI_BUSPROCESSND_CREATEMULTI' , I am able to create header and items but I am not able to create pricing conditions ( in table PRCD_COND).
Can any one please help me how to solve this issue?

Hi,
Use BAPI: BAPI_SALESORDER_CHANGE to update the data.
BAPI_SALESORDER_CREATEFROMDAT2 is used to create new Sales orders.
Regards,
Tim

Reg Pricing Conditions

Hi Gurus,
Im new to sap abap, can any one tell me what are pricing conditions, what is transaction code to creat pricing condition.
thanq in advance.

Hello,
the following transactions are necessary to use the pricing:
V/03 , V/04 , V/05
- create, change, display a condtion tabe which are use in the condition access sequence
V/06 - here you can create the pricing type
V/07 - maintain the condtion access sequence for pricing in SD
V/08 - maintain the pricing procedure
This are the customizing transactions for pricing.
VK11/VK12/VK13
- create, change and display a condition record
These are the master data transactions for pricing.
Furthermore I would recomend the link:
http://help.sap.com/saphelp_470/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
I hope that the information are helpful.
regards
Claudia

Uploading pricing conditions

hi i got requirement that i need to upload pricing conditions for transaction VK15 and the BAPI to be used is BAPI_PRICES_CONDITIONS can any one suggest what are the inputs for this BAPI for creating pricing conditions and which tables it will updated...

Check This thread
Sample code for BAPI_PRICES_CONDITIONS
Hope this helps..

Error while creating a pricing condition record.

Hi
I am trying to use the Material Group 1 (MVGR1) field from the field catalog to create a pricing condition table(9 series). I was able to create the table with MVGR1 as one of the columns but when I try to maintain condition records in the table, System gives me the following error. I have maintained certain values in the config for material group1. there is neither F4 values for the field Material group nor I can type in config values of MVGR1 in that field. I am getting this error. Any help on how to get past this issue will be highly appreciated.
Thanks
Object Material group 1 not provided with characteristic AS. (Note other fields!)
Message no. VK432
Diagnosis
The value entered in a field is not permitted.
System response
The system issues an error message.
Procedure
Check the entry and make the necessary corrections. Note any relationships between the individual fields. Entries in other fields may also be incorrect.
Example: There are two fields for maintaining the country and region. These fields are linked. The country chosen would be permitted if it were by itself. So would the region. But the region may not be in the the country chosen. In this case, an error message is issued. The country should then be corrected, not the region!
Edited by: Suraj Ramakrishnan on Dec 24, 2009 2:45 AM

Message no. VK432
Check note 750841
thanks
G. Lakshmipathi

Pricing condition redetermination for sales order created with reference

Hi,
Are there any exit or routines that can be used to redetermine MWST pricing condition alone when creating sales order with reference to another sales order? The pricing from preceeding sales order is copied but we need only MWST to be redetermined after saving the order
This is because we are making changes so that while saving the sales order the material tax classification is defaulted to M based on some conditions so that MWST picks up the value M
Regards,
Vin

Hello Vinod ,
did you tried following options :-
1.Using Exit ( MV45aFzz) and re calculte pricning using FM 'PRICING'.
2.or Using Copy Control (Tcode : VOFM ) while creating order with Ref.
regards
Prabhu

How to get pricing conditions while creating Sales Order

Hi Guys,
When we create sales order using VA01, price is automatically determined using pricing condition configured.
My requirement is, I need to know what would be the price of a particular item.Say i put one item A with quantity x,can I get which price conditions will be applied and what value will come for them.I need this because I need to validate this price with some other price put in a file .

I would suggest to use the Exit because that will be less efforts and you can implment and debug it easily. Moreover, you can restrict it by any condition e.g. order type, order reason because all the internal tables are available at that point.
Whereas, accessing the access sequence is cumbersome process. You need to go to all the combinations (tables) in the access sequcen and try to find out the suitable match .
Regards,
Naimesh Patel

CREATE PRICING CONDITIONS

Similar Messages

Maybe you are looking for