Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

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

Former Member
Former Member replied

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

1 View this answer in context
Not what you were looking for? View more on this topic or Ask a question