Skip to Content

Fetch existing validity periods of condition records

Oct 09, 2017 at 11:34 AM


avatar image
Former Member


We have a requirement to display existing validity periods of a condition records in table for custom report. I have checked konh, konp tables but the vakey keeps changing based on sequence control. Do we have any standard report or function module to get the validity periods of a condition records in table regardless of condition type selected (VA03-> Items-> Condition records->validity periods) with inputs like condition type, sales org, Dist. Channel, Material, customer. Any help is appreciated.


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Tammy Powlas
Oct 09, 2017 at 12:28 PM

Hi - I searched - the tables are listed - that should be a good start for you

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Tammy,

Thanks for the reply. The issue is i will not be having the Axxx table name to get the condition number and vakey to get info from konh, konp. Axxx table name is filled dynamically based on the condition types.


Jelena Perfiljeva
Oct 09, 2017 at 06:50 PM

I'd suggest for your company to look into V/LD (Pricing report) transaction.

Such requirement for a custom report doesn't make sense IMHO. When you're looking at the condition records in VA03, you're only shown the specific condition record, which has already been determined based on whatever criteria is in the configuration. If you just click on Analysis button on the Condition screen and spend some time there then I believe you'll have a better understanding of how pricing works.

I'm having hard time imagining what business process would possibly need to know all the validity periods for all the condition records. If the users know the condition type, they could just use VK13 and then go through all the keys quickly to check the existing records. And if you want to do the same in the program then, essentially, you'd have to do the same thing - determine all the applicable keys and then read every respective table. I still fail to see why though.

10 |10000 characters needed characters left characters exceeded