XK15

[Former Member]

Friends,

when I create customer specific conditions using XK15, it creates an additional line in database table A607.

the addition line is for example if I create the condition record from 01.08.2008 to 24.11.2008, then it will create another line from 25.11.2008 to 31.12.9999.

If I change this valid to date from 24.11.2008 to say 26.11.2008 line , then it will change but then the new line will be modifed from 27.11.2009 to 31.12.2009

This means that there is always one line additinal.

If this the standard behaviour then how we can overcome in this transaction?.

what if I use VK12 to create conditions, is there any reason why VK12 can not be used over XK15.

Regards,

Prashant

[Former Member]

Friends,

when I create customer specific conditions using XK15, it creates an additional line in database table A607.

the addition line is for example if I create the condition record from 01.08.2008 to 24.11.2008, then it will create another line from 25.11.2008 to 31.12.9999.

If I change this valid to date from 24.11.2008 to say 26.11.2008 line , then it will change but then the new line will be modifed from 27.11.2009 to 31.12.2009

This means that there is always one line additinal.

If this the standard behaviour then how we can overcome in this transaction?.

what if I use VK12 to create conditions, is there any reason why VK12 can not be used over XK15.

Regards,

Prashant

[Former Member]

Hi

Yes it's standard behaviour, because the field "Validity end date" is a key field for the condition record table A607.

VK12 is for pricing condition for sales, XK15 is a central trx for condition of every area: sales, logistic,.....

Max

[Former Member]

Hello,

Is there any SAP note which could change this behaviour, the users wanted this....

Regards,

Prashant

[Former Member]

HI

No I don't think!

The system don't delete the old record, so if the end date of validity is change, the system splits the interval in two intervals, but I think it should be the same for the user

Max