Error when using Vk12 transaction

[Former Member]

Hi All,

When i am trying to use transaction  VK12  for condition type i get the following hard stop.

Internal Error :T XKONH F KONDITION_ZUORDNEN I MV13AF0K.

I used VK+C for analysing and found some cocdition records mentioned under "Check condition key and VAKEY".

when i checked those records in KONH and KONP i could not find any errors as such.

What do you think is going wrong ? Any ideas ?

Regards

Kiran

[Former Member]

Hi All,

I found the error where it is causing it.

There is a record in A**table which does not have KNUMH and this is causing this error.

Thanks all for your suggestions.

Regards

Kiran

[former_member740571]

Hi, I have the same situation. What did you do after that? How did you solve this problem? I can't correct the inconsistencies in the condition table by VK11, becaise I have the same error message.

[Former Member]

Hi All,

I have ran VK+C and did not find any erros in overlapping records as i mentioned in my original thread some condition records in "CHECK VARKEY AND CONDITION TYPE".

i dont see any inconsistency in KOMH and KONP tables,

Thanks again!

[Shiva_Ram]

when i checked those records in KONH and KONP i could not find any errors as such.

Can you try to create those records again in VK11 and see what the system response is? You might have already checked OSS  94443 - Inconsistencies in condition master data (Termination VK067) if not check this note, point 1 under scope of check is of any use to your scenario.

Regards,

[Former Member]

hi,

This error happens when there is some inconsistency in that condition type. It means that the condition has many intervals that overlap each other.

For example:

1) 01.01.2014 => 01.02.2014

2) 02.02.2014 => 01.04.2014

3) 15.03.2014 => 01.05.2014

Herein, 2 and 3 overlap each other.

If you choose the period of valid on = 20.01.2014, it's ok. but when choosing 20.03.2014 => the system will display that error message.

and check customized condition tables also..........

[Lakshmipathi]

Check whether the following notes helps you:-

• Note 304696 - New cond maint: VK067:IVAKE F IVAKE_INSERT I MV130F0I
• Note 509115 - Error VK067 in VK32 and VK33

G. Lakshmipathi

[moazzam_ali]

Hi

What kind of error is this? Do you have some error message number for this error?

Thank$

[Former Member]

This is the message number : VK067

[moazzam_ali]

Hi

Check this note. I found it from Google. Did you try to find it in Google first?

Note 337706 - FTXP: Error VK067 when changing tax codes

Also check this link and see Lakshami's reply in this.

https://scn.sap.com/thread/1680245

Thank$

[Former Member]

Hi,

What do you think i have not searched Google before posting the question ?

btw the note what you have mentioned is related to displaying Tax codes? i clearly mentioned  VK12.

Did you try to read the question properly first?

[Lakshmipathi]

Kiran A

This is not the way to post in a global forum like SCN and definitely, you have to control your tone and avoid asking such an unwanted questions to the members who are trying to help you.

Moreover, it is highly impossible for members to read your mind and come to know that you searched the forum before posting, unless you indicate that clearly in your original post.   Please make it a habit of posting with positive attitude.

G. Lakshmipathi

[moazzam_ali]

Hi Kiran A

From your post its not clear that whether you have searched for it or not and I don't think anything, in fact I read what is written in question. If you had searched then you should have mentioned it because there are already many links and notes discussing this issue.

I had gone through your query very carefully and after that suggested you that note and link in which there are again 4 notes. This error is not that common and can be seen in varios programs/screens in SAP. Tax codes/tax conditions are used in VK12 and there are also many other transactions which use same logic and you don't need to be stick to VK12 only and think outside the box for resolving this type of issue.

FYI in SAP there can be many transactions or events where we get same error message and this is because SAP uses same logic in different programs. Condition technique is there in SD FI and MM.

You had asked for any idea and we are here to give suggestions and recommendtions when we don't know the exact solution. If you didn't get satisfactory answer then its better to raise your query to SAP.

Thank$