Condition record number issue

[Former Member]

Hi,

I have a situation where in a SA with LP agreement type, one item has 3 conditions PB00 for different periods.

Valid from      Valid    

Valid from	valid to	Price
01.01.2013	01.02.2013	10
02.02.2013	01.03.2013	11
02.03.2013	31.12.9999	10

Now in A016

Rows 1 and 3 have the SAME Condition record number, So changing Price in row one automatically changes row 3. How can this be resolved?

Thanks.

Richard

Message was edited by: Ajay Richard

[JL23 · Accepted solution]

in your screenshot you can see the red fields, these are the keyfields.

and since the valid to field is different, 2 records can have the same condition number.

If you have a price condition valid from 22.11.2013 to 31.12.9999

and you add another condition valid from 23.11.2013 to 31.12.2014, then you actually cut the original long term condition into 2 pieces. After 31.12.2014 the old price becomes valid again.

Hence both prices are connected via the same condition record number.

SAP explains it in OSS note 358998 - Conditions with several validity periods

[Former Member · Accepted solution]

Thanks Jürgen,

I'll check if the solution suggested in the Note resolves the issue but notice the validity periods don't overlap in the screen shot. So this means at some point the client has maintained the validity periods to be overlapping and thus the common Condition record Nr(although now they have changed it to not overlap but the condition record Nr remains same). That would be correct?

thanks.

[Former Member · Accepted solution]

Hi,

Please refer the note given by Jurgen explains that the same condition record is assigned to both when there is split by insertion of New validity period, You can also refer following blog

Thanks

[moazzam_ali]

Hi

Couldn't understand your issue. Are you talking about chganging condition record? Are you using automatic pricing? When we change a condition record, system always picks up the latest one and it is based on valid from valid to date. And another thing is that system always creates new condition record number. Can you explain your issue with some more details

Thank$

[Former Member]

Hi moazzam,

The issue is in the scheduling agreement when the client tries to change the Price in PB00 condition1 for the first period in screen shot, the price in the last condition PB00 also also changes. They dont want this and want to maintain different prices. The change is because the first and last conditions have same condition record number. (?)

Does it make sense? This might not even be an issue and standard SAP but I'd like to understand this.

Thanks.

[former_member197616]

Hi,

Open the SA at ME32L and press the conditions icon see whather there extxts differrerant periods existing or not . If so that could be OK with your phenominone . i have a tried a SA change with the new validity period with the same price of previous one . system did not create a new record for that rather it changed the previous one .

also not sure why u want to change the previous period price which was used alreday .

Regards,

[Former Member]

Hi Raghavendra,

I do not have access to the this particular system!! so is this normal procedure what the SS shows. So basically if the price on the future validity period is changed the old/past validity is automatically updated? But why is there a link between the two. If you see the screenshot the other 2 validity periods have a different condition record number.

This is unrelated to prev question but on my client I see that in the SA I can only give one validuty period per item level. How do I enter multiple validity periods with different prices in a SA for one live item? The "Change gross condition  PB00 validity Period" : All fields are greyed out.

Thanks.

Message was edited by: Ajay Richard

[moazzam_ali]

Hi

I am not MM guy. I am a SD guy but as far as I know condition record logic is there in MM and SD both and condition record number means there would be unique number for every new record we save. I am not sure about it but I guess this could be some bug or issue in standard SAP may be. It doesn't sound logical that same KNUMH is there in table. Did you find SAP notes for this? I could find those if I had some time but if you have SAP market place ID you can find with Duplicate KNUMH text.

Thank$

[ravindra_devarapalli]

Please share A016 screen shot

[Former Member]

thanks.