Change in Price validity.

[Former Member]

Hi,

i had a pricing condition in VK12 during mid of 2012 with validity period from 01.01.2012 till 31.12.9999, this was split up in such a way that the the validity was changed to 01.01.2012 till 29.12.2012 & the same condition value from 01.01.2013 till 31.12.9999, later on understanding that the price conditions are not available during 29.12.2012 to 31.12.2012, i had created the condition value & the change log appears this way

now on 4th July i made a change on the value again but only on the condition record between 01.01.2013 till 31.12.9999 to a new value along with validity end date as 31.12.2013, however i can now see that the condition value against 01.01.2006 till 29.12.2012 is also reflecting the new value which was made only against 01.01.2013 till 31.12.9999 & i could also see that the change log had captured only the former line. but i would like to know on how the value between the period 01.01.06 till 29.12.2012 got updated.

Note : the value maintained against 30.12.2012 - 31.12.2012 is not affected.

can some one help here?

Regards

Ilango

[former_member204407 · Accepted solution]

Hi,

Please provide complete change log screen shots.

the value maintained against 30.12.2012 - 31.12.2012 is not affected.

this is due to condition record exist till 31.12.9999

if you are trying to change the condition record between the existing  validity period then condition amount will not change.

further information please find the screen shots attached

here I am trying to change the material price(from 50 Rs/- to 100 Rs/-) for the month of July 2013

then I press enter

its taking old value only due to the condition record exist till 30.11.2013

Regards,

Krishna.

[Former Member · Accepted solution]

Hi Krishnakumar,

thanks for the information, the change logs were complete, i was not having any change log against the condition record on 30.12.12 till 31.12.12 & the value was also the same when viewed in VK13.

i think that in your example of changing the master record was against the existing condition record which was within the validity period, can you try doing the same update via VK11 as a new item which will throw a subsequent screen asking the update of existing records, hence will cause a split on the condition records as value between 8th July to 31st July & 1st August till 30th  Nov.

if the old record  was a record before 8th July ,say 1st July till 30th November, there would have been 3 splits.

1st july till 7th July

8th July till 31st July

1st Aug till 30th Nov

Please let me know your thoughts.

Regards

ilango

[former_member204407 · Accepted solution]

HI,

I maintained condition record by using VK11

please find the screen shots

for your understanding created with other material.

Regards,

Krishna.

[Former Member · Accepted solution]

Hi Krishna,

i am little confused with the way the change log appears, please confirm if you were able to save the condition value 50 for vallidity 8th July till 20th Nov 2013?

if not can you try creating a new cond.record without reference. i tried my proposal in my quality system & the changes were similar to my indication in my earlier post.

Regards

ilango

[Former Member · Accepted solution]

Just identified that the condition record number for the entry against the validity period 2006 to 2012 & Jan 2013 till Dec 2013 was the same.

I am on to 4.7 version on this particular scenario, on replicating the same in ECC 6.0 i was not getting the same error.

i would like to understand if this was the behavior on 4.7 or a Bug.

regards

ilango

[Former Member · Accepted solution]

proceeding to close this Request as there are no further open items, we had now created a new condition record with appropriate validity date, without changing the existing condition record & this had solved the issue.