SAP ABAP Message Class UMGLOG (Message class for the SPUMG Main Log)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-I18-UNI (Application Component) I18N Unicode
⤷
SUMIG (Package) Unicode Migration: Tabellen Umsetzer + Reparatur Tool
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-I18-UNI (Application Component) I18N Unicode⤷
SUMIG (Package) Unicode Migration: Tabellen Umsetzer + Reparatur Tool 
Attributes
| Message class |  |
UMGLOG |
| Short Description |  |
Message class for the SPUMG Main Log |
| Changed On |  |
20140121 |
| Last Changed At |  |
103812 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Problem happened when finding batch jobs ( JOBNAME= &1 ) | The short text describes the object sufficiently | |
| 2 | 001 |
No more table found for processing (&1) ! | The short text describes the object sufficiently | |
| 3 | 002 |
Initialization of worklist started. | The short text describes the object sufficiently | |
| 4 | 003 |
Error processing table &1 in &2 | The short text describes the object sufficiently | |
| 5 | 004 |
Job &1 already exists. Exit the job creation | The short text describes the object sufficiently | |
| 6 | 005 |
JOB_OPEN failed (JOBNAME = &1, call from &2) | The short text describes the object sufficiently | |
| 7 | 006 |
Consistency check released | The short text describes the object sufficiently | |
| 8 | 007 |
Analysis of tables without language field released | The short text describes the object sufficiently | |
| 9 | 008 |
Analysis of tables with language field released | The short text describes the object sufficiently | |
| 10 | 009 |
Reprocessing phase released | The short text describes the object sufficiently | |
| 11 | 010 |
Container analysis released | The short text describes the object sufficiently | |
| 12 | 011 |
INDX Analysis released | The short text describes the object sufficiently | |
| 13 | 012 |
INDX Repair released | The short text describes the object sufficiently | |
| 14 | 013 |
Unicode database size check released | The short text describes the object sufficiently | |
| 15 | 014 |
Analysis of tables with ambig. lang. released | The short text describes the object sufficiently | |
| 16 | 015 |
Unexpected analysis level found | The short text describes the object sufficiently | |
| 17 | 016 |
JOB_CLOSE failed (JOBNAME = &1, call from &2) | The short text describes the object sufficiently | |
| 18 | 017 |
Unexpected error during the release of the MASTERJOB | The short text describes the object sufficiently | |
| 19 | 018 |
Problem happens when finding batch jobs in the update phase | The short text describes the object sufficiently | |
| 20 | 019 |
DDIF_FIELDINFO_GET failed (table=&1, call from &2). | The short text describes the object sufficiently | |
| 21 | 020 |
Update of work list started at &1. | The short text describes the object sufficiently | |
| 22 | 021 |
Reset of table &1 ( &2 in level &3) | The short text describes the object sufficiently | |
| 23 | 022 |
DDIF_NAMETAB_GET failed (table=&1, call from &2) | The short text describes the object sufficiently | |
| 24 | 023 |
Exception entry created for table &1 (DEFCP=&2,GUESS=&3,SKIP=&4) | The short text describes the object sufficiently | |
| 25 | 024 |
Settings are saved without changes | The short text describes the object sufficiently | |
| 26 | 025 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 27 | 026 |
UMG_PMIG_GET_TEXTFLAG failed (table=&1, call from &2) | The short text describes the object sufficiently | |
| 28 | 027 |
Default settings written to database | The short text describes the object sufficiently | |
| 29 | 028 |
Could not write settings to database ! | The short text describes the object sufficiently | |
| 30 | 029 |
No authorization to execute this program ! (&1) | The short text describes the object sufficiently | |
| 31 | 030 |
Submit of &1 failed (call from &2) | The short text describes the object sufficiently | |
| 32 | 031 |
Could not stop a master batch job | The short text describes the object sufficiently | |
| 33 | 032 |
DB_EXISTS_TABLE failed (table=&1 / call from &2). | The short text describes the object sufficiently | |
| 34 | 033 |
Table &1 belongs to category &2 which cannot be repaired by hints yet. | The short text describes the object sufficiently | |
| 35 | 034 |
Job &1 was successfully released by report UMG_MASTER_PRE_MIG. | The short text describes the object sufficiently | |
| 36 | 035 |
No entry found in worklist (table=&1 / scan level = &2) | The short text describes the object sufficiently | |
| 37 | 036 |
No entry found in control table (table=&1) | The short text describes the object sufficiently | |
| 38 | 037 |
Unexpected data-type of the sort field (&1, table = &2) | The short text describes the object sufficiently | |
| 39 | 038 |
DD_GET_NAMETAB_HEADER failed (table=&1, call from &2) | The short text describes the object sufficiently | |
| 40 | 039 |
Language code page mapping table not initialized | The short text describes the object sufficiently | |
| 41 | 040 |
No table (UMG_PRE_MIG_EXE_HINT) | The short text describes the object sufficiently | |
| 42 | 041 |
No Hint ID | The short text describes the object sufficiently | |
| 43 | 042 |
Hint (table=&1 / hintid=&2) does not exist | The short text describes the object sufficiently | |
| 44 | 043 |
Hint lang. (table=&1 / hintid=&2) is initial | The short text describes the object sufficiently | |
| 45 | 044 |
Wordlist(Condition) (table=&1 / id=&2) not found (&3) | The short text describes the object sufficiently | |
| 46 | 045 |
Wordlist(Condition) is empty (table=&1 / id=&2, &3) | The short text describes the object sufficiently | |
| 47 | 046 |
Wordlist(Condition) is incorrect (table=&1 / id=&2) | The short text describes the object sufficiently | |
| 48 | 047 |
Vocabulary hint execution for (table=&1 / hintid=&2) started | The short text describes the object sufficiently | |
| 49 | 048 |
Vocabulary hint execution failed (table=&1 / hintid=&2) | The short text describes the object sufficiently | |
| 50 | 049 |
Vocabulary hint execution for (table=&1 / hintid = &2) successful | The short text describes the object sufficiently | |
| 51 | 050 |
AB_GET_TEXT_FROM_CLUSTER: Bad cluster (table=&1, key=&2) | Space: object requires documentation | |
| 52 | 051 |
Unknown error from AB_GET_TEXT_FROM_CLUSTER (table=&1, key=&2) | The short text describes the object sufficiently | |
| 53 | 052 |
No table specified (UMG_PRE_MIG_REPROCESS) | The short text describes the object sufficiently | |
| 54 | 053 |
Error in SET_TABNAME for table &1 | The short text describes the object sufficiently | |
| 55 | 054 |
Vocabulary import started | The short text describes the object sufficiently | |
| 56 | 055 |
Vocabulary import finished | The short text describes the object sufficiently | |
| 57 | 056 |
New language added to ambiguous language list. ( &1 ) | The short text describes the object sufficiently | |
| 58 | 057 |
Language deleted from ambiguous language list. ( &1 ) | The short text describes the object sufficiently | |
| 59 | 058 |
Language "SPACE" added to ambiguous language list | The short text describes the object sufficiently | |
| 60 | 059 |
Language &1 moved from ambig. lang. list to lang. list (new CP: &2) | The short text describes the object sufficiently | |
| 61 | 060 |
Language &1 moved from language list to ambiguous language list. | The short text describes the object sufficiently | |
| 62 | 061 |
No codepage available for a language | The short text describes the object sufficiently | |
| 63 | 062 |
No languages available in the instance | The short text describes the object sufficiently | |
| 64 | 063 |
Unexpected error occured in UMG_READ_LANG_INFO | The short text describes the object sufficiently | |
| 65 | 064 |
Active language &1 added to language list with code page &2 | The short text describes the object sufficiently | |
| 66 | 065 |
SET_CODEPAGE_IN_CLUSTER failed (table=&1, key=&2) | The short text describes the object sufficiently | |
| 67 | 066 |
Language not allowed (table=&1, key=&2) | The short text describes the object sufficiently | |
| 68 | 067 |
Exception list entry for table deleted (table=&1) | The short text describes the object sufficiently | |
| 69 | 068 |
HELP_OBJECT_SHOW failed | The short text describes the object sufficiently | |
| 70 | 069 |
Export Control Table edited (&1) | The short text describes the object sufficiently | |
| 71 | 070 |
SCP_GET_CODEPAGE_NUMBER -&1- (Cat &3 ) failed (&2) | The short text describes the object sufficiently | |
| 72 | 071 |
Language vector is empty (table=&1, in &2) | The short text describes the object sufficiently | |
| 73 | 072 |
Converter object for CPs(&1, &2) could not be created in &3 | The short text describes the object sufficiently | |
| 74 | 073 |
Hint &1 for table &2 contains a language which is not allowed (&3). | The short text describes the object sufficiently | |
| 75 | 074 |
No entry in export control table (table=&1 / category=&2) | The short text describes the object sufficiently | |
| 76 | 075 |
Object of cl_umg_repair_util cannot be created | The short text describes the object sufficiently | |
| 77 | 076 |
Reprocess log(tab &1,related with key1 &2 )was not found. | The short text describes the object sufficiently | |
| 78 | 077 |
The Reprocess log of table &1 contains the invalid language key &2. | The short text describes the object sufficiently | |
| 79 | 078 |
Method FIND_JOB failed (&1, call from &2) | The short text describes the object sufficiently | |
| 80 | 079 |
Job &1 not started (Reason: &2) | The short text describes the object sufficiently | |
| 81 | 080 |
Consistency check started (&1) | The short text describes the object sufficiently | |
| 82 | 081 |
Analysis of tables without language field started (&1) | The short text describes the object sufficiently | |
| 83 | 082 |
Analysis of tables with language field started (&1) | The short text describes the object sufficiently | |
| 84 | 083 |
Reprocessing phase started (&1) | The short text describes the object sufficiently | |
| 85 | 084 |
Container analysis started (&1) | The short text describes the object sufficiently | |
| 86 | 085 |
INDX analysis started (&1) | The short text describes the object sufficiently | |
| 87 | 086 |
INDX repair started (&1) | The short text describes the object sufficiently | |
| 88 | 087 |
Unicode database size check started (&1) | The short text describes the object sufficiently | |
| 89 | 088 |
Analysis of tables with ambig. lang. started (&1) | The short text describes the object sufficiently | |
| 90 | 089 |
Settings are saved | The short text describes the object sufficiently | |
| 91 | 090 |
Settings are not saved | The short text describes the object sufficiently | |
| 92 | 091 |
The file &1&2&3&4 cannot be opened | The short text describes the object sufficiently | |
| 93 | 092 |
The file &1&2&3&4 has been opened | The short text describes the object sufficiently | |
| 94 | 093 |
R3load log file &1&2&3&4 cannot be opened | The short text describes the object sufficiently | |
| 95 | 094 |
R3load log file &1&2&3&4 has been opened | The short text describes the object sufficiently | |
| 96 | 095 |
Could not convert &2 of table &1 with value &3. | The short text describes the object sufficiently | |
| 97 | 096 |
Table &1 is skipped, but no entry found in exception list. | The short text describes the object sufficiently | |
| 98 | 097 |
Creation of scanner object failed (table=&1, reason=&2). | The short text describes the object sufficiently | |
| 99 | 098 |
No fallback codepage for table &1 in export control table | The short text describes the object sufficiently | |
| 100 | 099 |
Table &1 has been saved in DB by &2 at &3 from SUMG | The short text describes the object sufficiently | |
| 101 | 100 |
Table &1 (cat &2) has been set to complete by &3 from SUMG Manual Repair | The short text describes the object sufficiently | |
| 102 | 101 |
Languages have been added to ambiguous language list (&1). | The short text describes the object sufficiently | |
| 103 | 102 |
Languages have beed added to language list (&1). | The short text describes the object sufficiently | |
| 104 | 103 |
Call of UMG_PRE_MIG with wrong scan level (OP_MODE=&2). | The short text describes the object sufficiently | |
| 105 | 104 |
Index part of table(&1) is still in manual repair, repair that part first | The short text describes the object sufficiently | |
| 106 | 105 |
Table &1 is not in UMGTSKQ with cat &2 and status &3 (&4). | Space: object requires documentation | |
| 107 | 106 |
Only category 1 tables have r3load/IMIG log | The short text describes the object sufficiently | |
| 108 | 107 |
Table &1 (cat &2) has been processed by auto-repair, and set to &3 | The short text describes the object sufficiently | |
| 109 | 108 |
Repair hint &1 for table &2 completed successfully. | The short text describes the object sufficiently | |
| 110 | 109 |
Worklist(UMGTSKQ) has been deleted by &1 at &2 | The short text describes the object sufficiently | |
| 111 | 110 |
Table &1 has been deleted from worklist | The short text describes the object sufficiently | |
| 112 | 111 |
Auto vocabulary language assign started using method &1 | The short text describes the object sufficiently | |
| 113 | 112 |
Auto vocabulary language assign finished using method &1 | The short text describes the object sufficiently | |
| 114 | 113 |
Auto repair log language assign started using method &1 | The short text describes the object sufficiently | |
| 115 | 114 |
Auto repair log language assign finished using method &1 | The short text describes the object sufficiently | |
| 116 | 115 |
Object of &1 cannot be created | The short text describes the object sufficiently | |
| 117 | 116 |
Problems in method &1 of class &2 | The short text describes the object sufficiently | |
| 118 | 117 |
&1 is empty for table &2 . | The short text describes the object sufficiently | |
| 119 | 118 |
Invalid language list according to method &1 of class &2 | The short text describes the object sufficiently | |
| 120 | 119 |
No repair log is available | The short text describes the object sufficiently | |
| 121 | 120 |
Could not convert field &3 of table &1 with value &2. | Space: object requires documentation | |
| 122 | 121 |
Worklist(UMGTSKQ) has been initialized by &1 at &2 | The short text describes the object sufficiently | |
| 123 | 122 |
Worklist(UMGTSKQ) has not been initialized totally by &1 at &2 | The short text describes the object sufficiently | |
| 124 | 123 |
SQL error for getting the row(s) of &1 in &2 | The short text describes the object sufficiently | |
| 125 | 124 |
Job &1 not scheduled (Reason: &2) | The short text describes the object sufficiently | |
| 126 | 125 |
Error in loading files of &1&2&3&4 to DB | The short text describes the object sufficiently | |
| 127 | 126 |
Worklist(UMGTSKQ) has been updated by &1 at &2 | The short text describes the object sufficiently | |
| 128 | 127 |
UMG_POOL_TABLE executed during initialization/update of the worklist. | The short text describes the object sufficiently | |
| 129 | 128 |
This is SPUMG running on basis release &1 and support package &2. | The short text describes the object sufficiently | |
| 130 | 129 |
Table TCPDB contains: &1 | The short text describes the object sufficiently | |
| 131 | 130 |
Table TCP0I contains: &1 | The short text describes the object sufficiently | |
| 132 | 131 |
System Type: &1 | The short text describes the object sufficiently | |
| 133 | 132 |
Table &1 / field &2 / struc &3: Invalid container information! (rc=&4) | Space: object requires documentation | |
| 134 | 133 |
Table status of &1 has been set from &2 to &3 by &4! | The short text describes the object sufficiently | |
| 135 | 134 |
Table status of &1 has not been set from &2 to &3 by &4! | The short text describes the object sufficiently | |
| 136 | 135 |
Report &1 has been executed by &2. | The short text describes the object sufficiently | |
| 137 | 136 |
Consistency check finished (&1) | The short text describes the object sufficiently | |
| 138 | 137 |
Analysis of tables without language field finished (&1) | The short text describes the object sufficiently | |
| 139 | 138 |
Analysis of tables with language field finished (&1) | The short text describes the object sufficiently | |
| 140 | 139 |
Reprocessing phase finished (&1) | The short text describes the object sufficiently | |
| 141 | 140 |
INDX analysis finished (&1) | The short text describes the object sufficiently | |
| 142 | 141 |
INDX repair finished (&1) | The short text describes the object sufficiently | |
| 143 | 142 |
Analysis of tables with ambig. lang. finished (&1) | The short text describes the object sufficiently | |
| 144 | 143 |
Contents of tables DDXTF_CONV_UC and DDXTT_CONV_UC deleted. | The short text describes the object sufficiently | |
| 145 | 144 |
Report RADCUCNT released. | The short text describes the object sufficiently | |
| 146 | 145 |
Report RADCUCNT started. | The short text describes the object sufficiently | |
| 147 | 146 |
Report RADCUCNT finished. | The short text describes the object sufficiently | |
| 148 | 147 |
Table TCP0D contains: &1 | The short text describes the object sufficiently | |
| 149 | 148 |
Save point(&2 R3load log rows processed by conversion) is made in &1. | The short text describes the object sufficiently | |
| 150 | 149 |
Start of report &1. | The short text describes the object sufficiently | |
| 151 | 150 |
Please read note &2 for additional information about the report. | The short text describes the object sufficiently | |
| 152 | 151 |
&2 &3 &4 | The short text describes the object sufficiently | |
| 153 | 152 |
End of report &1. | The short text describes the object sufficiently | |
| 154 | 153 |
Report &1 is not available in your system. | The short text describes the object sufficiently | |
| 155 | 154 |
The displayed rows in table &1 are already correct, log is deleted by &2. | The short text describes the object sufficiently | |
| 156 | 155 |
DD_TBHD_CHK_LANGUFLAG failed (Call from: &1, sy-subrc = &2). | Space: object requires documentation | |
| 157 | 156 |
Textflag inconsistency for table &1 (Type = &2, Field = &3). | Space: object requires documentation | |
| 158 | 157 |
There are duplicated R3load logs. Please check the SUMG Main Log. | Space: object requires documentation | |
| 159 | 158 |
R3load log was uploaded.See 'how to reload' in Unicode conversion guide. | The short text describes the object sufficiently | |
| 160 | 159 |
Copying table &1 into &2. | The short text describes the object sufficiently | |
| 161 | 160 |
Some entries exist already | The short text describes the object sufficiently | |
| 162 | 161 |
Total number of entries in TRDIR with empty RLOAD: &1 | The short text describes the object sufficiently | |
| 163 | 162 |
Number of TRDIR-RLOAD entries filled: &1 | The short text describes the object sufficiently | |
| 164 | 163 |
Number of TRDIR entries w/o corresp.TADIR entry: &1 | The short text describes the object sufficiently | |
| 165 | 164 |
Number of corresp. TADIR entries w/o MASTERLANG: &1 | The short text describes the object sufficiently | |
| 166 | 165 |
Update of status table failed. | The short text describes the object sufficiently | |
| 167 | 166 |
XML transformation failed (&1&2&3&4),use rep. UMG_SUMG_VERIFY_R3LOAD_XML. | The short text describes the object sufficiently | |
| 168 | 167 |
&1&2&3&4 was loaded before. | Space: object requires documentation | |
| 169 | 168 |
SPUMG scans must not run in a Unicode System (&1). | The short text describes the object sufficiently | |
| 170 | 169 |
Initialization of worklist finished. | The short text describes the object sufficiently | |
| 171 | 170 |
Update of work list finished. | The short text describes the object sufficiently | |
| 172 | 171 |
Table &1 is added to work list during update of work list. | The short text describes the object sufficiently | |
| 173 | 172 |
Selected tables are not in workist with manual repair status. | The short text describes the object sufficiently | |
| 174 | 173 |
Codepage changed for language &1 (old: &3, new: &2) | The short text describes the object sufficiently | |
| 175 | 174 |
Control Character U+0000 could not be represented in system codepage. | Space: object requires documentation | |
| 176 | 175 |
Table &1 deleted from worklist of the Consistency Check. | Space: object requires documentation | |
| 177 | 176 |
Table &1 is translation relevant but the text flag is not set. | The short text describes the object sufficiently | |
| 178 | 177 |
A system message for running SUMG is created with ID &1. | The short text describes the object sufficiently | |
| 179 | 178 |
The system message for running SUMG is deleted. | The short text describes the object sufficiently | |
| 180 | 179 |
The system message for running SUMG cannot be deleted. | The short text describes the object sufficiently | |
| 181 | 180 |
No system message for running SUMG exists. | The short text describes the object sufficiently | |
| 182 | 181 |
&1 entries read from file &2 | The short text describes the object sufficiently | |
| 183 | 182 |
File &1&2&3&4 was not added to table UMGXMLFILES. | The short text describes the object sufficiently | |
| 184 | 183 |
File &1&2&3&4 is a duplicate. | The short text describes the object sufficiently | |
| 185 | 184 |
Appending repair log of table &1 with data of &2. | Space: object requires documentation | |
| 186 | 185 |
No repair hints found for table &1. | The short text describes the object sufficiently | |
| 187 | 186 |
R3load log of table &1 of file &2 was not loaded. Reason: &3 | The short text describes the object sufficiently | |
| 188 | 187 |
&3 rows deleted from UMGR3LLOG for table &1 in package &2. Reason: &4 | The short text describes the object sufficiently | |
| 189 | 188 |
Table &1 locked by &2 was unlocked by user &3. | The short text describes the object sufficiently | |
| 190 | 189 |
INDX Repair: Could not set code page for table &1 (key &2) | The short text describes the object sufficiently | |
| 191 | 190 |
Table buffer could not be reset for table &1. | Space: object requires documentation | |
| 192 | 191 |
IUUC files download to: &1. | The short text describes the object sufficiently | |
| 193 | 192 |
IUUC files uploaded. | The short text describes the object sufficiently | |
| 194 | 193 |
IUUC mode switched on. | The short text describes the object sufficiently | |
| 195 | 194 |
Replacement for structure &1 defined already in UMGCONTAINER. | The short text describes the object sufficiently | |
| 196 | 195 |
No logging table found for &1. | The short text describes the object sufficiently | |
| 197 | 196 |
IUUC adjustments stored on database. | The short text describes the object sufficiently | |
| 198 | 197 |
Special option modified (Option: &1, Value: &2). | The short text describes the object sufficiently | |
| 199 | 198 |
Repair failed (table=&1, hintid=&2, affected rows=&3) | The short text describes the object sufficiently | |
| 200 | 199 |
Repair hints execution finished for table &1 (cat &2, runtime &3). | The short text describes the object sufficiently | |
| 201 | 200 |
Repair hints execution started for table &1 (hintid=&2, log=&3, disp=&4). | The short text describes the object sufficiently | |
| 202 | 201 |
Repair hint &1 is in process. | The short text describes the object sufficiently | |
| 203 | 202 |
Table &1 is locked by user &2. | Space: object requires documentation | |
| 204 | 203 |
Table &1 was added to Manual Repair by user &2. | The short text describes the object sufficiently | |
| 205 | 204 |
Table &1 was deleted from Manual Repair by user &2. | The short text describes the object sufficiently | |
| 206 | 205 |
Report &1 started for table &2, cat &3. | The short text describes the object sufficiently | |
| 207 | 206 |
Report &1 finished for table &2, cat &3, runtime &4. | The short text describes the object sufficiently | |
| 208 | 207 |
Hint status reset (table=&1, hintid=&2) | The short text describes the object sufficiently | |
| 209 | 208 |
File name &1 is cut; maximum length allowed is &2. | The short text describes the object sufficiently | |
| 210 | 209 |
R3load feature request &1 created. | The short text describes the object sufficiently | |
| 211 | 210 |
R3load feature request &1 deleted. | The short text describes the object sufficiently | |
| 212 | 211 |
SUMG scans must not run in a non Unicode System (&1). | The short text describes the object sufficiently | |
| 213 | 212 |
SPUMG settings adjusted to new version (&1). | The short text describes the object sufficiently | |
| 214 | 213 |
The short text describes the object sufficiently | ||
| 215 | 400 |
Status check &1 does not exist. | Space: object requires documentation | |
| 216 | 401 |
There are OTF spool requests which might not be printed out yet. | Space: object requires documentation | |
| 217 | 402 |
No open OTF spool request found. | The short text describes the object sufficiently | |
| 218 | 403 |
Language &1 has been imported which does not match the system config. | Space: object requires documentation | |
| 219 | 404 |
Imported languages match the system configuration. | Space: object requires documentation | |
| 220 | 405 |
&1 words have not been assigned a language. | Space: object requires documentation | |
| 221 | 406 |
All words in the vocabulary have been assigned a language. | Space: object requires documentation | |
| 222 | 407 |
&1 Reprocess Logs have not been maintained completely. | Space: object requires documentation | |
| 223 | 408 |
All Reprocess Logs are maintained completely. | The short text describes the object sufficiently | |
| 224 | 409 |
&1 INDX Logs have not been maintained completely. | Space: object requires documentation | |
| 225 | 410 |
All INDX Logs are maintained completely. | The short text describes the object sufficiently | |
| 226 | 411 |
&1 invalid language keys have not yet been assign to the language lists. | Space: object requires documentation | |
| 227 | 412 |
All invalid languages have been assign to a language list. | The short text describes the object sufficiently | |
| 228 | 413 |
Consistency Check: serious problems reported for tables. | Space: object requires documentation | |
| 229 | 414 |
&1: Batchjobs have been canceled (Table name: &2). | Space: object requires documentation | |
| 230 | 415 |
Consistency Check: no problems found. | The short text describes the object sufficiently | |
| 231 | 416 |
Unicode nametabs are consistent and up-to-date. | Space: object requires documentation | |
| 232 | 417 |
Unicode nametabs are not consistent or not up-to-date. | Space: object requires documentation | |
| 233 | 418 |
Table DDXTT contains entries. | Space: object requires documentation | |
| 234 | 419 |
No entries found in table DDXTT. | Space: object requires documentation | |
| 235 | 420 |
Table DDXTT_CONV_UC contains entries. | Space: object requires documentation | |
| 236 | 421 |
No entries found in table DDXTT_CONV_UC. | Space: object requires documentation | |
| 237 | 422 |
Please replace matchcode ID &1-&2 by a search help. | Space: object requires documentation | |
| 238 | 423 |
All matchcode IDs have been replaced. No further action required. | The short text describes the object sufficiently | |
| 239 | 424 |
Cluster check was executed sucessfully. No issues found. | The short text describes the object sufficiently | |
| 240 | 425 |
Cluster check found errors. Please consult note 1077403. | Space: object requires documentation | |
| 241 | 426 |
Please execute report SDBI_CLUSTER_CHECK and consult note 1077403. | Space: object requires documentation | |
| 242 | 427 |
SPUMG Language Lists: no problems found. | The short text describes the object sufficiently | |
| 243 | 428 |
SPUMG Language Lists are not consistent. Please check contents. | Space: object requires documentation | |
| 244 | 429 |
No inconsistencies found in the Export Control Table. | The short text describes the object sufficiently | |
| 245 | 430 |
Inconsistency found in the Export Control Table for table &1 (Reason &2). | Space: object requires documentation | |
| 246 | 431 |
Consistency Check not started yet. | Space: object requires documentation | |
| 247 | 432 |
Version of Exception List: &1 | Space: object requires documentation | |
| 248 | 433 |
SPUMG Exception List is empty. | Space: object requires documentation | |
| 249 | 434 |
Preparations for container tables finished. | Space: object requires documentation | |
| 250 | 435 |
Preparations for container tables not finished (current status: &1) | Space: object requires documentation | |
| 251 | 436 |
No outdated messages in SPUMG main log. | Space: object requires documentation | |
| 252 | 437 |
Outdated messages in SPUMG main log. | Space: object requires documentation |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 700 |
