cancel
Showing results for 
Search instead for 
Did you mean: 

Picking up Condition type.

Former Member
0 Kudos

Hi,

In our order (It is a Free Sample with 100% discount). There are two condition type Z001 has got access sequence Customer Hierarchy 02/Material whereas the condition type ZSV1 has got Sold-to/Pricing ref. Material/Document Currency. The condition type ZSV1 is picked up though the condition type Z001 has got the valid condition records and the sequence is also met in the SO.

The Access sequence acts (More specific to Generic) in a particular condition type but is the Access sequence works even in Picking the condition type also. I want to know why the system picked up Condition type ZSV1 instead of Z001.

Thanks,

Jans

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

This problem may have occured at the time of creating the condition table itself,pls check whether u have not checked the field key while creating the condition table,and while creating the condition record have u got any message such as "condition records with the same validity period overlap"?

Regards,

Ramesh.

Former Member
0 Kudos

hi jans,

please check the sequence of condition types in which way they are arranged in pricing procedure.

that means in pricing procedure - the condition type ZSV1 is first and the condition type Z001 might be second.

please check and confirm

balajia

former_member183879
Active Contributor
0 Kudos

Hi,

Go to teh sales order in display mode, and go to Item conditions. At the bottom, there is a button called "Analysis". Just click this button.

Now on the left hand side, you can click your condition type and find out the reason why an unwanted update is happening.