Pricing Condition record Problem

[ganeshsagar]

Hi SAP Gurus ,

I have created the Condition record with validity date from 01.03.2010 to 31.12.9999 and then we have two systems . These condition records are moved to another system through IDOCs with mesage type COND_A and all the transaction happened .

Now Business want to change the validity date to to say 09.09.2010. so i changed the validity Date in first system correctly using Vk12 and respective IDocs moved to another system , But after this i had a problem ,In the second system the Condition records are created with two validity Dates as 01.03.2010 to 09.09.2010 and 10.09.2010 to 31.12.9999 . So please if any body face the same problem let me know the Solution,

I am waiting for your suggestion and help .

Please let me knw any other details you required for the same.

Thanks & Regards

Ganesh Sagar

[Former Member]

Hi Ganesh Sagar,

I think like Krishnan about this issue and you should have done impact assesment for changing them. We faced it lke your problem and we have some customer hierarchies that should be updated with the new validity date. after doing these update like that in the system, system give some reactions like this and dividing their validity date according to the new date on BW side. I think you should delete all of them with problem from the system and again creating in the system after being sure proper to change them on impact assesment with the other intersection points with the other modules.

I hope these will be helpful for you.

Regards,

[former_member183879]

Hi,

This is expected behaviour. Process wise also, you need this. So you dont need to worry about it. Actually you should have done an impact analysis of your condition record change and you should have been aware of this even before doing the change.

[Former Member]

Hello Ganesh

1) Firstly ensure that Pricing Customizing - Condition type config especially (v/06)- in the source and target systems are the same.

2) I believe the inbound Idoc processing always works in the create mode (VK11) in the target system- See help documentation referred below-, so if a condition record exists already with a longer validity period than what is being sent, then it creates split records as you described.

Here is my reading of what's happening:

Transaction in Source Source validity Transaction in Target Target validity

VK11 01.03.2010 to 31.12.9999 ; VK11 01.03.2010 to 31.12.9999

VK12 01.03.2010 to 09.09.2010. Vk11 01.03.2010 to 09.09.2010

10.09.2010 to 31.12.9999

What you should do ( My guess)

a) Transfer (send) select condition records manually as opposed to automatic processing.

b) Use customer exit to reduce the field level and initialize the validity period first and then send a new create record.

c) See if you need to change Function Module RV_CONDITION_SAVE to suit your situation.

Refer to the following OSS notes for some clues:

109974 - Exchanging conditions via IDoc - possible problems

635676 - Condition exchange: Records without validity

654978 - No change IDocs are sent

146220 - Transfer of condition records with expired validity

Help Documentation:

http://help.sap.com/erp2005_ehp_04/helpdata/EN/63/71ccb745a911d3ad420000e8a5bd28/frameset.htm