Condition record of pricing

Dear all,
I have a requirement, where there are 100 materials but i need maintain only one condition record for one material .Then automaticaly rest 99 materials should trigger the same condition record?
Thanks in advance.

Hi
Go to VK34 select conditions/prices folder and select the required condition table and execute. you will get all the condiiton records created for the selected condition table.
Now select all and press the button Copy condition available in the bottom screen and specify the traget values and execute.
All the records will be copied to your new condition type. Make sure that you test it in development server before doing it in production server.
Hope this helps you.
Regards
Rajkumar K

Similar Messages

Material Description in Condition record for pricing

Hi All,
I want to have material description (not as key field but just for information) in the condtion record for pricing in VK11. What shud i do for it. Please suggest.
Thanks

Hi,
While changing Condition Table , select the Material & go to technical view.There is a radio button of Text Field ,select it & then check.
Best Regards,
Ankur

Condition record in pricing

system is newly installed and we are not able to create condition records for any condition type in the system, be it pricing or tax condition type
able to access the condition type, access sequence, tables as well. only at the time of creating condition records system is not able to open the screen for maintaing condition records. In one case got the screen but it could not update the transaction and it went into loop.
what could be the problem. Is there any problem with table activation.
could any body help us

Hi VSA
If VK11 or VK13 is getting into loop, immediately raise an OSS message to SAP and ask them to provide solution for this.
Also make a random check for all the frequently used transactions.

While copying condition records in pricing from one customer to another

While copying condition records from one customer to another for one material, need to give select rule, when I click that it supposed to come with values like "rule 1" but it does not have values. So I cannot copy data.
Any experts solution?
Fully rewarded.
Thanks,
Manohar

Hi,
for the condition copy, you must maintain the copy control for condition. the path:Sales and Distribution>Basic Functions>Pricing-->Copy Control For Conditions.
this is the reqirement.
I hope this useful for you.

Condition Record - Pricing Procedure

Hi
What is the T.code / IMG settings for creating a condition record in PRICING PROCEDURE ?
Thanks & Regards,
Senthil.

Hi,
Easy access> Logistics >Materials Management >Purchasing >Master Data > Conditions >Other .
MEK1 - create
MEK2 Change
MEK3 Display
Service condition records ML51.
SD condition records,
VK11 create
VK12 change
VK31 create
Regards,
Chandra

Copy Condition record

Hi,
I am Having Condition record for Pricing (PR00) with Key combination as sales org/ Customer/ Material.
Now I want to copy same Record for another customer with same materials
How to do this?
I tried In VK11 in with ref. to option in which i given previous records's ref. system is copying but in this i want to
change customer code but that field is in Grey I m not able to change customer code for the same materials.
regards,
akshay

Hi
Just make previous record invalid
Just go to VK12 and give the validity date of today.
From                 01.12.2008
Valid to             31.12.9999 (21.07.2009)
So from today onwards this condition type will be invalid
Just create the new condition record in VK11 for your different customer.
Now just create new record sales org/ Customer/ Material
      1000 / 594944 /   M10
New condition record valid.
Regards
Adi

Table for Rebate Condition Types( Condition Records)

Hello All,
I need the table and the FM name which stores the values of the Key Combination of the Rebate Condition Type maintained in a Rebate Agreement.
If not, at least, give me the name of the FM which stores the values of the key combination maintained in condition records for pricing.
Regards,
Raghu.

I'll give an example,what am looking for..:
I've a Condition Type: ZBAX for ex. it has a key combination: Sales OrgCustomerMaterial.
I maintain condition records as:
For CU70/21100043/3456 the value of the condition record is say 100 euro.
My question is where will I get the values CU70/21100043/3456 ?
FYI..in T685 the defintion of the Condition Type is stored. in SAP, no T-table is meant to store condition record values.
KONA contains data on Rebate Agreements i.e. RA no, Rebate Recepient etc..
I know that KONP stores the accrual %, scale base, scale values etc..
but, I want to know where are the values for the key stored? Or, the FM that would fetch me these details?
I hope am clear..
Regards,
Raghu.

Exclude Condition Record by Item Category

Hi All,
We need to exclude a condition record in pricing based on the line item category. We are trying to use a routine (VOFM->Formulas->condition base value)for this and haven't had much success so far in clearing out the condition value based on the item category. If anyone has done anything similar , can you let me know if we can use anything in requirements for this ? or can this be done by config ?
Thanks,
Sandeep.

Use a vofm pricing requirement routine. If komp-pstyv = item cat then set RC = 4. This will disable the condition.

Deleting a condition record

hi guys,
i want to delete a condition record using VK12, am selecting the row and pressing the icon 'Delete Row' but its not working out, and the row still remains the same(the condition record not getting deleted). More over, the 'Deletion ID' is selected in the condition record.
how do i delete the condition record in this case. this is very urgent. plz send the replies ASAP.
thanks in advance.
kumar.

Dear Kumar,
There are two possible procedures for deleting conditions. There is either immediate deletion or a deletion flag for archiving at a later date. You enter the type of deletion that should be proposed during condition maintenance into Customizing for a condition type, . When deleting immediately, a dialog box can be created which indicates immediate deletion but offers a deletion flag as an
alternative.
Deletion Flag
You can mark condition records for deletion. These are then no longer taken into consideration during automatic pricing. However they remain as condition records in the system until the next archiving update. This means you can reset a deletion and reactivate a condition record.
Physical Deletion
If you use physical deletion, the condition record disappears immediately. It is no longer available during condition record maintenance or pricing. This deletion cannot be reset once it has been carried out. You have to recreate the condition record if you need it again. To be more exact, the reference to the condition record for pricing and condition record maintenance is deleted completely with physical deletion. The actual condition record must be kept for old documents.
Recommendation:
SAP recommends the physical deletion procedure. The deletion flag improves upwards compatibility in the system.
A pricing error can occur when using hierarchical accesses in combination with the deletion indicator (See the hierarchical access documentation in the SAP library).
The deletion flag used to be used as a replacement for a missing release procedure. This is no longer necessary, as there is now a separate release procedure available (see the release procedure in the SAP library).
Physical deletion can be included using the change documents for example deletions in a specific period (Report RV16ACHD).
Reward points if this is helpful.
Regards,
Naveen.

Delete condition record??

how to delete condition record from VK11. can i have t code plz.

Hi,
Just to add,
There are two possible procedures for deleting conditions. There is either immediate deletion or a deletion flag for archiving at a later date. You enter the type of deletion that should be proposed during condition maintenance into Customizing for a condition type, . When deleting immediately, a dialog box can be created which indicates immediate deletion but offers a deletion flag as an alternative.
Deletion Flag
You can mark condition records for deletion. These are then no longer taken into consideration during automatic pricing. However they remain as condition records in the system until the next archiving update. This means you can reset a deletion and reactivate a condition record.
Physical Deletion
If you use physical deletion, the condition record disappears immediately. It is no longer available during condition record maintenance or pricing. This deletion cannot be reset once it has been carried out. You have to recreate the condition record if you need it again. To be more exact, the reference to the condition record for pricing and condition record maintenance is deleted completely with physical deletion. The actual condition record must be kept for old documents.
Recommendation:
SAP recommends the physical deletion procedure. The deletion flag improves upwards compatibility in the system.
A pricing error can occur when using hierarchical accesses in combination with the deletion indicator (See the hierarchical access documentation in the SAP library).
The deletion flag used to be used as a replacement for a missing release procedure. This is no longer necessary, as there is now a separate release procedure available (see the release procedure in the SAP library).
Physical deletion can be included using the change documents for example deletions in a specific period (Report RV16ACHD).
Hope this helps. Please reward if useful.
Thanks & Regards
Sadhu Kishore

Creating condition record by uploading

Hello all,
I am using FM BAPI_PRICES_CONDITIONS to create condition record.
But its creating the record even if i gave the invalid details ( like invalid material number,...).
Can you please tell me how can i handle the errors using this FM.
Thanks in advance.
regards,
Lokesh

hi..
This code snippet inserts a condition record for Pricing condition type Z123 with key sales order
and line number.
CONSTANTS: lc_kschl_z123 TYPE kscha VALUE 'Z123'.
DATA: lv_datum TYPE sydatum,
lv_count TYPE kopos,
lv_unit TYPE kpein,
is_bapicondct TYPE bapicondct,
is_bapicondhd TYPE bapicondhd,
is_bapicondit TYPE bapicondit,
it_bapicondct TYPE STANDARD TABLE OF bapicondct,
it_bapicondhd TYPE STANDARD TABLE OF bapicondhd,
it_bapicondit TYPE STANDARD TABLE OF bapicondit,
it_bapicondqs TYPE STANDARD TABLE OF bapicondqs,
it_bapicondvs TYPE STANDARD TABLE OF bapicondvs,
it_bapiret2 TYPE STANDARD TABLE OF bapiret2,
is_bapiret2 TYPE bapiret2,
it_bapiknumhs TYPE STANDARD TABLE OF bapiknumhs,
it_mem_initial TYPE STANDARD TABLE OF cnd_mem_initial.
lv_datum = sy-datum.
lv_count = 1.
LOOP AT gt_vbap INTO wa_vbap.
* BAPI Structure for Condition Tables
is_bapicondct-operation = '009'.
is_bapicondct-table_no = '700'.
is_bapicondct-applicatio = 'V'.
is_bapicondct-cond_usage = 'A'.
is_bapicondct-cond_type = lc_kschl_z123.
"Set the varkey from A700 table key fields
CONCATENATE wa_vbap-vbeln wa_vbap-posnr
INTO is_bapicondct-varkey.
is_bapicondct-valid_to = '12/31/2009'.
is_bapicondct-valid_from = lv_datum.
is_bapicondct-cond_no = '$000000001'.
**** BAPI Structure of KONH with English Field Names
is_bapicondhd-operation = '009'.
is_bapicondhd-cond_no = '$000000001'.
is_bapicondhd-created_by = sy-uname.
is_bapicondhd-creat_date = sy-datum.
is_bapicondhd-cond_usage = 'A'.
is_bapicondhd-table_no = '700'.
is_bapicondhd-applicatio = 'V'.
is_bapicondhd-cond_type = lc_kschl_z123.
is_bapicondhd-varkey = is_bapicondct-varkey.
is_bapicondhd-valid_to = '12/31/2009'.
is_bapicondhd-valid_from = lv_datum.
*** BAPI Structure of KONP with English Field Names
CLEAR is_bapicondit.
is_bapicondit-operation = '009'.
is_bapicondit-cond_no = '$000000001'.
is_bapicondit-cond_count = lv_count.
is_bapicondit-applicatio = 'V'.
is_bapicondit-cond_type = lc_kschl_z123.
is_bapicondit-scaletype = 'A'.
is_bapicondit-scalebasin = 'B'.
ADD 1 TO is_bapicondit-scale_qty.
is_bapicondit-calctypcon = 'B'.
lv_unit = wa_vbap-kwmeng.
is_bapicondit-cond_p_unt = lv_unit.
is_bapicondit-cond_value = wa_vbap-value.
is_bapicondit-condcurr = wa_vbap-waerk.
APPEND: is_bapicondct TO it_bapicondct,
is_bapicondhd TO it_bapicondhd,
is_bapicondit TO it_bapicondit.
ENDLOOP.
*** BAPI for pricing Condition Records
CALL FUNCTION 'BAPI_PRICES_CONDITIONS'
TABLES
ti_bapicondct = it_bapicondct
ti_bapicondhd = it_bapicondhd
ti_bapicondit = it_bapicondit
ti_bapicondqs = it_bapicondqs
ti_bapicondvs = it_bapicondvs
to_bapiret2 = it_bapiret2
to_bapiknumhs = it_bapiknumhs
to_mem_initial = it_mem_initial
EXCEPTIONS
update_error = 1
OTHERS = 2.
IF sy-subrc EQ 0.
WRITE: /1 'Return Messages for Condition create'(t03).
LOOP AT it_bapiret2 INTO is_bapiret2.
WRITE: /1 is_bapiret2-message.
ENDLOOP.
ULINE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'
IMPORTING
return = is_bapiret2.
ENDIF.

Reg !!! Condition record

Hi all,
What is the T.Code (or Path) to create the condition record for Pricing procedure ???
Regards
Sanjay

The path is
LOGISTICS--MATERIALS MANAGEMENT-PURCHASING-MASTERDATA-CONDITIONS---
Here you have prices, discounts, others
Using MEK1, you can maintain condition records for condition type of any of these kinds.

Condition records found but do not show up in the pricing - 208

Hi,
A) In some scenario though the CR is found, access is complete, message is 208, there is not exclusion etc, simple scales..yet the value of CR is not shown / included in the pricing procedure calculation.
B) Also in another situation, always the first scale value being read though the scale value being the next higher one, i.e. it should pick up the next condition record based on the order value but it remains at the first scale, which means the scale somehow always being read is the first one irrespective of the order value.
What could be possible reason for these, debug process?
Thanks much for the help!!

Check the following setting is the Price condition Type, I am assuming u are using simple scales.
in T.Code: V/06 go to the price condition type and double click it.
Check the entries:
Scale Basis: C
Check Value: A
Scale Type: Blank (This value can e maintained in the condition record for price condition type).
If further queries do post them.
Regards
AK
Please Award points if helpful

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

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.

Condition record of pricing

Similar Messages

Maybe you are looking for