Condition record exist but not set in SO

Hi SDN Team,
I have a problem. Where in the sales order for the Discount condition type condition record where already exist in diffferent validity period.
EG
ZAJ1 discount condition type - with the same key combination with different valididity period
EG:
ZAJ1 - 27.01.2009 to 15.02.2009
ZAJ1 - 16-02-2009 to 15-03-2009
The reason is not set for the ZAJ1 condition in the Sales Order is due to the sales order was created before the pricing condition record validity datet. Sales order where created on 11.02.2009. But the condition record where valid from 16.02.2009 that is the reason the condition record was not set in the sales order.
Based on this explanation user agreed and the call was closed.
I have also explained Where ZAJ1 has condition record. but which is not set in the document. if pricing was carried out again it will set the condition for the item.
But now again the call was reopened stating that -
At the time of creating the sales order the ZAJ1Condition record exist in the period 27-01-2009 to 15-02-2009. now the primary rebate should be used by the system. Unfortunately it did not.
Based on the reopend call - i have further investigated the issue but i could not find the root cause.
Based on this when i checked the previous order where the ZAJ1 condition was well picked up with the validity period 27-01-2009 to 15-02-2009, what might be the reason the condition type was not picked up in the sales order?
Can you please let me know with your expertise in solving this issue.
Regards,
J

1)Requirement is set with 2 (itme with pricing). and calculation type is assigned with own calculation type.
2) In the pricing analysis - it shows as per below
This message tells you that the condition record exists, but has not been set in the document. If pricing was carried out again for the document item, then the condition would be set.
There are different reasons for this:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing has been left completely and then started again.
If the condition type is used for subsequent settlement (rebate), there may be subsequent updating of business volume (the agreement is is created retrospectively). The document conditions do not contain the condition record, as the condition record was not created when pricing was carried out. Updating of business volume is carried out using special functions for subsequent settlement.
When an item was added, the condition record was accessed with key fields other than change time. This could lead to different results in the requirements check at the time of adding and the change time. This can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not determined in the source document (this is usually controlled by the pricing requirements). When creating the document, the document flow (TVCPF,TVCPA) is processed using a pricing type that does not redetermine these condition types, although they are supposed to be called via the requirements.
Thanks,
J

Similar Messages

Pricing error; ''Condition record exists, but has not been set''

hello friends
we created the order (credit memo req), refer to this created the credit memo.
in the order one line item and only 2 condition records
base price and tax (MWST)
in the order both conditions are coming and in the invoice it is not showing the condition (mwst) and in the Analysis it is showing as ''Condition record exists, but has not been set''
what would be the reason?
regards
siva

Hi,
if both the condition types are showing in the order then you need to update pricing in billing because sometimes when u chnage any condtion value for base price after creation of order then system is not able to find valid condition record at billing document level.
Narasimha

Condition record exists, but has not been set IN JVRD Condition

Dear Expert,
I am facing a problem, when trying to create P.O with Excise and Vat Condition. So i am getting Error like Condition record exists, but has not been set so all duties are Calculated Properly but JVRD condition is not Appearing. when going for analysis so that time i am finding this error.
Thanks You.

hi,
Please check that have you maintained Sett-off Conditions for JVRD Condition Types in T-Code: FV11 with respect to your combinations.
Thanks,
Raviteja

Condition record exist, but has not been set

I am creating proforma invoice for STO replenishment delivery. I am getting error log "Billing type contains split criteria, n invoiced:123456789, invoice not required". But I am able to save it. I used all standard settings for copy control and billing type.
For the proforma invoice the condition records are picking up some times and some times not picking up. In the analysis its showing "Condition record exist, but has not been set". When I update with carry out new pricing some times its updating with condition records some times not. I need a solution urgently. Please help.
Edited by: k c on Nov 4, 2009 7:50 AM

Hello,
The message "condition record exists, but has not been set" tells you
that the condition record exists, but has not been set in the document.
If pricing was carried out again for the document item, then the
condition would be set.
This can have different causes:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order
processing and pricing have buffer mechanisms. This means that a newly
added condition record might only be found after order processing have
been left completely and then started again.
When an item was added, the condition record was accessed with key
fields other than change time. This could lead to different results in
the requirements check at the time of adding and the change time. This
can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not
determined in the source document (this is usually controlled by the
pricing requirements). When creating the document, the document flow
(TVCPF,TVCPA) is processed using a pricing type that does not
redetermine these condition types, although they are supposed to be
called via the requirments."
Please check if any of those reasons apply to your problem.
Note that the condition type is determined just in the moment when
   the billing item is created. And it then that the userexit fills the
   field. When you save the billing document, pricing is called.
   Please ensure that you have any userexits switched off and then test
   this issue again.
If you have access to OSS notes. please see:
     24832      Pricing rules / TVC
    130416     Requirements in the condition preliminary st
      27636     Message: Condition exists (removed manually)
    859876     Condition is missing: Message VE 108 or VE 008
I hope you find this information very helpful and hopefully it will solve your problem.
Regards,
Martina McElwain
SD - Forum Moderator

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

Condition Record exits (but removed manually)

Dear All
when i am creating SA , some condition types are not being picked up. syastem shows Condition records exits (but removed manually) though problem doesnot fall under any of the reason given in analysis. Not to understand why is this happening
Help plzzz
Regards-
Ram

The message "condition record exists, but has not been set" indicates you that the condition record exists, but has not been set in the document. If pricing was carried out again for the document item, then the condition would be set.
There can be different causes/possibility for this, few of them can be:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing have been left completely and then started again.
When an item was added, the condition record was accessed with key fields other than change time. This could lead to different results in the requirements check at the time of adding and the change time. This can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not determined in the source document (this is usually controlled by the pricing requirements). When creating the document, the document flow (TVCPF, TVCPA) is processed using a pricing type that does not redetermine these condition types, although they are supposed to be called via the requirements."
Note: that the condition type is determined just in the moment when the billing item is created. And it then that the user exit fills the field. When you save the billing document, pricing is called. Please ensure that you have any user exits switched off and then test this issue again.
Also, refer following SAP Notes
Notes 24832 Pricing rules / TVC
Notes 130416 Requirements in the condition preliminary st
Notes 27636 Message: Condition exists (removed manually)
Notes 859876 Condition is missing: Message VE 108 or VE 008
Hopefully this would assist you in your requirement.
Thanks & Regards
JP

JCVS condition not coming in PO, Condition record exists (removed manually)

Hi Gurus,
I have created a new tax procedure which has the condition type JCVS.
Condition type has no routines attached to it and the condition record is maintained which is also valid.
I have also assigned the tax code to the company code in SPRO > Logictics general > Tax on goods mvmt > India > Determination of excise duty > Asssign tax code to company code.
However when the tax code is applied to a PO the condition type JCVS is not appearing and in analysis it shows Condition record exists (removed manually).
Please advice what will be the reason.
Thanks,
Prakash

No response.

Debit memo Condition record exists (removed manually) MWBO Italy

Currently I am working on an Italian pricing issue.
Pricing V/08
Cond     Description            Fr. To. P Req. Calc. BasT.
LCIT     VAT license Italy      900     S 33   37
MWST     Output Tax                     S 10         904
BOLL     Bollo in Fattura       900     S       903   26
MWBO     Opt.tax Bollo in Fat   924     S 924 903   26
The requirments, calculation type and are all based on SAP notes regarding the LCIT, BOLL. eg. 715399 and 593672
The main requirement here is that 924 is only to activate the MWBO condition in the invoice.
This means that for a normal order (TAN) item the LCIT, MWST and BOLL is shown. If we create a delivery - invoice, the pricing in the invoice shows LCIT, MWST, BOLL and MWBO. This is correct. MWBO is a tax condition.
But if we create a debit memo request the behavior is different and would appreciate some insight.
Debit memo request created, LCIT, MWST and BOLL is shown (as expected). MWBO not shown due to requirement, that's correct.
But when I create a debit memo from this one, the LCIT, MWST, BOLL are shown. If I go into the pricing analysis then I see that the condition record for MWBO has been found but with message: Condition record exists (removed manually). Saving the document does not trigger it afterwards.
I have looked on OSS (example note 859876) to determine the cause of not triggering it.
We are not using the user exits for these conditons in example: user_exit_pricing_prepare_tkomp, user_exit_pricing_prepare_tkomk, mv45afzz or rv60afzz.
The standard copy control of L2N to the invoice is set to D. If I change this for example to G (copy unchanged, redetermine taxes), then it works. But not sure if this causes disturbtion of the regular behavior of the L2N.
In best case I would only do the G pricing type for the MWBO condition so I do not disturb the existing process. Any suggestions? I know there is RV61AFZA for manipulating the pricing type (in case you want to have user defined pricing type eg. Y). But this can not be handled per condition type, or is that possible?

Routine 924 is a altered routine provided by SAP to suppress the condition in the order - not in the invoice.
http://service.sap.com/sap/support/notes/715399
quote:
"In this case, the bollo should only be reported on billing documents, not on the
order. However, pricing condition '24' delivered in the standard system
only partially covers this requirement."
The issue here is that it is triggered with normal order - delivery - invoice. But not with credit memo, it gives message that condition is removed manually. The L2N item category is set to D (copy pricing elements unchanged). When changing it to G (copy pricing elements unchanged - redetermine taxes), it works. But that has an effect on all standard usage of the L2N and I only want to actually fix it for that condition type.

Condition record exists (removed manually)

Hi
I have created one RFQ w.r.t PR. In ME47 transaction am not getting one condition type (ZNVS)automatically, though it is selected as "automatic display has high priority" in condition type.When analysis is selected system is showing the message "condition record exists (removed manually)
I have maintained condition record in MEK1 for ZNVS.ZNVS is negative value of NAVS (Non deductable condition type)
So that I can deduct the value from JEXS and only excise will be displayed.
how can I get that ZNVS condition type in RFQ conditions Automatically.
Need Help.

What the pricing analysis is saying is that a condition record has been found but it has been removed manually. It can happen in the following cases
1. If a user manually deleted it from the pricing screen, this seems unlikely in your case
2. There is a requirement on condition type K007 level or its access sequence K007 level in the pricing procedure, which removes the retrieved condition record. Check this in the pricing procedure-condition type assignment and access sequence definition
3. There is a formula (alternative calculation type) where there is some code written to remove the retrieve condition type
4. A user-exit is used during condition access and which removes specific condition records from the set retrieved for the pricing procedure
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define and assign pricing procedures (use this to check requirements and formulas at condition type K007 level)
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define access sequences (use this to check if there is any requirement at access sequence K007 level)

How to check whether a Record Exists or not in Ztable

Hi all,
I have Req like this
In ZTable i have 2 fields * Legacy System , Legacy Material No*
Environment Value is coming in one of the field in Idoc
The logic is if the Environment Value is UK and a Record Exists on the ZTable for Legacy Sysyetm = Leg1 means i have send Legacy Material No , else Send 01
Please suggest me the process for this
REgards
Vamsi
Edited by: Vamsi Krishna on May 19, 2009 5:31 PM

Hi Michal / Aamir,
Thanks for your replies.
The ZTable is at R/3 side only, iam using RFC Lookup for this, but iam bit confuse on how to construct the logic to check whether there is a record Exists or not on Ztable
Logic shld be If the Environment value is UK and a record exists on the Ztable for Legacy system "ABC" means then send Legacy material number else send 01
In Table we will have the fields Legacy System Legacy Material No & Environment value is coming from Idoc itself( Ex: UK or US)
Regards

Shipment cost :Cond. type FS00 - condition record exists (removed manualy)

hey all ,
my requirement is to charge for every container (packing material) in the shipment .
i coped condition FS00 (container) and called it Z100 .
the condition is defined with following parameters :
cond.class : B - prices
calc.type : S -number of shipping units
calc base : C -handling units
the condition opens in a pricing procedure under item category ZK01 which is defined the shipment header as cost relevant.
AND the problem :
when i opens the shipment cost document the condition doesn't appears .
in the analysis i get this message :
" condition record exists ( removed manually ) "
when i add the condition manually and double click on him there is a field that
specify that the condition is inactive because : " inactive due to calculation basis (shipping)
after checking the relevant notes :
i don't have a requirement in the procedure or the access to this condition .
i didnt delete is manually
so the above isn't the reasons that the condition isn't showing .
other condition types ( old condition types ) is active in this procedure ( new procedure )
does any body have an idea ?
Best Regards
ASA

hey RP ,
no exclusion and no formulas in this pricing procedure ?
any other ideas ?
i post this in an other forum and got this :
Hi,
There should not be two or more conditions with the condition class B in the
same pricing procedure.If there are two coditionswith the condition class B
in the same pricing procedure then it will invalidate all other conditions
in the pricing procedure.Check if any other condition(other than Z100) has
the same condition class. If yes use some other condition class for it.
Regards
Avinash Gyale
is it make any sense ?

HT204053 I have tried to load iCloud onto my Vista opperated pc but do not get a control panel with which to set it up. Each time I use my iTunes id to log into the iCloudI am told that it is an apple id but not set up for the Cloud. How do I get the cont

I have tried to install iCloud on to my Windows Vista pc. No control panel is present and when I try to login to iCloud using my iTunes id, I am told that it is an Apple id but not set up for the cloud. without the control panel where do I set up my iCloud id?

You can not setup a new iCloud account using a PC. You must use an Apple device (Mac or iPhone/iPad) to create the account, then sign into it using your PC.

Plz help me for checking the Header record exists or not

Hi
How we check the whether the Header record exists or not.. if it is not exists i have raise an exception.. i wanna do this using UDF
Plz help me its urgent..
venkat

Maybe you should read all the responses in your earleir threads and read the rules of engagement also,
/thread/117188 [original link is broken]
Regards
Bhavesh

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

Records syndicated but not in outbound folder

HI MDM Guru's,
I have a critical issue in our production system. We have modified 2 records in our data manager by running mdis (automatic import), these records has been flown to syndicator (as i could see these records greyed out & not in destination tab). Now, the major problem is i don't find these records in our outbound ready folder as of which our back end ERP system could not be updated.
when i do the modification process manually, then i could see these reocrds in outbound folder.
What could be the reasons? could it be that our mdss is not working properly or any other ......i don't know.
Could you please guide me to fix it ASAP.
Thanks in advance
Cheers
Srihari Reddy

Hi Simona,
Thanks for your updates.
We find some modified records missing in file prodcued in the outbound ready folder.
We found this issue on later Date after records were modified.
These Modified records which you are finding missing in the outbound folder,are they greyed out in MDM syndicator.
We had an update of these records on later dates after records were modified in Data Manager. Now , these records are greyed out and we find the modification of records in syndicator.
If so then check the values of these records for the field which it has got updated as per the incoming source file.
+ Records checked & found modified+.
If you are finding the field value changed to the new value as per the source file,then this record must not be greyed out but enabled for syndication.and if the records field value is still showing the old value,then it means it has not updated to the new value from the source file and so will rightly be supressed as per the property adn so greyed out.As only modified records will get syndiacted unchanged records will be suppressed by the property(Suppress unchanged records).
+ We use mdss for syndicating records. Process type - Automatic & Process Interval -continoues. So when ever there is change of values in Data Manager, then records are automatically syndicated to outbound folder, because of which all the records in the object pane of syndicator will be in grey color, after auto syndication.+
Try the following
Firstly check your import map's Import action it should have Create for new records and Update all mapped fields for existing records ,if this is not teh case then the new values coming from the source will not get updated in data manager.
Its checked & we maintain same while Importing Records.
Check you processing interval in the mdss.ini file. check by keeping a value of say 20 sec and then monitor the process slowly.
+ Processing interval in our mdss.ini file - 30+
Try importing a small set of records through the import server say 5 records with certain field values modified and then check in the data manager if the changes are imported,if so then those records must not show grey in the syndicator.
+ We use mdis to import data & mdss to syndicate data, when data is syndicated automatically , according to my understanding records in the syndicator object plane will be in grey color+.
*Records shown grey in the syndicator clearly indicates that they are being suppressed and will not go out
Make sure you have enabled key mapping if you are importing from remote system and map teh unique field from source to the remote key field in the destination*.
We have maintain Key Mapping = Yes.
Still i have a problem while syndicating Records.
Is the any way to find out that Number of records values created or modified in Data Manger = Number of records syndicated from syndicator.*
Does syndicator produce any kind of logs or any configuration/settings shuld be activated??
Kindly advice.
cheers
srihari Reddy.

Condition record exist but not set in SO

Similar Messages

Maybe you are looking for