How To Fix UMGLOG430 - Inkonsistenzen in Export Control Table für Tabelle &1 gefunden (Grund &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: UMGLOG - Message class for the SPUMG Main Log

• Message number: 430

• Message text: Inkonsistenzen in Export Control Table für Tabelle &1 gefunden (Grund &2)

Was verursacht dieses Problem?

The check "Export Control Table" searches for general inconsistencies in
the SPUMG Export Control Table. For each inconsistent record an error
message is shown together with an error return code (reason).

Systemantwort

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

Wie behebe ich diesen Fehler?

In general you can fix the inconsistency by resetting the table in the
worklist of the Consistency Check and by rescanning the table
completely. If this is not possible due to lack of time a manual
adjustment of the affected entries can be done:
Go to the Export Control Table, select the affected tables and try to
the remove the inconsistency by using the edit button. Below you find
the list of return codes and a description to remove the problem.
<ZH>Reason 1: Wrong table category</>
A table category has been found which is out of range. The table
category has to have one of the following values:
1 = Table with Language Information (TABCAT1)
2 = Table without Language Information (TABCAT2)
3 = Table containing 7BIT ASCII character only (TABCAT3)
A TABCAT1 is a table that has at least one language field of the data
type LANG and for which the "Text Language" indicator is set. All other
tables are TABCAT2 tables. Check the table structure in transaction SE11
and find out if it is a TABCAT1 or TABCAT2 table.
<ZH>Reason 2: The language field name is empty</>
A TABCAT1 table has been found for which the language field name is not
set. This must not occur. Go to transaction SE11 and find the correct
language field (data type LANG, "Text Language" indicator set). If the
table has no language field of data type LANG or if the "Text Language"
indicator is not set, the table is a TABCAT2 and the table category has
to be changed to "2".
<ZH>Reason 3: The language field name is not empty</>
A TABCAT2 table has been found for which the language field name is set.
This must not occur. In general you can remove the language field name.
But if the table has a language field of data type LANG and if the "Text
Language" indicator is set for that field you have to change the table
category to "1".
<ZH>Reason 4: The fallback code page is empty</>
A table has been found for which the table specific fallback code page
is empty. This must not occur. Please enter the "Global Fallback
Codepage" from the SPUMG Settings as table specific fallback codepage.
<ZH>Reason 5: The flag "Vocabulary entries exist" is out of range</>
The flag "Vocabulary entries exist" has to have one of the following
values:
0 = there are no vocabulary entries for the table
2 = there are vocabulary entries for the table
Check the SPUMG vocabulary for existing entries for the affected table
and set the flag according to your findings.
<ZH>Reason 6: The flag "Vocabulary entries exists" is not set correctly
</>
There are vocabulary entries for the table but the "Vocabulary entries
exist" flag is not set correctly.
Set the flag to "2".

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE