RSAR - Datentransfer und Metadatenpflege
The following messages are stored in message class RSAR: Datentransfer und Metadatenpflege.
It is part of development package RSAR in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Data import from source system".
It is part of development package RSAR in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Data import from source system".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Data request to source system / communication *** >> 049 *** |
| 001 | Serious internal error: & & & & |
| 003 | No transfer structure for InfoSource & and source system & |
| 004 | For InfoSource &, there is no & in source system & |
| 005 | Source system & is inactive |
| 006 | Please log on as an administrator in the following screen |
| 007 | Could not run check for RFC connection &3; check destination |
| 008 | BW &1 unknown in source system &2 |
| 009 | BW &1 inactive in source system &2 |
| 010 | Source system connection &1 OK |
| 011 | Activation terminated |
| 012 | Requested tasks with &1 were successful |
| 013 | Requested tasks with &1 were not successful |
| 014 | &1 could not be activated |
| 015 | Could not replicate DataSources from &1 |
| 016 | DataSources from &1 were replicated |
| 017 | Source system &1 was activated |
| 018 | Replication of DataSources from &1 not possible |
| 019 | DataSource &1 cannot be assigned to InfoSource &2 |
| 020 | Task: Check source system &1 |
| 021 | Task: Activate source system &1 |
| 022 | Task: Replicate metadata from source system &1 |
| 023 | Mass generation: No versioning for PSA table & for InfoSource & |
| 024 | Log-on client "&1" is not the same as the BW clients "&2" |
| 025 | Only one entry permitted for source system &1 for old objects |
| 026 | Data inconsistency; Partition & not deleted |
| 027 | No entry for original source system &1 for old objects |
| 028 | Source system &1 lies in the namespace for Content release types |
| 029 | Source system &1 may not have the same name as the release |
| 030 | Source system Release &1 &2 is unknown. Maintain it in table RS3DREL. |
| 031 | Name of source type &1 must not start with S or other reserved characters |
| 032 | Name of source type &1 must start with S (but cannot be SME or SAP) |
| 033 | Source system &1 could not be checked |
| 034 | Source system is not selected |
| 035 | The factory calender views are not available in the source system |
| 050 | *** Standard messages for BAPI *** >> 099 *** |
| 051 | & & & & |
| 052 | Source system does not require any parameters |
| 053 | InfoSource is unknown |
| 054 | Invalid source system name & entered |
| 055 | Obligatory Parameter(s) Missing |
| 056 | Invalid parameter(s) entered |
| 057 | Invalid user name / invalid password |
| 058 | Error in the selection criteria |
| 059 | No entry for & in table RSADMIN available |
| 060 | ------------------------------------------------------------------------- |
| 061 | Errors occurred! |
| 062 | Error occurred when activating the contents |
| 100 | *** Processing of data from the source system *** >> 199 *** |
| 101 | Combination of source system & and InfoSource & does not exist |
| 102 | Transfer str. & does not exist in tab. RSISOLTP |
| 103 | Programs not generated for InfoSource & and source system & |
| 104 | Transformation program & does not exist! |
| 105 | No entries found for request no. & |
| 106 | Info-Idoc contains no data to be evaluated |
| 107 | Transfer program & is incorrect. Short dump started |
| 108 | Data successfully transferred to the update |
| 109 | IDoc was successfully transferred to the monitor updating |
| 110 | Invalid request number (&) found in IDoc |
| 111 | Invalid IDoc segment & found |
| 112 | No valid data records found |
| 113 | No valid IDoc header segment found |
| 114 | Unspecified error has arisen while updating |
| 115 | Error when determining the update program for InfoSource & |
| 116 | Error in a data conversion in record & |
| 117 | Error in an arithmetic operation in record & |
| 118 | Return code & when converting field & in record & |
| 119 | Error & in the update |
| 120 | IDoc & does not exist (change) |
| 121 | IDoc & is not of inbound processing type (change) |
| 122 | IDoc status was reset |
| 123 | IDoc & has status &. Resetting unnecessary |
| 124 | Error in a data conversion in user-defined routine for record & |
| 125 | Error in an arithmetic operation in user-defined routine for record & |
| 126 | Data record & of the fragmented entry is too long |
| 127 | False fragment sequence in fragmented data record & |
| 128 | Transfer of master data using TRFC is not permitted |
| 129 | Transfer of master data from ODS is not permitted |
| 130 | Error & when adding to PSA |
| 131 | It is not possible to sort the hierarchy. |
| 132 | InfoSource & does not correspond to the data request |
| 133 | -> Start update of master data hierarchy |
| 134 | <- End update of master data hierarchy |
| 135 | Routine & was successfully created |
| 136 | Termination by user-defined routine in record & |
| 137 | Error in conversion exit &1 &3 |
| 138 | Request cannot be changed (see long text) |
| 139 | Termination through start routine in the update rules |
| 140 | Empty or invalid formula & |
| 141 | Invalid unique ID (25 places) |
| 142 | Error in delete |
| 143 | Invalid unique ID (32 places) |
| 144 | Incorrect text type for formula string |
| 145 | Error in the If function: incorrect value in ARG2 or 3: '&' / '&' |
| 146 | Formula & is not available in the table RSAFORMMAP |
| 147 | No formula ID has been transferred |
| 148 | No short text available for formula & |
| 149 | Error when updating the deletion flags in RSAFORMMAP |
| 150 | Pos. 1 of the InfoSource must be diff. to one of char.: 0123456789YZ. |
| 151 | No levels can be calculated for the hierarchy. |
| 152 | No where-used list available for & in & |
| 153 | Entry object & does not exist or is not active |
| 154 | Check the connection parameters for the source system |
| 155 | No data found in the RSADMIN table |
| 156 | Wrong Data Type |
| 157 | Entry is too long |
| 158 | Error when determining the type of logical system & |
| 159 | The system type (SAP or CUS) could not be determined. |
| 160 | No F1 help available |
| 161 | Conversion exit & does not exist. |
| 162 | No entries exist in table RSOSOFIELD for InfoObject &. |
| 163 | Information is missing for InfoObjects in the hierarchy. |
| 164 | Information missing for currency translation into internal format |
| 165 | Currency amount transferred with more than & digits after decimal point |
| 166 | No data can be loaded for InfoSource & (meta data refused) |
| 167 | The password for the OLTP user must be at least 5 characters long. |
| 168 | The password for the BW-ALE user is not correct. |
| 169 | The passwords entered do not agree with one another. |
| 170 | Invalid data source: & (valid values: A, C) |
| 171 | Error when reading control file & (type &) |
| 172 | Error when reading data file & (type &) |
| 173 | User successfully created |
| 174 | It is not possible to create source system & manually - see long text |
| 175 | Source system does not exist |
| 176 | Source system has same name as BW |
| 177 | Error when creating the RFC destination & |
| 179 | Invalid source sytem type |
| 180 | Error when opening the data file & (origin &) |
| 181 | Error when reading data file & (origin &) |
| 182 | Requested file & (origin &) does not contain any data |
| 183 | Requested file & (origin &) contains obselete data |
| 184 | Record & of requested file & (origin &) is invalid |
| 185 | Invalid number of records in file & (origin &) |
| 187 | The entered saving location in row & of the control file is invalid |
| 188 | The file type entered in row & of the control file is invalid |
| 189 | The file name entered in row & of the control file is invalid |
| 190 | Invalid number entry in row & of the control file |
| 191 | InfoObject & contains invalid characters in record & in value & |
| 192 | InfoObject & does not fulfill ref. integrity in record & in value & |
| 193 | Errors occurred when reading ODS & (ref. integrity cannot be checked) |
| 194 | Formula in InfoObject &: & |
| 195 | Error occurred while processing the transfer rule |
| 196 | InfoObject & contains non-alpha compliant value & |
| 197 | Record &:Contents & from field & cannot be converted in type & ->longtext |
| 198 | Record &:Contents & from field & cannot be converted in type & ->longtext |
| 199 | & error occurred in start routine of transfer rule |
| 200 | *** Meta data maintenance *** >> 399 *** |
| 201 | Source system & already exists. |
| 202 | Source system & can no longer be used. |
| 203 | Source system & does not exist |
| 204 | Error when calculating the node level in a hierarchy |
| 205 | No hierarchies available for InfoSource & (&), source system & |
| 206 | No meta data differences exist for source system & |
| 207 | InfoSource type & is not known |
| 208 | InfoSource & (&) is not known |
| 209 | No fields exist for InfoSource & (&) |
| 210 | InfoObject &1 is not available |
| 211 | Saving of communicatioin structure & in Dictionary failed |
| 212 | Activation of communication structure & in Dictionary failed |
| 213 | Function canceled due to user entry |
| 214 | & & activated |
| 215 | Source system & is not an external system |
| 216 | InfoSource type & (&) is not allowed here |
| 219 | & & & & does not contain fields |
| 220 | Communication structure & does not contain any fields |
| 221 | DataSource & (&) not available for source system & |
| 222 | Communication structure name & is not the same as & |
| 223 | Error & while generating transfer structure on source system & |
| 224 | Transfer structure & could not be deactivated |
| 225 | Master data InfoSoure & does not deliver any data |
| 226 | Master data InfoSource & refers to an invalid InfoObject |
| 227 | No transfer rules available for InfoObject & |
| 228 | You are not allowed to create hierarchies manually for ERP systems |
| 229 | Field name & used several times |
| 230 | No source system defined for client(s) & |
| 231 | Field definitions and change indicators are not synchronous |
| 232 | Error & when generating the upload program: Row &, message: & |
| 233 | Error & when compiling the upload program: row &, message: & |
| 234 | Error & when loading external data |
| 235 | Invalid statement(s) in the control file |
| 236 | InfoSource & already exists |
| 237 | Communication structure & for InfoSource & not found |
| 238 | IDoc type for source system & is not available |
| 239 | Name of BW source system is not defined (client &) |
| 240 | IDoc segment & could not be assigned to IDoc & |
| 241 | Rec. length of control file & does not correspond to that of IDOC seg & |
| 242 | The transfer structures and template do not have fields |
| 243 | InfoSource & (&) is already connected to source system & |
| 244 | No attributes exist for InfoObject & |
| 245 | Error generating program |
| 246 | Transfer structure for InfoSource & (&), source system & not available |
| 247 | Error & when activating report & |
| 248 | Error when determining the technical name of the InfoSource |
| 249 | InfoObject for the communication structure & cannot be determined |
| 250 | No fields selected, saving not possible. |
| 251 | Saving not possible, error in the transfer rules (change). |
| 252 | Communication structure for InfoSource & not maintained |
| 253 | Communication structure & could not be deactivated |
| 254 | Standard InfoSources cannot be changed |
| 255 | You are not allowed to maintain InfoSources of ERP systems manually |
| 256 | The communication structure does not contain InfoObjects |
| 257 | InfoSource & (&) not deleted |
| 258 | InfoSource & (type &) deleted |
| 259 | InfoObject for unit or currency key will be automatically transferred |
| 260 | Source system & is not active for this BW |
| 261 | Source system & not deleted |
| 262 | Source system & deleted |
| 263 | Error in global conversion rule for InfoObject & |
| 264 | Unit field & is not available in the InfoSource |
| 265 | Assignment of InfoSource & (&) to source system & not deleted |
| 266 | Assignment of InfoSource & (&) to source system & deleted |
| 267 | InfoSource & (&) cannot be deleted |
| 268 | Assignment of InfoSource & (&) cannot be deleted |
| 269 | The selection of the InfoObjects to be removed was adjusted |
| 270 | Only those InfoObjects not being used will be deleted |
| 271 | Source system & does not exist or cannnot be used |
| 272 | No source system found for the selection crtiteria entered |
| 273 | No InfoSource found for the selection criteria entered |
| 274 | Data element for InfoObject & could not be created |
| 275 | IDoc type name & is not in the valid namespace |
| 276 | Domain for InfoObject & could not be created |
| 277 | No InfoObject was found for InfoSource & |
| 278 | Source system name cannot be changed |
| 279 | Communication structure for InfoSource & not deleted |
| 280 | Communication structure for InfoSource & was deleted |
| 281 | Transfer structure for InfoSource & (&) not deleted |
| 282 | Transfer rules for InfoSource & (&) and source system & were deleted |
| 283 | Internal database error occurred |
| 284 | InfoSource & does not deliver attributes of type & |
| 285 | InfoSource & does not deliver texts |
| 286 | Error when creating transfer structure, please check log |
| 287 | InfoObject & used several times |
| 288 | InfoObject & does not exist in the InfoSource & |
| 289 | Meta data inconsistency in source system & |
| 290 | No fields found in transfer structure & |
| 291 | Communication structure for transfer structure & not found |
| 292 | Field & of type & requires a reference field of type & |
| 293 | Transfer structure & is invalid, or contains no fields |
| 294 | InfoSource & does not deliver hierarchies |
| 295 | InfoSource & contains no fields |
| 296 | The transfer rules for field & contain syntax errors |
| 297 | Internal error & |
| 298 | No transfer rules found for InfoSource & (inconsistency) |
| 299 | The name of the InfoObject is not given |
| 300 | The field name is not given |
| 301 | The existing RFC description does not corr. to that of the source system |
| 302 | Changes saved. & |
| 303 | Invalid data type: & |
| 304 | The field lengths entered must be greater than 0. |
| 305 | An RFC destination with the name & (type TCP/IP) already exists |
| 306 | Reference InfoObject & is not available |
| 307 | Reference InfoObject & automatically inserted |
| 308 | Transfer rules & do not exist |
| 309 | InfoSource & does not exist |
| 310 | No InfoSources found for the selection conditions |
| 311 | Invalid entry, hierarchy & does not exist |
| 312 | No InfoSources found for transfer structure & |
| 313 | No hierarchy found for the selection criteria entered |
| 314 | No texts have been found for the hierarchy ID & |
| 315 | No InfoObjects were found for the selection criteria entered |
| 316 | InfoObject &1 does not exist in version &2 |
| 317 | Invalid data type (&) for source systems of type &. |
| 318 | & &: Data type changed to CHAR. |
| 319 | No values are available for InfoObject & |
| 320 | Attribute flag cannot be changed as long as the attribute title is active |
| 321 | Text flag cannot be changed, as long as the text title is active |
| 322 | Hierarchy flag cannot be changed, as long as hierarchy title is active |
| 323 | Error when generating the delta logic in source system & |
| 324 | No text exists for log. system & in table TBDLST |
| 325 | Transfer structure prefix for source system & is not defined |
| 326 | InfoObject & ( & ) is not active |
| 327 | InfoObject & ( & ) is not active, total of & inactive InfoObjects |
| 328 | Meta data is missing for InfoObject & in the source system |
| 329 | Meta data is missing for InfoObject & in the BW System |
| 330 | InfoSource cannot be deleted. |
| 331 | InfoObject & has a fixed unit/currency &; no translation possible |
| 332 | Entering & is not allowed |
| 333 | F1 help for master data InfoSources |
| 334 | InfoObject & is not a non-cumulative value |
| 335 | InfoObject & is a non-cumulative value. |
| 336 | Activation not possible: & contains invalid field & |
| 337 | Error in meta data. Save cancelled. |
| 338 | A hierarchy & already exists for & &. |
| 339 | Interval entries only permitted for 0HIER_NODE |
| 340 | DataSource & is already linked to InfoSource & |
| 341 | Source system & recognized as BW system |
| 342 | Source system type in system & could not be read |
| 343 | Communication structures only possible for InfoSource type D, M and T |
| 344 | Error in creating the transfer structure/rules for texts |
| 345 | There are no InfoObjects that are allowed to be deleted |
| 346 | None of the selected InfoObjects can be deleted |
| 347 | No destination exists to source system & |
| 348 | No field mapping to the DataSource was found |
| 349 | An InfoSource & already exists for & |
| 350 | Only active InfoObjects are copied. |
| 351 | Compounded InfoObjects are automatically transferred. |
| 352 | Because of compounding, not all InfoObjects could be removed. |
| 353 | InfoObject & is compounded to &, but & is not in the communication str. |
| 354 | Compunded InfoObjects are transferred from the catalog. |
| 355 | Unit InfoObjects are transferred from the catalog. |
| 356 | Please maintain the assignment of DataSource & to IBU and NDP |
| 357 | No hierarchy for & (&) has been defined yet. |
| 358 | Error in determining the communication release |
| 359 | Source system & is being imported with the new name & |
| 360 | The comm. structure is currently blocked by user & (enter=display) |
| 361 | The name & is already in use for an InfoObject. Please enter again. |
| 362 | Source system cannot use any of the proposed connection names |
| 363 | No InfoObjects found for & & |
| 364 | Datefrom must be less than dateto. |
| 365 | & may not be smaller than & |
| 366 | No changes! Save not carried out |
| 367 | ConvExits for assigned InfoObjects inconsistent: & (&) - &(&) |
| 368 | ConvExits inconsistent for field and InfoObject: &(&) - &(&) |
| 369 | InfoObject & is already used as transfer rule for InfoObject & |
| 370 | No type & DataSource can be assigned to InfoSource & |
| 371 | IDoc type &1 is not the same as the source system IDoc type &2 |
| 372 | Source system not in Release 2.0 |
| 373 | Incorrect IDoc type &1 in the ALE definition of the source system |
| 374 | The following errors occurred in the source system: |
| 375 | Result of the destination check: &1 &2 |
| 376 | & & not found. Go to selection screen |
| 377 | InfoObject & references InfoObject & |
| 378 | InfoObject & (&) not supported in InfoSources of components & |
| 379 | Warnings occurred (see log) |
| 380 | No possible input values were found. |
| 381 | Only one possible input value was found. |
| 382 | DataSource & is not linked to InfoSource & |
| 383 | No available DataSources for source system & exist |
| 384 | DataSource & saved. |
| 385 | Check the use of transfer structure fields |
| 386 | Select at least one field in the transfer structure |
| 387 | Assignment of InfoObjects to DataSource & fields incomplete |
| 388 | Several source systems possible, source system & used |
| 389 | Not all key fields of characteristic &1 defined by the DataSource |
| 390 | Export DataSource not possible for hierarchies |
| 391 | Export DataSource not possible for generated ODS-PSAs |
| 392 | Formulas have been saved |
| 393 | Formulas have been activated |
| 394 | Select at least one InfoObject in the selection column |
| 395 | The compounded InfoObject &2 is missing for InfoObject &1 |
| 396 | Cannot generate PSAs with more than 1000 characters |
| 397 | UD Connect connection data is not correct |
| 398 | Destination &1 points to the wrong BW system |
| 399 | Source system &1 is a dummy. Object not executable |
| 400 | ***** Transport connection ***** >> 499 ***** |
| 401 | No content-compatible objects selected |
| 402 | & objects were written to BI Content release & |
| 403 | Object & cannot be changed. |
| 404 | No objects available for BI Content release & |
| 405 | Enter a BI Content release |
| 406 | & objects transferred from BI Content release & |
| 407 | The variant (&) entered does not exist |
| 408 | No mapping defined for source system & |
| 409 | Source system & does not exist |
| 410 | Import of object class & not allowed with upgrade |
| 411 | Non-referenced communication structure & deleted |
| 412 | Non-referenced InfoSource & (&), source system & deleted |
| 413 | Non-referenced transfer structure & deleted |
| 414 | Update rules for InfoSource &, InfoCube & deleted |
| 415 | InfoSource & (&) assigned to application component & |
| 416 | Application component & assigned to application component & |
| 417 | Link to next node in application component & deleted |
| 418 | Link to subordinate node in application component & deleted |
| 419 | Communication structure & deleted, rc = & |
| 420 | Communication structure & successfully activated |
| 421 | Transfer structure & deleted, rc = & |
| 422 | Transfer structure & successfully activated |
| 423 | DataSource &, source system & imported for source system & |
| 424 | No BI Content available |
| 425 | It does not invlove an SAP system. |
| 426 | Import of the communication structure & failed. |
| 427 | Communication structure & already exists. |
| 428 | Communication structure & already exists. |
| 429 | Transfer structure & already exists. |
| 430 | InfoSource & already exists. No import! |
| 431 | InfoSource & already exists in parts. No import! |
| 432 | InfoSource & already exists except for the OLTP link. No import! |
| 433 | No communication structure for Infosource & in the content |
| 434 | InfoSource & imported |
| 435 | InfoObject & does not actively exist. No import of InfoSource & possible |
| 436 | Reference to transfer structure & not available. No activation possible. |
| 437 | Non-referencing mapping for data source & source system & deleted |
| 438 | Source system & does not exist |
| 439 | InfoSource & not supported by the source system. No import |
| 440 | Transfer structure & does not exist |
| 441 | InfoSource &1 is assigned in Content Version to application &2 |
| 442 | InfoSource &1 has the name &2 in Content Version |
| 443 | In Content Version, communication structure &1 is missing field &2 |
| 444 | Field &2 is missing in Content Version of DataSource &1 |
| 445 | Field & from Content Version added |
| 446 | DataSource &1 ist assigned to InfoSource &2 in Content Version |
| 447 | In Content Version of the transfer structure &1, field &2 is missing |
| 448 | DataSource &1 for source system &2 is not available |
| 449 | Trans. struct. &1 for source system &2 has loading method &3 in Content |
| 450 | InfoObject &1 of the transfer structure is calculated differently in CV |
| 451 | Field &2 is missing from the content version of transfer structure &V1 |
| 452 | Transfer more than one transfer structure - relationship not clear |
| 453 | &1 &2 assigned to InfoArea &3 |
| 454 | InfoPackage &1 has group &2 assigned to it, which does not exist; delete |
| 455 | Rule & from content version was added |
| 456 | Assignment of DataSource &1 to InfoSource &2 deleted |
| 457 | Transfer structure &1 deleted because not delivered |
| 458 | Field &1 not delivered by source system -> Deleted from rule |
| 459 | InfoObj. &1 not delivered by transfer rules -> Deleted from tran. struct. |
| 460 | Source system for transfer structure &1 not found. Deletion not possible |
| 461 | DataSource for transfer structure &1 not found. Deletion not possible. |
| 462 | InfoObj &1 not delivered by comm. structure -> Deleted from tran. struct. |
| 463 | Merging fields |
| 464 | Filtering fields |
| 465 | Transfer of dependent routines |
| 466 | Error with Content merge: InfoObject & already in use |
| 467 | DataSource &1 for source system &2 was deleted |
| 468 | Cannot maintain object for Content version |
| 469 | DataSource &1 already exists |
| 470 | Routine &1 was not found in the new rules -> no transfer |
| 471 | Info object &1 belongs to unwanted component -> removed from rule |
| 473 | Text in formula &1/&2 language &3 differs in version &4 |
| 474 | Formula for &1/&2 differs in version &3 |
| 475 | Import of formula for &1 failed |
| 476 | Merging of the formula texts |
| 477 | Text in language &1 added from content version |
| 479 | The import of formula &1 failed |
| 480 | Formula &1 has been deleted |
| 481 | An error occurred when deleting formula &1 version &2 |
| 482 | An error occurred when activating formula &1 |
| 483 | Formula &1 has been activated successfully |
| 484 | Segmented update rules can not be delivered |
| 485 | Repeated import-subsequent processing for object &1 - object skipped |
| 486 | Could not create formula &1 in SFOBUEV000/001 |
| 487 | Syntax error in transfer routine for InfoObject &1 |
| 488 | Syntax error in start routine of transfer rules |
| 489 | InfoSources cannot begin with the number 8 |
| 490 | DataSource & source system & could not be read |
| 491 | Transfer structure & could not be saved |
| 492 | Field name & is too long (length > 16 characters) |
| 493 | Error in INSERT in table: & ID: & OBJVERS: & |
| 494 | Formula for FORMEX: & OBJVERS: & does not exist |
| 500 | ***** Technical error messages ***** >> 599 ***** |
| 501 | No connection to system & possible |
| 502 | Error in source system & |
| 503 | An RFC call-up triggered the exception |
| 504 | This function has not yet been implemented |
| 505 | Function terminated by user |
| 506 | No transport order available |
| 507 | Force flag is set; error being ignored |
| 508 | Transfer method 'TRFC with PSA' is not supported by the source system |
| 509 | File not found |
| 510 | Parameter not filled |
| 511 | Database system cannot be reached |
| 512 | Invalid GUID |
| 513 | Record & was intentionally skipped in formula & |
| 514 | A termination was intentionally triggered in formula & in record & |
| 515 | The extract structure has no component & |
| 516 | Error when determining the transfer structure fields |
| 517 | Non-usable transfer structure fields were removed |
| 518 | Internal error occured; Repeat activation |
| 519 | Formula &: & entries written in table & in version & |
| 520 | Formula &: & entries deleted in table & in version & |
| 521 | Formula & (object version &) written |
| 522 | Formula & (object version &) deleted |
| 523 | Formula & (object version &) could not be read |
| 525 | Formula & could not be loaded |
| 526 | Error when reading code page information |
| 527 | Error with structure alignment |
| 528 | Transfer rules &1 &2 are inconsistent. Activate them again |
| 529 | The InfoObject 0RECORDMODE is not contained in InfoSource &1 |
| 530 | Error during currency translation (record: &1; field: &2; ref.: &3) |
| 531 | No currency field assigned to field &1 of the DataSource |
| 532 | Content version not modified; activate InfoSource |
| 533 | Errors during structure alignment of record "&1" with language "&2" |
| 534 | Invalid language "&2" for structure alignment of record "&1" |
| 535 | Error in a formula function (routine &), record & |
| 536 | No active transfer rule for DS & and source system &; create first... |
| 537 | Different structures in dummy and original. Cannot execute |
| 538 | Original system &1 does not exist as an SAP / SAP BW system |
| 539 | Dummy source systems should not be used in a productive system |
| 540 | No ODP Context Information for source system &1 available in BW |
| 541 | Context &1 stored in BW, is not available in the source system &2 |
| 550 | Only 3.x InfoSources can be used as template |
| 555 | RSOLOGSYSMAP: Previously &1 -> &2, now &3 -> &4 |
| 561 | DB owner/schema &1 is not valid |
| 600 | ***** Messages for logging ***** >> 999 ***** |
| 601 | Source system & created |
| 602 | IDoc type & created |
| 603 | Partner agreement for source system & created |
| 604 | Create port definition for port & |
| 605 | Source system & creation successfully finished |
| 606 | Manual maintenance of InfoSource & (type &) of source system & |
| 607 | Manual maintenance of InfoSource & (&) of source system & finished |
| 608 | Manual recreation of generic InfoSource & (&) |
| 609 | InfoSource & was successfully created |
| 610 | Manual deleting of the generic InfoSource & (&) |
| 611 | Generic InfoSource & (&) successfully deleted |
| 612 | Deleting of generic InfoSoucre & (&) went wrong |
| 613 | Deleting of the assignment of InfoSoucre (&) to & |
| 614 | Assignment of InfoSource & (&) to & successfully deleted |
| 615 | Deleting of the assignment of InfoSource & (&) to & failed |
| 616 | Manual change of InfoSource & (&) |
| 617 | Text for InfoSource & changed |
| 618 | Manual deleting of source system & |
| 619 | Deletion of source system &: |
| 620 | Deleting source system & failed -> Check log ! |
| 621 | Change of the attributes of source system & |
| 622 | Attributes of the source system & changed |
| 623 | New short text: & |
| 624 | New basic IDOC type: & |
| 625 | Application name: & |
| 626 | Description: & |
| 627 | Finished generating D version for data sources for source system & |
| 628 | InfoSource & (&) cannot be manually deleted |
| 629 | Deletion of fields for InfoSources & (&): & |
| 630 | Deletion of the texts for InfoSource & (&): & |
| 631 | Deletion of InfoSource & (&): & |
| 632 | Deletion of the attributes for InfoSource & (&): & |
| 633 | Deletion of InfoSource & (&) for source system &: & |
| 634 | Deletion of fields for InfoSource & (&) to &: & |
| 635 | Attributes for InfoSource & (type &) of source system & deleted |
| 636 | Port definition for source system & deleted |
| 637 | Partner agreement for source system & deleted |
| 638 | Basic IDOC type & for source system & deleted |
| 639 | RFC name for source system & deleted |
| 640 | RFC name for source system & (type &) created |
| 641 | RFC Parameters: Server=&, system no=&, client=&, user=& |
| 642 | Connection of InfoSource & to source system & started |
| 643 | Call-up of manual meta data maintenance |
| 644 | Meta data for InfoSources loaded using RFC |
| 645 | InfoSource & connected with source system & |
| 646 | Message type & for source system & created |
| 647 | Message type & for source system & deleted |
| 648 | Partner agreement for source system & created |
| 649 | No RFC name for source system & (type &) created |
| 650 | Meta data of source system & read |
| 651 | Application hierarchy updated |
| 652 | Source system & meta data updated |
| 653 | Meta data for InfoSource & (&) of source system & read |
| 654 | Meta data for InfoSource & (&) of source system & updated |
| 655 | InfoSource & (&) has changed |
| 656 | InfoSource & (&) is up-to-date |
| 657 | New InfoSource & (type &) found |
| 658 | No changes to InfoSources (&) found |
| 659 | Changes to InfoSource (&) information saved |
| 660 | Obselete field definitions deleted |
| 661 | Information for new InfoSource & (&) saved |
| 662 | New attribute & for InfoSource & (&) inserted |
| 663 | New selection field & for InfoSource & (&) inserted |
| 664 | New compound field & for InfoSource & (&) inserted |
| 665 | Creating logical BW in source system & |
| 666 | Global InfoSource & (&) is new |
| 667 | Application assignment of global InfoSource & (&) changed |
| 668 | Source system & not of type file or external system |
| 669 | Port description contains errors: Incorrect destination &1 |
| 670 | Source system cannot be deleted in Content system |
| 671 | Source system release &1 is not the same as local information &2 |
| 672 | No metadata upload since upgrade |
| 673 | Destination &1 has incorrect Unicode setting; adjust it to destination |
| 674 | InfoObject catalog was updated |
| 675 | Changes to InfoSource (&) being carried out |
| 676 | & & |
| 677 | Domain & cannot be appended (type & length &) |
| 678 | RFC name for source system & (type &) changed |
| 679 | RFC name for source system & (type &) not changed |
| 680 | Start of program generation for InfoSource & of source system & |
| 681 | InfoObject & found (number of key fields &) |
| 682 | Syntax error in template &, row & |
| 683 | Syntax error in generated program, row & |
| 684 | Message: & |
| 685 | Program & with form routine & successfully created and generated |
| 686 | Generated source code: |
| 687 | &: & |
| 688 | & & of the transfer structure & removed from control table |
| 689 | No & available for the transfer structure & in the control table |
| 690 | & determined as name of the & |
| 691 | Domain of type & and length & cannot be read |
| 692 | Creation of domain & in Dictionary failed |
| 693 | Activation of domain & in the Dictionary failed |
| 694 | Saving of structure & in Dictionary failed |
| 695 | Activation of structure & in the Dictionary failed |
| 696 | InfoObject & does not exist, will be created |
| 697 | Text table & for InfoObject & found |
| 698 | Text table & for InfoObject & not found |
| 699 | Text table & for InfoObject & could not be read |
| 700 | Field comparison for InfoSource & (&) started (source system=&) |
| 701 | New InfoObject & inserted |
| 702 | Position of field & was changed from & to & |
| 703 | Data type of field & was changed from & to & |
| 704 | Length of field & was changed from & to & |
| 705 | Internal data type of field & was changed from & to & |
| 706 | Name of field & was changed to & |
| 707 | Unused InfoObject & was removed from the InfoSource |
| 708 | Attribute comparison for InfoSource & (&) started (source system=&) |
| 709 | Attribute comparison for InfoSource & (&) finished |
| 710 | No changes found on the field level |
| 711 | Error when determining a number from object & and number & |
| 712 | Error when determining the name for object & |
| 713 | Unknown error from the Transport Organizer |
| 714 | Structure & could not be deleted in the Dictionary! |
| 715 | Force flag active -> only show-stoppers are errors, the rest is ignored |
| 716 | & & deleted in table & -> key & |
| 717 | Entry & & not deleted in table & -> Field(s) & |
| 718 | Transfer method & does not exist |
| 719 | Communication structure & for InfoSource & (&) deactivated |
| 720 | Transfer structure & does not exist |
| 721 | InfoObjects for InfoSource & were updated |
| 722 | No rows selected in table & |
| 723 | Hierarchy table & for InfoObject & found |
| 724 | Hierarchy table & for InfoObject & not found |
| 725 | Hierarchy table & for InfoObject & could not be read |
| 726 | Only 1 row can be selected with this function in & |
| 727 | Function & is not defined here |
| 728 | Fixed value contains the forbidden character & |
| 729 | Only one transfer rule permitted per InfoObject, InfoObject & |
| 730 | The mandatory field indicator of field & changed to <&> |
| 731 | The data element of field & was changed from & to & |
| 732 | Reference field of field & changed from & to & |
| 733 | The internal length of field & changed from & to & |
| 734 | The conversion exit of field & changed from & to & |
| 735 | The decimal places of field & changed from & to & |
| 736 | Changed field & is used in transfer structure & |
| 737 | Deleted field & is used in transfer structure & |
| 738 | Transfer structure & was deactivated |
| 739 | Highlights for used fields set again |
| 740 | Necessary units/currency fields were highlighted |
| 741 | InfoObject & of communication structure still being used |
| 742 | No object for field & in position & (not transferred !) |
| 743 | Change to source system not possible |
| 744 | Error & when deleting transfer structure & in source system & |
| 745 | IDoc segment & could not be deleted from IDoc & |
| 746 | Only the following characters & allowed as fixed value for data type & |
| 747 | Fixed value is not possible for the data type & (entry undone) |
| 748 | No place behind decimal point intended for InfoObject & (please correct) |
| 749 | Too many places behind decimal point. Allowed & actual & (please correct) |
| 750 | Fixed value is too long. Allowed & actual length & (correct) |
| 751 | Jobs are still scheduled, deletion of transfer rules not possible |
| 752 | Manual deletion of the comunication structure for InfoSource & (&) |
| 753 | Communication structure for InfoSource & (&) successfully deleted |
| 754 | Deletion of communication structure for InfoSource & (&) failed |
| 755 | Communication structure & was deactivated |
| 756 | Transfer structure & was deactivated |
| 757 | Reorganization of InfoSource & (&) started |
| 758 | InfoObject & still being used in the tree in the data import |
| 759 | Transfer structure & could not be deleted -> Check log |
| 760 | Selection field comparison for InfoSource & (&) started (source system=&) |
| 761 | No changes found in the selection fields |
| 762 | Selection fields for InfoSource & (&) changed (source system=&) |
| 763 | No attributes available for InfoObject & |
| 764 | InfoObject & not in &. Cannot be used in &. |
| 765 | InfoObject & is deleted for good from & and &. |
| 766 | InfoObject & may not be used in a DataSource/transfer structure |
| 767 | Mapping for transfer structure & does not exist |
| 768 | Object &1 object version &2 not found in table &3 |
| 769 | Internal error &1 |
| 770 | Mapping for InfoSource & does not exist |
| 771 | Objects can only be displayed (change protected) |
| 775 | Error while writing data to table & |
| 780 | Error in the prefix determination. Start value & is unknown |
| 781 | Name range for prefix for source system / transfer structure exhausted |
| 782 | ODS Versioning not active. Saving not possible! |
| 790 | Code page is unknown |
| 800 | Load data for InfoSource & (&) |
| 801 | Control file: &, type: &. place: & |
| 802 | File: &, type: &, place: & |
| 803 | Field separator: &, voiding for special character: & |
| 804 | Record length: &, number of records: & |
| 805 | Time of last selection: & - & |
| 806 | Request number: &, packet size: & |
| 807 | Basic IDoc type: &, segment type: & |
| 808 | Data read without control file |
| 809 | Generated upload program started |
| 810 | Data loading successfully concluded |
| 811 | Error whilst reading entry file |
| 812 | Incorrect record layout or invalid number of records in entry file |
| 813 | Error when writing an IDoc |
| 814 | Template & does not exist |
| 815 | Decimal separator: &, 1000 separator: & |
| 816 | Incorrect parameter transfer to FM rsar_is_ls_get_single |
| 817 | You cannot rename the system; SAP or BW source systems still exist |
| 818 | The logical system name for this system was changed from & to &. |
| 819 | Logical system name for this BW is not allowed |
| 820 | DataSource name for 3rd-party system cannot be displayed |
| 821 | DataSource name for 3rd-party system is too long |
| 822 | The type of 3rd-party system &1 is not maintained |
| 823 | Release for 3rd-party system &1 is not maintained |
| 824 | Error occurred during activation of dependent table & |
| 825 | ALE partner &1 has several different ports |
| 826 | ALE partner &1 does not have any output parameters |
| 827 | ALE port &1 does not exist |
| 828 | ALE partner &1 does not exist |
| 840 | &1 routine copied to &2 |
| 841 | Cannot copy &1 routine |
| 842 | Error while reading a routine in &1 version |
| 843 | Error while writing a routine in &1 version |
| 844 | &1 entries (of &2 entries) refreshed in table &3 |
| 845 | It is not necessary to copy dependent objects for transfer structure &1 |
| 850 | Transaction data InfoSource & imported without source system reference |
| 851 | Master data InfoSource & imported without source system reference |
| 888 | Error while processing data for table &1 and action &2 |
| 889 | Only reconstruction supported for factory calendar |
| 890 | Error: No connection to source system & |
| 899 | Function available from version 1.2 GA |
| 980 | ODS was activated, see note 121560! |
| 999 | Function is not available until Release 1.2 GA |