KONH dates/condition record number not matching A * tables

[Former Member]

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

[Former Member]

The issue was caused due to splitting up on existing price to two records due to a new price being created within the validity period.

[Former Member]

The issue was caused due to splitting up on existing price to two records due to a new price being created within the validity period.

[Former Member]

The issue was caused due to splitting up on existing price to two records due to a new price being created within the validity period.

[Former Member]

The issue was caused due to splitting up on existing price to two records due to a new price being created within the validity period.

[Jelena]

I would suggest to send a message to SAP if this is causing issues in the system.

[Former Member]

Hi ,

Is there any update or development on this issue , i also faced the same issue .

please post the lastest development on this if any solution exist.

Thanks

[Former Member]

I've seen the same thing in other systems - KONH dates are not reliable. You'll have to go to the A* tables if you want to know the actual current validity dates for the condition.

[Former Member]

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.

[Jelena]

Too many questions...

KNUMH is a primary key in KONH, so there could be only one record. This field, however, is not a primary key in the A... tables, so it is technically possible that there is more than one record with the same KNUMH.

Not sure about the dates, but most likely the dates in KONH are for storing the earliest date and the latest date of all the existing condition records. So I'm not sure why you're surprised and expect them to match...

Actually I've never had to use the KONH table, why do you even care about it? Usually everything is available in KONV and A... tables....

Perhaps this link will shed some light:

http://www.sapmaterial.com/conditions.html