R8 - Nachrichten aus der Metadaten-Generierung
The following messages are stored in message class R8: Nachrichten aus der Metadaten-Generierung.
It is part of development package RSU0 in software component BC-BW. This development package consists of objects that can be grouped under "BW Service API: Data Transfer".
It is part of development package RSU0 in software component BC-BW. This development package consists of objects that can be grouped under "BW Service API: Data Transfer".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Messages from metadata generation *** |
| 001 | InfoObject &1 for &2 could not be created |
| 002 | InfoObject & was created |
| 003 | InfoObject &1 with type KYF requires a valid unit field |
| 004 | Assigned unit field &1 does not have a valid InfoObject |
| 005 | Assigned unit field &1 must have InfoObject type UNI |
| 006 | Not saved! InfoObject & can only be used once |
| 007 | not saved. & is not a valid info object. Create it first. |
| 008 | Assignment was saved |
| 009 | InfoObject &1 already exists |
| 010 | InfoObject & of type key figure does not exist yet |
| 011 | The assignment is not yet free of errors; check the log |
| 012 | Errors occurred; check the log |
| 013 | InfoObject &1 could not be created |
| 014 | Info object &1 cannot be created with an invalid type |
| 015 | InfoObject &1 could not be created; parameters are missing |
| 016 | Terminate at once! Data element is missing for the InfoSource field &1 |
| 017 | The editing was canceled by the user |
| 018 | Errors occurred; check the log |
| 019 | Data element &1 appears more than once in the field list |
| 020 | InfoObject &1 was not created; the data element already exists |
| 021 | InfoSource &1 not saved; there is no data for it in the buffer |
| 022 | Invalid InfoObject &2 was assigned to InfoSource field &1 |
| 023 | Compounded InfoObject &2 is missing for InfoObject &1 |
| 024 | InfoSource &1 not yet completely maintained |
| 025 | InfoObject &1 does not have the suitable type for this assignment |
| 026 | InfoObject &1 does not have the same INTLEN as the InfoSource field |
| 027 | InfoObject &1 was not created; mame must begin with letters |
| 028 | InfoObject &1 was created; but data element exists already |
| 029 | No InfoObject has been assigned to field &1 yet |
| 030 | InfoObject &1 was not created; (name length only max. 10 chars) |
| 031 | InfoObject &1 was not created; name length max.10+ 1 leading digit |
| 032 | The unit field assigend to InfoObject &1 must have InfoObject &2 |
| 033 | Data element &: Length is > 32 ( or > 60 with attributes ). |
| 034 | InfoObject &1 was not created; (name length min. 3 chars) |
| 035 | Select at least one row |
| 036 | InfoSource &1 does not exist. |
| 037 | InfoObject &1 does not exist. |
| 038 | Repeat this activity again later. |
| 039 | You cannot create InfoObject type &3 for data type &1 in field &2 |
| 040 | No errors found. |
| 041 | The specified metadata is incomplete |
| 042 | Metadata generation: System is not connected to a BW system |
| 043 | No DataSources exist for this selection |
| 044 | Extraction structure &1 could not be generated |
| 045 | Structure &1 field &2 is invalid |
| 046 | No unique short name for DataSource &1 |
| 047 | Profile parameter '&1' could not be read: Error code is &2 |
| 048 | ************************************************************************* |
| 049 | * Current Values for Selected Profile Parameters * |
| 050 | * &1 &2 |
| 052 | Segmented DataSources (type 'SEGM') are not generally released |
| 053 | No valid application component hierarchy exists |
| 054 | You can only transfer hierarchies from BI Content in dialog mode |
| 055 | Metadata for DataSource &1 is not complete or contains errors |
| 060 | Previous maintenance interface can be accessed using transaction RSA2OLD |
| 070 | Error in authorization check (S_RO_OSOA) |
| 071 | You do not have authorization to display DataSource &1, component &2 |
| 072 | You do not have authorization to maintain DataSource &1, component &2 |
| 073 | You do not have authorization to extract from DataSource &1, component &2 |
| 100 | * Messages from the meta data consistency check |
| 101 | Application component & is not contained in table DF14L |
| 102 | Application component &: Entry in table ROAPPL not complete |
| 103 | Application component &: Missing description in language & |
| 104 | InfoSource &: Error in entry in table ROIS |
| 105 | InfoSource &: Missing description in language & |
| 106 | InfoObject &: Missing entry in relevant Basis table |
| 107 | InfoObject &: Incomplete entry in relevant Basis table |
| 108 | InfoObject & is not used |
| 109 | InfoSource &: Obsolete entries in table ROISIOBJ |
| 110 | InfoObject &: Missing entry in table RODIOBJCMP |
| 111 | Key figure &: Entry in RODKYF without header entry in RODIOBJ |
| 112 | Characteristic &: Entry in RODCHA without header entry in RODIOBJ |
| 113 | Basic characteristic &: Entry in RODCHABAS without header entry in RODCHA |
| 114 | Basic characteristic &: Entry in RODIOBJCMP w/o header entry in RODCHABAS |
| 115 | Unit &: Entry in RODUNI w/o header entry in RODIOBJ |
| 116 | InfoSource &: Missing entry in table ROIS |
| 117 | InfoSource &: Missing entry in table ROISIOBJ |
| 118 | Error in input (ROIS structure: &) for field list |
| 119 | Assigned InfoObject & is not created in table RODIOBJ |
| 120 | Time characteristic &: Entry in RODTIM w/o header entry in RODIOBJ |
| 121 | InfoSource &: Contains incorrect assignment of a unit field |
| 122 | InfoObject &: Entries were deleted |
| 123 | InfoObject &: Assigned unit does not exist |
| 124 | InfoObject &: A unit was assigned with TYPE 'NUM' |
| 125 | InfoObject &: Is of length > 32 |
| 126 | Basic characteristic &: the master data table does not exist |
| 127 | Basic characteristic &: the text table does not exist |
| 128 | InfoSource &: No update mode supported |
| 129 | InfoSource &: Delta update and delta INIT permitted individually |
| 130 | InfoSource &1: (Structure, View, API...) &2 not correct |
| 131 | InfoSource &1: Selection not allowed for any field |
| 132 | InfoSource &1: Selfag missing for compounded InfoObjects from &2 |
| 133 | InfoSource &1: No longer exists, but still has texts in ROIST |
| 134 | InfoSource &1: Not all compounded InfoObjects are available |
| 135 | InfoObject &1 cannot be created |
| 136 | Domain &1 is not in the extract structure |
| 137 | Transformation InfoSource &1 in DataSource &1 |
| 138 | Transform attributes for basic characteristic &1 in DataSource &2 |
| 139 | Transforming hier.class &3 for basic characteristic &1 in DataSource &2 |
| 140 | Writing DataSource &1 transfer structure to system &2 by &3 at ... |
| 141 | Settings in RSADMIN have been saved |
| 142 | Connection to BW source system &1 from BW receiver system &2 deactivated |
| 143 | Connection between source system &1 and BW &2 deactivated |
| 144 | Creating flat application component hierarchy for DataSources |
| 145 | LIS DataSource Event Update for DataSource &1 |
| 146 | Update 2.0A metadata tables from 1.2B metadata ... |
| 147 | Units field &3 for field &2 of DataSource &1 is hidden |
| 148 | Name '&1' is invalid for a DataSource |
| 149 | The application component hierarchy was applied from the content |
| 150 | Cannot maintain segments for DataSource of type &1 |
| 151 | Invalid transfer method '&1&; '2' only permitted for segmented DataSource |
| 152 | Invalid extract method '&1&; 'FS' only permitted for segmented DataSource |
| 153 | No primary segment defined |
| 154 | Component &1 does not exist in extract structure &2 |
| 155 | Primary segment &1; invalid internal data type '&2' (use type 'u') |
| 156 | Secondary segment &1; invalid internal data type '&2' (use type 'h') |
| 157 | No segments defined |
| 158 | Segment &1 exists more than once |
| 159 | Invalid segment ID |
| 160 | No field name defined for object ID |
| 161 | Different type definition in segment &1; DataSource &2 - DDIC &3 |
| 162 | Segment &1; field name of object ID &2 exists in extract structure |
| 163 | Segment &1; field &2 does not exist in DDIC structure &3 |
| 164 | Only generic interfaces are allowed for extraction method &1 |
| 165 | Direct access must be supported for DataSources for data reconciliation |
| 166 | Segment &1, field &2: unit field &3 does not exist in this segment |
| 167 | The content version was not maintained -> SAP Note 817476 |
| 168 | Indicator for direct access not defined |
| 169 | XPRA : Deactivating connection to the BW system ... |
| 170 | XPRA: Already executed for &1 - no action necessary |
| 171 | The delta methods in the content are irreversibly overridden |
| 172 | Cannot create extract structure &1 |
| 174 | These two parameters are mutually exclusive |
| 175 | Parameters saved |
| 177 | Field name &1, component &2: Position &3 - &4 |
| 178 | Field name &1, component &2: Data element &3 - &4 |
| 179 | Difference in the field list. Field &4 column &1 value &2 - &3 |
| 180 | Transforming texts for the basic characteristic &1 in DataSource &2 |
| 181 | Difference in field &1, value &2 - &3 |
| 182 | Difference in field &1, value: &2 - &3 |
| 183 | CO-PA DataSource: Event Update for DataSource &1 |
| 184 | Generic DataSource: Event Update for DataSource &1 |
| 185 | Delta process &2 for DataSource &1 requires a cancelation field |
| 186 | No differences found between the versions |
| 187 | &1 &2 missing in version &3 |
| 188 | Difference &1 &2, &3: &4 |
| 189 | Cancelation field &1 does not exist in the extract structure of DS &2 |
| 190 | Name of field &1 is longer than 16 characters |
| 191 | Invalid field name &1 |
| 192 | Hierarchy name &1 is invalid |
| 200 | *** Service programs for removing inconsistencies *** |
| 201 | No valid entry found according to the selection criteria |
| 202 | No entries in table RSBASIDOC - Inconsistency |
| 203 | The connection between source system & and SAP BW System & is not known |
| 204 | Compare DataSource &1:&2 - &3 |
| 206 | Field &1 does not exist in DataSource &2 version &3 |
| 207 | Text for DataSource &1 in version &2 is not maintained in language &3 |
| 208 | Hier. component &4 for field &3 of DataSource &1 in version &2 missing |
| 209 | Field &1 is missing in DataSource &2 in version &3 &4 |
| 219 | Check for DataSource &1 |
| 234 | No DataSources assigned to application component &1 yet |
| 235 | No DataSources assigned to application component &2 in version &1 |
| 237 | Field &2 for DataSource &1 does not exist |
| 242 | Editing partner possible as of Basis release 4.0 |
| 243 | Application hierarchy exists already -> Creation not necessary |
| 244 | Application component hierarchy &1 already exists |
| 245 | Application component hierarchy &1 does not exist in A version |
| 246 | The application component hierarchy &1 does not exist |
| 247 | Invalid selection options for field &1 |
| 248 | Obsolete selection options for field &1 with chosen selection '&2' |
| 251 | DataSource &1 has an inconsistent version.info &3 in language &2 |
| 252 | DataSource &1 has an inconsistent key info. &3 in the ALE delta |
| 253 | DataSource &1 has an inconsistent version.info &3 in language &2 |
| 254 | DataSource &1 has an inconsistent key info. &3 in language &2 |
| 255 | DataSource &1 has an inconsistent vers.info &3 for field &2 |
| 256 | DataSource &1 has an inconsistent key info. &3 for field &2 |
| 257 | DataSource &1 has an invalid object version &2 |
| 258 | The F4 type &3 of the field &1 of the DataSource &2 is not permitted |
| 259 | You specified an invalid F4 extractor &3 in field &2 of DataSource &1 |
| 260 | The matchcode &3 for field &2 of DataSource &1 is not active |
| 261 | The DataSource &1 in field &2 is inconsistent -> no input help |
| 262 | ALE and the generic delta cannot be activated at the same time |
| 263 | Only application components can be created |
| 264 | The application component &1 still has subcomponents |
| 265 | Parent node &1 does not exist |
| 266 | There is no application component &1 |
| 267 | The application component & cannot be executed |
| 268 | No nodes can hang from the root |
| 269 | There is no DataSource with the extract structure &1 |
| 270 | Deletion of DataSource: &1 |
| 271 | Function module & does not exist or has syntax errors |
| 272 | The system could not find any inconsistencies |
| 273 | The DataSource was generated successfully |
| 274 | Function module for calculating maximum is missing |
| 275 | The DataSource was not generated because the user terminated the process |
| 276 | The F4 DataSource &3 of field &2 of the DataSource &1 is not available |
| 277 | The F4 DS &3 of the field &2 of the DS &1 is not a text source |
| 278 | Delta method does not support extraction from different clients |
| 279 | Field & is delta-relevant, but does not exist in the field list |
| 280 | Cancelation indicator for &1 changed from the delivered version |
| 281 | Warnings have occurred (see log) |
| 282 | Additional information exists for DataSource (see log) |
| 283 | Action executed |
| 284 | Real time is only possible with queue or extraction delta |
| 285 | Extraction structure &1 of append DataSource &2 must be append ('APPE') |
| 286 | Field &1 of append DS &2 already declared in standard DS &3 (D version) |
| 287 | Event with errors &1 in DataSource &2 |
| 300 | ****************** Hierarchy Metadata in Source System ***************** |
| 301 | Choose a Hierarchy from the Hierarchy Catalog |
| 302 | DataSource & still does not contain any additional info in table & |
| 303 | Error when checking the hierarchy additional info in the source system |
| 304 | Error when writing hierarchy additional info to the table |
| 305 | No structure of the DataSource & was found for hier. in source system |
| 306 | No hierarchy extraction function & exists in source system |
| 307 | Error when calling extraction function & for hierarchy in source system |
| 308 | Error when calling form routine & for hierarchy in source system |
| 309 | Error at end of user exit function & for hierarchy in source system |
| 310 | Error in send & of the hierarchy table |
| 311 | No metadata exists for hierarchy in source system & |
| 312 | DataSource & with & must assign with a hierarchy class |
| 313 | Error in check function & for additional information in source system |
| 314 | Hierarchy additional information for DataSource & was changed |
| 315 | Hierarchy additional information for DataSource & already exists in the & |
| 316 | Compound information of DataSource & already exists in the & |
| 317 | Service APIs for hierarchies does not support extraction type & |
| 318 | The data element & does not exist in the source system in table & |
| 319 | The domain & does not exist in the source system in table & |
| 320 | You are not authorized for actions with the DataSource & |
| 321 | The generated objects of DataSource & could not be deleted |
| 322 | The hierarchy additional information for DataSource & were not deleted |
| 323 | Check function & does not contain the complete DataSource structure & & |
| 324 | Duplicate compounding entries are not allowed |
| 325 | No authorization for DataSource & |
| 326 | Error when calling function & for the hier. catalog in source system |
| 327 | No hierarchy catalog in the source system |
| 328 | Error calling the form routine & for the hierarchy in the source system |
| 329 | No active DataSource with the HIER type exists in the source system |
| 330 | The length of the data element & does not exist in the source system |
| 331 | Mapping of dictionary type & to ABAP type is not possible in source syst. |
| 332 | Error in function & for determining compounding information |
| 333 | Generated hierarchy: Hierarchy class & does not exist |
| 334 | Generated hierarchy: Data element & does not exist |
| 335 | Genenerated hierarchy: Domain & does not exist |
| 336 | There is no corresponding F4 field in textextr. for field &1 of DS &2 |
| 337 | There is no text field for input help of field &1 of DataSource &2 |
| 338 | No extraction method exists for &1 for DataSource &2 |
| 339 | Field &2 is missing from hierarchy segment &1 |
| 340 | Field type &1 in hierarchy segment &2 is incorrect |
| 341 | Hierarchy segment &1 does not exist or is not active |
| 342 | Hierarchy segment &1 is not equivalent to reference structure &2 |
| 343 | The data element &1 of DataSource &2 does not exist |
| 344 | Hierarchy segement &1 is not compatible with reference structure &2 |
| 345 | ALE delta is only supported for attributes and texts |
| 346 | The ALE pointer &2 of DataSource &1 does not support table &3 |
| 347 | The ALE delta info key is different to the DataSource |
| 348 | ALE pointers maintained for DataSource &1. This is not right for deltaver |
| 349 | ALE pointers can only be assigned if DataSource uses ALE delta |
| 350 | Compound key &1 for DataSource &2 is too long |
| 351 | DS &1 object list cannot be included |
| 352 | Error in event segment key of data source & |
| 353 | Error in event &2 of DataSource &1 |
| 354 | The D version of the DataSource & could not be deleted |
| 355 | Save first |
| 356 | The delta process &1 does not exist |
| 357 | The data process &1 is inconsistent |
| 358 | Function module &1 is not available for conversion exit &2 |
| 359 | Invalid extract structure template &2 of DataSource &1 |
| 360 | Record mode '&1' not allowed in update mode '&2' |
| 361 | Record mode '&1' is invalid |
| 362 | Update mode '&1' is unknown |
| 363 | Field &1 of the interval segments does not match with the node segment |
| 364 | Extract structure is missing for hierarchy segment '&1' |
| 365 | Extract structure '&1' was not activated with warnings |
| 366 | Specify a delta method |
| 367 | The DataSource &1 is inconsistent |
| 368 | The function module &1 has errors: &2 |
| 369 | Generating DataSource &1 |
| 370 | DataSource &1 not assigned to a valid application component |
| 371 | DataSource &1; switch to package &2 is off |
| 372 | DataSource does not support data transfer method "PSA" |
| 373 | DataSource &1 cannot be activated in after-import |
| 374 | A DataSource can only be a leaf in the hierarchy |
| 375 | Invalid value for the import parameter i_maxsize |
| 376 | Error in selection: field & |
| 377 | The genflag of the data source & has an invalid value |
| 389 | The data element &1 of the DataSource &2 for the field &3 does not exist |
| 390 | Field &1 with reference field &2: Reference table &3 is replaced by &4 |
| 399 | Basis DataSource &1 for append DataSource &2 does not exist |
| 400 | From here the messages for MAPI BW2.0 |
| 401 | Program error: BI service API (component BC-BW) terminated: &1 |
| 402 | You are not authorized to perform this action with DataSource &1 |
| 403 | The necessary authorization object is not available |
| 404 | DataSource &1 does not exist in version &2 |
| 405 | The DataSource & already exists |
| 406 | The OLTP source &1 is not available in this version |
| 407 | You cannot perform the action & with a DataSource |
| 408 | The DataSource & is not in the namespace |
| 409 | Invalid system type & |
| 410 | The structure & is either not in ABAP Dictionary or it is a view |
| 411 | Action canceled by the user |
| 412 | There were no changes in the database |
| 413 | Invalid extraction type; no input help |
| 414 | No objects matched the selection criteria |
| 415 | This action cannot be carried out in display mode |
| 416 | The object has already been saved. You do not need to save. |
| 417 | The OLTP source still has errors |
| 418 | Application component &1 of DataSource &2 does not exist |
| 419 | The short text of DataSource &1 is not maintained in language &2 |
| 420 | The medium text of DataSource &1 is not maintained in language &2 |
| 421 | The long text of DataSource &1 is not maintained in the language &2 |
| 422 | The DataSource type &1 of DataSource &2 is not permitted |
| 423 | The view &1 of DataSource &2 is not active |
| 424 | The extraction view &1 of DataSource &2 has the wrong type |
| 425 | ALE delta must be set up for the view & |
| 426 | The extractor cannot support this delta type |
| 427 | The extractor cannot fill field &2 of the extract structure &1 |
| 428 | Different internal lengths of field &1 |
| 429 | Different data types of field &1 |
| 430 | Function module & not active |
| 431 | The extractor does not contain the field & as import parameter |
| 432 | The extractor is missing the import parameter I_REQUNR |
| 433 | The extractor is missing the import parameter i_maxsize |
| 434 | The extractor is missing the import parameter i_initflag |
| 435 | The extractor is missing the import parameter i_updmode |
| 436 | The extractor is missing the exception 'no_more_data' |
| 437 | The extractor is missing the exception 'ERROR_PASSED_TO_MESS_HANDLER' |
| 438 | The extractor has the exception & |
| 439 | The extractor is missing the table parameter E_T_DATA |
| 440 | The extraction method & is not supported |
| 441 | The domain is not active |
| 442 | The domain has no fixed values |
| 443 | The extract structure is not permitted |
| 444 | The extract structure &1 of the DataSource &2 is invalid |
| 445 | DS &3: Field &1 of the provider structure is missing in extract str. &2 |
| 446 | The InfoSource was saved successfully |
| 447 | The metadata was added to the buffer |
| 448 | The selection option &1 of field &2 of DataSource &3 is invalid |
| 449 | DataSource &3: Field &1 of extr struct &2 is not in the provider struct. |
| 450 | The unit field &1 of DataSource &2 is not in the extr. structure &3 |
| 451 | Docu can only be created if the OLTP source has been saved |
| 452 | There is only hierarchy additional information for hier. DataSources |
| 453 | DataSource & with HIER type does not have any hierarchy additional info |
| 454 | Error in the check function of the hierarchy additional information |
| 455 | Error writing to the hierarchy additional information table |
| 456 | Hierarchy additional information was saved successfully |
| 457 | Hierarchy additional information of DataSource & already exists |
| 458 | Metadata inconsistencies between DataSource and hier. additional info |
| 459 | No DataSource with HIER type exists in source system -> 329 |
| 460 | There is no hier. additional information for DataSource &1 in version &2 |
| 461 | Choose a hierarchy name |
| 462 | Error calling function & for hier. catalog in source system -> 326 |
| 463 | Error calling form routine & for hierarchy in source system -> 328 |
| 464 | No hierarchy extraction function & exists in source system (306) |
| 465 | No entry exists in the hierarchy transfer table |
| 466 | The DataSource & does not contain a hierarchy class type |
| 467 | Data element & does not exist in source system in table & -> 318 |
| 468 | Domain & does not exist in source system in table & -> 319 |
| 469 | No hierarchy catalog exists in source system -> 327 |
| 470 | Action canceled by user |
| 471 | BW Release & is not supported in the source system |
| 472 | InfoSource is consistent |
| 473 | Extractor & does not exist |
| 474 | No InfoObject is assigned to the selection field &. Info is lost. |
| 475 | DS &1: The extraction domain &2 is not active |
| 476 | The field & does not exist in the extract structure |
| 477 | The InfoObject & does not exist in this OLTP |
| 478 | Extraction type & is not supported |
| 479 | DS &1: Cancelation field is only useful for transaction data |
| 480 | The InfoObject &2 that is compounded to IO &1 has not been maintained |
| 481 | Data element &2 of InfoObject &1 is not active |
| 482 | Data element &2 of InfoObject &1 is not active |
| 483 | Start of XPRA phase 1: Transformation 12B Metadata > 20A Metadata... |
| 484 | Start of XPRA phase 3: Transformation 20A metadata > 20B... |
| 485 | End of XPRA phase 1: Transformation unnecessary |
| 486 | ALE delta only possible for text/attribute DataSources in view extraction |
| 487 | InfoSource & does not exist |
| 488 | This column cannot be sorted |
| 489 | No errors |
| 490 | DataSource & was saved successfully |
| 491 | No errors or warnings |
| 492 | There is no corresponding characteristic for InfoSource & |
| 493 | There is no corresponding basis characteristic for InfoSource & |
| 494 | DataSource & has been deleted successfully |
| 495 | DataSource & could not be deleted |
| 496 | Field &1 cannot be a cancelation field; it has the data type &2 |
| 497 | Application component & does not exist |
| 498 | The text for application component &1 does not exist in language &2 |
| 499 | The extract structure & does not contain any fields |
| 500 | ************* Message for the central delta ********************** |
| 501 | Client & does not exist in the source system |
| 502 | The delta queue entries could not be deleted |
| 503 | The delta queue could not be read |
| 504 | There are no transfer rules for the DataSource |
| 505 | No parameters exist yet for the delta transfer |
| 506 | The queue is empty |
| 507 | DataSource & does not support delta update |
| 508 | Queue & does not exist in the source system |
| 509 | There are still no BW systems connected to the DataSource |
| 510 | You cannot repeat the last delta selection |
| 511 | Invalid selection options |
| 512 | Errors writing to table & |
| 513 | The extraction structure &1 of DS &2 is a view. This allows no CustApp |
| 514 | The queue management metadata could not be deleted |
| 515 | The RFC queue data could not be deleted |
| 516 | The selection for the field &1 has still not been initialized |
| 517 | Transfer of application component hier. &1 from Content... |
| 518 | DS &1: The extraction domain &2 has no fixed values |
| 519 | Info object &1 has multiple fields assigned to it |
| 520 | Extraction from the archive is not possible for extraction method '&1' |
| 521 | Importing parameter I_CALLMODE is missing from extraction module '&1' |
| 522 | Application component hierarchy '&1' copied from D to A |
| 523 | Cannot copy application component hierarchy '&1' to 'A' |
| 524 | Application component hierarchy '&1' cannot be edited |
| 525 | DataSource &1 does not allow append structures |
| 526 | Data in queue management of DataSource & has been deleted |
| 527 | Data in queue of DataSource & has been deleted |
| 528 | Generic delta not converted yet |
| 529 | Generic delta for DataSource & already converted |
| 530 | Generic delta of DataSource & converted |
| 531 | Delta management for DataSource & could not be read |
| 532 | Generic delta management converted completely |
| 533 | Cannot deregister BI agent for DataSource &1 |
| 534 | Extraction method 'CA' only possible in Basis Release 7.10 and higher |
| 535 | ESR attributes can only be maintained in Basis Release 7.10 and higher |
| 536 | Selection option &1 is invalid (allowed: EQ, NE, LT, LE, GE, GT, CP) |
| 537 | Too many entries: Tree cannot be constructed |
| 538 | Table &1 does not exist in active version |
| 539 | Inconsistent table data |
| 540 | Tables may not appear more than once |
| 541 | Only editing of DataSources (hierarchy locked by &1) |
| 542 | Select a DataSource with the cursor or by highlighting it |
| 543 | No DataSources found with inconsistent A and D versions |
| 544 | Choose exactly one DataSource |
| 545 | Select at least one DataSource |
| 546 | Not possible to have hierarchy nodes under DataSources |
| 547 | Error in chaining of nodes |
| 550 | You have not selected any DataSources |
| 551 | The system could not find any inconsistencies |
| 552 | Editing of object version &1 is not possible |
| 553 | Editing mode &1 is not valid |
| 555 | The DataSource & was not applied |
| 558 | You can only delete DataSource & from the corresponding application |
| 559 | Deleting DataSource &1... |
| 565 | Multiple data sources selected; select one only |
| 568 | You have chosen no DataSource. Choose one. |
| 569 | The even-numbered length of the DEC field &1 can cause problems |
| 570 | Extraction structure includes invalid field &1 with ABAP type &2 |
| 571 | Selection field &1 has not-supported type &2 |
| 600 | The request with the number & is not known in the source system |
| 601 | OLTP source & does not extract data with domain fixed values |
| 602 | Termination: Program &1, include &2, line &3 |
| 603 | Request &1 belongs to DataSource &3 from source system &2 |
| 604 | DataSource &1 does not support generic data |
| 650 | Changes in the content system are not allowed |
| 651 | DataSource with data type &1: key change not supported |
| 652 | DataSource &1: transport failed |
| 653 | Modified DataSource &1 contains errors |
| 654 | Field &1: key field (not dependent on extract structure) |
| 655 | Field &1: no key field (not dependent on extract structure) |
| 656 | Field &1: Key field after Dictionary property (such as extract structure) |
| 657 | Key change on DataSource &1 was applied |
| 658 | Key change on DataSource &1 |
| 670 | No DataSource specified in class &1 |
| 671 | Error in class &1 |
| 672 | Correction already implemented for DataSource &1 in class &2 |
| 673 | DataSource &1 corrected using class &2 |
| 674 | Handled corrections |
| 675 | Field &1 does not exist in DataSource &2 |
| 676 | Correction &1 has errors and was not applied |
| 677 | Correction &1: no changes compared to current D version |
| 678 | Correction &1: Changed D version contains errors and was not applied |
| 679 | Changed DataSource &1 saved in Database |
| 680 | No changes to DataSource &1 |
| 681 | Check changed D version (DataSource &1) |
| 682 | No changes can be made to attribute &1 |
| 683 | Attribute &1: value &2 is invalid |
| 684 | Attribute &1 does not exist |
| 685 | Attribute &1: Value '&2' was applied |
| 800 | &&&& |
| 801 | Error in proxy data (table ROPROXY) |
| 802 | Cannot send data using push |
| 803 | Data sent (asynchronous processing) |
| 804 | Data sent (synchronous processing) |
| 890 | H extraction &1 is completely incorrect |