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
⤷ 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 | 000 | *** Error when processing request IDocs *** | Space: object requires documentation | |
2 | 001 | The request IDoc contains an invalid segment & | Space: object requires documentation | |
3 | 002 | Target system & is not known in the source system. | Space: object requires documentation | |
4 | 003 | Error & when sending an IDoc | Space: object requires documentation | |
5 | 004 | Object type & is not defined in the source system | Space: object requires documentation | |
6 | 005 | InfoSource & is not defined in the source system. | Space: object requires documentation | |
7 | 006 | InfoObject & is not defined in the source system | Space: object requires documentation | |
8 | 007 | No transfer structure is available for InfoSource & in the source system | Space: object requires documentation | |
9 | 008 | Incorrect call-up of the extraction program | Space: object requires documentation | |
10 | 009 | The extraction program does not support object & | Space: object requires documentation | |
11 | 010 | Selection criterion & is missing in the data request | Space: object requires documentation | |
12 | 011 | Update mode & is not supported by the extraction API | Space: object requires documentation | |
13 | 012 | InfoObject & does not support hierarchies | Space: object requires documentation | |
14 | 013 | The transfer structure for object & must be regenerated | Space: object requires documentation | |
15 | 014 | Invalid selection condition in the data request | Space: object requires documentation | |
16 | 015 | Domain & cannot be used for data extraction | Space: object requires documentation | |
17 | 016 | DataSource &1 has to be replicated (time stamp, see long text) | Space: object requires documentation | |
18 | 017 | Request IDoc does not contain any segments | Space: object requires documentation | |
19 | 018 | Request &1 does not exist in target system &2 | Space: object requires documentation | |
20 | 019 | Error & when starting the extraction program | Space: object requires documentation | |
21 | 020 | Error in customer exit & | Space: object requires documentation | |
22 | 021 | Error in BTE exit & | Space: object requires documentation | |
23 | 022 | No data available | Space: object requires documentation | |
24 | 023 | Data package &1: &2 records before call-up of customer exit | ||
25 | 024 | Data package &1: &2 records after call-up of customer exit | ||
26 | 025 | Runtime in customer exit: &1, added records: &2 | ||
27 | 026 | Request IDoc does not contain any language information | Space: object requires documentation | |
28 | 027 | Error & when generating the data transfer program | Space: object requires documentation | |
29 | 028 | Transfer structure & for InfoSource & does not contain any fields | Space: object requires documentation | |
30 | 029 | No extract structure available for object & in the source system | Space: object requires documentation | |
31 | 030 | Incomplete control parameter for commmunication with the BW system | Space: object requires documentation | |
32 | 031 | DataSource &1 does not support IDOC transfer | Space: object requires documentation | |
33 | 032 | Error in a parallel process for sending data | Space: object requires documentation | |
34 | 033 | Error when determining the transfer IDoc | Space: object requires documentation | |
35 | 034 | View & cannot be used for data extraction | Space: object requires documentation | |
36 | 036 | Data request does not contain any hierarchy names | Space: object requires documentation | |
37 | 037 | Transfer structure field not contained in DataSource | ||
38 | 038 | tRFC: Data Package = &1, TID = &2, Duration = &3, ARFCSTATE = &4 | Space: object requires documentation | |
39 | 039 | tRFC: Start = &1 &2, End = &3 &4 | Space: object requires documentation | |
40 | 040 | No message category for texts from basic characteristic & | Space: object requires documentation | |
41 | 041 | Error when reading the changes for characteristic & | Space: object requires documentation | |
42 | 042 | Error when generating the selection for characteristic & (view &) | Space: object requires documentation | |
43 | 043 | Exit: Data package = &1, interface = &2, data records before = &3 &4 | ||
44 | 044 | Exit: Data package = &1, interface = &2 | ||
45 | 045 | ***** Processing, Checking, and Transferring Hierarchies into SAPI ***** | ||
46 | 046 | Hierarchy class & is not defined in the source system | ||
47 | 050 | *** Processing and Transferring Hierarchies in the DC RHIE/BHIE *** | Space: object requires documentation | |
48 | 051 | Assignment in ROHIEBAS in source system is not correct | Space: object requires documentation | |
49 | 052 | Hierarchy flags & for basic charact. & are incorrect in the source system | Space: object requires documentation | |
50 | 053 | Requested hierarchy selection & is incorrect in the source system | Space: object requires documentation | |
51 | 054 | Function & is not supported in the source system | Space: object requires documentation | |
52 | 055 | Form routine & is not supported in the source system | Space: object requires documentation | |
53 | 056 | Requested language & is not supported in the source system | Space: object requires documentation | |
54 | 057 | Hierarchy tables not found in the source system | Space: object requires documentation | |
55 | 058 | Error when calling up the application function for hierarchies | Space: object requires documentation | |
56 | 059 | Error when calling up the customer exit function for hierarchies | Space: object requires documentation | |
57 | 060 | Error when sending hierarchy tables | Space: object requires documentation | |
58 | 061 | Unidentifiable error in program & line & | Space: object requires documentation | |
59 | 062 | Hierarchy catalog for & & & not found in the source system | Space: object requires documentation | |
60 | 063 | Hierarchy class & not defined in the source system | Space: object requires documentation | |
61 | 064 | Request &1 is to be terminated immediately at user's request | Space: object requires documentation | |
62 | 070 | *** Error when connecting BW to the source system *** | Space: object requires documentation | |
63 | 071 | No entry in table T000 for client & | Space: object requires documentation | |
64 | 072 | User could not be created in the source system | Space: object requires documentation | |
65 | 073 | RFC destination BW could not be created in the source system | Space: object requires documentation | |
66 | 074 | Entry TSPREFIX for table RSBASIDOC could not be created | Space: object requires documentation | |
67 | 075 | Source system connection was terminated | Space: object requires documentation | |
68 | 076 | Function & does not exist in the source system | Space: object requires documentation | |
69 | 077 | RFC user logon failed. Check connection &1 | Space: object requires documentation | |
70 | 078 | RFC destination &1 for BW is not maintained in source system | ||
71 | 087 | IDOC: Data Package &1, IDOC No. &2, Duration &3 | Space: object requires documentation | |
72 | 088 | IDOC: Info IDoc &1, IDoc No. &2, Duration &3 | Space: object requires documentation | |
73 | 089 | IDoc: Start = &1 &2, End = &3 &4 | Space: object requires documentation | |
74 | 099 | Unidentified error in the data transfer | Space: object requires documentation | |
75 | 100 | *** IDoc Segment Generation *** | Space: object requires documentation | |
76 | 101 | InfoSource & is not available in source system & | Space: object requires documentation | |
77 | 102 | Name of transfer structure & in BW does not match name of srce systm & | Space: object requires documentation | |
78 | 103 | When deleting transfer structure & in source system & errors occurred | Space: object requires documentation | |
79 | 104 | Error when creating transfer structure & in source system & | Space: object requires documentation | |
80 | 105 | Error when assigning transfer structure & to IDoc type & | Space: object requires documentation | |
81 | 106 | IDoc type & is not available in source system & | Space: object requires documentation | |
82 | 107 | Transfer structure & is not available in IDoc type & (&) | Space: object requires documentation | |
83 | 108 | Dictionary error when creating transfer structure & in source system & | Space: object requires documentation | |
84 | 109 | Activation error of transfer structure & in source system & | Space: object requires documentation | |
85 | 110 | InfoSource & has no transfer structure in source system & (error) | Space: object requires documentation | |
86 | 111 | InfoSource & does not have a transfer structure in source system & | Space: object requires documentation | |
87 | 112 | System prefix of the transfer structure & is in the SAP name range | Space: object requires documentation | |
88 | 113 | System prefix of the transfer structure & is in customer name range | Space: object requires documentation | |
89 | 114 | Source system release & is not compatible with extractor release & | Space: object requires documentation | |
90 | 115 | Error when generating the message type for transfer structure & | Space: object requires documentation | |
91 | 116 | Incorrect or missing entry in RSMDDELTA for basic characteristic & | Space: object requires documentation | |
92 | 117 | Delta transfer for basic characteristic &: Unknown field & ignored | Space: object requires documentation | |
93 | 118 | Incorrect object type & transferred to function & | Space: object requires documentation | |
94 | 119 | Incorrect or missing table entry for characteristic & | Space: object requires documentation | |
95 | 120 | No suitable entries found for text view & in structure & | Space: object requires documentation | |
96 | 121 | Error in delta generation & | Space: object requires documentation | |
97 | 122 | Error when removing the connection IDoc & to IDoc type & | Space: object requires documentation | |
98 | 123 | Unable to delete program & in source system & | Space: object requires documentation | |
99 | 124 | ALE message type & is not active | ||
100 | 125 | No name could be determined for the ALE message type | ||
101 | 126 | Error during generation: Incorrect DS type '&1' for program class '&2' | The short text describes the object sufficiently | |
102 | 127 | &1 entries in table &2 without a corresponding entry in &3 | The short text describes the object sufficiently | |
103 | 158 | Unable to determine a name for the transfer structure | ||
104 | 159 | Transfer structure for segment &1 not available (table ROOSGENSEG) | ||
105 | 200 | *** Logging BIW/OLTP connection *** | Space: object requires documentation | |
106 | 201 | Connection with BW & started, IDOC type is & | Space: object requires documentation | |
107 | 202 | Partner agreement to BW & exists already | Space: object requires documentation | |
108 | 203 | Message type & for partner agreement with BW & already exists | Space: object requires documentation | |
109 | 204 | Connection to BW & created successfully | Space: object requires documentation | |
110 | 205 | No logical system exists for client & | Space: object requires documentation | |
111 | 206 | Logical system name has been changed for this system | Space: object requires documentation | |
112 | 207 | SAP BW client & is not the same as your logon client & | Space: object requires documentation | |
113 | 208 | System manipulation!!! | Space: object requires documentation | |
114 | 210 | Deleting connection to BW & | Space: object requires documentation | |
115 | 211 | Connection to BW & deleted successfully | Space: object requires documentation | |
116 | 215 | ALE partner &1 does not exist | The short text describes the object sufficiently | |
117 | 216 | ALE port &1 does not exist | The short text describes the object sufficiently | |
118 | 217 | ALE partner &1 has several different ports | The short text describes the object sufficiently | |
119 | 218 | ALE partner &1 does not have any output parameters | The short text describes the object sufficiently | |
120 | 220 | No RFC dest.parameters maintained for the Warehouse & in source system & | Space: object requires documentation | |
121 | 221 | The basic IDoc type & is already available | Space: object requires documentation | |
122 | 222 | Logical system & exists already | Space: object requires documentation | |
123 | 223 | No connection between Warehouse & and source system & | Space: object requires documentation | |
124 | 224 | Process code & is not known across the system | Space: object requires documentation | |
125 | 225 | Name & of client & is not the same as the name & of the Warehouse | Space: object requires documentation | |
126 | 226 | ALE change pointers are not set up correctly | ||
127 | 250 | *--------- Messages for Extraction from Archives (250-299) -------------* | ||
128 | 251 | Select at least one archive file | ||
129 | 252 | Extractor for DataSource &1 cannot be called up | ||
130 | 253 | No archiving object specified | ||
131 | 254 | Archive file selection contains errors or is empty | ||
132 | 299 | & & & & | Space: object requires documentation | |
133 | 300 | **** Display with the Hierarchy Checks in the DC RHIE/BHIC **** | ||
134 | 301 | Error in program &(&) | ||
135 | 302 | Error in functin &(&) | ||
136 | 303 | Entry for basic characteristic & is incorrect, or not defined in & | ||
137 | 304 | Incorrect entry, or the assignment (&-&) is not defined in & | ||
138 | 305 | Basic characteristic & does not support any hierarchy flags in table &. | ||
139 | 306 | Entry does not contain any language information | ||
140 | 307 | Incorrect entry, or the assignment &-& is not defined in the source systm | ||
141 | 308 | Choose a hierarchy name | ||
142 | 309 | Choose an assignment for the meta data. | ||
143 | 310 | Currently not possible to maintain hierarchy metadata | ||
144 | 311 | Specify the name of the basic characteristic | ||
145 | 312 | Specify the name of the hierarchy class | ||
146 | 313 | Basic characteristic & for data element & and domain & is available | ||
147 | 314 | Basic characteristic & has no metadata assignment in & for hierarchies | ||
148 | 325 | No authorization for DataSource &1 | ||
149 | 400 | * Other SAPI messages | ||
150 | 401 | Warnings have appeared when extracting data | ||
151 | 402 | Information has been derived from data extraction | ||
152 | 403 | Initialization of extractor &1: | ||
153 | 404 | &1 &2 | ||
154 | 405 | Selection conditions for field &1 (SIGN OPTION LOW HIGH) | ||
155 | 406 | Fetch data package &1: &2 records, return code = &3 | ||
156 | 407 | Call customer enhancement &1 (&2) with &3 records | ||
157 | 408 | Result of customer enhancement: &1 records | ||
158 | 409 | Asynchronous send of data package &1 in task &2 (&3 parallel tasks) | ||
159 | 410 | Synchronous send of data package &1 (&2 parallel tasks) | ||
160 | 411 | Remote extraction is not supported for DataSource type '&1' | Space: object requires documentation | |
161 | 412 | No active transfer structure exists in source system &1 for DataSource &2 | Space: object requires documentation | |
162 | 413 | Asynchronous transmission of info IDoc &1 in task &2 (&3 parallel tasks) | Space: object requires documentation | |
163 | 414 | Synchronized transmission of info IDoc &1 (&2 parallel tasks) | Space: object requires documentation | |
164 | 415 | Direct access is not supported for hierarchy DataSource &1 | Space: object requires documentation | |
165 | 416 | Errors occurred when extracting data from DataSource &1 | The short text describes the object sufficiently | |
166 | 420 | Multibyte alignment; cannot initialize converter | ||
167 | 421 | Assigning languages to code pages from target system &1 failed: &2 | ||
168 | 422 | Error during multibyte alignment for language &1 (position &2) | ||
169 | 500 | *** Editing Hierarchies in the DC RHIE for APIs *** | ||
170 | 501 | Assigning the application = MCS and hierarchy class = LEGN | ||
171 | 502 | Functions & and & for general hierarchies in logistics must be provided | ||
172 | 503 | Function & does not exist in the table TFDIR | ||
173 | 504 | No general hierarchy in the table MCSHIERK | ||
174 | 505 | No basic characteristic for data element & and domain & | ||
175 | 700 | *----------------- Messages for Utilities ----------------------------* | ||
176 | 701 | Error occured when importing data from RFC container, RC = &1 | ||
177 | 702 | Converter not found for exchange format | ||
178 | 703 | Conversion of exchange format for target release &1 had errors | ||
179 | 704 | Conversion of exchange format for target release &1 not possible | ||
180 | 800 | *** Messages XPRA SAP BW 1.0 -> 1.2. delete from 1.2 *** | ||
181 | 801 | No Business Information Warehouse System connected -> No deletion | ||
182 | 802 | Removing objects for source system & and BW & |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |