cancel
Showing results for 
Search instead for 
Did you mean: 

Condition record existed but not being fetched

venu_ch8
Active Contributor
0 Kudos

Dear SD Experts,

This issue might be explained no of times in the forum but I have maintained all settings correct but still problem exist.

I am maintaining scales based on volume.

While creating sales order below issue I am facing.

Condition record exists,but not has been set ...Due to this condition record is not fetched.

Other settings in V/06

In vk11

V/07

And In place of k004 maintained Z004 also ...but same result...

Please guide me how to proceed...

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member200650
Active Participant
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi Venu,

Can u share the screen shot of your pricing procedure?

venu_ch8
Active Contributor
0 Kudos

Could you please check the pricing procedure screen shot

Former Member
0 Kudos

Hi Venu,

Its all because of requirement type 2. Check whether you have marked exclusion in condition record or condition type PR00.

former_member220617
Contributor
0 Kudos

Hi Venu ,

can you check weather that item category configuration Pricing is on or not ?

Because if it is on, then only value will pass, other wise this Routine - 02 will block the value .

Regards,

C B Reddy.

venu_ch8
Active Contributor
0 Kudos

Dear CB Reddy

Pricing is active

Shall I remove routine 02 from Pricing procedure?

Former Member
0 Kudos

Hi Venu,

Please share the complete screen shot of your condition type and vk11 overview screen.

You can remove routine and test the scenario but better we look at the root cause rather than removing the routine in pricing.

See the use of requirement 2 in pricing

SD requirement 2 in pricing procedure . | SCN

venu_ch8
Active Contributor
0 Kudos

Hi Sahoo,

Please check below attached screen shots

VK11

Former Member
0 Kudos

Hi Venu,

No need to check k004 condition type. Check all condition types before K004 in pricing procedure. Does any condition type has exclusion indicator?

keyur_mistry1
Active Participant
0 Kudos

Venu,

Now just change your condition calculation type C to F. It will work. (Below to condition class)

venu_ch8
Active Contributor
0 Kudos

Dear Mistry,

I maintained calculation type F also in the v/06 ( Calculation type ).

But still same problem.

former_member220617
Contributor
0 Kudos

Hi Venu ,

Can you remove routine 02 from Pricing procedure and try once ?


lets hope the value will pass to SO .


Regards,

C.B Reddy.

venu_ch8
Active Contributor
0 Kudos

Dear CB Reddy,

No use after removing 02 routine.

VeselinaPeykova
Active Contributor
0 Kudos

I am probably stating something obvious, but your condition type is set with condition category E - cash discount. In standard it is ' '. Why did you change the standard condition type like that?

keyur_mistry1
Active Participant
0 Kudos

Venu,

Sorry but I am very sure this problem is only because of too many standard configuration change. It is just creating conflicting between the condition type control and scale restriction. 

As Veselina said E- Cash discount for the fright. How and why keeping control like wise?

I think you have to do suggested changes for the K004 (Material discount) not for KF00 (Fright). Just be cool and start checking configuration from the first.

former_member233510
Active Contributor
0 Kudos

Hi Venu,

Please check SAP note 859876 - Condition is missing: Message VE 108 or VE 008. The probable causes are explained in this note. Please check did you customize structures KOMK (Header pricing) & KOMP (Item pricing), if yes then ensure all those custom conditions are working fine suppose if the custom condition interrupts the standard logic, you'll face the error VE 108 when you create sale order.

BR, Rosh.

venu_ch8
Active Contributor
0 Kudos

Dear Rosh,

Please check below screen shots.

K004 Condition type fetched..but not value.

keyur_mistry1
Active Participant
0 Kudos

Venu,

This is only problem with the Scale only.

Your condition record is working now. It retrieve the condition type too. But the condition value is not getting infer because of the scale issue only.

Can you keep scale type blank and try? It should work.

Thanks,

venu_ch8
Active Contributor
0 Kudos

Dear Mistry,

Maintained scale type blank in condition type K004...But still same issue...

Again condition record created.

Confused ..

keyur_mistry1
Active Participant
0 Kudos

Venu,

Okay lets discuss some more information.

1. Any routine is assign at sales order pricing procedure for condition type K004?

2. Your sales order booking is happening in Volume? Milliliter?

3. Sales unit of measurement is ML?

Can you check other condition types which has scale in your business? Is it similar?

venu_ch8
Active Contributor
0 Kudos

Dear Mistry,

Sales order creation is happening for ML but it is based on volume.

venu_ch8
Active Contributor
0 Kudos

Hi All,

Any one comment please..

But If I change the payment terms then K004 Condition type is beeing fetched but that is also irrespective of scales in VK11.

Confused ...

Lakshmipathi
Active Contributor
0 Kudos

Normally system will pop up this message if the condition record is maintained subsequent to sale order creation.  So you have to ensure this from change log.  Also, why in access sequence, for the table 304, Exclusive check box is blank?  It should have been ticked.

G. Lakshmipathi

venu_ch8
Active Contributor
0 Kudos

Dear Lakshmipathi sir,

I tried with activating as well but no use.

I created some condition records

Now, if we want to solve this issue what needs to be done.

Thanks a lot

keyur_mistry1
Active Participant
0 Kudos

venu gopa,


There are many reason behind this let me direct you to check some of the configuration.

- Check Condition record date.

- Try to redetermine the price at sales order.

- Check if any problem with scale type. Change scale type and check.

Scale type:

Indicator that controls the validity of the scale value or percentage:

  • From a certain quantity or value (base scale)
  • Up to a certain quantity or value (to-scale)

Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.

I am surprise here, when you change the payment term how price can determine automatically without system read condition record from VK11.

venu_ch8
Active Contributor
0 Kudos

Dear Mistry,

After keeping this option system not bringing the discount value but condition type fetching

  • From a certain quantity or value (base scale)
jignesh_mehta3
Active Contributor
0 Kudos

Hope you are creating a new order after creating / modifying Condition Records or its Scales.

Many times, system would not fetch the newly updated Condition Records in existing Orders when Pricing is re-determined. 

Thanks,

Jignesh Mehta

venu_ch8
Active Contributor
0 Kudos

Dear Jiginesh,

Many times, system would not fetch the newly updated Condition Records in existing Orders when Pricing is re-determined. 

In this case what we do ?