EM - IS-U Migration
The following messages are stored in message class EM: IS-U Migration.
It is part of development package EEMI in software component FI-CA. This development package consists of objects that can be grouped under "IS-U Migration".
It is part of development package EEMI in software component FI-CA. This development package consists of objects that can be grouped under "IS-U Migration".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Delete all the substructures first |
002 | Save the structure first |
003 | &1 already exists |
004 | &1 &2 does not exist |
005 | You have not specified a conversion rule |
006 | No initial value is allowed in required input: &1 &2 |
007 | Field must exist in customer structure |
008 | Please enter a value |
009 | No generated automation data structure exists for object &1 |
010 | No conversion rules exist for object &1 |
011 | &1 was generated |
012 | &1 date &2 time of day &3 |
013 | Migration report &1 has not yet been generated |
014 | Enter a file name |
015 | The fields have no substructure |
016 | You must specify a variable category for multiple structures |
017 | Cursor is not positioned on a table entry |
018 | Function not possible with this status |
019 | No data records were selected |
020 | No generation indicator has been set for the specified structure |
021 | Comparison with data dictionary showed no difference |
022 | Error opening file &1 |
023 | Information for file header &1 |
024 | Object in import-file header does not correspond to the migration object |
025 | Documentation was not created |
026 | No documentation available |
027 | Fixed value &1 already exists |
028 | Fixed value &1 is still being used in conversion rules |
029 | Fixed value &1 in unknown |
030 | Migration was carried out |
031 | File &1 is being overwritten |
032 | File and error file may not be identical |
033 | Mig. object &1 blocked by user &2 client &3, object can only be displayed |
034 | System error |
035 | Code page &1 does not exist |
036 | File &1 was not created with character set &2 |
037 | Conversion rules still exist for the fields of structure &1 |
038 | File &1 was opened in mode &2 |
039 | You have blocked object &1 |
040 | User &1 does not exist |
041 | Select a migration object |
042 | Select a substructure of the automation data |
043 | Select a field from the automation data structure |
044 | Change not possible due to blocking status of the migration object |
045 | Company &1 does not exist |
046 | File does not exist |
047 | File already exists |
048 | No user parameters exist for user &1 |
049 | Initial field not permissible for mandatory entry |
050 | The structure does not contain fields that must be filled with data |
051 | Starting time cannot be in the past |
052 | Migration carried out in background |
053 | Object name ALL may not be used |
054 | Migration object "ALL" is not supported |
055 | Path not allowed for the current operating system |
056 | Company: &1 object: &2 user: &3 |
057 | Date: &1 Time: &2 |
058 | Field &1: Content &2 is not a number (legacy system key: &3) |
059 | Error in conversion exit &1 (legacy system key: &2) |
060 | Conversion object &1 already exists |
061 | Conversion object &1 is still used in conversion rules |
062 | Conversion object &1 is unknown |
063 | Domains are only allowed for data types "Numeric" or "Character" |
064 | Domain &1 (conversion object &2) is not valid for the field |
065 | No migration object found in company &1 |
066 | Conversion not possible (field &1, legacy system key: &3) |
067 | Change in upper/lower case: Check the conversion values |
068 | Input length shortened:Check the conversion values |
069 | Please enter a standard value |
070 | Field &1: An initial value is not allowed for required entries |
071 | No input help is available |
072 | Domain &1 has output length &2 (greater than 30) |
073 | The file to display is too large (>&1). Change mode deactivated |
074 | Documentation is displayed in language "EN" |
075 | Data type &1 already exists in object &2 |
076 | Migration object &1 created in company &2 with blocking status '100' |
077 | Short description &1 already assigned to migration obj. &2 in company &3 |
078 | Describe the return field completely |
079 | Object in import file header does not correspond to conversion object |
080 | report &1 could not be generated |
081 | Server &1 is not available. Maintain your user parameter |
082 | Protocol was created in client &1 and cannot be displayed in client &2 |
083 | Field &1 is already in maximum transfer structure &2 |
084 | Field &1 is already in the auto structure |
085 | Device allocation type &3 (device &1 for device &2 &4) not found |
086 | Event &1 for time &2 removed |
087 | Error during removal of event &1 for time &2 |
088 | Delete last entered function, perform or include |
089 | Migration object &1 from company &2 deleted |
090 | File &1 could not be opened |
091 | Could not read file header (file &1) |
092 | System code page could not be determined |
093 | No authorization for data import |
094 | You are not authorized to perform this action |
095 | You are only authorized to display |
096 | The server and/or migration path of the import file have been changed |
097 | Job released on start date &1 &2 |
098 | Job released for immediate execution |
099 | Program error |
100 | General program error (FM: &1: external ID: &2) |
101 | Legacy system key &1 has already been migrated |
102 | The higher-level object for &1, &2, does not exist |
103 | The higher-level object &2 from &1 has no IS-U key |
104 | The IS-U table for &1 was not supplemented |
105 | The new key for &1 in IS-U is unknown |
106 | No external system key exists for &1 |
107 | Key and status management for &1 was not supplemented |
108 | Incorrect processing mode |
109 | Termination due to data type &1 |
110 | Error during processing of legacy system key &1 |
111 | Field &2: An initial value is not allowed for required fields |
112 | Field &1 has an invalid format (legacy system key &2) |
113 | Runtime object with IS-U key &1 has not been defined |
114 | No external system key found for selection |
115 | Error during reading of BDC object &1 |
116 | Error during processing of legacy system key &1: message not found |
117 | Migration class &1 cannot be assigned to existing migration object |
118 | Migration object &2 from migration class &1 cannot be referenced |
119 | Cannot make changes to data of referenced migration object |
120 | Time: &1 - Data records: ok &2 / error &3 (&4 rec/h) |
121 | At least one field is not in the dictionary |
122 | Creation of BDC object &1 was cancelled |
123 | Error in creation of structure &1 |
124 | The recording defined no fields |
125 | Error in management of the recording hierarchy |
126 | Internal error reading the recording data (&1) |
127 | Field name format is invalid |
128 | Company &1 has no development class allocated |
129 | Selection of transport requests was cancelled |
130 | Position the cursor on a valid line |
131 | Enter a valid &1 |
132 | Select one of the migration objects diplayed |
133 | Select one of the auto structures displayed |
134 | Select one of the displayed fields of the auto structure |
135 | Select one of the runtime objects displayed |
136 | The entries you selected were deleted from the KSM |
137 | Changed entries were saved |
138 | Error during deletion of external system key &2 from migration object &1 |
139 | Migration object &1 already exists with external system key &2 |
140 | Error during deletion of the selected external system key |
141 | External system key &1 allocated to IS-U system key &2 |
142 | Migration object &1 does not exist in company &2 |
143 | Check completed |
144 | Check not possible |
145 | Autostructure &1 already exists at same level |
146 | Data type &1 (migr. object &2) in migration object &3 already exists |
147 | Cannot remove autostructure for a referenced migration object |
148 | Error when creating reference for migration object &1 |
149 | Autostructure with reference to migration object &1 created |
150 | IS-U release from file header different than IS-U system |
151 | SAP release from file header different than IS-U system |
152 | Activity &1 terminated |
153 | Compare with dictionary |
154 | The migration objects you selected were included in transport request &1 |
155 | Choose one or more transport requests |
156 | You have entered the wrong category/name for the transport object &1, &2 |
157 | Only make emergency changes in company &1 |
158 | Object &2 (&1) is locked |
159 | &1 is not possible |
160 | Syntax check &1: error |
161 | Error processing legacy system key &1 for referenced migration object &2 |
162 | No entries made in key and status management for hyper objects |
163 | Cannot upload Customizing due to references in hyperobjects |
164 | References to more than one migration object in data record |
165 | Place the cursor on a valid position |
166 | Insert is not possible - maximum entry of 5 migration objects |
167 | Cannot delete - migration objects found in company &1 |
168 | Place the cursor on a valid column |
169 | Controlled device &1 (reg. &2) not found in installation or dev. location |
170 | ------------------------------------------------------------------------- |
171 | &1: &2 &3 |
172 | Start parameter loading report |
173 | Start migration run |
174 | Start of error messages for migration run |
175 | Cannot find data type for referenced migration object |
176 | Cannot delete - migration object &1 is referenced |
177 | You cannot create an autostructure in a referenced migration object |
178 | You cannot delete an autostructure in a referenced migration object |
179 | Company &1 deleted |
180 | &2 is an invalid date in field &1; legacy system &3 |
181 | Select at least one migration object |
182 | Selected migration objects were created in company &1 |
183 | Selected migration objects were deleted in company &1 |
184 | You have no authorization to generate function group &1 |
185 | Function group &1 with function module for data import was deleted |
186 | Function group &1 with function module for data import does not exist |
187 | Function module &1 does not exist |
188 | Mandatory indicator for &3 deleted; indicator selected in original object |
189 | Import in selected mode is only possible in dialog work process |
190 | Field name &1 that you entered is already used in recording |
191 | Transaction code &1 of recording and &2 of BDC objects are different |
192 | Rerecording of BDC object &1 was canceled |
193 | Error &1 occured during rerecording of transaction &2 |
194 | &1 &2 added to the user shelf |
195 | Statistics for &1 read data objects: |
196 | Message &1 created |
197 | Message &1 deleted |
198 | Message &1 was changed |
199 | Message &1 was included in transport request &2 |
200 | One or more sets of field contents were truncated |
201 | Choose a valid line |
202 | Enter a name for control parameter |
203 | Enter &2; &1 is invalid |
204 | Check the fixed value definition |
205 | Entry &2 does not exist in table &1 |
206 | You cannot use fixed value &1 (cat.: code) in autodata field |
207 | Field &2 in structure &1 is not a migration field |
208 | Migration object &1 already exists in company &2 |
209 | Statistics record was selected |
210 | Selection for statistics record was undone |
211 | Statistics record(s) deleted |
212 | Enter a value &1 &2 |
213 | No messages found |
214 | Data type &1: &2 data records |
215 | Auto data structure not defined with dictionary reference |
216 | Enter a value greater than 0 |
217 | Application server/PID: &1 / &2 |
218 | Deletion not possible. Lock table for migration company &1 is locked. |
219 | Disconnection reason &1 does not exist |
220 | Disconnection reason &1: Enter data in field &2 |
221 | Reference object is not unique |
222 | The device with equipment number &1 is not installed |
223 | Document number &1 can only be referred to once per migration object |
224 | Migration File Uploaded |
225 | Migration File Downloaded |
226 | More than one contract account when selecting dunned open items |
227 | Open item already refers to disconnection object |
228 | Could not find open item with dunning history for contract account &1 |
229 | You can only start workflow for disconn. docs. with disconn. reason 01 |
230 | You can only start disconn.workflow for disconn.docs. after disconn.entry |
231 | System cannot migrate meter read.res. with meter read.reason &1 (equi &2) |
232 | Meter read.date &1 is different to meter read.date &2 for equipment &3 |
233 | Incorrect object category & or incorrect object & |
234 | No changes were made |
235 | The name of the migration company contains an impermissible character: &1 |
236 | Entry found in table &1 for user &2 |
237 | Current total throughput: &1 rec/hr |
238 | IS Migration Workbench is not released for your industry solution |
239 | Allocation of software components for migration object &1 was changed |
240 | Allocation of software components for structure &1 was changed |
241 | Enter an alternative job distribution |
242 | Deletion not permitted as job distribution &1 is still in use |
243 | Cannot find a use for job distribution &1 |
244 | Function module &1 is not a BAPI |
245 | Function module &1 called without RETURN parameter |
246 | Creation of BAPI object &1 canceled |
247 | No documentation is available for field &1 |
248 | No further information exists for processing type for field &1 |
249 | Only one historical move-in/out is possible for each data object |
250 | No &1 found for field &2 in auto structure &3 |
251 | &1 &4 not found for field &2 in auto structure &3 |
252 | Generation indicators missing in fields with processing type other then 1 |
253 | Correct the migration objects that were not generated |
254 | The same &1 &2 are used in auto structures &3 &4 |
255 | Field &2 from auto structure &3 not found in DDIC |
256 | Autostructure &3 not found in DDIC |
257 | Indicator for commit buffering is set but is not active |
258 | Enter a name for the distributed import |
259 | The name has already been used in another distributed import |
260 | Enter a value in field &1 |
261 | Item number &1 exists twice. Check the sequence |
262 | Active group run stopped |
263 | Released group run canceled successfully |
264 | Error canceling released group run |
265 | No distributed import &1 found |
266 | Cannot find group &1 |
267 | Group &1 alreay created |
268 | Enter the group that you want to copy |
269 | Group &1 was deleted |
270 | Deletion not possible due to use in import group(s) &1 |
271 | Deletion not possible due to active import runs in import group &1 |
272 | Import group &1 is blocked: Display only |
273 | Import runs are active for import group &1 |
274 | No import run is activated for import group &1 |
275 | Issue date of dunning notice is initial |
276 | Document &1 does not belong to master data group &2 &3 &4 |
277 | Dunning by collection strategy is not active for company code |
278 | Dunning notice &1 &2 already exists |
279 | Enter the meter reading time &2 for meter reading reason &1 |
280 | No meter reading order (equipment &1, reg. &2, date &3, MR reason &4) |
281 | New blocking status of migration object does not allow further changes |
282 | Execution not possible. Upgrade is running |
300 | Add-on Release &1 in remote system is different to local Release &2 |
301 | Remote system has SAP Release &1; different to local Release &2 |
302 | Add-on release in remote system is smaller then local Release &1 |
303 | Error with set up connection to remote system &1 (see long text) |
304 | Not possible to compare the same object |
305 | Enter a comparison company and comparison object |
306 | No comparison data found |
307 | No original object exists |
308 | Comparison object &1 &2 not found |
309 | Job group &1 &2 |
310 | Job group already exists |
311 | Superior job group &1 cannot be the same as the job group |
312 | Error in access to directory &1 |
313 | No migration directory found for company &1, user &2 |
314 | Enter &1 |
315 | File name &1 does not contain generic symbols |
316 | &1 already reached |
317 | &1 not found in table &2 |
318 | &1 &2 not found |
319 | Definition of distributed import not found for specified data |
320 | More import jobs scheduled than BTC work processes available on server &1 |
321 | File name &1 contains more than one wildcard |
322 | Internal error processing a distributed import |
323 | More import jobs (&1) scheduled than available global BTC work processes |
324 | Distributor import for migration object &1 only partially possible |
325 | No write access on file directory &2 from server &1 |
326 | Call does not come from own system |
327 | Multibyte code pages are not supported completely |
400 | Question catalog &1 created in project &2 |
401 | Internal error creating question catalog &1 in project &2 |
402 | Select one of the displayed catalogs |
403 | Select one of the displayed question lists |
404 | Migration object &1 not allowed for activity list |
405 | You did not change question &1 |
406 | Select a column |
407 | Question &1 created |
408 | Question list &1 saved |
409 | Error calling a method of the tree control |
410 | Position the cursor on a line in the question catalog |
411 | Maximum nesting depth reached |
412 | First remove all questions below the selected question |
413 | Position the cursor on an answer sign in the question catalog |
414 | Unlocking not possible - unlock the higher-level activity first |
415 | You cannot insert a question at the root node level |
416 | Catalog &1 in project &2 saved |
417 | Activity group &1 created |
418 | Activity group &1 saved |
419 | Activity group &1 deleted |
420 | Position the cursor on a line in the overview |
421 | Complete your entry |
422 | Activity group &1 is not allowed; enter a different activity group |
423 | Enter a unique name for the activity group |
424 | Delete the duplicate entries |
425 | Select a line |
426 | Selected line(s) deleted |
427 | Recursive use of activity group &1 |
428 | Activity group &1 is used in activity group &2 |
429 | Activity group is used in catalog &2 in project &1 |
430 | Select one of the displayed categories |
431 | Category &1 saved |
432 | Category &1 created |
433 | Category &1 is used in question &2 |
434 | Category &1 is used in activity group &2 |
435 | Category &1 deleted |
436 | Question is used in catalog &2 in project &1 |
437 | Question &1 deleted |
438 | Question catalog &1 deleted from project &2 |
439 | Catalog is locked - unlock the catalog first |
440 | Catalog &1 saved |
441 | Enter a migration company and a migration object |
442 | Select a line |
443 | No structures/fields found for transfer |
444 | Position the cursor on a line in the execution plan |
445 | Position the cursor on a migration object in the execution plan |
446 | Short name &1 already assigned for mig. object &2 in execution plan |
447 | The migration object name has already been assigned in the execution plan |
448 | Displayed migration object(s) created/changed in company &1 |
449 | Migration object &1 not compatible with reference obj. &2 in company &3 |
450 | No changes were made in company &1 |
451 | Lock activated |
452 | Lock deactivated |
453 | No use for activity group &1 found in search range |
454 | No use found for question &1 in the search range |
455 | You must use the Migration Workbench to maintain projects |
456 | Migration object &1 is referenced from companies &2 and &3 |
457 | Multiple use of &1 &2 within the activity group |
458 | Choose one or more transport requests |
459 | The selected objects were added to transport request &1 |
460 | Special character % not allowed in catalog names |
461 | Migration object &2 can be changed in company &1 |
462 | Migration object &2 can be created in company &1 |
463 | User &2 in client &3 is blocking catalog &1: display only |
464 | User &2 in client &3 is blocking activity group &1; display only |
501 | Extract &1 of &2 is already completed |
502 | Extract &1 already exists with different attributes |
503 | Extract header missing |
504 | Insert error in table &1, extract &2, document &3 |
505 | You cannot change the extract header |
506 | Following message was converted from category &1 to category &2 |