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 ?

Similar Messages

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.

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.

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)

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

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

Change Sacle Type in Condition Record

Hi Friends,
Is there any way by which we can change the scale type while maintaining the condition records. We have maintained scale type A (Base Scale) in V/06 for a condition type. Now the business requirement is such that we need to maintain two condition records for the same condition type, first one with 'From' and the second one with 'To' scale type. Can this be done at the time of maintaining the condition records.
Regards,
Abhishek.

Hi,
It is possible to change the scale type in condition record.
Do the following.
1. In V/06 for the condition type, maintain the scale type as empty (can be maintained in the c. record)
2. nowcreate c.record in vk11
3. go to scales view
4. here put the cursor in the scale type and click the lens at top right
5. now u can change the scale type in the control tab of the view
now come back to scales view and maintain the values
Hope this helps you
Pls reward if it helps.

Shipment cost - Change definition of condition types

Change definition of condition types in work pricing procedure
hey all ,
we implemented the shipment cost module and now we have to make some changes
in working condition types because the requirements of the customer changed .
is it recomended and what are the effects of changing the definition of condition types
and by that changing working pricing procedures .
for example if i change condition type from D - wight, V - Volume F - Formula to T scale
( and makeing the properchanges in the scale ) or add some more condition the existing pricing
procedures ?
BR
ASA
Edited by: ASA MOKED on May 22, 2009 3:33 PM

hey and thanks for the reply ,
did you make changes in the definition of existing condition types ?
for example change condition calc.type from d-weight to t-scale ?
BR
ASA .

Shipment cost transfer to invoice - condition twice in invoice

Hi experts,
I created a stat. condition in the SCD and calculated a vaule which I need in the invoice to calculate the total.
I have 2 items in the SCD - one of the header and one of the stage level. For both the condition is found and calculated with the same value.
E.g. on header level 5€ and on stage level 5€ (same condition record).
Transfer to invoice is working but I get the condiotion twice. both 5 €.
Should I calculate only on one level?
What is the reason and how can I solve it?
Thanks and regards
Marc

Hi Frasch,
Is this issue related to Sap TM or ECC? Since you are using word Conditions i am assuming you are referrring to Shipment costing from ECC.
1) Are the condition selected Header and Item in condition type or have you ticked both?
2) Are you getting a single condition record for a Condition Type Twice?
Look in to pricing procedure and settings again ,
Cheers,
Ajay Kaushik YGR

Shipment cost & shipping type

Hi all,
i have some question about routes & stages.
1) in one routes with two stages: these stages can be different for shipping type? (for instance: 1) by ship 2) by road
2) when i calculate shipment cost: (a condition record with scales in function of tariff zone of departure and tariff zone of destination)----->
why the costs are only calculated by the system for 2nd stage e not for 1st stage.????
if i configure 1st stage (by road as the 2nd stage) the system calculates cost for 1some st and 2nd stage... (and it's right)!!!
Any solutions??
best regards
Alba

Hi,
Dear Imran,
You have posted this question twice and there is no such condition
You have to maintain scale and if need to develop routine and that I already suggested to you.
Kindly do not post 1 question many time
Kapil

Standard Report with Condition Type and Condition Records

Hello to all,
Is there any standard report available in which Condition Type and Condition values are displayed in either column or row format? The selection criteria can be either Quotation, Contract, Sales Order, Delivery, Invoice or Billing. Thanks anyways...

Hi Huzefa,
Pls check the relevant table where the condition records are stored. then do a query with that condition table and KONP. say for eg: condn type ZINV,ZMRP gets stored in condition table A821, then combine A821 and KONP, u can input condition type and get the values........................
go to vk13, display and click on layout, u will able to see the condition table.
Rgds,
Anitha J

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

Whith out condition type and condition records charging fright frm customer

Hi friends
I didn't see any freight charges for the customers in pharma business (but not industry specific).
What I mean - shipping condition type, condition records doesn't maitained for the shipping.
with out frieght charges will do business-?
Any other ways to charge frieght -? or any thoughts -?
Thanks
Kris

Despite warning, you keep on posting the same question again and again. Please dont do this.
thanks
G. Lakshmipathi

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

Similar Messages

Maybe you are looking for