SAP ABAP Message Class R3 (Service API messages)
Basic Data
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷
BC-BW (Application Component) BW Service API
⤷
RSU0 (Package) BW Service API: Data Transfer
⤷
⤷
Attributes
| Message class | R3 | |
| Short Description | Service API messages | |
| Changed On | 20130531 | |
| Last Changed At | 092728 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | *** Error when processing request IDocs *** | Space: object requires documentation | ||
| 2 | The request IDoc contains an invalid segment & | Space: object requires documentation | ||
| 3 | Target system & is not known in the source system. | Space: object requires documentation | ||
| 4 | Error & when sending an IDoc | Space: object requires documentation | ||
| 5 | Object type & is not defined in the source system | Space: object requires documentation | ||
| 6 | InfoSource & is not defined in the source system. | Space: object requires documentation | ||
| 7 | InfoObject & is not defined in the source system | Space: object requires documentation | ||
| 8 | No transfer structure is available for InfoSource & in the source system | Space: object requires documentation | ||
| 9 | Incorrect call-up of the extraction program | Space: object requires documentation | ||
| 10 | The extraction program does not support object & | Space: object requires documentation | ||
| 11 | Selection criterion & is missing in the data request | Space: object requires documentation | ||
| 12 | Update mode & is not supported by the extraction API | Space: object requires documentation | ||
| 13 | InfoObject & does not support hierarchies | Space: object requires documentation | ||
| 14 | The transfer structure for object & must be regenerated | Space: object requires documentation | ||
| 15 | Invalid selection condition in the data request | Space: object requires documentation | ||
| 16 | Domain & cannot be used for data extraction | Space: object requires documentation | ||
| 17 | DataSource &1 has to be replicated (time stamp, see long text) | Space: object requires documentation | ||
| 18 | Request IDoc does not contain any segments | Space: object requires documentation | ||
| 19 | Request &1 does not exist in target system &2 | Space: object requires documentation | ||
| 20 | Error & when starting the extraction program | Space: object requires documentation | ||
| 21 | Error in customer exit & | Space: object requires documentation | ||
| 22 | Error in BTE exit & | Space: object requires documentation | ||
| 23 | No data available | Space: object requires documentation | ||
| 24 | Data package &1: &2 records before call-up of customer exit | |||
| 25 | Data package &1: &2 records after call-up of customer exit | |||
| 26 | Runtime in customer exit: &1, added records: &2 | |||
| 27 | Request IDoc does not contain any language information | Space: object requires documentation | ||
| 28 | Error & when generating the data transfer program | Space: object requires documentation | ||
| 29 | Transfer structure & for InfoSource & does not contain any fields | Space: object requires documentation | ||
| 30 | No extract structure available for object & in the source system | Space: object requires documentation | ||
| 31 | Incomplete control parameter for commmunication with the BW system | Space: object requires documentation | ||
| 32 | DataSource &1 does not support IDOC transfer | Space: object requires documentation | ||
| 33 | Error in a parallel process for sending data | Space: object requires documentation | ||
| 34 | Error when determining the transfer IDoc | Space: object requires documentation | ||
| 35 | View & cannot be used for data extraction | Space: object requires documentation | ||
| 36 | Data request does not contain any hierarchy names | Space: object requires documentation | ||
| 37 | Transfer structure field not contained in DataSource | |||
| 38 | tRFC: Data Package = &1, TID = &2, Duration = &3, ARFCSTATE = &4 | Space: object requires documentation | ||
| 39 | tRFC: Start = &1 &2, End = &3 &4 | Space: object requires documentation | ||
| 40 | No message category for texts from basic characteristic & | Space: object requires documentation | ||
| 41 | Error when reading the changes for characteristic & | Space: object requires documentation | ||
| 42 | Error when generating the selection for characteristic & (view &) | Space: object requires documentation | ||
| 43 | Exit: Data package = &1, interface = &2, data records before = &3 &4 | |||
| 44 | Exit: Data package = &1, interface = &2 | |||
| 45 | ***** Processing, Checking, and Transferring Hierarchies into SAPI ***** | |||
| 46 | Hierarchy class & is not defined in the source system | |||
| 47 | *** Processing and Transferring Hierarchies in the DC RHIE/BHIE *** | Space: object requires documentation | ||
| 48 | Assignment in ROHIEBAS in source system is not correct | Space: object requires documentation | ||
| 49 | Hierarchy flags & for basic charact. & are incorrect in the source system | Space: object requires documentation | ||
| 50 | Requested hierarchy selection & is incorrect in the source system | Space: object requires documentation | ||
| 51 | Function & is not supported in the source system | Space: object requires documentation | ||
| 52 | Form routine & is not supported in the source system | Space: object requires documentation | ||
| 53 | Requested language & is not supported in the source system | Space: object requires documentation | ||
| 54 | Hierarchy tables not found in the source system | Space: object requires documentation | ||
| 55 | Error when calling up the application function for hierarchies | Space: object requires documentation | ||
| 56 | Error when calling up the customer exit function for hierarchies | Space: object requires documentation | ||
| 57 | Error when sending hierarchy tables | Space: object requires documentation | ||
| 58 | Unidentifiable error in program & line & | Space: object requires documentation | ||
| 59 | Hierarchy catalog for & & & not found in the source system | Space: object requires documentation | ||
| 60 | Hierarchy class & not defined in the source system | Space: object requires documentation | ||
| 61 | Request &1 is to be terminated immediately at user's request | Space: object requires documentation | ||
| 62 | *** Error when connecting BW to the source system *** | Space: object requires documentation | ||
| 63 | No entry in table T000 for client & | Space: object requires documentation | ||
| 64 | User could not be created in the source system | Space: object requires documentation | ||
| 65 | RFC destination BW could not be created in the source system | Space: object requires documentation | ||
| 66 | Entry TSPREFIX for table RSBASIDOC could not be created | Space: object requires documentation | ||
| 67 | Source system connection was terminated | Space: object requires documentation | ||
| 68 | Function & does not exist in the source system | Space: object requires documentation | ||
| 69 | RFC user logon failed. Check connection &1 | Space: object requires documentation | ||
| 70 | RFC destination &1 for BW is not maintained in source system | |||
| 71 | IDOC: Data Package &1, IDOC No. &2, Duration &3 | Space: object requires documentation | ||
| 72 | IDOC: Info IDoc &1, IDoc No. &2, Duration &3 | Space: object requires documentation | ||
| 73 | IDoc: Start = &1 &2, End = &3 &4 | Space: object requires documentation | ||
| 74 | Unidentified error in the data transfer | Space: object requires documentation | ||
| 75 | *** IDoc Segment Generation *** | Space: object requires documentation | ||
| 76 | InfoSource & is not available in source system & | Space: object requires documentation | ||
| 77 | Name of transfer structure & in BW does not match name of srce systm & | Space: object requires documentation | ||
| 78 | When deleting transfer structure & in source system & errors occurred | Space: object requires documentation | ||
| 79 | Error when creating transfer structure & in source system & | Space: object requires documentation | ||
| 80 | Error when assigning transfer structure & to IDoc type & | Space: object requires documentation | ||
| 81 | IDoc type & is not available in source system & | Space: object requires documentation | ||
| 82 | Transfer structure & is not available in IDoc type & (&) | Space: object requires documentation | ||
| 83 | Dictionary error when creating transfer structure & in source system & | Space: object requires documentation | ||
| 84 | Activation error of transfer structure & in source system & | Space: object requires documentation | ||
| 85 | InfoSource & has no transfer structure in source system & (error) | Space: object requires documentation | ||
| 86 | InfoSource & does not have a transfer structure in source system & | Space: object requires documentation | ||
| 87 | System prefix of the transfer structure & is in the SAP name range | Space: object requires documentation | ||
| 88 | System prefix of the transfer structure & is in customer name range | Space: object requires documentation | ||
| 89 | Source system release & is not compatible with extractor release & | Space: object requires documentation | ||
| 90 | Error when generating the message type for transfer structure & | Space: object requires documentation | ||
| 91 | Incorrect or missing entry in RSMDDELTA for basic characteristic & | Space: object requires documentation | ||
| 92 | Delta transfer for basic characteristic &: Unknown field & ignored | Space: object requires documentation | ||
| 93 | Incorrect object type & transferred to function & | Space: object requires documentation | ||
| 94 | Incorrect or missing table entry for characteristic & | Space: object requires documentation | ||
| 95 | No suitable entries found for text view & in structure & | Space: object requires documentation | ||
| 96 | Error in delta generation & | Space: object requires documentation | ||
| 97 | Error when removing the connection IDoc & to IDoc type & | Space: object requires documentation | ||
| 98 | Unable to delete program & in source system & | Space: object requires documentation | ||
| 99 | ALE message type & is not active | |||
| 100 | No name could be determined for the ALE message type | |||
| 101 | Error during generation: Incorrect DS type '&1' for program class '&2' | The short text describes the object sufficiently | ||
| 102 | &1 entries in table &2 without a corresponding entry in &3 | The short text describes the object sufficiently | ||
| 103 | Unable to determine a name for the transfer structure | |||
| 104 | Transfer structure for segment &1 not available (table ROOSGENSEG) | |||
| 105 | *** Logging BIW/OLTP connection *** | Space: object requires documentation | ||
| 106 | Connection with BW & started, IDOC type is & | Space: object requires documentation | ||
| 107 | Partner agreement to BW & exists already | Space: object requires documentation | ||
| 108 | Message type & for partner agreement with BW & already exists | Space: object requires documentation | ||
| 109 | Connection to BW & created successfully | Space: object requires documentation | ||
| 110 | No logical system exists for client & | Space: object requires documentation | ||
| 111 | Logical system name has been changed for this system | Space: object requires documentation | ||
| 112 | SAP BW client & is not the same as your logon client & | Space: object requires documentation | ||
| 113 | System manipulation!!! | Space: object requires documentation | ||
| 114 | Deleting connection to BW & | Space: object requires documentation | ||
| 115 | Connection to BW & deleted successfully | Space: object requires documentation | ||
| 116 | ALE partner &1 does not exist | The short text describes the object sufficiently | ||
| 117 | ALE port &1 does not exist | The short text describes the object sufficiently | ||
| 118 | ALE partner &1 has several different ports | The short text describes the object sufficiently | ||
| 119 | ALE partner &1 does not have any output parameters | The short text describes the object sufficiently | ||
| 120 | No RFC dest.parameters maintained for the Warehouse & in source system & | Space: object requires documentation | ||
| 121 | The basic IDoc type & is already available | Space: object requires documentation | ||
| 122 | Logical system & exists already | Space: object requires documentation | ||
| 123 | No connection between Warehouse & and source system & | Space: object requires documentation | ||
| 124 | Process code & is not known across the system | Space: object requires documentation | ||
| 125 | Name & of client & is not the same as the name & of the Warehouse | Space: object requires documentation | ||
| 126 | ALE change pointers are not set up correctly | |||
| 127 | *--------- Messages for Extraction from Archives (250-299) -------------* | |||
| 128 | Select at least one archive file | |||
| 129 | Extractor for DataSource &1 cannot be called up | |||
| 130 | No archiving object specified | |||
| 131 | Archive file selection contains errors or is empty | |||
| 132 | & & & & | Space: object requires documentation | ||
| 133 | **** Display with the Hierarchy Checks in the DC RHIE/BHIC **** | |||
| 134 | Error in program &(&) | |||
| 135 | Error in functin &(&) | |||
| 136 | Entry for basic characteristic & is incorrect, or not defined in & | |||
| 137 | Incorrect entry, or the assignment (&-&) is not defined in & | |||
| 138 | Basic characteristic & does not support any hierarchy flags in table &. | |||
| 139 | Entry does not contain any language information | |||
| 140 | Incorrect entry, or the assignment &-& is not defined in the source systm | |||
| 141 | Choose a hierarchy name | |||
| 142 | Choose an assignment for the meta data. | |||
| 143 | Currently not possible to maintain hierarchy metadata | |||
| 144 | Specify the name of the basic characteristic | |||
| 145 | Specify the name of the hierarchy class | |||
| 146 | Basic characteristic & for data element & and domain & is available | |||
| 147 | Basic characteristic & has no metadata assignment in & for hierarchies | |||
| 148 | No authorization for DataSource &1 | |||
| 149 | * Other SAPI messages | |||
| 150 | Warnings have appeared when extracting data | |||
| 151 | Information has been derived from data extraction | |||
| 152 | Initialization of extractor &1: | |||
| 153 | &1 &2 | |||
| 154 | Selection conditions for field &1 (SIGN OPTION LOW HIGH) | |||
| 155 | Fetch data package &1: &2 records, return code = &3 | |||
| 156 | Call customer enhancement &1 (&2) with &3 records | |||
| 157 | Result of customer enhancement: &1 records | |||
| 158 | Asynchronous send of data package &1 in task &2 (&3 parallel tasks) | |||
| 159 | Synchronous send of data package &1 (&2 parallel tasks) | |||
| 160 | Remote extraction is not supported for DataSource type '&1' | Space: object requires documentation | ||
| 161 | No active transfer structure exists in source system &1 for DataSource &2 | Space: object requires documentation | ||
| 162 | Asynchronous transmission of info IDoc &1 in task &2 (&3 parallel tasks) | Space: object requires documentation | ||
| 163 | Synchronized transmission of info IDoc &1 (&2 parallel tasks) | Space: object requires documentation | ||
| 164 | Direct access is not supported for hierarchy DataSource &1 | Space: object requires documentation | ||
| 165 | Errors occurred when extracting data from DataSource &1 | The short text describes the object sufficiently | ||
| 166 | Multibyte alignment; cannot initialize converter | |||
| 167 | Assigning languages to code pages from target system &1 failed: &2 | |||
| 168 | Error during multibyte alignment for language &1 (position &2) | |||
| 169 | *** Editing Hierarchies in the DC RHIE for APIs *** | |||
| 170 | Assigning the application = MCS and hierarchy class = LEGN | |||
| 171 | Functions & and & for general hierarchies in logistics must be provided | |||
| 172 | Function & does not exist in the table TFDIR | |||
| 173 | No general hierarchy in the table MCSHIERK | |||
| 174 | No basic characteristic for data element & and domain & | |||
| 175 | *----------------- Messages for Utilities ----------------------------* | |||
| 176 | Error occured when importing data from RFC container, RC = &1 | |||
| 177 | Converter not found for exchange format | |||
| 178 | Conversion of exchange format for target release &1 had errors | |||
| 179 | Conversion of exchange format for target release &1 not possible | |||
| 180 | *** Messages XPRA SAP BW 1.0 -> 1.2. delete from 1.2 *** | |||
| 181 | No Business Information Warehouse System connected -> No deletion | |||
| 182 | Removing objects for source system & and BW & |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in |