Condition Record maintenance Doubt

Dear SD collegures,
when i maintain a basic price condition record for example Pr00 i maintained material 'A' is costing 100. then Today i changed the value to 98 and 100 rupees validity is changed to yesterday. then i give new price 98 is valid from today. after saving when i go back and see the condition record it says no record found.
Kindly throw some light
regards,
Sudhir

Dear Sudhir,
Try this,
You first change the validity date of 100 rupees with yesterday date
Now you go through VK11 transaction maintain new condition record for 98 rupees with validity from Taday's date.
I hope this will help you,
Regards,
Murali.

Similar Messages

Dates in the condition record maintenance for the condition type?

Hi,
Condition type has the following dates when maintaining the condition record,
Valid from date:
Valid on :
Please ellaborate on the above dates?
Thanks

Dear Rajiv
Valid from date:- The date from which the said condition type is applicable. For example, in VK11, if you changed (let us assume PR00 changed to Rs.250 from 200) a condition with a date as 01-06-08 in the above field, only from 1st of June'08, whatever sale orders you generated, revised value of Rs.250 will flow in the respective sale orders. Whatever created b4 1st June'08 will be having Rs.200.
Valid on :- As in the above case, if you input a date as 30-05-08 for the above condition type, system will populate Rs.200/- and if you input 01-06-08, it will propose Rs.250/-.
Hope this explanation is suffice for you to understand the difference between the two fields.
thanks
G. Lakshmipathi

Error during condition record maintenance EXEM

Hello Guys,
I am trying to maintain condition records for the condition type EXEM. I am getting an error during this process.
When I get into VV11 and enter the condition type EXEM and hit enter, I get the list of key combinations. For any key combination I select and press enter, I get an error and the following log details. Please find the log details below. Any inputs to fix this error during condition maintenace would be appreciable. The config is maintained perfectly and does not indicate any error.
Thanks
Venkat
Status      Note
Information     882 Coding generator started
Information     851 Report RV13B998 saved
Information     883 Text pool for report RV13B998 written in language E
Error           806 Report RV13B998 has a syntax error
Information     722 Text pool for program RV13B000 does not exist in language 0
Information     883 Text pool for report RV13B998 written in language 0
Information     883 Text pool for report RV13B998 written in language 1
Information     722 Text pool for program RV13B000 does not exist in language 2
Information     883 Text pool for report RV13B998 written in language 2
Information     883 Text pool for report RV13B998 written in language 3
Information     722 Text pool for program RV13B000 does not exist in language 4
Information     883 Text pool for report RV13B998 written in language 4
Information     722 Text pool for program RV13B000 does not exist in language 5
Information     883 Text pool for report RV13B998 written in language 5
Information     722 Text pool for program RV13B000 does not exist in language 6
Information     883 Text pool for report RV13B998 written in language 6
Information     722 Text pool for program RV13B000 does not exist in language 7
Information     883 Text pool for report RV13B998 written in language 7
Information     722 Text pool for program RV13B000 does not exist in language 8
Information     883 Text pool for report RV13B998 written in language 8
Information     722 Text pool for program RV13B000 does not exist in language 9
Information     883 Text pool for report RV13B998 written in language 9
Information     722 Text pool for program RV13B000 does not exist in language A
Information     883 Text pool for report RV13B998 written in language A
Information     722 Text pool for program RV13B000 does not exist in language B
Information     883 Text pool for report RV13B998 written in language B
Information     883 Text pool for report RV13B998 written in language C
Information     883 Text pool for report RV13B998 written in language D
Information     883 Text pool for report RV13B998 written in language E
Information     883 Text pool for report RV13B998 written in language F
Information     722 Text pool for program RV13B000 does not exist in language G
Information     883 Text pool for report RV13B998 written in language G
Information     883 Text pool for report RV13B998 written in language H
Information     722 Text pool for program RV13B000 does not exist in language I
Information     883 Text pool for report RV13B998 written in language I
Information     883 Text pool for report RV13B998 written in language J
Information     722 Text pool for program RV13B000 does not exist in language K
Information     883 Text pool for report RV13B998 written in language K
Information     883 Text pool for report RV13B998 written in language L
Information     883 Text pool for report RV13B998 written in language M
Information     883 Text pool for report RV13B998 written in language N
Information     883 Text pool for report RV13B998 written in language O
Information     883 Text pool for report RV13B998 written in language P
Information     883 Text pool for report RV13B998 written in language Q
Information     883 Text pool for report RV13B998 written in language R
Information     883 Text pool for report RV13B998 written in language S
Information     883 Text pool for report RV13B998 written in language T
Information     722 Text pool for program RV13B000 does not exist in language U
Information     883 Text pool for report RV13B998 written in language U
Information     883 Text pool for report RV13B998 written in language V
Information     722 Text pool for program RV13B000 does not exist in language W
Information     883 Text pool for report RV13B998 written in language W
Information     722 Text pool for program RV13B000 does not exist in language X
Information     883 Text pool for report RV13B998 written in language X
Information     722 Text pool for program RV13B000 does not exist in language Y
Information     883 Text pool for report RV13B998 written in language Y
Information     722 Text pool for program RV13B000 does not exist in language a
Information     883 Text pool for report RV13B998 written in language a
Information     722 Text pool for program RV13B000 does not exist in language b
Information     883 Text pool for report RV13B998 written in language b
Information     722 Text pool for program RV13B000 does not exist in language c
Information     883 Text pool for report RV13B998 written in language c
Information     722 Text pool for program RV13B000 does not exist in language d
Information     883 Text pool for report RV13B998 written in language d
Information     722 Text pool for program RV13B000 does not exist in language i
Information     883 Text pool for report RV13B998 written in language i
Status      Note
Information     884 Screen generator started
Information     860 Screen SAPMV13B 1998 saved
Information     858 Screen SAPMV13B 1998 generated
Status      Note
Information     890 Text field for field INSMK not found
Information     860 Screen SAPMV13B 2998 saved
Information     858 Screen SAPMV13B 2998 generated

What part of the code would you like?
It says there is an error in Report RV13B998. This is part of standard.
Thanks
Venkat.

Condition record exists, but has not been set

Hi
in the pricing analysis this is the explanation i got.
the reasons could be an Condition record overflow or the condition record wpuld have been created after the documnet is created.
But i found the record has been mainatined earlier to the creation of document.
this was for MWST condition type in IS Oil. where the tax rate manatined for this condition record is zero%
Since this is a mandatory condition, the document could not be completed.
Your help in this regard is highly appreciated.
thanks
C.Sivakumar

Hi,
Check the pricing procedure for the condition type MWST. Whether this condition is taken from any prevoius steps
(check the from and to for the condition type MWST).
If this condition is with reference to somw other condition, then check whether that condition is maintianed or not?
Check the condition record maintenance in VK13, did you maintian the right access?
Prase

Pricing ZCondition Types are not appearing in Condition Record Maintanence

Hi All,
We have a requirement in SAP CRM Opportunity Management where the pricing determination should happen. So, to facilitate the requirement we have done the following
Downloaded the DNL_CUST_CNDALL and DNL_CUST_CND from ECC to CRM
But the Problem is when I am trying to maintain the Condition record in T-Code "/SAPCND/GCM" 　our Z-Condition types are not appearing in the list, also in Product Master Condition Tab.
Please suggest me how to resolve this issue.
Regards,
karthik J

Hi Karthik,
As a best practice -
1. If you are downloading the condition type and pricing procedure from ECC, then it is advisable to use ECC as a master system for all your Z condition type/condition record maintenance.
2. Similarly if you are using Pricing procedure as of ECC, then ensure that the downloaded pricing procedure in CRM is used for pricing procedure determination.
3. The condition record in T-Code "/SAPCND/GCM" is advisable to use if you are mainly using CRM Pricing.
By looking at your problem statement you are using ECC pricing procedure, condition types by downloading it to CRM.
If you have any other comments to make, please give the exact problem statement or any appropriate problem screenshot for further analysis.
Hope this will be useful
Thanks and Regards
DJ

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.

BP Role Category, condition record maintenace restricted to CRM

Dear Gurus,
Please enlighten me on the below
1) what is the prominence of BP Role Category. Please explain me with an example as i could nt understanding what is meant in the std documentaion
2) How can we restrict the condition record maintenance of a condition type only to CRM? i.e.. in ECC condition record maintenance should not be allowed
Thanks & Regards,
Raghu

HI Sunil,
The problem here is that when i can create a order in CRM for which HR****** is the benefitting rep it is not getting replicated to ECC.So i think the link is broken somewhere and so wanted to know where to check to fix it.
Thanks in advance........

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

Some condition records

hi,
could you explain about CONDITION RECORDS maintenance for FRIGHT. my requirement is
for 1 carton is Rs.56/- and more than one carton of material i want to calculate with that & gross weight also should be calculated, could any body explained this issue. I want to use scales is it right.
i have some requirement like that,
regards,
m s r prakash

Hi Shankar,
1a) Assign an access sequence for your frieght condition type. (M/06)
1b)Then you can create condition records for frieght condition with validity periods. (MEk1/MEk2)
1c)Ensure that your PO (and vendor master) have price date category 5 (GR date)
2) Yes. Possible.
a) Condition type should be of 'Delivery cost condition'
b) Define Transaction/event key
c) In the pricing procedure for this condition type, assign the Txn/event key in accrls column. This key determines that amount will be posted to another account.
Also, position the condition type after your tax related condition types so that tax is not calculated.
d) In OBYC, define GL Accounts for this Trasaction/event key (check with FI team)
if you give me brief i can help you out more.
if helpful REWARD points
Thank you .
Regards
Ram

Table Maintenance- Condition Records

Hi Friends,
I have created a custom table and i have done a Table Maintenance for that custom Table..
In that i have one field called DATBI(which is To-date).
My Requirement is how to set condition in this table maintenance where IF TO-DATE < SYSDATE
those records should not be displayed in Table maintenance but that should be there in Data base table..
Can anyone help me on this.. I think something need to be done in PBO.
Plz help me on this..
Sample code will be helpful.
Thanks in advance.
kishore

Hi genji,
Goto ur table and then utilities----
>table maintenance generator .
Then double click on the overview screen u specifed..It will direct u to PBO screen.
There inside PBO in the beginning create one module X(some name).
inside that specify ur condition whichever you want to..
piece of code which i have done for my condition records inside PBO
module modif_screen output.
data: datbi type datbi.
clear total.
loop at total.
move total+32(8) to datbi.
 if datbi < sy-datum.
 delete total.
 endif.
clear : datbi.
endloop.
Here total is the internal table from where values are populated.
Think this wil solve ur issue.

Massive maintenance of condition records

hey all ,
do you know a way to massive maintenance of condition records ?
for example - every time i want to edit all the condition records for particular Service Agent i have to go
to transaction TK12 and edit one condition record at a time .
( is there any pricing report for all the relevant conditions ? )
thanks in advance
Asa Moked

hi rp ,
do you know if vk32 deals with the relevant shipment cost condition records ?
as far as i know vk12 ( vk32 ) only enables the maintenance of condition records in sales orders .
Regards ,
ASA

Maintenance of Condition records in CRM

Hi all,
Environment CRM 4.0, R/3 4.6c,
where do i create condition records in CRM?
we have pricing procedure,Document pricing procedure,Customer pricing procedure and Sales area in place and also configured Pricing procedure determination, assigned Document pricing procedure to the respective document, assigned Customer pricing procedure to the respective BP.But when i am trying to create sales transaction when i go to display header level of Sales Transaction the pricing procedure is not picked up the pricing procedure field is empty.
i am under impression that is it because of not having maintained Condition record?
can you plz anyone suggest me in this regards at the earliest?
Thanks in advance.
DV.

Hi MDV,
Make sure that sales area data for the Partner you are using in your sales transaction has been maintained in the BP transaction under the SALES AREA DATA button on the top. Sales area data has the customer pricing procedure field.
The pricing procedure has nothing to do with conditions.
Reward points if it helps.
Regards,
Amit Mishra

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

Maintenance of condition record

Hi experts,
Q: Any chances to use the standard transaction code to maintain condition record for different condition type?
Case: ZPR1& ZPR2 are copied from PR00. When maintaining condition records for those 3 condition types, the customer wants to do that at the same time. Then, no need to return to VK11, re-set another condition type after completing one condition record.

Check this link, similar question is answered,
Re: copying the value of a condition type to another condition type
Below is the SAP Help link
http://help.sap.com/saphelp_47x200/helpdata/en/93/743305546011d1a7020000e829fd11/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/93/743305546011d1a7020000e829fd11/frameset.htm
Regards

Error in creation of a condition record

Hi to all, I've this error when I try to create a condition record :
Implementation of Method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION for BAdI /SAPCND/ROLLNAME for filter ZIUSERSTATUS is missing
Message no. /SAPCND/MAINTENANCE719
Diagnosis
Implementation of BADI /SAPCND/ROLLNAME or method FIELD_CHECK/DEFAULT_VALUE_SUGGESTION is missing for the filter characteristic ZIUSERSTATUS.
If, however, the implementation is correct (see BADI Interface Documentation) and active, there is an error in the condition maintenance layer.
System Response
An exception or error occurred because condition maintenance cannot check, convert or lock/unlock the fields of a condition record.
Procedure
Contact the department responsible for carrying out the missing implementation in the case of application fields in the customer namespace. SAP is responsible for SAP fields which are set in the field catalog (/SAPCND/CTFC) and delivered, and if the field is supported as a possible field in a condition table. SAP is also responsible for the implementation of usage fields for SAP applications, just as with condition technique fields.
In cases where SAP is responsible, contact your responsible support organization.
Could someone help me please ?

Hi I just put the coding:
e_was_executed = 'X'.
into every method and however it worked.
Best Regards

Condition Record maintenance Doubt

Similar Messages

Maybe you are looking for