RSOH - Nachrichten zum Open Hub Interface unf zur InfoSpoke
The following messages are stored in message class RSOH: Nachrichten zum Open Hub Interface unf zur InfoSpoke.
It is part of development package RSB in software component BW-WHM-DBA-OHS. This development package consists of objects that can be grouped under "Business Information Warehouse: Data Marts".
It is part of development package RSB in software component BW-WHM-DBA-OHS. This development package consists of objects that can be grouped under "Business Information Warehouse: Data Marts".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Specify a name |
| 002 | Version &2 of InfoSpoke &1 does not exist |
| 003 | Error while writing to database table &1 |
| 004 | Invalid entry &1 &2 |
| 005 | No authorization to edit InfoSpokes |
| 006 | No authorization to change InfoSpokes |
| 007 | The action was cancelled by the user |
| 008 | Structure & is not active in the ABAP Dictionary |
| 009 | InfoObject &1 is missing from extract structure &2 of object &3 |
| 010 | Transfer structure & could not be generated |
| 011 | The field list may not be empty |
| 012 | Background job &1 scheduled to process request &2 |
| 013 | Request & has been processed |
| 014 | Object &1 of type &2 was not found |
| 015 | There is no new data |
| 016 | The processing of request & has been started |
| 017 | Processing of request & has been completed correctly |
| 018 | Processing of request & completed with errors |
| 019 | Units field &1 for key figure &2 missing in InfoSpoke |
| 020 | You cannot use more than 16 characteristics (at the moment &3) |
| 021 | Place key fields at beginning of field list |
| 022 | The InfoObject list contains no key fields |
| 023 | Navigation attributes in DB tables can cause inconsistencies |
| 024 | Short dumps are possible during extraction due to duplicated records |
| 025 | Simulation: &1 data records would have been transferred to file &2 |
| 026 | &1 data records transferred to file &2 |
| 028 | Request &1 cannot be locked |
| 030 | DataSource &1 &2 is 3.x and cannot be used |
| 031 | Primary client &1 already defined. Start transaction on this client |
| 032 | Current client entered as &1 primary client |
| 035 | &1 data records transferred to the database table |
| 036 | &1 records discarded with identical key |
| 037 | Simulation: &1 data records would have been transferred to database table |
| 040 | The name is not valid. The object could not be checked. |
| 042 | Error while writing to the file &1 |
| 050 | DB &1 is not supported |
| 051 | No authorization for connection &1 |
| 052 | &1 is an invalid entry in DBCON |
| 100 | *** Generated Open Hub Destination *** |
| 101 | Variant is being generated. Cannot be created |
| 102 | OH Destination &1 already exists and cannot be created |
| 103 | OH Destination &1 does not exist and cannot be deleted |
| 104 | Process chain for &1 cannot be deleted or does not exist |
| 105 | Destination type &1 is not allowed |
| 106 | No authorization for OH destination &1 |
| 107 | Error deleting OH destination &1 |
| 108 | OH destination &1 cannot be changed |
| 109 | Full update is the only update mode permitted |
| 279 | InfoSpoke "&1" is locked by the Change and Transport Organizer |
| 299 | Invalid program status |
| 310 | Error in deserialization of open hub destination & |