RSO -
The following messages are stored in message class RSO: .
It is part of development package RSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW Repository: Infastructure and Core GUI Components".
It is part of development package RSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW Repository: Infastructure and Core GUI Components".
Message Nr ▲ | Message Text |
|---|---|
| 000 | -------------- Message for matching A/D version InfoObjects ------------- |
| 001 | InfoObject &1: active and revised version are different |
| 002 | InfoObject &1: &2 was changed inappropriately (from '&3' to '&4') |
| 003 | InfoObject &1: SAP version is protected - you cannot change object |
| 004 | InfoObject &1: '&2' will not be changed from '&3' to '&4' |
| 005 | InfoObject &1: '&2' is changed from '&3' to '&4' |
| 006 | The "Transfer Content" function is not allowed in the Content system |
| 007 | InfoObject &1: InfoObject &2 is included again in the compounding |
| 008 | InfoObject &1: InfoObject &2 is included again as attribute |
| 009 | InfoObject &1: InfoObject &2 is included again as navigation attribute |
| 010 | Attribute &1: &2 will not be changed from &3 to &4 |
| 011 | Attribute &1: &2 is changed from &3 to &4 |
| 012 | The versions (&2 and &3) of InfoObject &1 agree |
| 013 | Manual match of InfoObject &1 |
| 014 | InfoObject &1 matched with Content version |
| 015 | InfoObject &1 copied from Content version |
| 016 | Error when matching InfoObject &1 with Content version |
| 017 | InfoObject &1 used and activated (from modified version) |
| 018 | InfoObject &1: InfoObject &2 is included as an ext. hierarchy charstic. |
| 019 | Action canceled |
| 020 | No hits found with this search term |
| 021 | Authorization relevance reset for characteristic &1 |
| 022 | InfoObject &1: InfoObject &2 is included again as XXL attribute |
| 100 | ------ Messages for comparing A/D version of InfoObjectCatalog ------ |
| 101 | Still have available texts on InfoObjectCatalog &1 in language &2 |
| 102 | InfoObject &1 entered in InfoObjectCatalog &2 |
| 103 | The versions of InfoObjCat &1 concur in all properties |
| 200 | ---------- Messages for interface Repository ----------------------- |
| 201 | No objects are loaded in the repository (main memory) |
| 202 | Maintenance of object '&1' of type '&2' is not yet available |
| 203 | Node &1 is not available in tree |
| 204 | No document found for object &2 of type &1 |
| 205 | No documents available for type &1 of object &2 |
| 206 | No corresponding entries were found in tree |
| 207 | The comparison of versions &2/&3 is 'not available' for type '&1' |
| 208 | You are not authorized to change documents for object &2 (&1) |
| 209 | Further objects will be sought only &1 level deeper |
| 210 | InfoArea &2 of InfoCube &1 does not exist |
| 211 | Choose one or more source systems |
| 212 | Could not open file on the application server: &1 |
| 213 | File &1 was written successfully to the application server |
| 214 | Search index is not available. Start structure via 'Extras' menu |
| 215 | Object &1 &2 is generated, and cannot be transported |
| 219 | ======================================================================== |
| 220 | ------------ Messages for Controls ----------------------------------- |
| 221 | Error &1 occurred in display control |
| 250 | ------------ BW Repository Messages ---------------------------------- |
| 251 | Object type '&1' of object '&2' is not yet supported |
| 252 | Object '&1' (&2) of type '&3' is not available in version '&4' |
| 253 | Object type (TLOGO) is missing |
| 254 | Name of object of type '&1' is missing |
| 255 | Where-used list for object &1 (&2) not yet implemented |
| 256 | Function module &1 is not active |
| 257 | Object type (TLOGO) of object '&1' is missing |
| 258 | Name of object of type '&1' is missing |
| 259 | Object '&1' of type '&2' already exists in tree |
| 260 | Activation of Content with type &1 (FB &2) is not yet available |
| 261 | Object '&1' of type '&2' already exists in network |
| 262 | Root object '&1' (type '&2') of an association is not yet available |
| 263 | Input help for objects of type '&1' (&2) is not yet available |
| 264 | No objects of type '&1' (&2) are available in version &3 |
| 265 | Could not export file '&1' (error &2) |
| 266 | File '&1' could not be opened during export |
| 267 | File '&1' could not be written during export |
| 268 | Error occurred in front end (GUI) when exporting file '&1' |
| 269 | There is no data to export |
| 270 | Approximately &1 MB of data will be transported |
| 271 | Target object '&1' (type '&2') of an association is not available |
| 272 | No relevant data was found |
| 273 | The higher-level application component &1 is missing from &2 |
| 274 | Object '&1::&2' refers to the invalid object '&3::&4' |
| 275 | The object '&1::&2' cannot be activated (see long text) |
| 276 | Localized texts have been installed |
| 278 | Job &1 (&2) could not be started (&3) |
| 279 | Job &1 (&2) was started successfully |
| 280 | Installation could not be started as job &1 (&2) |
| 281 | Installatio started successfully as job &1 (&2) |
| 282 | Job &1 in group &2 could not be scheduled (error &3) |
| 283 | Program &3 could not be scheduled in job &1, no. &2 (&4) |
| 284 | No reversal can be determined for association &1 |
| 287 | Collecting process started successfully as job &1 (&2) |
| 288 | Could not start the collecting process as job &1 (&2) |
| 290 | InfoPackage &1 does not exist. Data was not loaded. |
| 291 | InfoPackage &1 is locked. Data was not loaded. |
| 292 | The loading process for InfoPackage &1 is already running |
| 293 | The loading process for InfoPackage &1 is already scheduled |
| 294 | The data files could not be written (&1) |
| 295 | Could not create source system '&1' (&2): Cause &3 |
| 296 | Object &1 (&2) could not be collected for object &3 (&4) |
| 297 | Transfer of &1(&2) necessary, due to &3(&4) |
| 298 | Transport of &1(&2) necessary, due to &3(&4) |
| 299 | Technical name '&1' for object of type &2 '&3' is invalid |
| 300 | Error when checking the long-term block for '&1', type '&2' |
| 301 | System name missing when checking the long-term block for '&1', '&2' |
| 302 | System type missing when checking the long-term block for '&1', '&2' |
| 303 | Order &1 of the block is invalid (object '&2', '&3') |
| 304 | Object '&1' (type '&2') locked by request &3 |
| 305 | Objects that are locked by other transport requests |
| 306 | Transport requests that first have to be released |
| 307 | Transport request &1 of user &2 (request &3 of &4) |
| 308 | No authorization for transporting role &1 (see long text) |
| 309 | Cannot transport local object &1 |
| 310 | Transport of activity groups was canceled |
| 311 | Transport not possible. Required objects are missing |
| 312 | Cannot install Business Content. Objects are missing |
| 313 | Installation of: &1 (&2) |
| 314 | Installation (simulation mode) of: &1 (&2) |
| 315 | Transferring the &3 objects from type &1 took &2 seconds |
| 316 | Transferring the documents for objects of type &1 |
| 317 | Transferring the documents for type &1 took &2 seconds |
| 318 | Post-processing of Objects after activation |
| 319 | The post-processing lasts &1 seconds |
| 320 | Internal error &1 when reading the object catalog entry (TADIR) |
| 321 | Source systems are not transported |
| 322 | Error &3 when changing object catalog entry for object &1 (&2) |
| 323 | Exception '&3' in progrmm '&4' when passing type '&1' &2 |
| 330 | Documentation for object &1 could not be read from &2 (&3) |
| 331 | Document &1 must be in HTML format and not '&2' |
| 340 | Activation of content package number &1 |
| 341 | Searching for dependent objects for &1 objects |
| 342 | &1 objects were collected (including the incoming objects) |
| 343 | Content is activated for &1 objects |
| 344 | No content is activated because "Collect Only" was selected |
| 345 | Reading objects from the DB |
| 346 | Could not find package of &1 &2 (version &3); object is ignored |
| 347 | Special messages for BYD (method &1) |
| 348 | Activation not executed due to special messages for BYD |
| 360 | Exporting BW Repository metadata into system &1... |
| 361 | Importing BW Repository metadata from system &1... |
| 362 | Reading metadata from system &1 ... |
| 363 | Writing metadata to system &1... |
| 364 | Metadata of &1 objects was read in system &2 |
| 365 | Export of metadata to system &1 completed |
| 366 | Import of metadata from system &1 completed |
| 367 | The RFC destination for logical system &1 does not exist |
| 368 | No RFC connection to system &1: &2&3&4 |
| 369 | No other BW systems (data marts) are connected to this one |
| 370 | &1 &2 was modified and is not copied from the content |
| 380 | --------------- Messages for CTC Content Activation ----------------- |
| 381 | Not all the required content objects for &1 &2 were available |
| 382 | Process chain not activated; no monitoring data supplied |
| 383 | Collection of Required Content Objects |
| 384 | Activation of Required Content Objects |
| 385 | Reactivation of Required Process Chains |
| 386 | Connect source system with VirtualProvider |
| 400 | --------------- Messages for generic functions ------------------ |
| 401 | &1 &2 is already active |
| 402 | &1 &2 is already saved |
| 403 | &1 &2 activated |
| 404 | Error when activating &1 &2 |
| 405 | Object &1 &2 is not transferred (component &3 is not active) |
| 406 | Error when deleting InfoSets, or InfoSet queries |
| 407 | Object &1 &2 was set to 'inactive' |
| 408 | Object &1 &2: Business Content component &3 is not active |
| 409 | &1 &2 was reset to the active version |
| 410 | Error when resetting &1 &2 to the active version |
| 411 | The documentation of &1 &2 is currently locked by user &3 |
| 412 | '&1' '&2' is not active - Texts in the M version have not been translated |
| 413 | Object &1 &2 has been deleted |
| 414 | Error when deleting object &1 &2 |
| 415 | Using &1 &2: |
| 416 | Object &1 &2 used in object &3 &4 (not deleted) |
| 417 | Usage check object type &1 |
| 418 | Still used in &1 &2 (&3) |
| 419 | Object &1 &2 not found |
| 420 | &1 &2 cannot be deleted because of references |
| 421 | Object &1 &2 is required by &3 (&4) |
| 422 | DDIC Object &1 &2 has not been activated |
| 423 | DDIC Object &1 &2 has not been deleted |
| 424 | Object &1 &2 is not available in version &3 |
| 425 | Object &1 &2: Installation of the Content Version |
| 426 | Object &1 &2: will also be transferred (&3 / &4) |
| 427 | Object &1 &2: must be activated (&3 / &4) |
| 428 | Object &1 &2: Merge with the Content Version |
| 429 | TLOGO type &1 does not require treatment after translation |
| 430 | Impact analysis of &1 &2 |
| 431 | Object &1 &2: Error installing the Content version |
| 432 | Target name for object &1 &2 in &3 was not found |
| 433 | Object &1 &2 is already deleted |
| 434 | Function not possible for TLOGO type &1 with these parameters |
| 435 | Error during creation of DDIC sources of &1 &2 |
| 436 | Object &1 &2 can only be displayed and cannot be edited |
| 437 | Object &1 &2 (version &3) deleted from database |
| 438 | Error while deleting object &1 &2 (version &3) from database |
| 439 | Could not determine pseudo D version of object &1 &2 |
| 440 | Source system-dependent object &1 &2 inconsistent (instance not avail.) |
| 441 | Object &1 &2 belongs to technical Content; changes will be overwritten |
| 442 | &1 &2 scheduled/executed successfully |
| 443 | Error when Scheduling / Executing &1 &2 |
| 444 | Execute authorization check |
| 445 | Object &1 &2 cannot be deleted; you do not have authorization |
| 446 | Object &1 &2 has no TADIR entry |
| 447 | Error while editing after saving the DDIC sources of &1 &2 |
| 448 | Cannot schedule or execute &1 &2 because not active |
| 449 | Object catalog of last imported object &1 is being used |
| 450 | Package &1 is transferred from catalog entry of imported object |
| 451 | Object is local and is not transported when changed |
| 452 | &1 &2 &3 &4 |
| 500 | ----------------------- Content admin messages |
| 501 | Business Content component &1 does not exist (obsolete) |
| 502 | Business Content component changed from &1 to &2 (obsolete) |
| 503 | You do not have administration authorization for the Content system |
| 504 | The system was set as a "Content system" |
| 505 | The system was set as a normal ("non Content") system |
| 506 | Namespace &1 cannot be used for roles |
| 507 | Customer namespace &1 is a prefix of customer namespace &2 |
| 508 | Customer namespace &1 is used more than once |
| 509 | D version of role &1 renamed as &2, as per table RSOTLOGONSPDEL |
| 550 | ------------------------Messages Appends / Enhancements-------------- |
| 551 | Enhancement with name &1 already exists - change name |
| 552 | A general error with append &1 occurred |
| 553 | append &1 does not exist (version &2) |
| 554 | Name of append &1 is invalid |
| 555 | Enhancement &1 is not a BW enhancement |
| 556 | Appends still exist for main object - cannot delete |
| 557 | Append &1 of main object &2 not saved |
| 558 | Append &1 deleted |
| 559 | Cannot create - append &1 is not active |
| 560 | Only objects with the same switch may be included |
| 561 | Append &1 has no objects, cannot save |
| 562 | Internal error: Append inconsistent - &1 &2 &3 &4 |
| 563 | Only one append can exist for each switch |
| 564 | Append &1 and append &2 are in the same switch (&3) |
| 565 | Append must be assigned to a switch (development class: &1) |
| 566 | Error while determining package of append |
| 567 | Append &1 of main object &2 saved |
| 568 | Append &1 is locked (can only be displayed) |
| 569 | Error (&1) while activating (deleting) append &2; see long text |
| 570 | Error while deleting append &1 |
| 571 | Error while saving append &1 (&2) |
| 572 | Append &1 is locked |
| 573 | Unable to activate append &1 |
| 574 | Append &1 of main object &2 was activated |
| 575 | Switch &3 for object &1(&2) is inactive |
| 576 | Switch for object &1 is inactive |
| 577 | Append cannot be assigned to main object |
| 578 | Check of append &1 in version &2 |
| 579 | Object &1 may not be assigned to append &2 |
| 580 | Object &1 may not be assigned to main object &2 |
| 581 | Appends are not supported for object type &1 |
| 582 | Switches are not supported for object type &1 |
| 583 | Append &1 is displayed |
| 584 | Append &1 is processed |
| 585 | No main object found for append &1 (is ignored) |
| 586 | Creation of appends not allowed for content activation user |
| 600 | ----- Messages for Matching A/D Version InfoCubes / MultiProvider ------- |
| 601 | InfoProvider &1: The active version is different to the modified version |
| 602 | Keep existing texts for InfoProvider &1 in language &2 |
| 603 | InfoObject &1 transferred from the 'M' version of InfoProvider &2 |
| 604 | InfoObject &1 was assigned to dimension &2 |
| 605 | Dimension &1 was added |
| 606 | Still have available texts for dimension &1 in language &2 |
| 607 | InfoProvider &1, relevant to MultiProvider &2, has been added |
| 608 | Assignment of InfoObject &1 has changed in Provider &2 from &3 to &4 |
| 609 | In Provider &2, the assignment of InfoObject &1 to &3 has been added |
| 610 | Versions of InfoProvider &1 have the same properties |
| 612 | InfoObject &1 was added during version comparison |
| 613 | Dimension &1 was added during version comparison |
| 614 | InfoObject &1 has been added to dimension &2 |
| 615 | Navigation attribute &1 was added during version comparison |
| 616 | InfoProvider &1 was added during version comparison |
| 617 | Key figure &1 was added to hierarchy node &2 |
| 618 | Hierarchy was added (comparison with existing hierarchy) |
| 619 | Available texts for InfoProvider &1, language &2, InfoObject &3 are kept |
| 650 | ---------------------- Checks Before Export ---------------------------- |
| 651 | Cannot perform check for &1 &2: Error &3 &4 |
| 652 | Error reading request &1 |
| 653 | Error while converting from D or shadow object &1 &2 to A version. |
| 654 | Reading request &1 |
| 655 | Checking objects of request &1 |
| 656 | Transportable object &1 &2 needs local object &3 &4 |
| 657 | Object &1 &2 needs object &3 &4; latter is not in a request |
| 658 | &1 needs &2; latter is in request &3 (release request) |
| 659 | Inconsistent objects: |
| 660 | Local dependent objects: |
| 661 | Dependent objects that are not in a transport: |
| 662 | Dependent objects that need to be released: |
| 663 | Object &1 &2 needs object &3 &4; the latter does not exist |
| 664 | Dependent objects that do not exist: |
| 665 | Request is consistent |
| 666 | Inactive Objects: |
| 667 | Object &1 &2: Active version differs from modified version |
| 668 | Deletions: |
| 669 | Object &1 &2 does not exist. Will also be deleted in target system |
| 670 | Shadow object &1 &2 is inconsistent |
| 671 | Active version of &1 &2 does not exist - dependent objects unknown |
| 672 | Object &1 &2 is generated and cannot be transported |
| 673 | Request &1 inconsistent. Not released |
| 674 | Object &1 &2 on exception list. Dependents not checked |
| 675 | Request &1 on exception list. Not checked |
| 676 | Release check switched off. Request &1 not checked |
| 677 | Request &1 is consistent |
| 678 | Exemption of consistency check, transport & granted in 'RSTPCHECKEXC' |
| 679 | Exemption of consistency check, transport & already set in 'RSTPCHECKEXC' |
| 680 | ------------------BOBJ Transport/Checks---------------------------- |
| 681 | Object '&1' (&2) of type '&3' is local and must be transported |
| 682 | Found &1 as package for new objects (using user parameter DVC) |
| 683 | &1 is package for n objects (using packages of dependent objects) |
| 684 | Could not determine a package for new objects. See long text |
| 685 | Transport request &1 from user &2 |
| 686 | Transport object &1 (type &2) in BW system manually |
| 698 | BW Check of transp. & returns errors, exemption can't cre. in backgrd. |
| 699 | Task(s) of transport &1 not released, exemption not possible |
| 700 | ----------------- Generic Copy Tool ------------------------------------ |
| 701 | Object type &1 does not support copying. Please remove. |
| 702 | The number of copies for object &1 &2 is different from the others |
| 703 | There are no copies for object &1 &2 |
| 704 | Object &1 &2 exists already in version &3 (will be skipped) |
| 705 | Object &1 &2 has been copied successfully to &3 |
| 706 | Error when checking the copy rules for type &1 |
| 707 | Object &1 &2: The new name is not specified |
| 708 | Target name &2 is assigned more than once for Object type &1 |
| 709 | Wild card character '*' only allowed at end of name &1 |
| 710 | Wild card character '+' not allowed in name &1 |
| 711 | Name &1 must contain wild card character '*' |
| 712 | Object &1 &2 already in conversion table (cannot appear twice) |
| 713 | &1 entries added to copy table |
| 740 | Transport &1 skipped. No new object collection required. |
| 741 | Reserved for BR1 correction |
| 742 | Reserved for BR1 correction |
| 750 | Only objects that match the following TLOGO filter are processed: |
| 751 | Sign: & Option: & Low: & High & |
| 752 | Request &1 (time stamp: &2) does not contain object after TLOGO filtering |
| 765 | "BW Import All Buffer" purged during SUM upgrade |
| 766 | "BW Import All Buffer" not purged during SUM upgrade |
| 767 | &1 is not a BW system. Objects of type &2 skipped in BW AIM processing. |
| 768 | &1 is not a BW system. Special object types are allowed for BW AIM. |
| 769 | AIM already executed for the following objects: |
| 770 | ----------------------Parallel AIMs------------------------------------ |
| 771 | * Parallel after import handling for object type &1 (&2 packages) |
| 772 | * Processing package &1 in background job &2; Start time &3; Objects &4 |
| 773 | * Processing of package &1 in main process; start time &2; objects &3 |
| 774 | * Start of after import background process &1 (Number: &2) |
| 775 | * End of after import background process &1 (number: &2; runtime: &3) |
| 776 | * Start of AIM function module &1 for object type &2 |
| 777 | * After-import method &1; Package no. &2 (Status: &3) |
| 778 | End of after import methode &1 (&2) - runtime: &3 |
| 779 | Termination in background job &1 while processing package &2 |
| 780 | * Object &1 contained in package &2 |
| 781 | Invalid objects: 'After Import' terminated (see long text) |
| 782 | Skipped pseudo D version for object type &1 (see Note 1649901) |
| 783 | Object & of request &, AIM mode 'ACT' already processed. |
| 784 | Object &1 of request &2, AIM mode 'DEL' already processed. |
| 785 | Restart point for BW-TLOGO objects: Request & saved |
| 786 | Save of BW TLOGO restart points: |
| 787 | Object &1 of request &2 already fully processed; 'LOCKFLAG = 3' |
| 788 | Import All request &1: Post-processing object list after interruption |
| 789 | Import object &1 &2 incorr. processed with this request with obj ID &3 |
| 790 | Object &1 &2 processed with errors on this request |
| 791 | Object &1 &2 imported with errors on subsequent request &3 |
| 792 | Object &1 &2 processed with errors on request &3 |
| 793 | Error with request &1. Import All log refers to request &2. |
| 794 | Import object &1 &2 incorr. processed with request &3 with obj ID &4 |
| 795 | Request &1 (time stamp: &2), not relevant for BW after import |
| 796 | Request &1 (time stamp: &2), erroneous objects follow: |
| 797 | Request &2 aborted. Follow-up request &1 inherits RC = 12. |
| 798 | After-import request &2 RC = 12. Request &1 not processed completely. |
| 799 | Erroneous object &1 &2 skipped by exception handling |
| 800 | ---- Function Group RSVERS / REORGS / generic Messages ------ |
| 801 | Logical transport object &1 not found in table RSTLOGOPROP |
| 802 | Object &1 &2 copied (or deleted) from A version to D (&3) |
| 803 | Object &1 &2 copied in shadow object &3 &4 |
| 804 | Object &1 &2: D version deleted |
| 805 | Object &1 &2 &3 cannot be converted in D Version |
| 806 | TADIR entry written for object &1 &2 |
| 807 | Object &1 &2 written to request/task &3 |
| 808 | Object &1 &2 deleted from request/task &3 |
| 809 | Object &1 &2 is locked in request &3 |
| 810 | Specify a transportable package. ('&1') not possible |
| 811 | Error in development class, object &1 &2 not saved to the request |
| 812 | Object &1 &2 could not be saved to an request |
| 813 | Error in saving the documents of &1 &2 to a request (&3) |
| 814 | TADIR entry for object &1 &2 changed |
| 815 | Error in changing TADIR entry for object &1 &2 |
| 816 | TADIR entry for object &1 &2 deleted |
| 817 | Error while deleting TADIR entry for object &1 &2 |
| 818 | Release request &1 |
| 819 | Enter a transport request in the next popup |
| 820 | Package &1 is not possible - transport target is not '&2' |
| 821 | Local TADIR entry for object &1 &2 created |
| 822 | Error in creating the local TADIR entry for object &1 &2 |
| 823 | Enter a customer development class (&1 belongs to SAP) |
| 824 | Object &1 &2 could not be saved to order &3 |
| 825 | Object &1 &2 is not connected to the CTO in the Content system |
| 826 | Error while deleting the BDS documents from object &1 &2 |
| 827 | BEx transport request '&1' is not available or not suitable |
| 828 | No new BEx transport request necessary, as request &1 still exists |
| 829 | No documents have been maintained yet for &1 &2 |
| 830 | The documentation display was started in a separate window |
| 831 | Processing of the documents has been started in a separate window |
| 832 | R3 Link for object &1 &2 has been deleted |
| 833 | Application &1 is not assigned to a document type (table TOADD) |
| 834 | Documentation from &1 &2 deleted |
| 835 | Documentation from &1 &2 saved in the BDS |
| 836 | The documentation can only be displayed |
| 837 | Package &1 is already in use |
| 838 | R3 Link for object &1 &2 created |
| 839 | Write to transport requests terminated by the user |
| 840 | Error while writing objects to a transport request |
| 841 | Saving &1 &2... |
| 842 | &1 &2 saved |
| 843 | Error while saving &1 &2 |
| 844 | No connection found for document &1 |
| 845 | Several documents found for document &1 |
| 846 | Document &1 &2 (&3) converted |
| 847 | Object &1 &2 is not being processed |
| 848 | Standard transport activated (see long text) |
| 849 | Standard transport deactivated (see long text) |
| 850 | Object &1 &2 cannot be processed in the Content system |
| 851 | Upgrade is running (phase &1). You cannot change objects until complete. |
| 852 | You can only display BW objects in this system |
| 853 | System can be changed; settings not necessary |
| 854 | Start after-import methods for texts |
| 855 | Object &1 &2 was delivered as Content to this system |
| 856 | BEx request &1 already released and removed |
| 857 | Error &2 during after import handling of objects with type(s) &1 |
| 858 | &1 &2: Dependant objects are not subject to recording in requests |
| 859 | Error occurred when saving dependent object &4 of &1 &2 to a request (&3) |
| 860 | BW systems with MDMP configuration are not supported |
| 861 | Upgrade running (phase &1) - you can only make limited changes to objects |
| 862 | Object &1 &2 cannot be edited during the upgrade (phase &3) |
| 863 | All edited objects (target &1) already locked on request &2 |
| 864 | The edited objects with target &1 are locked on the following requests: |
| 865 | System is set to not changeable; objects cannot be changed |
| 866 | Objects are consistent |
| 867 | Starting automatic activation of BI Content |
| 868 | Deleting objects of type &1 |
| 869 | Starting after import method &1 for object type(s) &2 in delete mode |
| 870 | Starting after import method &1 for object type(s) &2 in Content mode |
| 871 | Short dump &1 &2 occurred during After Import handling in area &3 |
| 872 | Deletion of &1 TLOGO objects |
| 873 | Content status entry for object &1 &2 (version &3) generated |
| 874 | Content status entry for object &1 &2 (version &3) deleted |
| 875 | Text processing for content objects is skipped |
| 876 | Error &1 &2 (&3) in TP command &4 |
| 877 | Could not determine the BW client |
| 878 | Could not determine the RFC destination in the BW client |
| 879 | Object &1 &2 to be deleted could not be written to transport request |
| 880 | No request specified for transport destination &1 |
| 881 | Call of BAdI implementation for BW after import handling |
| 882 | Error calling BAdI implementation "BW After Import Handling" |
| 883 | After import handling of order &1 has been performed for order &2 |
| 884 | After import order &1: The following orders are also processed common: |
| 885 | Error while reading objects from request &1 (-> individual import) |
| 886 | Request &1 (time stamp: &2) |
| 887 | Object &1 &2 is generated and cannot be transported |
| 888 | BW BYD upgrade: Request &1 rebuilds the BW buffer (MAINFL=&2) |
| 889 | BW BYD upgrade: Handling of request &1 and dependents completed |
| 890 | Error - not related to request &1. Log displayed for subsequent request |
| 891 | Error with objects of request &1. See log for request &2 |
| 892 | Error with request &1. Import All log will follow |
| 893 | No error with object of request &1. See log for request &2 |
| 894 | No errors with request &1. Log displayed for subsequent request |
| 895 | Not an error (last request &1). Full log will follow (see request &2) |
| 896 | Request &1: Simulated call of after import handling |
| 897 | Request &1 marked as incorrect due to type &2 (may possibly be correct) |
| 898 | Processing of request &1 is also recorded in the log |
| 899 | Summary of objects with errors from request &1 |