RSAOLTP - Meldungen im OltpSource Umfeld
The following messages are stored in message class RSAOLTP: Meldungen im OltpSource Umfeld.
It is part of development package RSAOLTP in software component BW-WHM-DST. This development package consists of objects that can be grouped under "OLTP Metadata <-> BW Metadata Interface".
It is part of development package RSAOLTP in software component BW-WHM-DST. This development package consists of objects that can be grouped under "OLTP Metadata <-> BW Metadata Interface".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Fatal error: &1 |
| 001 | Object version & is invalid (rsobjvers fixed values) |
| 002 | InfoSource & does not exist |
| 003 | DataSource &1 does not exist in source system &2 of version &3 |
| 004 | Transferred field list is empty |
| 005 | Field list contains rows with various keys |
| 006 | InfoObject &1, to be assigned to field &2, is not active |
| 007 | Field &1 will not be delivered from DataSource &2 in source system &3 |
| 008 | InfoObject &1 from field &2 violates the naming conventions |
| 009 | The length of InfoObject &1 is less than the length of field &2 |
| 010 | The data type of InfoObject &1 is incompatible with field &2 |
| 011 | The DataSource is already assigned to InfoSource & |
| 012 | Transfer structure & does not exist |
| 013 | The replica of DataSource &1 from source system &2 was not saved |
| 014 | Source system "&" is not an SAP source system ==> no metadata upload |
| 015 | RFC connection to source system & is damaged ==> no Metadata upload |
| 016 | Background job scheduled successfully |
| 017 | Error scheduling background job |
| 018 | Transfer structure for DataSource &1(&2) is inactive |
| 021 | Rep. info. on DataSource &2 from source system &1 was still current |
| 022 | DataSource &1 is no longer supported by source system &2 |
| 023 | Obsolete DataSource &1 from source system &2 was not deleted |
| 024 | There is no DataSource with these attributes |
| 025 | Metadata &1 for DataSource &2 is the wrong type |
| 026 | Mapping for DataSource &1 could not be generated |
| 027 | Mapping for DataSource & was generated |
| 030 | Transfer structure & was successfully deactivated |
| 031 | Properties of DataSource &1 from system &2 were refreshed |
| 032 | Cannot replicate DataSource |
| 033 | Replication completed successfully |
| 035 | Source system &: No authorization for remote activation of DataSources |
| 036 | Source system &: remote activation of DataSources not possible |
| 037 | No Content delivery intended for system "&1", type "&2" |
| 050 | Error in deleting the assignment of DataSource &1 to characteristic &2 |
| 051 | Assignment of DataSource &1 to characteristic &2 was deleted |
| 052 | Error in deleting InfoObject &1 from field assignment of DataSource &2 |
| 053 | InfoObject &1 was deleted from field assignment of DataSource &2 |
| 060 | ********** Documentation of DataSource with R/3 Links ********* |
| 061 | No documentation of DataSource &1 is available in source system &2 |
| 062 | Error in function &1 when displaying the documentation |
| 063 | No information about add-on products available in source system &1 |
| 064 | No information about plug-in products available in source system &1 |
| 065 | Error message from function &1 |
| 066 | Invalid object name &1 in object catalog, use F4 help |
| 067 | Invalid SAP software component &1, use F4 help |
| 068 | Software component &1 does not exist in source system &2 with release &3 |
| 069 | Version & does not exist for the delivered DataSource & |
| 070 | No link exists for DataSource &1 with source system &2 |
| 071 | No documentation link exists for DataSource &1 |
| 072 | Source system &1 information could not be determined |
| 073 | PI-Release &1 for the DataSource &2 is not suitable for existing link &3 |
| 074 | AddOn info for DataSource &1 exists in source system &2 |
| 075 | No active SAP source system exists |
| 076 | No DataSource in source system &1 |
| 077 | Cannot save DataSource 3.x &1(&2) |
| 078 | DataSource &1(&2) refreshed successfully |
| 123 | Obsolete DataSource &1 from source system &2 was deleted |
| 124 | No authorization to extract DataSource &1 from source system &2 |
| 125 | Deletion of DataSource &1(&2), object type &3, &4 |
| 126 | Caller (Depth &1): Program &2, Include &3, Row &4 |
| 127 | Caller see date/time/user: &1 / &2 / &3 |
| 131 | No DataSources of source system &2 were assigned to InfoSource &1 |
| 148 | Invalid object version &3 in DataSource &1 in source system &1 |
| 149 | Invalid source system &2 for DataSource &1 |
| 150 | Could not make connection to source system &1 |
| 154 | Serious log error |
| 234 | Application hierarchy has no root nodes |
| 235 | DataSource & from source system &2 has transfer rules in Content |
| 236 | InfoObj. &1 from fld &2 of dataSource &3 is not active but BCT ex. -> Dtl |
| 237 | DataSource &1 from &2 is already mapped to InfoSource &3 |
| 238 | There is inactive Content for DataSource &1 from &2 ---> Detail |
| 239 | Application component hierarchy for Logsys "&1" does not exist |
| 304 | The RFC connection for destination &1 does not work |
| 305 | RFC destination &1 cannot be used without dialog -> Repeat replication |
| 323 | You have no authorization for Datasource &1 from source system &2 |
| 324 | DataSource & does not exist in source system &2 |
| 325 | Connection to source system & is damaged |
| 326 | InfoObject &1 is assigned to several fields of data source &2 |
| 333 | Hierarchy Metadata for DataSource & is incorrect |
| 334 | Doubled key in DataSource &1 from source system &2 with field &3 |
| 343 | Execution: Application proposal for DataSource &1 from SourceSytm &2... |
| 345 | InfoSource &1 is not active but exists in the BCT -----> Detail |
| 346 | DataSource &1 from source system &2 could not be activated |
| 347 | Invalid communications release with source system &1 |
| 358 | Determine Infosource name proposal: &1 |
| 364 | There is no F4 Help for field &1 of DataSource &2 in system &3 |
| 366 | Field &2 of DataSource &1 is not assigned to an InfoObject --> no F4 |
| 376 | Invalid InfoSource type & |
| 380 | Mapping between data source &1 and source system &2 is inconsistent |
| 381 | Mapping between &1 &2 &3 is inconsistent |
| 400 | SAP internal errors |
| 401 | Fatal error: &1 |
| 402 | Source system & does not exist |
| 403 | DataSources can not be written to shadow tables |
| 404 | Shadow mapping does not exist for DataSource '&1' and Release '&2' |
| 429 | Determine field <-> InfoObject mapping... |
| 430 | Generate required InfoSource ... |
| 431 | Generate required InfoObjects... |
| 432 | Incons. key in segment &4 for DataSource &1 from &2 in vers &3 |
| 433 | Field item &2 of DataSource &1 is filled twice |
| 434 | Field name &2 for DataSource &1 is duplicated |
| 435 | The selections &1 &2 &3 &4 specify more than one DataSource |
| 456 | No authorization to replicate: DataSource &1 from source system &2 |
| 457 | Mapping between InfoSource &1 and DataSource &2 was created |
| 458 | DataSource & is of Type &2, but contains hierarchy information |
| 459 | &1 |
| 460 | DataSource &1, from source system &2, is locked (se12) |
| 465 | Internal error: Interface incorrectly filled |
| 553 | Could not activate source system & |
| 554 | Inactive Content exists for source system &1. Detail --> Object collector |
| 556 | InfoSource & has created a name conflict during update |
| 600 | ********* RFC Queue Connection ********* |
| 601 | DataSource &1 For Source System &2 Is Incorrect |
| 602 | Function For DataSource Type &1 Is Not Available |
| 603 | Error Occured When Checking DataSource &1 For RFC Queue Connection |
| 604 | DataSource &1 For RFC Queue Connection Could Not Be Generated |
| 605 | RFC Queue Connection For DataSource &1 Could Not Be Generated |
| 606 | Error With DataSource Replication |
| 607 | Invalid DataSource name "&1"; non-alphanumeric characters exist |
| 608 | Invalid DataSource name "&1"; name has to begin with letter A to Z |
| 610 | DataSource Can Only Be Loaded in Delta Mode |