DMCLG - DMC Tool Development
The following messages are stored in message class DMCLG: DMC Tool Development.
It is part of development package CNV_DMCM in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Maintenance".
It is part of development package CNV_DMCM in software component CA-LT. This development package consists of objects that can be grouped under "Data Mapping and Conversion: Maintenance".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Error calling input help |
| 001 | Enter Rule Name |
| 002 | Rule &1 already exists and cannot be created |
| 003 | The project &1 already exists |
| 004 | Specify a unique name for the project |
| 005 | Project &1 does not yet exist |
| 006 | Enter a valid name for the migration object, not <&1> |
| 007 | Project &1 deleted |
| 008 | Specify a unique name for the subproject, not <&1> |
| 009 | Error accessing text elements in ABAP Dictionary |
| 010 | Transfer rule &1 saved |
| 011 | Type assignment is not correct for parameter &1 |
| 012 | Specify unique rule names |
| 013 | Internal error when generating object &1 |
| 014 | Internal error When inserting in database |
| 015 | No currency is specified in date and time fields: &1 |
| 016 | A length must be specified in char and hex fields (&1) |
| 017 | Inconsistencies when reading type information |
| 018 | Data of project &1 has been saved |
| 019 | Editing of project &1 has been finished without saving |
| 020 | Processing project &1 |
| 021 | Migration object &1 already exists |
| 022 | Migration object data saved: &1 |
| 023 | An existing project must also be specified |
| 024 | Subproject &1 does not yet exist |
| 025 | Position cursor on valid lines |
| 026 | Specify an existing sub-project |
| 027 | Rule not found, inconsistent data |
| 028 | Error when reading table &1 from DDIC |
| 029 | Only elementary data types can be defined For fields (field &1) |
| 030 | No documentation available |
| 031 | migration object &1 created |
| 032 | Migration object &1 does not yet exist |
| 033 | Only data types from F4 help are allowed (field &1) |
| 034 | No decimal places can be defined for this type (field &1) |
| 035 | Sender structure &1 created |
| 036 | Application must be entered when generating a direct input |
| 037 | Type must be entered when generating a direct input |
| 038 | Application &1 already exists |
| 039 | Subproject &1 created |
| 040 | Invalid structure relationship type for relationship &1 - &2 |
| 041 | Internal error when structuring the interface |
| 042 | Application data saved |
| 043 | Subproject &1 unknown |
| 044 | Application data has not been saved |
| 045 | Receiver structure &1 has been created |
| 046 | Internal error when deleting an object |
| 047 | Project &1 could not be deleted |
| 048 | Subproject &1 deleted |
| 049 | Enter an existing migration object |
| 050 | Structure &1 already exists |
| 051 | Double click to select a recipient node |
| 052 | Program errors |
| 053 | Relation cannot be inserted twice |
| 054 | You attempted to transfer a relation twice |
| 055 | Transfer rule &1 does not exist |
| 056 | Rule name &1 already exists |
| 057 | Transfer rule &1 did not yet exist in target (sub)project, was now copied |
| 058 | The name of the template program &1 is not valid |
| 059 | Template program &1 could not be generated |
| 060 | The selected application &1 does not exist |
| 061 | The application type &1 of this application does not exist |
| 062 | Set the application type at first |
| 063 | XML description from file &1 already exists |
| 064 | Enter a valid file name |
| 065 | First specify the recipient field |
| 066 | It has been attempted to define the sender field &1 twice |
| 067 | Missing input parameter(s) for rule call of rule &1, event &2 |
| 068 | Radio button XML is not selected |
| 069 | Select the appropriate import interface (radio button) |
| 070 | Further import interfaces are not yet realized |
| 071 | Select sender structure |
| 072 | Line could not be deleted |
| 073 | Application &1 or type &2 do not exist |
| 074 | &1 could not be deleted |
| 075 | Structure ID names are automatically unique |
| 076 | Parameter &1 not found in the assigned sender structure |
| 077 | The field length of field &1 is not determined |
| 078 | Project &1 generated on &2 |
| 079 | Sub-project &1 generated on &2 |
| 080 | Migration object &1 created on &2 |
| 081 | Migration object &1 deleted on &2 |
| 082 | Top level sender structure &1 does not have key fields |
| 083 | Type &1 is unknown; select using F4. |
| 084 | You have not chosen the file interface as import type |
| 085 | Log data saved |
| 086 | Log data could not be updated |
| 087 | Select file descriptions or wild cards only by double clicking |
| 088 | First update log data in the general settings |
| 089 | File with name &1 not specified |
| 090 | First select the appropriate output interface |
| 091 | Field name &1 is entered twice |
| 092 | Enter name for transaction code |
| 093 | Transfer rule &1 generated |
| 094 | Chosen data structure &1 is not permitted |
| 095 | Application not configured |
| 096 | Parameter &1 already exists |
| 097 | Incomplete parameter entry |
| 098 | Line could not be inserted |
| 099 | First select the action via radio button |
| 100 | This user action is not allowed in display mode |
| 101 | Sub-project &1 already exists |
| 102 | The project &1 already exists |
| 103 | Editing of the subproject &1 has been ended without saving |
| 104 | Editing of migration object &1 has been ended without saving |
| 105 | Editing of rule &1 has been ended without saving |
| 106 | Project &1 has been deleted on &2 |
| 107 | Subproject &1 has been deleted at &2 |
| 108 | Mapping rule &1 has been generated on &2 |
| 109 | Mapping rule &1 has been deleted on &2 |
| 110 | Data from subproject &1 has been saved |
| 111 | Project &1 has been created |
| 112 | Migration object &1 has been deleted |
| 113 | You are in display mode |
| 114 | Mapping rule &1 has been deleted |
| 115 | Enter a valid name, not &1 |
| 116 | Editing cancelled |
| 117 | No object has been found |
| 118 | First determine sender range and inbound processing |
| 119 | First determine recipient range and outbound processing |
| 120 | Change mode not permitted |
| 121 | &1 already exists and cannot be created again |
| 122 | Text pool &1 not maintained |
| 123 | Editing of the structure relationships ended without saving |
| 124 | Editing of the field relationships ended without saving |
| 125 | Editing of the structures ended without saving |
| 126 | Migration object &1 could not be deleted |
| 127 | &1 has been deleted successfully |
| 128 | &1 could not be deleted |
| 129 | Invalid data path type for structure relationship &1 - &2 |
| 130 | Enter exactly one export parameter |
| 131 | Rule &1 is used by migration object(s) and has not been deleted |
| 132 | Structure &1 has been deleted |
| 133 | Transfer type &1 already exists for this application |
| 134 | The project, subproject or migration object is incorrect |
| 135 | Enter a valid field length in field &1 |
| 136 | Editing of the import interface ended without saving |
| 137 | Editing of the input files ended without saving |
| 138 | Internal Error |
| 139 | File-identifier <&1> exists at least twice |
| 140 | The data types of key relationship &1 are not equal |
| 141 | Field name '&1' does not exist |
| 142 | You must set identifying field content |
| 143 | Internal error reading the screen information |
| 144 | First select an existing application |
| 145 | No project exists yet under application &1 |
| 146 | Enter an existing project |
| 147 | Identifying field content is invalid |
| 148 | Field value for group exchange is invalid |
| 149 | Field is not relevant for split |
| 150 | Split and aggregation are not possible in the same structure |
| 151 | Rule calls of the fields of recipient structure &1 are deleted |
| 152 | Enter the type of parameter &1 |
| 153 | A maximum of one split structure can be assigned to a structure |
| 154 | Editing of the recipient range ended without saving |
| 155 | Make a selection |
| 156 | Enter a valid project, not &1 |
| 157 | Enter a numerical value |
| 158 | Select a sender node by double clicking |
| 159 | Source and target objects cannot be the same |
| 160 | Migration object &1 has been overwritten |
| 161 | Migration object &1 has been copied to &2 |
| 162 | Only select templates by double clicking |
| 163 | Internal error while copying an object |
| 164 | No rules found to copy |
| 165 | Processing interface for &1 is not configured |
| 166 | Object copy terminated |
| 167 | Identifier &1 for inbound processing already assigned |
| 168 | Identifier &1 for outbound processing already assigned |
| 169 | Name of the interface in line &1 has not been specified |
| 170 | Name of the attribute to be implemented in line &1 has not been specified |
| 171 | Attribute name &1 not known, declare as implementable interface |
| 172 | Implementation &2 of interface &1 in &3 is no longer supported |
| 173 | No original entry exists in the interface registry for selection &1 |
| 174 | You do not have authorization for this function |
| 175 | You only have authorization '&2', not '&1' |
| 176 | Method &1 is unknown |
| 177 | Key &1 already exists |
| 178 | Class name &1 is not known in class builder |
| 179 | Migration object &1 is not productive |
| 180 | Fatal error: BDoc processing not defined |
| 181 | Name for BDoc not specified |
| 182 | Fatal error: Self defined recipient range not defined |
| 183 | Recipient range from BW data source is not determined |
| 184 | Installed rule &1 does not exist yet |
| 185 | Installed rule &1 already exists |
| 186 | Migration object &1 already exists and will not be created |
| 187 | Migration object &1 has been created |
| 188 | Migration rule &1 does not exist or has not been created |
| 189 | Specify what you want to be copied |
| 190 | Internal error when loading BW data source master data |
| 191 | Data structure &1 exists in the DDIC in another version, compare |
| 192 | Data structure &1 has not been imported from DDIC |
| 193 | Data structure &1 is the same as DDIC version |
| 194 | Data structure &1 does not exist actively in DDIC, please check |
| 195 | No changes found |
| 196 | Error when connecting to Change and Transport System |
| 197 | Save project first |
| 198 | Internal error: Listbox could not be initialized |
| 199 | Internal error: Documentation could not be read |
| 200 | Internal error: PAI could not be triggered |
| 201 | Direct input type could not be added |
| 202 | Project &1 is locked by user &2 |
| 203 | Structure &1 could not be added |
| 204 | Application could not be set |
| 205 | Subproject &1 is locked by user &2 |
| 206 | Migration object &1 is locked by user &2 |
| 207 | Field &1 could not be deleted |
| 208 | Rule &1: No export parameter allowed for this rule type |
| 209 | Rule &1 is locked by user &2 |
| 210 | Application &1 is locked by user &2 |
| 211 | Object name &1 is not within a valid name space |
| 212 | Action has been terminated |
| 213 | Development classes must not be different |
| 214 | Error when changing the object catalog entries |
| 215 | Global rule that is used in rule calls will not be deleted |
| 216 | Rule is not used in migration objects |
| 217 | IDoctyp &1 with segments could not be imported |
| 218 | Data transfer object &1 with segments could not be imported |
| 219 | At first select an existing data transfer object |
| 220 | Data transfer object &1 does not exist |
| 221 | Data transfer object &1 has no subtype &2 |
| 222 | At first create the sender container |
| 223 | At first create the receiver container |
| 224 | Enter structure-ID in line &1 |
| 225 | Enter name of a DDIC structure or DDIC table in line &1 |
| 226 | Direct input type &1 is no longer supported |
| 227 | This type of inbound processing does not need any specific customizing |
| 228 | Choose button in a valid line |
| 229 | At first set the type of inbound processing to active |
| 230 | No export parameter has been found for rule &1 |
| 231 | The application is not set, please check |
| 232 | Project &1 could not be unlocked |
| 233 | Serious error during generation |
| 234 | Applications cannot be deleted from here |
| 235 | Type of receiver container for the migration object is not defined |
| 236 | A type for Direct Input 2 must be set |
| 237 | Internal error loading the steps |
| 238 | Application abbreviation &1 is not unique |
| 239 | Default application does not exist |
| 240 | Function module &1 does not exist or is not active |
| 241 | Technical fields could not be read |
| 242 | Object &1 does not exist |
| 243 | Error during generation of the reading interface of the runtime object |
| 244 | Error during generation of the output interface of the runtime object |
| 245 | During assignment you need to specify exactly one input/output file |
| 246 | Specify a user defined path |
| 247 | Error reading the meta-data: table &1 via RFC destination &2 |
| 248 | Error when reading from ABAP Dictionary for table &1 (RFC destination &2) |
| 249 | Missing entry in Field &1 |
| 250 | Subproject &1 is not assigned to project &2 |
| 251 | Copy could not be made due to the specified problems |
| 252 | Error during INSERT in table &1 |
| 253 | Error in database operation &2 on table &1 |
| 254 | There is no mass transfer with ID &1 |
| 255 | Mass transfer with ID &1 is not active |
| 256 | Error during creation of a TADIR entry for &1 &2 |
| 257 | Processing of access plans and precalculations has been cancelled |
| 258 | First select access plan, then calculate |
| 259 | Access plan &1 of migration object &2 has been calculated |
| 260 | &1: Access plan could not be calculated, block size limit exceeded |
| 261 | &1: Access plan could not be calculated, delimitation is not possible |
| 262 | Access plan for &1 is being calculated (ID &2, &3 blocks) |
| 263 | Field &1 (&2) has been chosen as selection parameter |
| 264 | Access plan has already been calculated |
| 265 | Copying migration object &1 failed |
| 266 | Copy possible only after an access plan has been selected |
| 267 | Access plan &1 already exists |
| 268 | Calculation cannot be executed as block size limit is exceeded |
| 269 | Block size is too big, only values up to 2.147.483.647 are possible |
| 270 | Changes have been saved |
| 271 | &1: Runtime object is invalid and must be regenerated |
| 272 | Access plan calculation failed |
| 273 | Table type &1 is not supported for calculation of an access plan |
| 274 | No tables have been found for the specified mass transfer |
| 275 | Access plan &1 of migration object &2 does not exist |
| 276 | No selection parameter has been selected |
| 277 | More than one selection parameter has been selected |
| 278 | Business object with key &1 does not exist |
| 279 | Wrong level of header structure in business object &1 |
| 280 | Wrong higher level structure(s) in business object &1 |
| 281 | Wrong sequence number(s) in business object &1 |
| 282 | Wrong level for header-/dependent structure(s) in business object &1 |
| 283 | Fieldname &1 in current view does not exist |
| 284 | Error in PRETTY PRINT |
| 285 | No syntax errors found |
| 286 | Pretty Print completed |
| 287 | Download directory already exists; files are overwritten |
| 288 | Creation of download directory failed |
| 289 | Download of file &1 failed |
| 290 | Object selection for creating runtime information is ambiguous |
| 291 | No download directory has been selected yet |
| 292 | Logs have been downloaded, program is finished |
| 293 | Download of Excel templates not possible |
| 294 | Download of logs cancelled |
| 295 | One or more migration objects are invalid |
| 296 | Use only event related rules for events |
| 297 | Use only processing related rules for structure fields |
| 298 | Application has been adapted as required |
| 299 | Error during adaptation of table &1 |
| 300 | No access plan found for migration object &1 |
| 301 | Package number &1 does not exist |
| 302 | Domain &1 already exists |
| 303 | Data element &1 already exists |
| 304 | No rule could be created for field &1, table &2 |
| 305 | There are no table entries for package number &1 |
| 306 | No domain rule proposals found |
| 307 | At first select a column |
| 308 | Migration object &1 is not valid or does not exist in the database |
| 309 | RFC settings have been saved |
| 310 | Saving the RFC settings failed |
| 311 | No domain rule found for migration object &1 |
| 312 | Rule &2 has been assigned to receiver field &1 |
| 313 | Rule &1 has &2 import parameters, maintenance required |
| 314 | Mass transfer &1 has been created |
| 315 | Mass transfer &1 has not been created |
| 316 | Maintain all data |
| 317 | &1: Field relations need to be checked for reason &2 |
| 318 | Start of function - &1 - on &2 at &3 |
| 319 | End of function - &1 - on &2 at &3 |
| 320 | There is more than one suitable rule proposal for field &1 |
| 321 | Error in migration object &1 |
| 322 | No rule could be created for event &1 |
| 323 | RFC settings have been deleted |
| 324 | Deletion of RFC settings failed |
| 325 | RFC destination &1 has not been defined |
| 326 | The RFC settings for the project were reassigned |
| 327 | The RFC settings of the subproject have been reassigned |
| 328 | Attention: The rule's applicability will be restricted |
| 329 | Maintain RFC destinations first |
| 330 | Function not possible, select dependent structure |
| 331 | Literal must be created with inverted commas, example 'literal' |
| 332 | Foreign key relationships have been adapted |
| 333 | Method GET_FOREIGN_KEY_FIELDS(CL_DMC_RUNTIMEOBJECT) is obsolete |
| 334 | Saving the foreign key failed |
| 335 | Access plan calculation for &1 started in sender (ID &2, Blks &3) |
| 336 | Access plan calculation still running in sender system |
| 337 | Scheduling of background job failed (see long text) &1 |
| 338 | Table &1 does not exist at RFC destination &2 |
| 339 | Mass processing &2 is locked for definition by user &1 |
| 340 | Table DMC_MT_TABLES could not be locked |
| 341 | Object belongs to an inactive mass processing, display mode only |
| 342 | Start of access plan calculation |
| 343 | Begin of data transfer (mass processing &1, access plan/precalc. &2) |
| 344 | "Automatic" cannot be both standard and alternative behaviour |
| 345 | &1 is included in pool of tables &2 |
| 346 | Table &1 is a cluster |
| 347 | Deviations were found, see application log for details |
| 348 | Higher level table &1 is not transparent |
| 349 | Precalculation &1 already defined |
| 350 | &1 &2 marked for deletion |
| 351 | No corresponding migration objects found |
| 352 | &1 &2 has already been calculated; no recalculation |
| 353 | &1 &2 marked for deletion; calculation not possible |
| 354 | For pool and cluster tables no precalculations can be created |
| 355 | Precalculation for &1 is being calculated (ID &2, sgmnts &3) |
| 356 | Precalculation has been calculated |
| 357 | Start of access plan creation |
| 358 | End of access plan creation (&1 access plans have been created) |
| 359 | The RFC settings of the subproject have not been completed yet |
| 360 | Enter a valid key |
| 361 | Deletion flag for &1 &2 has been reset |
| 362 | Calculation has been cancelled |
| 363 | Error during calculation of &1 &2 |
| 364 | Blocksize invalid, standard blocksize has been set |
| 365 | No linking operator has been specified |
| 366 | No linking operator must be entered in the last entry |
| 367 | Precalculation &1 does not exist for migration object &2 |
| 368 | Structure &1 does not exist in DDIC (RFC destination &2) |
| 369 | Subproject &1 has been copied to &2 |
| 370 | Calculation of a pool or cluster table; see long text |
| 371 | Name &1 does not begin with Y or Z (customer namespace) |
| 372 | Specify both the pattern to be replaced and the new pattern |
| 373 | Conv.Obj. name too long (original &1 and prefix/suffix &2) |
| 374 | Pattern &2 not found in original name &1 |
| 375 | Migration object name too long (original &1, &2 replaced by &3) |
| 376 | Migration object name too long (original &1) |
| 377 | Migration object &1 uses (sub)project rule &2 |
| 378 | Original migration object &1 is already assigned to mass processing &2 |
| 379 | Copy behavior "automatic" cannot be combined with another behavior |
| 380 | Please enter either Z or Y |
| 381 | Select at least one copy behavior |
| 382 | Migration object &1 is already contained in subproject &2 |
| 383 | RFC communication error &2 (RFC destination &1) |
| 384 | The RFC destination has not been specified |
| 385 | Program terminated in remote system &1: &2 &3 |
| 386 | Assignment of rules in source and target area is missing or incorrect |
| 387 | No ID could be assigned to append structure &1 |
| 388 | System ID has not been specified |
| 389 | Called function module is not compatible to the system release |
| 390 | Release of the system has not been specified |
| 391 | DDIC structure name has not been specified |
| 392 | DDIC provider object could not be created |
| 393 | System type could not be determined (rfc destination &1) |
| 394 | Error during construction of structure name (maximum length exceeded) |
| 395 | Insertion of structure &1 into the data dictionary failed |
| 396 | Object could not be copied due to missing RFC settings |
| 397 | DDIC activation failed for one of the structures listed below (Table &1): |
| 398 | Copy done in background job; see application log in SLG1 |
| 399 | Report cannot be executed in background |
| 400 | Specify name of target migration object |
| 401 | Header table &2 is already included in mass transfer &1 |
| 402 | A rule with the same name &1 already exists in the target environment |
| 403 | Conv.obj. &2: (sub-)project specific rule &1 will not be copied |
| 404 | Receiver field &2: rule call for rule &1 has not been created |
| 405 | Rule &1 is already used and cannot be overwritten |
| 406 | Assignment of rules of different types is not allowed |
| 407 | Same rule name &1 for &2 and &3 |
| 408 | Rule name &1 is already used for another rule within the project |
| 409 | Mass transfer ID must be the same as either the suffix or replace pattern |
| 410 | Conv. obj. &1 was not assigned to mass transfer due to missing structure |
| 411 | Conv.obj. name &1 does not end with mass transfer ID &2 |
| 412 | Receiver field &1: rule import param. field &2 missing in sender struct. |
| 413 | Data type &3 of rec.field &1 deviates from data type &4 of snd. field &2 |
| 414 | Output field length of receiver field &1 less than that of snd. field &2 |
| 415 | Field length &3 of receiver field &1 less than that of snd. field &2 (&4) |
| 416 | Import parameter &2 missing for receiver field &1 |
| 417 | There is no rule call for receiver field &1 |
| 418 | Prim. struct. relationship &1: different DDIC-struct. f. sender/receiver |
| 419 | Not used sender fields in structure &1 |
| 420 | Field &2 of structure &1 has been added |
| 421 | &3 of field &2 in structure &1 has been changed |
| 422 | Field &2 of structure &1 deleted |
| 423 | Messages for migration object &1 |
| 424 | For receiver structure &1 there is no primary structure relationship |
| 425 | Sender structure &1 is not used in any structure relationships |
| 426 | Migration object &1 is invalid |
| 427 | Precalculation &2 of conv.obj. &1 has not yet been completely calculated |
| 428 | Access plan &2 of migration object &1 has not yet been calculated |
| 429 | Syntax error in rule &1 |
| 430 | Migration object &1 has mass transfer status "failed" |
| 431 | Key indicator for field &1 cannot be deselected |
| 432 | Empty container for migration object &1 |
| 433 | Rule &1 has not yet been released and cannot be used |
| 434 | Mass transfer &1 is in active phase &2, start in phase &3 not possible |
| 435 | Rec.field &1: Type conflict btw. data types of sender field and act.param |
| 436 | Foreign key maint. is not possible if struct. does not exist in database |
| 437 | More than one top level table for sender container of conv.obj. &1 |
| 438 | Processing not possible due to missing structure(s) / container(s) |
| 439 | Foreign key type "initial" is not valid |
| 440 | For message &1 &2 maximum number of application log entries reached |
| 441 | Migration object &1; no header structure has been specified |
| 442 | migration object &1; more than one header structure has been specified |
| 443 | Error in structure hierarchy of migration object &1 |
| 444 | Selection field &1 is not key field in header structure of conv.obj. &2 |
| 445 | Rule &1 does not have a formal parameter &2 |
| 446 | Structure relationship error: Sender structure &1 does not exist |
| 447 | Structure relationship error: receiver structure &1 does not exist |
| 448 | Relationship btw. sender struct. &1 and rec. struct. &2 already exists |
| 449 | No subproject has been assigned to mass transfer id &1 |
| 450 | Subproject &2 which is assigned to mass transfer ID &1 does not exist |
| 451 | A field that is not supported was chosen as selection parameter |
| 452 | Subproject &1 is already assigned to another mass transfer |
| 453 | Mass transfer ID &1 already exists |
| 454 | Mass transfer id &1 already includes the objects to be inserted |
| 455 | No line has been selected |
| 456 | Mass transfer with ID &1 has been deleted |
| 457 | Migration object &1 cannot be generated due to DDIC differences |
| 458 | The specified receiver field &1 does not exist in structure &2 |
| 459 | Different activation time stamps for structure &1 in migration object &2 |
| 460 | Instance of class CL_DMC_MT_CONV_OBJECT could not be created |
| 461 | Setting the environment parameters failed |
| 462 | Foreign key relationship with fields of different types - Field name '&1' |
| 463 | &1 access to table &2 is not possible in migration object &3 |
| 464 | Processing type &1 is not supported |
| 465 | For table type '&1' precalculation is not supported |
| 466 | Access plan for &1 prelim. calc. &2 is calculated (ID &3, Blks &4) |
| 467 | Access plan calc. for &1 prel.calc. &2 started in sender (ID &3, Blks &4) |
| 468 | Preliminary calculation for &1 started in sender (ID &2, Sgmnts &3) |
| 469 | Error while preparing the preliminary calculation |
| 470 | Preliminary calculation in sender is still running |
| 471 | Error while reading calculation data in sender |
| 472 | Preliminary calculation &1 has already been completed |
| 473 | Invalid segment size; segment size is set to default value |
| 474 | Invalid look-up-depth; look-up-depth is set to default value |
| 475 | Invalid ID; enter a valid value |
| 476 | &1 : Flags for migration object &2 are reset |
| 477 | Error while checking RFC connection &1 |
| 478 | Job &1 with ID &2 started on &3 at &4 |
| 479 | Job &1 with ID &2 has been completed successfully |
| 480 | Executing job &1, ID &2 failed |
| 481 | Data for merge scenario has not been maintained completely |
| 482 | No data for mass transf. &1, run &2 is available, check the merge scen. |
| 483 | No application log exists |
| 484 | Copy successfully tested, object &1 has not been created |
| 485 | Creation of migration object &2 failed due to invalid table type &1 |
| 486 | No differences found during DDIC comparison |
| 487 | Different data path in structure relationship &1 << &2 in '&3' u. '&4' |
| 488 | Different data path type in structure relation &1 << &2 in '&3' and '&4' |
| 489 | Different rule for event '&1' in '&2' and '&3' |
| 490 | Start of comparison of migration objects for table &1 |
| 491 | End of comparison of migration objects for table &1 |
| 492 | Sender containers of mig. objects '&1' and '&2' are equal |
| 493 | Sender containers of mig. objects '&1' and '&2' are different |
| 494 | Receiver container of mig. objects '&1' and '&2' are equal |
| 495 | Receiver containers of mig. objects '&1' and '&2' are different |
| 496 | Structure relation '&1 << &2' does not exist in mig. object &3 |
| 497 | Different relation in structure relation '&1 << &2' in '&3' and '&4' |
| 498 | Containers are different (sender /receiver); comparison not possible |
| 499 | No objects for comparison found for mass data transfer &1, table &2 |
| 500 | No mass transfer for checking specified; enter required data |
| 501 | Migration object for mass transfer &1, table &2 not found |
| 502 | Subproject for migration object &1 not found |
| 503 | Project for migration object &1 not found |
| 504 | Application for migration object &1 not found |
| 505 | There is no migration object for mass transfer &1, table &2 |
| 506 | Error loading migration object &1 |
| 507 | Structure &1 does not exist in &2 |
| 508 | ID of structure &1 is different in '&2' and '&3' |
| 509 | The sequence of the structures in '&1' differs from the one in '&2' |
| 510 | Structure &1 has been created at different levels in '&2' und '&3' |
| 511 | Structure &1 is assigned to different structures in '&2' and '&3' |
| 512 | Conv.-obj. '&1' and '&2' have different selection parameters |
| 513 | Error checking selection parameters; header structure not found |
| 514 | Foreign key '&1' of structure &2 (&3) is not maintained in '&4' |
| 515 | Foreign key '&1' of structure &2 maintained differently in &3 and &4 |
| 516 | Field '&1' of structure &2 (&3) does not exist in '&4' |
| 517 | Length of field '&1' (structure &2) is different in '&3' and '&4' |
| 518 | Decimal places of field '&1' (&2) different in '&3' and '&4' |
| 519 | Internal type of field '&1' (&2) different in '&3' and '&4' |
| 520 | Data type of field '&1' (structure &2) different in '&3' and '&4' |
| 521 | Different rule for field '&1' (structure &2) in '&3' and '&4' |
| 522 | Parameter &1 of rule for &2 (&3) has a different field assigned in &4 |
| 523 | Parameter &1 of rule for &2 (&3) not found in &4 |
| 524 | Check has been started in background; see log for results |
| 525 | Check completed; see log for results |
| 526 | Different relation types in structure relation &1 << &2 in '&3' and '&4' |
| 527 | Field for parameter &1 of rule for &2 (&3) in &4 from different structure |
| 528 | Cardinality of receiver structure in '&1 << &2' in '&3' and '&4' differs |
| 529 | Cardinality of sender structure in '&1 << &2' in '&3' and '&4' differs |
| 530 | Structure &1 of type &2 cannot be added to hierarchy level 1 |
| 531 | System data for destination &1 is not complete |
| 532 | Destination for process &1 is missing |
| 533 | Settings can only be changed at subproject level |
| 534 | Rule cannot be created because object does not yet exist in database |
| 535 | Unexpected program error; obsolete coding has been used |
| 536 | RFC cannot be maintained because object does not yet exist in database |
| 537 | Object cannot be created until data has been saved |
| 538 | Updating the steps for &1 failed |
| 539 | No dialog or batch processes are defined for destination &1 |
| 540 | Server &1 is not defined |
| 541 | Error encountered while handling substitution names in ODQ scenario |
| 542 | Additional computers are available for process &1 |
| 543 | Server &1 has already been assigned |
| 544 | Subproject &1 has a different destination (&2) |
| 545 | Load number &1 lies outside the range [0,255] |
| 546 | Subproject &1 has a different release level &2 |
| 547 | Destination for process &1 is missing |
| 548 | Destination &1 runs with operation mode &2 |
| 549 | Processing is not possible due to missing runtime object |
| 550 | Wizard processing has been cancelled |
| 551 | For subproject &1 no &3 is maintained for &2 |
| 552 | Table type has been changed from &1 to &2; regeneration required |
| 553 | Function terminated; registration via RFC-dest. &2 (&1) not possible |
| 554 | Confirm the rfc data change for your subproject |
| 555 | Processing not possible due to missing DDIC sync |
| 556 | DDIC comparison has been started in background |
| 557 | No migration objects with source &1 have been selected yet |
| 558 | Invalid input in field &1 |
| 559 | Invalid data type &1 |
| 560 | Specify your run id |
| 561 | Update for table &1 failed |
| 562 | Mass transfer &1 has been changed |
| 563 | Maintenance of RFC data is not possible in display transaction |
| 564 | Source and target systems are the same |
| 565 | It is not possible to lock table &1 |
| 566 | Run-id &1 does not exist |
| 567 | For system &1 only &2 batch processes are defined |
| 568 | Run id &1 already exists |
| 569 | Root structure cannot be obtained for migration object &1 |
| 570 | Field information cannot be obtained for migration object &1 |
| 571 | Index information cannot be obtained for migration object &1 |
| 572 | collective access plan &2 has been created for migration object &1 |
| 573 | Updating selection parameter failed for migration object &1 |
| 574 | Updating analysis status failed for migration object &1 |
| 575 | Invalid table name &1 of migration object &2 |
| 576 | Invalid fieldname &1 for migration object &2 |
| 577 | Event rule &1 does not exist |
| 578 | Timestamp comparison finished |
| 579 | Table class invalid for migration object &1 |
| 580 | No record exists with run id &1 and status &2 |
| 581 | Setting selection parameter failed for migration object &1 |
| 582 | Failure in getting the next migration object |
| 583 | Destination &1 is currently locked for transfer |
| 584 | Migration objects have been adapted successfully |
| 585 | No DDIC table has been specified for structure &1 |
| 586 | Analysis of run id &1 failed |
| 587 | Analysis of run id &1 successful |
| 588 | Adding/deleting migration objects to/from run id &1 failed |
| 589 | Adding/deleting migration objects to/from run-id &1 successful |
| 590 | Worklist of run id &1 is empty |
| 591 | Refresh operation successful |
| 592 | For mig. object &1 none of the key fields is sufficiently selective |
| 593 | Invalid run id |
| 594 | Specify run id |
| 595 | For mig. object &1 selection parameter and blocksize were determined |
| 596 | Receiver field &1; rule &2 does not exist |
| 597 | Creation of run id failed |
| 598 | For migration object &1, selection field &2 has been determined manually |
| 599 | Data type mismatch |
| 600 | Modification failed |
| 601 | Invalid parameter |
| 602 | Check entry in cell &1 row no. &2 |
| 603 | Higher level structure &1 does not exist |
| 604 | No table has been selected for foreign key field &1 |
| 605 | Conversion logic cannot be maintained until it has been saved |
| 606 | The number of jobs scheduled exceeds number of background processes |
| 607 | No scheduling was done; total number of jobs = 0 |
| 608 | 1 job with ID &1/&2 has been scheduled for execution on server &3 |
| 609 | Total number of jobs scheduled is &1 |
| 610 | No translation object available for variant &1 |
| 611 | Function not possible; select conversion type |
| 612 | Function merely possible after selection of rule |
| 613 | Function merely possible after selection of fixed value |
| 614 | Function merely possible after selection of control parameter |
| 615 | Function merely possible after selection of translation object |
| 616 | Multiple selection is not allowed for this function |
| 617 | Object &1 exists already |
| 618 | Maximum number of import parameters for translation object reached |
| 619 | Export parameter must not be deleted |
| 620 | Function not available for global rule &1 |
| 621 | Fixed value &1 does not exist or lies outside of visibility range |
| 622 | Control parameter &1 does not exist or lies outside of visibility range |
| 623 | Translation object &1 does not exist or lies outside visibility range |
| 624 | Rule &1 does not exist or lies outside of visibility range |
| 625 | Translation object &1 is locked by user &2 |
| 626 | Translation object &1 is still in use and cannot be deleted |
| 627 | Fixed value &1 is still in use and cannot be deleted |
| 628 | &1 &2 already exists within visibility |
| 629 | Control parameter &1 is still in use and cannot be deleted |
| 630 | Variant &1 is deleted although it may still be used |
| 631 | No standard variant has been chosen |
| 632 | Action has been cancelled due to errors in foreign key relationships |
| 633 | Control parameter &1 is locked by user &2 |
| 634 | Fixed value &1 is locked by user &2 |
| 635 | Navigation has been refreshed |
| 636 | No fixed value has been maintained for variant &1 |
| 637 | Actual param. of transl. object in variant &1 is not completely defined |
| 638 | Variant &1 does not exist in rule &2 |
| 639 | Variant &1 does not exist in control parameter &2 |
| 640 | Rule customizing is locked by user &1 |
| 641 | Fixed value customizing is locked by user &1 |
| 642 | Control parameter customizing is locked by user &1 |
| 643 | Function is not possible; no history available |
| 644 | Input does not comply with defined data type &1 |
| 645 | Input is too long; predefined length &1 |
| 646 | Maximum length of a fixed value is 128 characters |
| 647 | Start date &1 of the batch job lies in the past |
| 648 | Start time &1 of the batch job lies in the past |
| 649 | Number of batch jobs &1 differs from ideal value &2 |
| 650 | Required import or export parameter has not been maintained |
| 651 | Sequence of parameters has not been kept |
| 652 | Parameter &1 &2 has not been maintained completely |
| 653 | Translation object is not valid; data cannot be changed |
| 654 | Saving of data has been cancelled by user |
| 655 | Database update failed |
| 656 | Translation value &1 in line &2 has not been maintained |
| 657 | Combination of input values (line &1) already exists |
| 658 | Duplicate translation values; data has not been saved |
| 659 | Runtime objects of conv.obj. &1 regenerated due to time stamp deviation |
| 660 | Input contains illegal characters |
| 661 | Status "Supplied by rule call" is set automatically |
| 662 | DDIC timestamp comparison started |
| 663 | Invalid supply status; change has been revoked |
| 664 | Variable &1 does not exist or lies outside of visibility range |
| 665 | &2 batch jobs are started for computer &1 |
| 666 | Computer &1 has optimal start number &2 |
| 667 | Regeneration is required due to DDIC deviation for conv.obj. &1 |
| 668 | Function merely possible after selection of variable |
| 669 | Variable &1 is locked by user &2 |
| 670 | Maximum length of a variable is 255 characters |
| 671 | Function not possible; function group has not been generated yet |
| 672 | Invalid object name; do not use any spaces |
| 673 | End of processing &1 lies before batch start &2 |
| 674 | No inconsistencies found during check |
| 675 | Domain &1 is already assigned to rule &2; mapping is deleted |
| 676 | Data element &1 is already assigned to rule &2; assignment is deleted |
| 677 | &1 &2 already exists in a lower level object (&3 &4) |
| 678 | Navigation has been synchronized with database |
| 679 | Rule &1 has been changed; users need to be aligned |
| 680 | Datatype is not maintained; enter datatype or choose 'TYPE_ANY' |
| 681 | Rule user &1 is locked by user &2 |
| 682 | Switch to display mode of parameter maintenance |
| 683 | Function not available until data has been saved |
| 684 | Identifier is too long; maximum valid length in SAP namespace: &1 |
| 685 | Enter a transport request |
| 686 | Transport request &1 cannot be used |
| 687 | Migration object &1 cannot be generated due to XML schema differences |
| 688 | No XML file specified for inbound processing of migration object &1 |
| 689 | The specified directory does not exist |
| 690 | The specified directory does not contain a project file |
| 691 | The specified directory does not contain a subproject file |
| 692 | XML synchronization has been completed successfully |
| 693 | Comparison; no differences found |
| 694 | No XML schema definition found |
| 695 | XML schema file successfully parsed |
| 696 | Structure &1 not found in right place in XML schema |
| 697 | Use input help to select rule; input has been reset |
| 698 | Translation object customizing is locked by user &1 |
| 699 | Background job in sender system for access plan calcul. not yet started |
| 700 | Number of deleted records &1 |
| 701 | Importing table keys for table &1 failed |
| 702 | Not all records could be deleted |
| 703 | Start of processing for table &1 |
| 704 | Number of records to be deleted: &1 |
| 705 | Runtime information has been reset |
| 706 | Conv.obj. &1: Calculation job in sender system could not be started |
| 707 | FROM DDIC flags have been removed successfully |
| 708 | No imports found for specified selection (conv. obj. &1) |
| 709 | There is no deletion information for run id &1 |
| 710 | There is no runtime information for run id &1 |
| 711 | All data for migration object &1 / run id &2 has been deleted |
| 712 | Rule &1: Inconsistency regarding position numbers of rule parameters |
| 713 | Variable &1 is still in use and cannot be deleted |
| 714 | Specify valid &1 |
| 715 | & does not exist |
| 716 | No projects found |
| 717 | Select migration objects |
| 718 | Copy suffix is not unique |
| 719 | No conflict information available |
| 720 | Generation of checks for &1, &2, &3 |
| 721 | End of generation of value checks for &1, &2, &3 |
| 722 | Table name &1 is different from name of foreign key table &2 |
| 723 | Identifier &1 is protected; choose another identifier |
| 724 | &1-&2: no domain fixed values, no foreign keys, no value tables |
| 725 | &1: Name of foreign key table contains string &2 |
| 726 | Parameter &1: &2 is not a valid value for domain &3 |
| 727 | Parameter &1: &2 is not a valid value of table &3 (field &4) |
| 728 | No valid domain has been specified |
| 729 | Domain &1 does not contain any check values |
| 730 | Table/field combination does not exist or does not contain any data |
| 731 | &1-&2: Not all required data for reading foreign key table is available |
| 732 | Table &1: For &3 of a total of &2 fields, value checks have been created |
| 733 | The selected migration object does not exist any more |
| 734 | The selected project does not exist any more |
| 735 | &1-&2: Non unique key of check table &3 |
| 736 | &1-&2: Check not possible because key is not a field of the domain |
| 737 | For conv.object &1, field &2 of index &3 at pos. &4 was set as sel.par |
| 738 | Rule &1 is still in use and cannot be deleted |
| 739 | Only transparent, pool or cluster table classes are allowed |
| 740 | Table class succeessfully changed to &1 for table &2 |
| 741 | Specified table class &1 is the same as the existing one (&2) |
| 742 | No valid writing behavior has been specified |
| 743 | For conv.object &1, field &2 of primary idx at pos. &3 was set as selpar |
| 744 | Maximum valid length for identifier has been exceeded |
| 745 | Data import is not possible; maintain run ID or local path |
| 746 | Actual parameter &1 is not a valid |
| 747 | Select a migration object |
| 748 | Translation values for the object must be maintained at project level |
| 749 | Mass transfer ID &1 has already been assigned to another subproject |
| 750 | Migration object &1 was added to mass transfer &2 |
| 751 | DB analysis job in sender system could not be started |
| 752 | Reading type successfully changed to &1 for table &2 |
| 753 | The specified reading type &1 is the same as the existing one (&2) |
| 754 | Different database systems used in sender and receiver system |
| 755 | No mig. objects exists with status "Generated" for mass transfer &1 |
| 756 | Reading type has been changed; runtime objects need to be regenerated |
| 757 | Mass activation has failed |
| 758 | The application &1 is locked for Workbench processing |
| 759 | Invalid project; there is no or more than one subproject |
| 760 | XML sync cannot be performed because XML schema file is invalid |
| 761 | Reading type &1 is not supported for access plan calculation |
| 762 | Action not possible; no migration object has been assigned |
| 763 | Action not possible as no write behaviour has been selected |
| 764 | Action not possible because there is no receiver structure |
| 765 | Action not possible because there is no sender structure |
| 766 | Migration Object &1: structure &2 doesn't include any fields |
| 767 | Delete cluster data in the sender system for mass transfer &1 |
| 768 | Cluster deletion in sender system finished on &1 at &2 |
| 769 | Loading of cluster data in sender system started on &1 at &2 |
| 770 | Please select project |
| 771 | Please select migration object |
| 772 | Load of cluster data in the sender system completed on &1 at &2 |
| 773 | Sender structure is not a single table; reading type 3 not possible |
| 774 | Job execution has been discontinued on user request |
| 775 | Save project &1 |
| 776 | Save subproject &1 |
| 777 | Transport for project &1 created on &2 |
| 778 | Transport for subproject &1 created on &2 |
| 779 | Transport for migration object &1 created on &2 |
| 780 | Save migration object &1 |
| 781 | Save sender container of migration object &1 |
| 782 | Save receiver container of migration object &1 |
| 783 | Transport &1 has been created |
| 784 | Select project, subproject or migration object |
| 785 | Fixed value &1: &2 is no valid value of domain &3 |
| 786 | Fixed value &1: &2 is no valid value of table &3 and field &4 |
| 787 | Source object &1 and target object &2 are not of same type |
| 788 | Source object &1 and target object &2 belong to different applications |
| 789 | &1 is not an attribute of the object type &2 |
| 790 | For migration object &1 no sender container exists |
| 791 | For migration object &1 no receiver container exists |
| 792 | Enter the correct combination of mass transfer and migration object |
| 793 | Append / structure &1 doesn't contain any fields |
| 794 | Migration object &1 is not assigned to subproject &2 |
| 795 | Collective access plan &1 does not exist for migration object &2 |
| 796 | Collective access plan &1 does not exist for migration object &2 |
| 797 | To each receiver structure at least one sender structure must be assigned |
| 798 | Rule call of field &1-&2 has been modified |
| 799 | Please enter permissible values |
| 800 | Specified run id &1 does not exist |
| 801 | Specified run id &1 has been deleted successfully |
| 802 | Run id &1 has been created successfully |
| 803 | Specified run id &1 already exists |
| 804 | Specify valid application |
| 805 | Specify valid customer project |
| 806 | Run id &1 is locked by user &2 |
| 807 | Scope determination of run id &1 has failed |
| 808 | Scope determination of run id &1 is successful |
| 809 | Execute step 'Define Scope' prior to this step |
| 810 | CU analysis for run id &1 has been completed successfully |
| 811 | CU analysis for run id &1 has failed |
| 812 | Resetting "In-Process" flag completed successfully |
| 813 | Resetting "Define" flag completed successfully |
| 814 | Resetting "Analysis" flag completed successfully |
| 815 | Status of run id &1 is not "In-Process" |
| 816 | No delta information available for selected object &1 |
| 817 | The &1 &2 doesn't have a corresponding original object in the system |
| 818 | For table type '&1' a collective access plan is not supported |
| 819 | Reduced sender field list determined successfully for mig. object &1 |
| 820 | Specific name required for mig.obj.s with names not ending with &1 |
| 821 | Transl. object &1 already exists in the target environment of the copy |
| 822 | Collective access plan &1 does not exist for migration object &2 |
| 823 | Subproject &1 does not belong to applicationi 'R/3-R/3 Migration' |
| 824 | No foreignkey rel.s do exist yet for struct. &1 |
| 825 | Reading type 1 (access plan) not allowed for POOL- und CLUSTER tables |
| 826 | Input for search depth and segment size required |
| 827 | Search depth and segment set to zero |
| 828 | Key must be greater than 0 |
| 829 | Key must be unique |
| 830 | Collective access plan &1 already defined |
| 831 | Primary relationship type can not be Aggregation for structure &1 |
| 832 | Secondary relationship type can't be 'split' for structure &1 |
| 833 | Sender field has reference null |
| 834 | Maintain data path for the relationship of structure &1 |
| 835 | Translation object can't be saved as no parameters have been maintained |
| 836 | Fixed value &1 already exists in the target environment |
| 837 | Control parameter &1 already exists in the target environment |
| 838 | Variable &1 already exists in the target environment of the copy |
| 839 | Action not possible because of missing RFC settings |
| 840 | No migration object selected, only subproject will be copied |
| 841 | Invalid reading type has been specified |
| 842 | Batch job scheduled for the copy of migration objects, see log SLG1 |
| 843 | Version &1 created successfully for &2 &3 |
| 844 | No structures have been created in sender container |
| 845 | No versions exist for &1 &2 |
| 846 | Variant &1 is maintained in customizing; Deletion is not possible |
| 847 | A value help has been defined without a value check |
| 848 | sender field is empty |
| 849 | Document not available |
| 850 | Block &1 does not exist in current job net |
| 851 | A block cannot be it's own predecessor |
| 852 | The specified job net &1 does not exist |
| 853 | The specified job net &1 already exists |
| 854 | Job net is not active; schedule agent has not been started |
| 855 | Job net &1 started successfully |
| 856 | Error starting job net &1 |
| 857 | Task &1 started |
| 858 | No valid resource could be determined |
| 859 | Sender field is unknown |
| 860 | Input help has been called with a wrong parameter |
| 861 | Input help has been completed without result |
| 862 | Scope refreshed |
| 863 | Call to function module &1 failed |
| 864 | Error when copying rule call for rule &1 of object &2 |
| 865 | Wrong assignment to transfer rule |
| 866 | Wrong metadata source type |
| 867 | Creation of metadata extractor failed &1 |
| 868 | MD File open failure |
| 869 | MD File: No Header available |
| 870 | MD File: No send structures available |
| 871 | No sender container available |
| 872 | Field cannot be inserted into the list |
| 873 | Structure can not be inserted into the list |
| 874 | Unknown file place |
| 875 | Modeler can't be displayed while corresponding object has not been saved |
| 876 | Structures are not compatible: &1 &2 |
| 877 | Field has already been checked. Changes are not possible |
| 878 | Action not possible since not all relevant information has been provided |
| 879 | View Modeling not yet done. Rule Modeler cannot be accessed |
| 880 | User has no authorization to execute this action |
| 881 | Too many parameters (fields, values); 10 parameters are allowed at most |
| 882 | The specified object does not exist in master record of user |
| 883 | There is no profile in master record of user |
| 884 | Field names of the check do not match those of the authorization check |
| 885 | Incorrect structure for master record of user |
| 886 | Specified combination of application and project is invalid |
| 887 | Scope determination is not done for the specified customer project |
| 888 | No delta information available for the specified project |
| 889 | The specified project &1 does not exist in table DMC_ORIG_CPY_LNK |
| 890 | Customer project &1 does not exist |
| 891 | Template project &1 does not exist |
| 892 | Do you really want to extend the visibility range of this rule? |
| 893 | Scope has not been done for project &1 |
| 894 | Translation object &1 already exists and will not be created |
| 895 | Run ID status is not 'in process' |
| 896 | 'Execute Analysis' step has not yet been performed for this run id |
| 897 | The step 'Define Scope' has not yet been performed for this run id |
| 898 | Step &1 cannot be performed as other users are working on the same run id |
| 899 | This step is not possible as other users are working on the same run id |