/SAPTRX/CONS_CHECK -> Foreign Keys error.

[Former Member]

Hello experts,

CASE ONE:

When i check the transaction /SAPTRX/CONS_CHECK, with the option "Foreign Keys", the system shows error message like this:

Entry T PMF10_NOTIF does not exist in /SAPTRX/CONDID (check entry)

Message no. 00058

In this case i have two conditions:

I. PMF10_NOTIF it´s a standard entry i don´t know why show this error.

II. When i check: SPRO -> Event Management -> General Settings in SAP Event Management -> Functions, Conditions and activities in SAP Event Management -> Define Conditions for SAP Event Management.

I check in EH Type conditions and there is the PMF10_NOTIF Condition.

Why the system show this entries as errors when the entry it´s really there?????

CASE TWO:

Other problem i have It´s when i select the option "Foreign Keys" and "Text table(s)" in /SAPTRX/CONS_CHECK, the system show an error like this:

Entry 1 ZPCM10_MOD_V_RI_ZA34 00000040 does not exist in /SAPTRX/ACT_TASK (check entry)

Message no. 00058

This Entry don´t exist in /SAPTRX/ACT_TASK table and neither in SPRO -> Event Management -> General Settings in SAP Event Management -> Functions, Conditions and activities in SAP Event Management -> Define Activities for SAP Event Management.

Why the system show entries that i deleted in previous time, why still show these?????

It´s necessary to run some report or something????

Thanks a lot by your help and best regards.

Julian.

[Former Member]

Hello experts,

According to the CASE ONE i exposed in this Question, SAP created the Note 1649598 - /SAPTRX/EH_CONSISTENCY_CHECK: Too many results, it is a pilot note, but correct this case.

According to the CASE TWO i exposed in this Question, These messages indicate that there are entries in tables /SAPTRX/ACTIVTXand /SAPTRX/ACT_TSKT, for which no entries in tables /SAPTRX/ACTIVITY

and /SAPTRX/ACT_TSKT could be found, it don´t represent a problem, however in this case the option is to delete this records.

[Former Member]

Hello,

Steffen and Kevin, thanks a lot by your collaboration, i will create an oss Message in order to get a correction.

Thanks and best regards.

Julián.

Edited by: Julian Fernando on Sep 30, 2011 4:18 PM

[former_member190756]

Hello Julian,

somehow the report checks on the wrong table: In EM system conditions are stored in table /SAPTRX/EM_COND. /SAPTRX/CONDID is the table in the Application interface. So the message can be ignored.

You Z-entry error could come up when you delete customizing entries that are referenced in other customizing views.

E.g. you delete an activity but it is still referenced in a rule set.

Best regards,

Steffen

[former_member583013]

Steffen,

Is there an OSS to correct this report?

[former_member190756]

He Kevin,

unfortuantely not. I couldn't find any one dealing with that.

Best regards,

Steffen