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

Procedure
In general you can fix the inconsistency by resetting the table in theworklist of the Consistency Check and by rescanning the tablecompletely. If this is not possible due to lack of time a manualadjustment of the affected entries can be done:
Go to the Export Control Table, select the affected tables and try tothe remove the inconsistency by using the edit button. Below you findthe list of return codes and a description to remove the problem.
Reason 1: Wrong table category
A table category has been found which is out of range. The tablecategory 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 datatype LANG and for which the "Text Language" indicator is set. All othertables are TABCAT2 tables. Check the table structure in transaction SE11and find out if it is a TABCAT1 or TABCAT2 table.
Reason 2: The language field name is empty
A TABCAT1 table has been found for which the language field name is notset. This must not occur. Go to transaction SE11 and find the correctlanguage field (data type LANG, "Text Language" indicator set). If thetable 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 hasto be changed to "2".
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 "TextLanguage" indicator is set for that field you have to change the tablecategory to "1".
Reason 4: The fallback code page is empty
A table has been found for which the table specific fallback code pageis empty. This must not occur. Please enter the "Global FallbackCodepage" from the SPUMG Settings as table specific fallback codepage.
Reason 5: The flag "Vocabulary entries exist" is out of range
The flag "Vocabulary entries exist" has to have one of the followingvalues:
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 tableand set the flag according to your findings.
Reason 6: The flag "Vocabulary entries exists" is not set correctly

There are vocabulary entries for the table but the "Vocabulary entriesexist" flag is not set correctly.
Set the flag to "2".