Condition type not determined

Hello All,
I am using COPY CONTROL to create contract through VA41.
Problem i am facing is condition type not getting picked up at item level, though correct pricing procedure is getting determined. In that pricing procedure this condtion type is maintained but still it is not picking the condition type.
Rushikesh

Hi,
Can you check condition type detailed screen"Manual entries" field,the value in that field is either B or D.
Regards,
Chandra

Similar Messages

Condition type not determine in sales order

I have condition record maintained for the condition type as per the order reason. When I create the sales order system is not reading the condition record so no condition type is getting determined. Pricing date from the sales order is within the validity period of condition record.Parmeters are also matching but still in the sales order condition type is not getting determine.
Thanx
PNU

In that case, do update of pricing.
To do that, Sales Order - Item data - Condition Tab - Click Update button and choose option B - Carry out new pricing.
To know who manually remove this.
Choose Enviroment from menu bar in sales order - choose Change for display of change in the doc.
Regards
JP

EDI1 Condition type not determined automaitcally in ORDERS process

Hi Experts,
We are in the process of creating the Sales order by receiving EDI data from customer and converting in to IDOC format and trying to create the sales order. While executing the ORDERS IDOC message type sales order is getting created successfully. But Condition type EDI1 is not getting activated even after maintaining the value in E1EDP01-VPREI.
During foreground mode, if we maintain the EDI1 condition type manually then, its accepting without any issue. But during IDOC process its not getting added automatically.
Please give your suggestion on this.
Warm Regards,
Nag

Problem with the IDOC FM. We identified and rectified the issue. Thank u

VA00 condition type not getting determined for the returns order

Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputs

Hi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O

Condition type not flown(not determined) into the sales order

Hello Experts,
There is one discount condition type which is having proper condition records, validity date.However, it is not getting determined properly and is not flown into the sales order. the user wants to know why this may happen.I tried to reason it may be the sales order date and the conditon record date may be different or the condition record is changed after the creation of the sales order.neither of the reasons seem to hold good. any ideas?
Regards,
Raj

Hello,
I have looked into the analysis and asked him to update the condition by clicking on that.also, I found that the condition record is having a proper valid date. now the user would update only after knowing the exact reason why it did not flow into the sales order,he knows he has to update the condition but would not do so till he knows the right reason why condition is not determined in the sales order. now this is the situation.
the probable reasons as per analysis of the conditon type are as follows(for your information). can it be one ofThere are different reasons for this:
1)The condition was deleted manually in the item condition screen.
2)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. them?
Regards,
Raj.

HM00 -Condition type not present in pricing procedure.

I have included HM00 as manual condition type in pricing procedure attached to the sales order through prcing procedure detrmination. But in sales order when I am entering the value manually for HM00, the error is "HM00 -Condition type not present in pricing procedure", but actually it is present in pricing procedure.
Any idea how to fix thie problem ?

Hi Sunil,
Just check in V/08 > <b>YOUR</b> pricing procedure and see if HM00 is included in it or not.
Hope this will definitely solve your issue
Reward suitably
Regards
SD

Condition types not getting displayed

i have uploaded a smartform & copied the standard program(/SMB40/FM06P) of it into my system.the condition type texts & their amounts are getting displayed for import purchase order(conditions are getting picked from me22n--->conditions) but for domestic invoice im unable to display condition type texts & their amounts.(these are picked from me22n-->invoice---->taxes).
in program lines this code exists.
<FS>   like EKPO.
<KO> like KOMV.
input parameters            output parameters
ZXEKKO                        G_KSCHL
L_NETWR                      G_VTEXT
<KO>                             G_KWERT
G_VTEXT                        G_FRAKWERT
G_FRAKWERT               G_TAX
G_TOTAL
<FS>
G_TAX
L_KWERT
CLEAR: g_vtext,g_kwert,l_kwert.
CHECK NOT <ko>-kwert = <fs>-netwr.
Get Condition Type Text from table T685T and the value
SELECT SINGLE vtext INTO g_vtext FROM t685t
WHERE spras = sy-langu
AND kschl = <ko>-kschl.
IF sy-subrc = 0.
MOVE <ko>-kwert TO g_kwert.
ENDIF.
Check document currency
IF NOT l_netwr IS INITIAL.
WRITE g_kwert TO l_kwert CURRENCY zxekko-waers.
ENDIF.
*Determine if the discount is based on %
IF g_vtext CS '%' OR
g_vtext CS 'percentage' OR
<ko>-kschl = 'SKTO'.
<ko>-kbetr = <ko>-kbetr / 10.
MOVE '%' TO <ko>-waers.
ENDIF.
Determine Tax
IF g_vtext CS 'tax'.
ADD <ko>-kwert TO g_tax.
CLEAR g_kwert.
ENDIF.
Determine Freight Charges
IF g_vtext CS 'Freight'.
ADD: <ko>-kwert TO g_frakwert.
CLEAR g_kwert.
ENDIF.
i feel the data is coming from above code only.please suggest where i have to make changes so that it picks data from ME22N->INVOICE--->TAXES which has conditions for domestic purchase order.please help.

Hi
Keep a break-point (hard) in these program lines and debug and see that whether the condition type(KSCHL) related to Taxes is appearing here or not.
If the condition type for taxes is coming then you can print the taxes.
First check the related condition type for Taxes in T685 table and see here in the code.
<b>Reward points for useful Answers</b>
Regards
Anji

Condition types not copied correctly from Me11 to Me21

Dear All,
I am facing a problem in my client place, it is a import scenario where i create ME11 for a material with a combination of a vendor. After maintaining condition types like J1CV, JSDB when I am creating PO for that vendor condtion types are not copied exactly..system excludes some condtions i dont know why but it is working perfectly ion the Qlty system problem is only in Production..pls help me to over come this problem
Regards
Saru

Hi,
Mike is right, it is likely to be a problem aith the priccing procedure.
The procedure allocated to the PO may have been set up without the conditions you used in the Info record?
Check the assignment of the pricing procedure to the PO (there may be a vendor schema group on the vendor master record purchasing view that is pointing to a different schema)
Check in SPRO Logistics > Materials management > Purchasing > conditions > define price determination process > define schema determination.
Look for any setting that uses the schema group from the vendor (if the vendor schema group is blank then the system will use the schema associated qwith a blank schema group).
Then when you can see what schema the P org and vensdor group are pointing to, check the condition types linked to that in the "define calculation schema" menu above the one you just used in SPRO.
Steve B
Steve B

Condition type not appearing in PO line item

Dear All
I made a condition type Y001 for agriculture tax with below mentioned config. and marked as both header and item condition.
Cond. class A Discount or surcharge
Calculat.type A Percentage
Cond.category B Delivery costs
Manual entries C Manual entry has priority
Now problem is that when I am making contract in contract line item condition Y001 condition is appearing in dropdown and I am able to enter the same in contract and save it.But when I am trying to make a PO by referring the same contract with line item condition Y001, this same condition is not appearing in PO and also it is not appearing in dropdown also so that I can manually enter the same.
Please let me know why system is behaving like this.
Regards
SK

satish kumar wrote:
In short condition type Y001 is appearing in contract line item condition tab while making contract but same condition is not appearing in PO line item condition tab while making PO.
Hi Satish,
Perhaps you have not assigned the pricing procedure to the Purchasing Orgn & Vendor in IMG Schema determination. Have a chk once and if you have assigned try maintaining a PIR and I hope it should populate the priceing procedure and your cond type Y001 in the PO also.
Anything pls revert
Regards
Shiva

How to block particular condition type not being posted

Hi,
We don't want a particular condition type ( customized & accruel ) to be posted into accounting when creating a billing. That condition type is deleted and after that this is how it works now.
1. When a billing is cretaed from a new sale order ( which does not have that condition type ) it works fine.
2. When a billing is created from a sale order which refers to the old sale order which in turn has this condition type, then this conditon type is posted into accounting.
Can some one help in this issue so that I want to block this condition type being get posted in accounting. Is there any Userexit or can it be done with other options. I am an ABAPer, please give specific answer.

Hi Jagadish,
The reason why we do account determination is that we would want the system to post the respective amounts to respective G/L accounts automatically. What amounts to be posted to what G/L accounts is decided by the Account keys .
Now if for a particular condition type in the pricing procedure if you remove Account key the system will not post to the G/L accounts. But generally in this case I believe while creating the Bill system will throw an error in account determination.
For that what you can do is create completely new accont key and assign a provisional G/L account which is not to be included in your Balance Sheet accounts or P & L accounts (can be restriscted by FI Guys).
But remember to use a completely new oricing proicedure for this case.
Hope this helps.....
J Nagesh

Condition record not determined in PO for Taxes

HI All,
I have maintained the necessary condition type in ZTAXIN (Copy of TAXINN) Procedure for Surcharge which is calculating on VAT 12.5% for Haryana State. System is not calculating for this condition type but system is calculating Taxes for other condition types.
I have checked in FV12 also, records are exists. I have also checked in Tax condition type it is also showing the records for access.
When i am checking analysis for Tax Procedure for Surcharge condition it is showing error as - "Condition record exists (Manually removed)".
Kindly help me to resolve this issue.
Thanks in advance.
Sure points will be awarded.
Regards,
Neeraj Saini

If u are using copy of TAXINN , u need to classify condition types. The condition type u r using for VAT shud be classified as combination of tax procedure and condition classification
following is the path to the setting
Logistics - General >>>>>Tax on Goods Movements>>>>>India>>>>>Basic Settings>>>>>>Determination of Excise Duty >>>>>>Condition-Based Excise Determination >>>>>>Classify Condition Types
enter ur tax procedure .. vat condition type ... and vat tax classification.
hope it help.
regards
Avinash

Pricing condition type not working

Hi all,
A pricing condition type is present which is supposed to make the netvalue to zero after the order reason is changed to rejection using va02. But even after the order reason is changed to rejection and we tried to genrate new pricing document, the netvalue is not becoming zero. How can I debug this? The condition type is not determined by using condition records.
Thanks in advance.

Hi Smith
This should be working in the following ways.
1) Order Reason/Rejection Reason being a field in the Key combination with 100% Discount triggering Zero Net Value
if this the case, then you should check in Condition Analysis wheather the value has conrrectly flown in the condition table , if not why it has not flown in to the condition table (It could be missing value in the condition record or a prblem in the field catalogue user exit- you need to take Developer's help as suggested by others)
2) Using a Requirement and changing the Net Value Zero without any condition table field.
If so, put a break point in the requirement and check why this has not been successful in this scenario.
I hope the replies would help you to some extent in solviing the issue.
Thanks
Subbu

VPRS condition type not to display

Hi all
I have condition type VPRS in my pricing procedure but my client wants it should not be display to the all user while creating sale order. Is there any way.
Kindly replay urgently.
Vinod

Hi Vinod,
Specific condition types can be hidden on pricing screens; we did the same for VPRS condition type.
In include LV69AFZZ there is a user exit - USEREXIT_FIELD_MODIFICATION; here you need to add code as follows.
if <whatever conditions in which you want to hide it>
CASE SCREEN-NAME.
WHEN 'KOMV-KBETR'.
IF KOMV-KSCHL = 'VPRS'.
SCREEN-ACTIVE = 0.
ENDIF.
WHEN 'KOMV-KWERT'.
IF KOMV-KSCHL = 'VPRS'.
SCREEN-ACTIVE = 0.
ENDIF.
WHEN 'KOMV-KWERT_K'.
IF KOMV-KSCHL = 'VPRS'.
SCREEN-ACTIVE = 0.
ENDIF.
ENDCASE.
ENDIF (for conditions in which the field has to be hidden)
However we found that this happened only at item level; header still showed the condition type. Smart users can proportionately allocate the header condition amount to arrive upon the item level values. But you may investigate along these lins to determine if it is possible at header too.
Please reward with points if useful.
Cheers,
KC
SAP SD

WMTA output type not determining in outbound delivery

Hi,
Im in is-retail we are using lean WM for automatic transfer order creation, recently we made immediate delivery also, after this auto TO is not creating and WMTA output type also not determining in delivery.
pls help me any body why out put type is not determining and what is the solution?
Regards,
MMReddy.

There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
If thats done already then check whether you have maintianed the condition record.
If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
regds
Jude

VPRS condition type not getting computed while retro billing.

Dear All,
I have an issue while generation of Reto billing using the T.Code : VFRB.While running VFRB the values are getting computed correctly and the supplimentary debit / credit note gets created.
But the values for the condition type VPRS is not getting computed and getting transfered to CO-PA.
On pricing analysis agaist VPRS i am getting the message (Condition ignored (requirement 004 not fulfilled)).
The Item category used is TAN and the Determine cost Indicator is marked.Also while doing a sales invoice the VPRS condition type is getting computed and the value is posted in CO - PA.
What would be the reason for the error .Could some one suggest a solution .Kindlye help.
Regards,
K.Vivek

Hello vivek,
this is usually caused by userexit. Please check userexit_pricing_prepare_tkomp userexit_number_range using in rv60afzz.
Best regards,
Ivano.

Condition type not determined

Similar Messages

Maybe you are looking for