Valid to dates on KONH table not matching the dates in A* tables- SD pricin

Question

We have an issue in our KONH/A* tables. Please review the data below:
A583: ( This is for a Z condition type ZCTR)
MANDT KAPPL KSCHL  VKORGAU MATNR                DATBI      DATAB      KNUMH                                                                               
028   V     ZCTR   0006    000000000000031886   03/31/2006 01/01/2006 0071519869
028   V     ZCTR   0006    000000000000031886   06/30/2008 03/02/2008 0071519869
KONH
MANDT KNUMH  DATAB      DATBI    
028   0071519869 01/01/2006 12/31/9999
If you look in VK13, for this ZCTR record/material you will see the following dates.  We can see that two records have the same KNUMH , is this a SAP bug?
Also what is the difference in dates in KONH and A* tables ? I see that the valid from dates match but the valid to date in KONH is the valid to date of the last record in the A table.                                                                           
MANDT KAPPL KSCHL  VKORGAU MATNR                DATBI      DATAB      KNUMH                                                                               
028   V     ZCTR   0006    000000000000031886   03/31/2006 01/01/2006 0071519869
028   V     ZCTR   0006    000000000000031886   12/31/2007 03/13/2007 1032266853
028   V     ZCTR   0006    000000000000031886   03/01/2008 01/01/2008 1061605348
028   V     ZCTR   0006    000000000000031886   06/30/2008 03/02/2008 0071519869
028   V     ZCTR   0006    000000000000031886   12/31/9999 07/01/2008 1093084511

Answer 1

Thanks for putting so much thought into this, but I still fail to see the advantage/reason of maintaining the original dates in KONH if the new dates are prior to the original date ( in case of valid to). We always have the change log to determine the origibal dates with which the record was created.
Thanks for all the responses.
The duplicate KNUMH is causing the issue for us:
A583: ( This is for a Z condition type ZCTR)
MANDT KAPPL KSCHL VKORGAU MATNR DATBI DATAB KNUMH
028 V ZCTR 0006 000000000000031886 03/31/2006 01/01/2006 0071519869
028 V ZCTR 0006 000000000000031886 06/30/2008 03/02/2008 0071519869
As you can see two records have the same KNUMH. We were trying to run archiving for condition records and came across an issue.
As there is a duplication of KNUMH ( which is wrong) the program does not pick up the 2006 record . This is because it considers the 2008 record to be compared against the residency date and skips the older one too. We tried changing the validity dates of the 2008 record to an older date so that both are within the residency date. This is how the records looks now :
028 V ZCTR 0006 000000000000031886 06/30/2005 03/02/2005 0071519869
028 V ZCTR 0006 000000000000031886 03/31/2006 01/01/2006 0071519869
KONH
Cond.record no. Usage Table Application Condition type Valid From Valid To
0071519869 A 583 V ZCTR 03/02/2005 12/31/9999
Once we did this the archiving program was able to pick this record up.
Has any one faced this issue before? Is this a known SAP issue ? I could not find any OSS for this.
Edited by: harikrishnan balan on May 28, 2009 11:03 PM