SAP ABAP Message Class EA (IDoc Basis Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Attributes
Message class | EA | |
Short Description | IDoc Basis Messages | |
Changed On | 20140121 | |
Last Changed At | 103715 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | -->> Display linked objects <<-- | ||
2 | 001 | Process code & of type & | The short text describes the object sufficiently | |
3 | 002 | Old process codes no longer exist in the system | The short text describes the object sufficiently | |
4 | 004 | Error when writing statistic record | Space: object requires documentation | |
5 | 007 | Report RSEIDOCM is scheduled, but obsolete. | Space: object requires documentation | |
6 | 010 | Internal error | Space: object requires documentation | |
7 | 011 | Function is only supported for IDoc record types SAP Release 4.x | The short text describes the object sufficiently | |
8 | 012 | Queue processing is not supported for version 3.x | The short text describes the object sufficiently | |
9 | 015 | Object & not found | Space: object requires documentation | |
10 | 020 | No IDocs linked | Space: object requires documentation | |
11 | 025 | Object type & object & unknown | Space: object requires documentation | |
12 | 030 | --> Messages from function group EDII (IDoc conversion for Office) | ||
13 | 031 | Object type & is not known | ||
14 | 032 | IDoc & could not be read | ||
15 | 035 | Errors occurred during conversion | ||
16 | 036 | Function module EDI_IDOC_R3I_OUTGOING can only process references | Space: object requires documentation | |
17 | 037 | Function module EDI_IDOC_R3I_INCOMING can only process IDoc data | Space: object requires documentation | |
18 | 038 | Conversion error: segment too long | ||
19 | 039 | Length entry & is invalid | Space: object requires documentation | |
20 | 041 | '&' File Has Not Been Accepted for Processing | Space: object requires documentation | |
21 | 042 | '&' File Has Not Been Accepted for Processing | Space: object requires documentation | |
22 | 050 | -> Send messages via Internet | ||
23 | 051 | Error occurred while sending IDoc via Internet | Space: object requires documentation | |
24 | 052 | IDoc could not be sent | Space: object requires documentation | |
25 | 053 | IDoc sent via Internet | Space: object requires documentation | |
26 | 054 | Office function module showed return code '&'. | ||
27 | 055 | Created IDoc '&' was sent via the Internet | ||
28 | 056 | Created IDoc '&' could not be sent via the Internet | ||
29 | 057 | Receiver port '&' is not an Internet port in the current client | ||
30 | 060 | -> Outbound procg via background task | Space: object requires documentation | |
31 | 061 | IDoc '&' was created and forwarded for transmission | Space: object requires documentation | |
32 | 066 | Messages from IDoc processing can be found in application log | Space: object requires documentation | |
33 | 067 | Display of all data records not possible | Space: object requires documentation | |
34 | 070 | -> Export to R/2 | Space: object requires documentation | |
35 | 071 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | |
36 | 072 | IDoc '&' was sent to R/2 System | Space: object requires documentation | |
37 | 073 | IDoc sent to R/2 System | Space: object requires documentation | |
38 | 074 | qRFC used to send IDoc to SAP system | Space: object requires documentation | |
39 | 075 | IDoc received via qRFC | Space: object requires documentation | |
40 | 076 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | |
41 | 077 | IDoc written to file | Space: object requires documentation | |
42 | 078 | IDoc '&' written to file | Space: object requires documentation | |
43 | 079 | Incorrect parameter combination when calling EDI_OUTPUT_NEW | Space: object requires documentation | |
44 | 080 | Internal error: Program &, command & | Space: object requires documentation | |
45 | 081 | Error occurred while IDoc '&' was being sent | Space: object requires documentation | |
46 | 082 | IDoc '&' sent to SAP system | Space: object requires documentation | |
47 | 083 | IDoc sent to SAP system or external program | Space: object requires documentation | |
48 | 084 | Error while writing IDoc to file | Space: object requires documentation | |
49 | 085 | Error while sending IDoc (conversion error) | Space: object requires documentation | |
50 | 086 | Internal error | Space: object requires documentation | |
51 | 087 | Internal error - generated file & may not be processed | Space: object requires documentation | |
52 | 088 | IDoc sent to Internet address | Space: object requires documentation | |
53 | 089 | IDoc '&' sent to Internet address | Space: object requires documentation | |
54 | 090 | IDoc '&' transferred to function module '&' | Space: object requires documentation | |
55 | 091 | IDoc '&' transferred to ABAP-PSS port | Space: object requires documentation | |
56 | 092 | IDoc has been written in XML format in a file | Space: object requires documentation | |
57 | 093 | IDoc cannot be sent to an XML port | Space: object requires documentation | |
58 | 094 | IDoc cannot be sent in XML format | Space: object requires documentation | |
59 | 095 | IDoc sent by HTTP in XML format | Space: object requires documentation | |
60 | 096 | Error when sending by HTTP | Space: object requires documentation | |
61 | 097 | IDoc '&' has already been received, therefore reception is refused | Space: object requires documentation | |
62 | 098 | Communication error when sending with HTTP | Space: object requires documentation | |
63 | 099 | The expected 'encoding="UTF-8" has not been sent, therefore refused | Space: object requires documentation | |
64 | 100 | -->>Archiving programs<<-- | ||
65 | 101 | Unknown direction | Space: object requires documentation | |
66 | 102 | Enter period with length greater than zero | Space: object requires documentation | |
67 | 103 | Time conflict | Space: object requires documentation | |
68 | 104 | Only positive entries allowed | Space: object requires documentation | |
69 | 105 | No time unit entered | Space: object requires documentation | |
70 | 106 | No IDocs found for selection criteria | Space: object requires documentation | |
71 | 107 | Settings saved | The short text describes the object sufficiently | |
72 | 110 | You can only select relationship types for this function | Space: object requires documentation | |
73 | 111 | You can only select message types for this function | Space: object requires documentation | |
74 | 112 | All Message Types are Excluded for this Relationship Type | Space: object requires documentation | |
75 | 114 | IDoc queue '&1' of sender '&2' not processed completely | The short text describes the object sufficiently | |
76 | 115 | IDoc set to queue status again after edit | The short text describes the object sufficiently | |
77 | 120 | IDoc archived | ||
78 | 121 | IDoc reloaded | ||
79 | 122 | Error while setting status for container '&' with IDoc links | Space: object requires documentation | |
80 | 123 | No queue entries selected | The short text describes the object sufficiently | |
81 | 124 | Select an IDoc number by clicking a link | Space: object requires documentation | |
82 | 125 | Select a queue name by clicking a link | The short text describes the object sufficiently | |
83 | 126 | All IDocs in queue '&' sent to receiving port '&' by qRFC | The short text describes the object sufficiently | |
84 | 127 | Queue '&' sent to port '&' in separate task | The short text describes the object sufficiently | |
85 | 128 | IDoc '&' no longer in IDoc outbound queue. Refresh the queue. | Space: object requires documentation | |
86 | 129 | IDoc removed from outbound queue | Space: object requires documentation | |
87 | 130 | IDoc &1 removed from outbound queue &2 | The short text describes the object sufficiently | |
88 | 131 | IDoc &1 set to status '31' and removed from outbound queue &2 | The short text describes the object sufficiently | |
89 | 132 | IDoc '&' no longer in IDoc inbound queue. Refresh the queue. | The short text describes the object sufficiently | |
90 | 133 | IDoc removed from inbound queue | Space: object requires documentation | |
91 | 134 | IDoc &1 set to status '68' and removed from inbound queue &2 | The short text describes the object sufficiently | |
92 | 135 | IDoc &1 removed from inbound queue &2 | The short text describes the object sufficiently | |
93 | 136 | Function module for processing queue missing in target system | Space: object requires documentation | |
94 | 137 | Rule name '&1' does not exist | Space: object requires documentation | |
95 | 138 | Command file not maintained | Space: object requires documentation | |
96 | 139 | Also maintain command file for logical file | Space: object requires documentation | |
97 | 140 | -> Further messages port maintenance | Space: object requires documentation | |
98 | 141 | No folder exists for saved folder ID | Space: object requires documentation | |
99 | 142 | Access to a stored directory not possible in this environment | Space: object requires documentation | |
100 | 143 | Logical directory '&' has not been defined in the SAP System | Space: object requires documentation | |
101 | 144 | Also maintain the function module for the logical directory | Space: object requires documentation | |
102 | 145 | The possible entry is only possible for 'logical directory' | Space: object requires documentation | |
103 | 146 | Enter a logical directory | Space: object requires documentation | |
104 | 147 | Port & already exists and could not be created | Space: object requires documentation | |
105 | 148 | Save the port first! | Space: object requires documentation | |
106 | 149 | Port '&' was created and not saved! Deletion not possible! | Space: object requires documentation | |
107 | 150 | -> continue FuGr EDI1 | Space: object requires documentation | |
108 | 151 | IDoc '&' should be opened again in EDIT mode | Space: object requires documentation | |
109 | 152 | No data records to be edited could be found for IDoc '&' | Space: object requires documentation | |
110 | 153 | IDoc '&' has no data record with number '&' | Space: object requires documentation | |
111 | 154 | Error while updating data records for IDoc '&' | Space: object requires documentation | |
112 | 155 | Direction cannot be changed when modifying control record | Space: object requires documentation | |
113 | 156 | This IDoc cannot be changed | Space: object requires documentation | |
114 | 157 | This IDoc has been generated through a test transaction | Space: object requires documentation | |
115 | 158 | This IDoc data record cannot be edited - field is too long | Space: object requires documentation | |
116 | 159 | You Are Not Authorized to Edit This IDoc | Space: object requires documentation | |
117 | 160 | No IDocs Were Transferred for Display | Space: object requires documentation | |
118 | 161 | IDoc created without syntax check | The short text describes the object sufficiently | |
119 | 163 | It was not possible to send any IDoc | Space: object requires documentation | |
120 | 164 | '&' IDocs in queue '&' were sent by qRFC to destination '&' | The short text describes the object sufficiently | |
121 | 165 | You will find detailed information in the previous status records | The short text describes the object sufficiently | |
122 | 166 | '&' IDoc(s) set to status '31' and removed from outbound queue | The short text describes the object sufficiently | |
123 | 167 | '&' IDoc(s) set to status '68' and removed from inbound queue | The short text describes the object sufficiently | |
124 | 168 | '&' IDoc(s) removed from outbound queue | The short text describes the object sufficiently | |
125 | 169 | '&' IDoc(s) removed from inbound queue | The short text describes the object sufficiently | |
126 | 170 | --> Where-used list for segments | Space: object requires documentation | |
127 | 171 | Where-used list for IDoc segments | Space: object requires documentation | |
128 | 172 | System & Date & Time & | Space: object requires documentation | |
129 | 173 | Segment type & (&) | Space: object requires documentation | |
130 | 174 | Use in basic types: | Space: object requires documentation | |
131 | 175 | & (&) | Space: object requires documentation | |
132 | 176 | Use in extensions: | Space: object requires documentation | |
133 | 177 | All segments | Space: object requires documentation | |
134 | 178 | Unused segments | Space: object requires documentation | |
135 | 179 | Used segments | Space: object requires documentation | |
136 | 181 | Immediate Processing Not Possible | Space: object requires documentation | |
137 | 182 | Immediate Processing Was Not Possible | Space: object requires documentation | |
138 | 183 | Immediate Processing was Canceled | Space: object requires documentation | |
139 | 184 | Immediate Processing Was Not Possible | Space: object requires documentation | |
140 | 185 | Immediate Processing was Canceled | Space: object requires documentation | |
141 | 186 | Immediate Processing Was Not Possible | Space: object requires documentation | |
142 | 187 | Immediate Processing in Job '&' | Space: object requires documentation | |
143 | 188 | Immediate processing through bgRRC was triggered | Space: object requires documentation | |
144 | 189 | User &1 is already processing the configuration | The short text describes the object sufficiently | |
145 | 190 | --> Messages from AFTER_IMP-Methods for IDoc types | Space: object requires documentation | |
146 | 191 | Program ID &, object type & not processed | Space: object requires documentation | |
147 | 192 | Object name is blank | Space: object requires documentation | |
148 | 193 | Entries for & in table EDISYN were deleted | Space: object requires documentation | |
149 | 194 | No entries for & had to be deleted | Space: object requires documentation | |
150 | 200 | >>>> Messages from EDIJ/ Automatic creation of IDoc segments | ||
151 | 201 | Error while creating table '&' entry '&' | Space: object requires documentation | |
152 | 202 | Error while changing table '&' entry '&' | Space: object requires documentation | |
153 | 203 | Error while deleting table '&' entry '&' | Space: object requires documentation | |
154 | 204 | Internal error & | ||
155 | 205 | Source structure '&' in ABAP/4 Dictionary has status '&' | ||
156 | 206 | Segment with description '&' already exists in ABAP/4 Dictionary | ||
157 | 207 | Source structure '&' is unknown in ABAP Repository | Space: object requires documentation | |
158 | 208 | Source structure '&' has no fields in ABAP Repository | Space: object requires documentation | |
159 | 209 | Target structure '&' exceeds maximum length of 1000 bytes | ||
160 | 210 | Segment locked in transport '&', order '&' | ||
161 | 211 | Segment placed in transport '&', order '&' | ||
162 | 212 | Name of source structure not entered | ||
163 | 213 | Dictionary structure '&' could not be created | Space: object requires documentation | |
164 | 214 | Creation of IDoc segment for source structure '&' canceled | ||
165 | 215 | Activation of IDoc segment for source structure '&' canceled | ||
166 | 216 | Creation of IDoc segment for source struct. '&' completed successfully | ||
167 | 217 | Unknown ABAP data type '&' | ||
168 | 218 | Deletion of '&' was not completed successfully | ||
169 | 219 | Name of source structure '&' could not be transferred completely | ||
170 | 220 | Table entries for segment for structure '&' exist already | ||
171 | 221 | Maintain the fields of segment & in the segment editor. | Space: object requires documentation | |
172 | 222 | Processing canceled by user | Space: object requires documentation | |
173 | 223 | Enter an object name | Space: object requires documentation | |
174 | 224 | Basic type '&' is unknown | Space: object requires documentation | |
175 | 226 | Extension '&' is unknown | Space: object requires documentation | |
176 | 227 | Extended basic type '&' is unknown | Space: object requires documentation | |
177 | 228 | Development class & has integration system & | Space: object requires documentation | |
178 | 229 | Segment & exists already | Space: object requires documentation | |
179 | 230 | Error while creating segment & | Space: object requires documentation | |
180 | 231 | Development class & is unknown | Space: object requires documentation | |
181 | 232 | Length determination for data element & failed | Space: object requires documentation | |
182 | 233 | Data element & is unknown | Space: object requires documentation | |
183 | 234 | Data element & is not active | Space: object requires documentation | |
184 | 235 | Segment '&' : Internal error & | Space: object requires documentation | |
185 | 236 | Segment '&' : Dictionary structure unknown | Space: object requires documentation | |
186 | 237 | Error while deleting segment & | Space: object requires documentation | |
187 | 238 | Segment & does not exist | Space: object requires documentation | |
188 | 239 | Error while changing segment & | Space: object requires documentation | |
189 | 240 | Activate segment & in dictionary failed | Space: object requires documentation | |
190 | 241 | Change segment & in Dictionary failed | Space: object requires documentation | |
191 | 242 | Error while changing segment & | Space: object requires documentation | |
192 | 243 | Error during existence check for segment & | Space: object requires documentation | |
193 | 244 | Error while releasing segment & | Space: object requires documentation | |
194 | 245 | Transferred structure has different field names, field & | Space: object requires documentation | |
195 | 246 | Segment definition & unknown | Space: object requires documentation | |
196 | 247 | Segment definition & has been released and cannot be deleted | Space: object requires documentation | |
197 | 248 | Segment type cannot have same name as source structure & | Space: object requires documentation | |
198 | 249 | No segment type entered | Space: object requires documentation | |
199 | 250 | No segment structure entered | Space: object requires documentation | |
200 | 251 | Last segment definition & not released | Space: object requires documentation | |
201 | 252 | Segment & defined locally, development class & | Space: object requires documentation | |
202 | 253 | First segment definition in segment & cannot be deleted | Space: object requires documentation | |
203 | 254 | Segment definition & has been released and cannot be deleted | Space: object requires documentation | |
204 | 255 | Last segment definition & has been released and cannot be changed | Space: object requires documentation | |
205 | 256 | Name range violation : Name & not permitted in & system | Space: object requires documentation | |
206 | 257 | Segment &1 is unknown in Release &2/&3 | Space: object requires documentation | |
207 | 258 | External segment name & cannot be interpreted | Space: object requires documentation | |
208 | 259 | Error while resetting release of segment & | Space: object requires documentation | |
209 | 260 | Object directory entry with development class & could not be generated | Space: object requires documentation | |
210 | 261 | Transferred structure longer than existing structure, line & | Space: object requires documentation | |
211 | 262 | Transferred structure contains different data element, line & | Space: object requires documentation | |
212 | 263 | Maximum length of segment is 1000 characters, current length is & | Space: object requires documentation | |
213 | 264 | Error while generating check log for segment & | Space: object requires documentation | |
214 | 265 | Segment definition for current release &1/&2 already exists | Space: object requires documentation | |
215 | 266 | Change segment table for & failed | Space: object requires documentation | |
216 | 267 | Error while changing segment definitions for & | Space: object requires documentation | |
217 | 268 | Error while updating segment table for & | Space: object requires documentation | |
218 | 269 | Name range violation : Name & not permitted in & system | Space: object requires documentation | |
219 | 270 | Name '&' contains no valid prefix | Space: object requires documentation | |
220 | 271 | Name '&' does not correspond to naming convention | Space: object requires documentation | |
221 | 272 | Error in transport connection | Space: object requires documentation | |
222 | 273 | No entry in conversion table for external segment name &1 | Space: object requires documentation | |
223 | 274 | No entry in conversion table for external segment name &1 | Space: object requires documentation | |
224 | 275 | Unknown IDoc control record type: '&' | Space: object requires documentation | |
225 | 276 | Segment definition & already exists for Release & | Space: object requires documentation | |
226 | 277 | No object dictionary entry available for & | Space: object requires documentation | |
227 | 278 | '&' entries changed in segment table | Space: object requires documentation | |
228 | 279 | New segment definition '&' has no additional fields | Space: object requires documentation | |
229 | 280 | A released definition already exists for '&3' in Release &1/&2 | Space: object requires documentation | |
230 | 281 | Released segment definitions already exist for segment & | Space: object requires documentation | |
231 | 282 | Current segment definition is already released for segment & | Space: object requires documentation | |
232 | 283 | The DTD cannot be generated | Space: object requires documentation | |
233 | 284 | The DTD cannot be generated | Space: object requires documentation | |
234 | 290 | --> Messages from forwarding (FuGr EDIFORWARD) | Space: object requires documentation | |
235 | 291 | Outbound IDoc & sent to system & | Space: object requires documentation | |
236 | 293 | -> Unicode outbound processing | Space: object requires documentation | |
237 | 294 | Conversion error occurred for OPEN DATASET | Space: object requires documentation | |
238 | 295 | IDoc file with replacement character | Space: object requires documentation | |
239 | 296 | Segment & was written in the file with the replacement character | Space: object requires documentation | |
240 | 297 | Control record was written in the file with the replacement character | Space: object requires documentation | |
241 | 298 | Could not write IDoc to file | Space: object requires documentation | |
242 | 299 | Could not write IDoc to file | Space: object requires documentation | |
243 | 300 | *** Messages for SAPLEDID | ||
244 | 301 | No segment definition exists for segment type & | Space: object requires documentation | |
245 | 302 | Segment type & does not exist | Space: object requires documentation | |
246 | 303 | Structure of IDoc type & could not be found | Space: object requires documentation | |
247 | 304 | IDoc type &, object type & is unknown | Space: object requires documentation | |
248 | 305 | Error reading fixed values from table & field & | ||
249 | 306 | Object type & is unknown | ||
250 | 307 | IDoc type & is unknown in Release & | Space: object requires documentation | |
251 | 308 | Description for IDoc basic type & not found | Space: object requires documentation | |
252 | 309 | Segment & is unknown | ||
253 | 310 | Structure of segment & is unknown | ||
254 | 311 | Segment & is inconsistent | ||
255 | 312 | Segment &1 is unknown in Release &2/&3 | Space: object requires documentation | |
256 | 313 | Data for segments for IDoc type &, object type & is incomplete | Space: object requires documentation | |
257 | 314 | Structure of IDoc type &, object type & is unknown | Space: object requires documentation | |
258 | 315 | Attributes for segment & is unknown | ||
259 | 316 | Field in segment & is unknown | ||
260 | 317 | Domain & for data element & is unknown | ||
261 | 318 | Error reaading IDoc record structures | ||
262 | 319 | Internal error in API for IDoc documentation tools | ||
263 | 320 | Export canceled by user | Space: object requires documentation | |
264 | 321 | Error opening file '&' in directory '&' | ||
265 | 322 | Error while writing to file '&' in directory '&' | ||
266 | 323 | Error while creating file '&' in directory '&' | ||
267 | 324 | '&' is not an IDoc segment | ||
268 | 325 | Inconsistent data for IDoc type '&' | ||
269 | 326 | Export to directory '&', file(s) '&' completed successfully | ||
270 | 327 | Export to directory '&', file '&.h' completed successfully | ||
271 | 328 | Record type & unknown | ||
272 | 329 | Version & unknown | ||
273 | 330 | No IDoc types for SAP Release '&' found | ||
274 | 331 | Texts for IDoc types could not be read in language '&'. | ||
275 | 332 | Required format '&' is not supported | ||
276 | 333 | Some data not found | ||
277 | 334 | Invalid directory '&' | ||
278 | 335 | Presentation server error | ||
279 | 336 | Directory '&' could not be checked | ||
280 | 337 | No valid working directory found | ||
281 | 338 | No file name entered | ||
282 | 339 | List of IDoc types in HTML format created in directory '&', file '&' | Space: object requires documentation | |
283 | 340 | Foreign key for structure '&1', field '&2' cannot be evaluated | Space: object requires documentation | |
284 | 341 | Data element '&1' of field '&2' unknown | Space: object requires documentation | |
285 | 342 | Extension &1 is not linked to any basic types | Space: object requires documentation | |
286 | 343 | Extension &1 is not assigned to basic type &2 | Space: object requires documentation | |
287 | 344 | Description for extension & not found | Space: object requires documentation | |
288 | 345 | The format selected is not supported for the objects selected | Space: object requires documentation | |
289 | 346 | Make a selection | Space: object requires documentation | |
290 | 347 | Errors occurred in the control framework | Space: object requires documentation | |
291 | 348 | Object name missing (enter a name) | Space: object requires documentation | |
292 | 350 | ----> Segments consistency check | Space: object requires documentation | |
293 | 351 | Segment &1 has repository structure in status &2 | Space: object requires documentation | |
294 | 352 | Entries missing in table of &2 for segment &1 | Space: object requires documentation | |
295 | 353 | Last user to make changes in repository &1, last user to change seg. &2 | Space: object requires documentation | |
296 | 354 | Time of last change in repository &1, time of last change to segment &2 | Space: object requires documentation | |
297 | 355 | No. of fields in repository structure &1, no. of fields in segment &2 | Space: object requires documentation | |
298 | 356 | Field name in repository '&1', field name in segment '&2', position &3 | Space: object requires documentation | |
299 | 357 | Field &1: External length &2 smaller than &3 for appl. data element &4 | Space: object requires documentation | |
300 | 358 | Field &1: External length &2 larger than &3 for appl. data element &4 | Space: object requires documentation | |
301 | 359 | Segment version &1 contains more/less fields (&2) than structure (&3) | Space: object requires documentation | |
302 | 360 | Inconsistent overall length in segment version &1 | Space: object requires documentation | |
303 | 361 | Segment version & not released | Space: object requires documentation | |
304 | 362 | Segment & has no short text | Space: object requires documentation | |
305 | 363 | Repository structure missing for segment & | Space: object requires documentation | |
306 | 364 | Segment & consistent | Space: object requires documentation | |
307 | 365 | Check segment & | Space: object requires documentation | |
308 | 366 | Segment & has no object dictionary entry | Space: object requires documentation | |
309 | 367 | Object dictionary entry for segment & has no development class | Space: object requires documentation | |
310 | 368 | Field &1, data element &2 with length problem | Space: object requires documentation | |
311 | 369 | Field &1, data element &2 with length problem | Space: object requires documentation | |
312 | 370 | & is an SAP segment | Space: object requires documentation | |
313 | 371 | Entries exist in table of &2 for segment &1 | Space: object requires documentation | |
314 | 372 | Segment & consistent with warnings | Space: object requires documentation | |
315 | 373 | Segment & is inconsistent | Space: object requires documentation | |
316 | 374 | Inconsistency in segment structure table, segment '&1', field '&2' | Space: object requires documentation | |
317 | 380 | Could not write IDoc inbound queue | The short text describes the object sufficiently | |
318 | 381 | Queue &1 started. &2 IDoc(s) posted successfully. | Space: object requires documentation | |
319 | 382 | Queue & started | The short text describes the object sufficiently | |
320 | 383 | Queue & not started. First IDoc had error status. | The short text describes the object sufficiently | |
321 | 384 | Queue &1 started. &2 of &3 IDoc(s) processed. | The short text describes the object sufficiently | |
322 | 385 | Incorrect interface of function module | The short text describes the object sufficiently | |
323 | 386 | IDocs are stored in the queue | The short text describes the object sufficiently | |
324 | 387 | &1 IDoc(s) in queue &2 given error status and deleted from queue | The short text describes the object sufficiently | |
325 | 388 | &1 IDoc(s) in queue &2 deleted from queue | The short text describes the object sufficiently | |
326 | 390 | Problem with SOAP class | Space: object requires documentation | |
327 | 391 | No IDoc saved in target system (SOAP HTTP) | Space: object requires documentation | |
328 | 392 | IDoc sent with SOAP HTTP | Space: object requires documentation | |
329 | 393 | No XML fragment specified | The short text describes the object sufficiently | |
330 | 400 | >>> Messages for IDoc test tool <<< | ||
331 | 401 | IDoc type & does not exist | ||
332 | 402 | Internal error while selecting IDoc types | ||
333 | 403 | No IDoc selection possible (too many IDoc types). Please enter directly. | ||
334 | 404 | IDoc tree could not be constructed (internal error) | ||
335 | 405 | No segments in clipboard | ||
336 | 406 | IDoc & was saved but cannot or should not be processed | Space: object requires documentation | |
337 | 407 | Function modules up to Release 2.x are not supported | ||
338 | 408 | Interface for function & is incorrect | ||
339 | 409 | & is not a valid function module | ||
340 | 410 | IDoc & was saved and processed by function & | ||
341 | 411 | IDoc & contains errors. No hierarchies can be displayed. | ||
342 | 412 | Segment(s) transferred to clipboard | ||
343 | 413 | Following IDoc type serves as template: & | ||
344 | 414 | Pattern IDoc written to database. Not defined for processing. | Space: object requires documentation | |
345 | 415 | IDoc saved to file | ||
346 | 416 | IDoc saved to file and file forwarded for IDoc inbound processing | ||
347 | 417 | Error trying to write file (OPEN_DATASET) | Space: object requires documentation | |
348 | 418 | Error while writing IDoc data to file | ||
349 | 419 | Entry for no. of IDocs is missing. IDoc written to file. | Space: object requires documentation | |
350 | 420 | Entry for no. of IDocs is missing. IDoc written to file. | Space: object requires documentation | |
351 | 421 | No authorization for writing to file & | Space: object requires documentation | |
352 | 422 | IDoc & was saved but cannot or should not be sent | Space: object requires documentation | |
353 | 423 | IDoc created using test tool by user & | Space: object requires documentation | |
354 | 424 | IDoc no. & saved in database | Space: object requires documentation | |
355 | 425 | No authorization to open file & | Space: object requires documentation | |
356 | 426 | & is processed by altogether & IDocs. | Space: object requires documentation | |
357 | 427 | Check time format | Space: object requires documentation | |
358 | 428 | No IDoc was found in file &. | Space: object requires documentation | |
359 | 429 | The IDoc syntax is correct. | Space: object requires documentation | |
360 | 430 | Inbound IDoc: CCMS statistic update failed. | Space: object requires documentation | |
361 | 431 | No file is generated as the status and IDoc numbers are empty. | Space: object requires documentation | |
362 | 432 | Conversion error when reading from the file '&' | Space: object requires documentation | |
363 | 433 | Use IDoc Test Tool in a productive client | The short text describes the object sufficiently | |
364 | 439 | Characters cannot be displayed in the requested code page. | Space: object requires documentation | |
365 | 440 | --> Messages from API for IDoc types | Space: object requires documentation | |
366 | 441 | Basic type & is locked by user & | Space: object requires documentation | |
367 | 442 | Extension & is locked by user & | Space: object requires documentation | |
368 | 443 | Lock failed (system error) | Space: object requires documentation | |
369 | 444 | You have no authorization for basic types (activity &) | Space: object requires documentation | |
370 | 445 | You have no authorization for extensions (activity &) | Space: object requires documentation | |
371 | 446 | Extension & does not exist | Space: object requires documentation | |
372 | 447 | Basic type & does not exist | Space: object requires documentation | |
373 | 448 | Segments are not numbered sequentially | Space: object requires documentation | |
374 | 449 | Basic type & contains no segments | Space: object requires documentation | |
375 | 450 | Extension & contains no segments | Space: object requires documentation | |
376 | 451 | Extension & is already released | Space: object requires documentation | |
377 | 452 | Basic type & is already released | Space: object requires documentation | |
378 | 453 | Predecessor & of extension & is not released | Space: object requires documentation | |
379 | 454 | Predecessor & of basic type & is not released | Space: object requires documentation | |
380 | 455 | Basic type & could not be changed | Space: object requires documentation | |
381 | 456 | Basic type & could not be created | Space: object requires documentation | |
382 | 457 | Extension & could not be changed | Space: object requires documentation | |
383 | 458 | Extension & could not be created | Space: object requires documentation | |
384 | 459 | Extension & has been released and cannot be deleted | Space: object requires documentation | |
385 | 460 | Basic type & has been released and cannot be deleted | Space: object requires documentation | |
386 | 461 | & already has successor & | ||
387 | 462 | & already has successor & | ||
388 | 463 | Extension & could not be deleted | Space: object requires documentation | |
389 | 464 | Basic type & could not be deleted | Space: object requires documentation | |
390 | 465 | Basic type & has successor & | Space: object requires documentation | |
391 | 466 | Basic type & is not released | Space: object requires documentation | |
392 | 467 | Extension & has successor & | Space: object requires documentation | |
393 | 468 | Extension & is not released | Space: object requires documentation | |
394 | 469 | Entry in EDBAS for basic type & is inconsistent | Space: object requires documentation | |
395 | 470 | Entry in EDCIM for extension & is inconsistent | Space: object requires documentation | |
396 | 471 | No basic types exist in system | Space: object requires documentation | |
397 | 472 | No suitable basic types found for extension & | Space: object requires documentation | |
398 | 473 | Extensions are available for basic type & | Space: object requires documentation | |
399 | 474 | Check basic type & | Space: object requires documentation | |
400 | 475 | Check extension & | Space: object requires documentation | |
401 | 476 | Extension & exists | Space: object requires documentation | |
402 | 477 | Basic type & exists | Space: object requires documentation | |
403 | 478 | Segment & exists | Space: object requires documentation | |
404 | 479 | Several basic types are assigned to extension & (see long text) | Space: object requires documentation | |
405 | 480 | Basic type & exists already | Space: object requires documentation | |
406 | 481 | Extension & exists already | Space: object requires documentation | |
407 | 482 | Segment type & is still used | Space: object requires documentation | |
408 | 483 | & is an SAP basic type | Space: object requires documentation | |
409 | 484 | Basic type & has been generated and cannot be deleted | Space: object requires documentation | |
410 | 485 | Extension & has been generated and cannot be deleted | Space: object requires documentation | |
411 | 486 | View & exists already | Space: object requires documentation | |
412 | 487 | View & could not be created | Space: object requires documentation | |
413 | 488 | View & does not exist | Space: object requires documentation | |
414 | 489 | View & is locked by user & | Space: object requires documentation | |
415 | 490 | View & could not be modified | Space: object requires documentation | |
416 | 491 | View & could not be deleted | Space: object requires documentation | |
417 | 492 | View & refers to basic type &, which has not been released | Space: object requires documentation | |
418 | 493 | View & refers to extension &, which has not been released | Space: object requires documentation | |
419 | 494 | Extension & is not linked to basic type & | Space: object requires documentation | |
420 | 495 | Segment & cannot be included in view | Space: object requires documentation | |
421 | 496 | View already contains this segment | Space: object requires documentation | |
422 | 497 | View does not contain this segment | Space: object requires documentation | |
423 | 498 | Segment & cannot be deleted from this view | Space: object requires documentation | |
424 | 499 | You do not have authorization for views (activity &) | Space: object requires documentation | |
425 | 500 | Consider the consequences of your changes to &, see long text | Space: object requires documentation | |
426 | 501 | Enter a valid application | ||
427 | 502 | Combination of application and output type does not exist | ||
428 | 503 | Assignments of basic type & to views are available | Space: object requires documentation | |
429 | 504 | Assignments of extension & to views are available | Space: object requires documentation | |
430 | 505 | Basic type for a released extension is to be changed | Space: object requires documentation | |
431 | 506 | The release of the basis types cannot be reset | Space: object requires documentation | |
432 | 507 | The release of the extension cannot be reset | Space: object requires documentation | |
433 | 510 | --> Additional messages from FuGr EDI8 (E0) | Space: object requires documentation | |
434 | 511 | Extension & is already assigned to basic type & | Space: object requires documentation | |
435 | 512 | Extension & is not assigned to any basic type | Space: object requires documentation | |
436 | 513 | Enter extension | Space: object requires documentation | |
437 | 514 | Object & lies in customer name range | Space: object requires documentation | |
438 | 515 | Object & lies in SAP name range | Space: object requires documentation | |
439 | 530 | --> Messages from conversion of IDoc types and messages | Space: object requires documentation | |
440 | 531 | Basic type & exists already | Space: object requires documentation | |
441 | 532 | Short extension name & should not exist as extension | Space: object requires documentation | |
442 | 533 | Short logical message type & should not exist as message type | Space: object requires documentation | |
443 | 534 | & status process code(s) would be changed | The short text describes the object sufficiently | |
444 | 535 | & status process code(s) changed | The short text describes the object sufficiently | |
445 | 550 | --> Messages from fast entry for partner profiles | Space: object requires documentation | |
446 | 551 | Invalid value '&' for execution mode PI_MODE | Space: object requires documentation | |
447 | 552 | No templates available for partner type & | Space: object requires documentation | |
448 | 553 | Possible entries for partner number & exist already | Space: object requires documentation | |
449 | 554 | No entries made | Space: object requires documentation | |
450 | 555 | 1 entry made | Space: object requires documentation | |
451 | 556 | & entries were made | Space: object requires documentation | |
452 | 557 | ALE port '&' is already defined for logical destination '&' | Space: object requires documentation | |
453 | 558 | No authorization for deleting file & | The short text describes the object sufficiently | |
454 | 559 | Determination of inbound queue name was not successful | The short text describes the object sufficiently | |
455 | 560 | One of the passed parameters was empty | The short text describes the object sufficiently | |
456 | 561 | Formed queue name is too long: &1 | The short text describes the object sufficiently | |
457 | 562 | Inbound destination &1 has too many prefixes | The short text describes the object sufficiently | |
458 | 570 | -> Messages from API for ports or from port maintenance | Space: object requires documentation | |
459 | 571 | Port '&' of type '&' does not exist | Space: object requires documentation | |
460 | 572 | Port '&' to be deleted of type '&' does not exist | Space: object requires documentation | |
461 | 573 | Detailed data for port '&' of type '&' is not available | Space: object requires documentation | |
462 | 574 | Database error while deleting port '&' | Space: object requires documentation | |
463 | 575 | Port '&' to be copied of type '&' does not exist | Space: object requires documentation | |
464 | 576 | Port '&' is already available or a system error occurred during insertion | Space: object requires documentation | |
465 | 577 | No port name entered for new port | Space: object requires documentation | |
466 | 578 | Port '&' to be found does not exist | Space: object requires documentation | |
467 | 579 | tRFC ports cannot be copied! | Space: object requires documentation | |
468 | 580 | Logical destination '&' is not compatible with port version '&' | Space: object requires documentation | |
469 | 581 | Function module '&' does not exist | Space: object requires documentation | |
470 | 582 | Position the cursor on the appropriate field to access & | Space: object requires documentation | |
471 | 583 | No test, as RFC destination '&' is maintained for start on '&' | Space: object requires documentation | |
472 | 584 | Carry out test using 'Connection test' from RFC destination '&' | Space: object requires documentation | |
473 | 585 | No test possible as directory '&' is not available or cannot be read | Space: object requires documentation | |
474 | 586 | RFC destination is not maintained | Space: object requires documentation | |
475 | 587 | Logical directory '&' has not been defined for operating system '&' | Space: object requires documentation | |
476 | 588 | Function module '&' has not been defined for '&'. | Space: object requires documentation | |
477 | 589 | Access to directory possible from current application server | Space: object requires documentation | |
478 | 590 | ---> Additional messages from process code maintenance | Space: object requires documentation | |
479 | 591 | Processing via function module -> ID remains blank | Space: object requires documentation | |
480 | 592 | Processing type changed! Please enter ID again! | Space: object requires documentation | |
481 | 593 | Processing without ALE via function module is not possible | Space: object requires documentation | |
482 | 594 | Enter a valid port version | Space: object requires documentation | |
483 | 595 | Also maintain process code allocation for the logical message. | Space: object requires documentation | |
484 | 596 | Also maintain process code allocation for the logical message. | Space: object requires documentation | |
485 | 597 | Please do not use old process technology! | Space: object requires documentation | |
486 | 598 | The ALE table is not yet maintained for process code & ! | Space: object requires documentation | |
487 | 599 | When saving, process code '&' is also deleted in the ALE table | Space: object requires documentation | |
488 | 600 | --> IDoc API | Space: object requires documentation | |
489 | 601 | EDI: Receiver port in control record is default | Space: object requires documentation | |
490 | 602 | EDI: Receiver port in control record is invalid | Space: object requires documentation | |
491 | 603 | EDI: Receiver partner type in control record is default | Space: object requires documentation | |
492 | 604 | EDI: Receiver partner number in control record is default | Space: object requires documentation | |
493 | 605 | EDI: Sender port in control record is invalid | Space: object requires documentation | |
494 | 606 | EDI: Sender port in control record is default | Space: object requires documentation | |
495 | 607 | EDI: Sender partner type in control record is default | Space: object requires documentation | |
496 | 608 | EDI: Sender partner number in control record is default | Space: object requires documentation | |
497 | 609 | EDI: Field MANDT in data record is invalid | Space: object requires documentation | |
498 | 610 | EDI: Field DOCNUM in data record is invalid | Space: object requires documentation | |
499 | 611 | EDI: Field SEGNAM in data record is default | Space: object requires documentation | |
500 | 612 | EDI: Error during database insert in table EDIDC | Space: object requires documentation | |
501 | 613 | EDI: Error during database update in table EDIDC | Space: object requires documentation | |
502 | 614 | EDI: IDOCTP field in control record is invalid | Space: object requires documentation | |
503 | 615 | EDI: CIMTYP field in control record is invalid | Space: object requires documentation | |
504 | 616 | EDI: DOCTYP field in control record is invalid | Space: object requires documentation | |
505 | 617 | EDI: Interval to be read is not available in data records | Space: object requires documentation | |
506 | 618 | EDI: IDoc & contains no segments | Space: object requires documentation | |
507 | 619 | EDI: Next data record could not be read | Space: object requires documentation | |
508 | 620 | EDI: No data records could be read | Space: object requires documentation | |
509 | 621 | EDI: IDoc cannot be unlocked | Space: object requires documentation | |
510 | 622 | Combination of DOCTYP and CIMTYP fields is invalid | Space: object requires documentation | |
511 | 623 | Combination of IDOCTP and CIMTYP fields is invalid | Space: object requires documentation | |
512 | 624 | DOCTYP and IDOCTP fields are empty | Space: object requires documentation | |
513 | 630 | Internal error in DOM creation | Space: object requires documentation | |
514 | 650 | Data records for this IDoc could not be edited | Space: object requires documentation | |
515 | 651 | IDoc &1 Segment &2 | Space: object requires documentation | |
516 | 660 | --> Messages from segment editor for 4.0 | Space: object requires documentation | |
517 | 661 | Entry of development class is mandatory | Space: object requires documentation | |
518 | 662 | Segment & is locked by user & | Space: object requires documentation | |
519 | 663 | Segment & exists already | Space: object requires documentation | |
520 | 664 | Segment & does not exist yet | Space: object requires documentation | |
521 | 665 | Current segment definition & can still be changed | Space: object requires documentation | |
522 | 666 | Current segment definition & can no longer be changed | Space: object requires documentation | |
523 | 667 | Segment type & cannot be changed | Space: object requires documentation | |
524 | 668 | & does not exist as active data element | Space: object requires documentation | |
525 | 669 | Field name & appears several times in segment | Space: object requires documentation | |
526 | 670 | Segment definition not saved because user data was not maintained | Space: object requires documentation | |
527 | 671 | Segment & could not be read completely | Space: object requires documentation | |
528 | 672 | Segment definition & was saved with transport request & | Space: object requires documentation | |
529 | 673 | Segment definition & was saved as local object | Space: object requires documentation | |
530 | 674 | Export length for field & was set to & | Space: object requires documentation | |
531 | 675 | Segment type & is not used yet | Space: object requires documentation | |
532 | 676 | Segment type & is not yet assigned to a development class | Space: object requires documentation | |
533 | 677 | Segment type & is not yet assigned to a development class | Space: object requires documentation | |
534 | 678 | Segment definition must contain at least one field. Data was not saved. | Space: object requires documentation | |
535 | 679 | There is already a released segment definition of & for Release & | Space: object requires documentation | |
536 | 690 | --> Additional messages from EDI8 | Space: object requires documentation | |
537 | 691 | Basic type & could not be converted | Space: object requires documentation | |
538 | 692 | Extension & could not be converted | Space: object requires documentation | |
539 | 693 | Basic type & and extension & cannot be converted to IDoc type | Space: object requires documentation | |
540 | 694 | Message type & could not be converted | Space: object requires documentation | |
541 | 695 | Structure & already exists | Space: object requires documentation | |
542 | 700 | >>> IDoc inbound processing | ||
543 | 701 | Process & could not be started for IDoc number & | Space: object requires documentation | |
544 | 702 | IDoc: Event-event receiver coupling activated successfully | ||
545 | 703 | Transferred IDoc data records are empty (internal error) | Space: object requires documentation | |
546 | 704 | Transferred IDoc control records are empty (internal error) | Space: object requires documentation | |
547 | 705 | Status set to '50' during IDoc inbound processing | Space: object requires documentation | |
548 | 706 | No authorization to send IDocs with message type & | Space: object requires documentation | |
549 | 707 | Party to be notified from partner profile must be a user | Space: object requires documentation | |
550 | 708 | IDoc inbound: IDoc number & invalid | Space: object requires documentation | |
551 | 709 | IDoc number & transferred to application | Space: object requires documentation | |
552 | 710 | IDoc received repeatedly. | Space: object requires documentation | |
553 | 711 | IDoc receieved again, no further processing | Space: object requires documentation | |
554 | 713 | >>> XML inbound processing | Space: object requires documentation | |
555 | 714 | Prolog & does not have the syntax <?xml version="..."?>. | Space: object requires documentation | |
556 | 715 | Field & does not appear in segment &. | Space: object requires documentation | |
557 | 716 | Instead of end day & the character string & was found. | Space: object requires documentation | |
558 | 717 | Character string & cannot be interpreted as XML tag. | Space: object requires documentation | |
559 | 718 | The character string & is not a valid XML tag for the IDoc type | Space: object requires documentation | |
560 | 719 | The control record must begin with <EDI_DC40 segment="1"> instead of & | Space: object requires documentation | |
561 | 720 | The segment & is not defined in the current IDoc type & | Space: object requires documentation | |
562 | 721 | The segment & is not defined. | Space: object requires documentation | |
563 | 722 | The character string & cannot be interpreted as a tag. | Space: object requires documentation | |
564 | 723 | The start tag <IDOC begin="1"> or the end tag </IDOC> is missing. | Space: object requires documentation | |
565 | 724 | The character string & is not the start tag of a segment field. | Space: object requires documentation | |
566 | 725 | The XML data could not be processed completely | Space: object requires documentation | |
567 | 726 | Error occurred when parsing XML document in line & column & | Space: object requires documentation | |
568 | 727 | XML parser: Internal error | Space: object requires documentation | |
569 | 728 | IDoc SOAP Namespace - Violation (&) | Space: object requires documentation | |
570 | 729 | IDoc SOAP Namespace: EOIO-ID invalid | Space: object requires documentation | |
571 | 730 | --> Messages from name conversion for IDoc types | Space: object requires documentation | |
572 | 731 | Basic type & could not be converted | Space: object requires documentation | |
573 | 732 | Extension & could not be converted | Space: object requires documentation | |
574 | 733 | Field DOCTYP will not be able to be completed | Space: object requires documentation | |
575 | 734 | Message type & could not be converted | Space: object requires documentation | |
576 | 749 | Structure of predecessor type different from specified structure | Space: object requires documentation | |
577 | 750 | --> Messages from consistency check for IDoc types | Space: object requires documentation | |
578 | 751 | Extension type & does not appear in EDCIM | Space: object requires documentation | |
579 | 752 | Basic type & does not appear in EDBAS | Space: object requires documentation | |
580 | 753 | Basic type & has no syntax entries | Space: object requires documentation | |
581 | 754 | Extension & has no syntax entries | Space: object requires documentation | |
582 | 755 | Segment type & does not exist | Space: object requires documentation | |
583 | 756 | Basic type & is not released | Space: object requires documentation | |
584 | 757 | Extension & is not released | Space: object requires documentation | |
585 | 758 | Syntax entries are not numbered sequentially | Space: object requires documentation | |
586 | 759 | Parent segment & has no children | Space: object requires documentation | |
587 | 760 | Segment & has incorrect number for parent segment | Space: object requires documentation | |
588 | 761 | Parent segment for segment & could not be found | Space: object requires documentation | |
589 | 762 | Segment & has incorrect hierarchy level | Space: object requires documentation | |
590 | 763 | Segment & does not exist | Space: object requires documentation | |
591 | 764 | Predecessor of basic type & does not exist | Space: object requires documentation | |
592 | 765 | Predecessor of basic type & is not released | Space: object requires documentation | |
593 | 766 | Predecessor of extension & does not exist | Space: object requires documentation | |
594 | 767 | Predecessor of extension & is not released | Space: object requires documentation | |
595 | 768 | Basic type & has no short description | Space: object requires documentation | |
596 | 769 | Extension & has no short description | Space: object requires documentation | |
597 | 770 | Basic type & is linked to logical message & | Space: object requires documentation | |
598 | 771 | Basic type & is not linked with any logical message | Space: object requires documentation | |
599 | 772 | Extension & is linked with logical message & | Space: object requires documentation | |
600 | 773 | Extension & is not linked with any logical message | Space: object requires documentation | |
601 | 774 | Basic type & is released | Space: object requires documentation | |
602 | 775 | Extension & is released | Space: object requires documentation | |
603 | 776 | No predecessors exist | Space: object requires documentation | |
604 | 777 | Predecessor & exists | Space: object requires documentation | |
605 | 778 | Predecessor & is released | Space: object requires documentation | |
606 | 779 | Syntax table for predecessor & is empty | Space: object requires documentation | |
607 | 780 | Segment & appears only in predecessor | Space: object requires documentation | |
608 | 781 | Segment & has other attributes in predecessor | Space: object requires documentation | |
609 | 782 | New segment & does not have to be a mandatory segment | Space: object requires documentation | |
610 | 783 | Extension & is not assigned to any basic type | Space: object requires documentation | |
611 | 784 | Extension & is assigned to basic type & | Space: object requires documentation | |
612 | 785 | Extension & and basic type & are not compatible | Space: object requires documentation | |
613 | 786 | Changes to & will have an effect on several extensions | Space: object requires documentation | |
614 | 787 | No development class has been specified | Space: object requires documentation | |
615 | 788 | Development class & does not exist | Space: object requires documentation | |
616 | 791 | Segment & is parent segment but parent flag is missing | Space: object requires documentation | |
617 | 792 | Segment & has invalid frequency of use | Space: object requires documentation | |
618 | 793 | No new segments have been added | Space: object requires documentation | |
619 | 794 | View has no short description | Space: object requires documentation | |
620 | 795 | Syntax error: Segment & must appear in view & | Space: object requires documentation | |
621 | 796 | Syntax entry numbering contains errors. | Space: object requires documentation | |
622 | 797 | Enter copy template | Space: object requires documentation | |
623 | 798 | Attributes cannot be modified | Space: object requires documentation | |
624 | 799 | Segment & is used multiple times in IDoc types | Space: object requires documentation | |
625 | 800 | ---- Archiving of IDocs | ||
626 | 801 | Invalid access & to archive | Space: object requires documentation | |
627 | 802 | Insert in table & with key & & failed | Space: object requires documentation | |
628 | 803 | System format cannot be determined | Space: object requires documentation | |
629 | 804 | IDoc & not found | Space: object requires documentation | |
630 | 805 | IDoc & found | ||
631 | 806 | Data decompression for archiving class IDoc contains errors | Space: object requires documentation | |
632 | 807 | Data compression for archiving class IDoc failed | Space: object requires documentation | |
633 | 808 | IDoc data read contains errors | Space: object requires documentation | |
634 | 809 | Failed to delete IDoc table & with key & | ||
635 | 810 | Character conversion from code page & to & for IDoc failed | Space: object requires documentation | |
636 | 811 | IDoc has unknown status value & | Space: object requires documentation | |
637 | 812 | Table specifying which status values can be archived is empty | Space: object requires documentation | |
638 | 813 | Control record of IDoc with number & not found | ||
639 | 814 | Archiving object IDoc is inknown | Space: object requires documentation | |
640 | 815 | Archiving class IDoc (internal error) | Space: object requires documentation | |
641 | 816 | Update not possible | ||
642 | 817 | Archiving not possible due to missing classification | ||
643 | 823 | Internal error for IDoc & | Space: object requires documentation | |
644 | 824 | IDoc '&' : '&' when reloading | Space: object requires documentation | |
645 | 825 | IDoc '&': Inconsistent data in archive '&' | Space: object requires documentation | |
646 | 826 | IDoc '&': Control record exists already | Space: object requires documentation | |
647 | 827 | IDoc '&': Data records exist already | Space: object requires documentation | |
648 | 828 | IDoc '&': Status records exist already | Space: object requires documentation | |
649 | 829 | IDoc '&' does not exist | Space: object requires documentation | |
650 | 830 | IDoc '&' locked | Space: object requires documentation | |
651 | 831 | IDoc '&' cannot be deleted | Space: object requires documentation | |
652 | 832 | IDoc '&' only partly deleted | Space: object requires documentation | |
653 | 833 | IDoc '&': Processing cannot be completed correctly | Space: object requires documentation | |
654 | 834 | IDoc '&': Status records could not be read | Space: object requires documentation | |
655 | 835 | IDoc '&': Data records could not be read | Space: object requires documentation | |
656 | 836 | Archive information for archive & could not be read | Space: object requires documentation | |
657 | 837 | IDoc '&' could not be opened for reading | Space: object requires documentation | |
658 | 838 | IDoc '&' could not be opened to set status | Space: object requires documentation | |
659 | 839 | IDoc '&' could not be closed after status was set | Space: object requires documentation | |
660 | 840 | IDoc '&': Status could not be set | Space: object requires documentation | |
661 | 841 | Number range & not found | Space: object requires documentation | |
662 | 842 | IDoc number '&' is not suitable for current number level | Space: object requires documentation | |
663 | 843 | IDoc '&' from system '&' not reloaded | Space: object requires documentation | |
664 | 844 | IDoc & from Release & not reloaded | Space: object requires documentation | |
665 | 860 | --> Additional messages (inb. status) | Space: object requires documentation | |
666 | 861 | Invalid name '&' in status record & for version of port '&' | Space: object requires documentation | |
667 | 862 | IDoc: Different table names in inb. status via IDoc | Space: object requires documentation | |
668 | 863 | IDoc: Invalid table name '&' in inb. status via IDoc | Space: object requires documentation | |
669 | 864 | IDoc: Status message in inb.status via IDoc is not complete | Space: object requires documentation | |
670 | 865 | Error in status inbound from IDoc type SYSTAT01 | Space: object requires documentation | |
671 | 866 | IDoc number & has been put down for deletion | Space: object requires documentation | |
672 | 867 | IDoc number & already has status 31 | Space: object requires documentation | |
673 | 868 | In status postprocessing the IDoc has been released for sending | Space: object requires documentation | |
674 | 869 | The IDoc is currently now in status '&' | Space: object requires documentation | |
675 | 870 | --> Error FuGr EDIPAKET | Space: object requires documentation | |
676 | 871 | IDocs to be processed not found in database | Space: object requires documentation | |
677 | 872 | Status of IDocs to be processed cannot be reset | Space: object requires documentation | |
678 | 873 | IDocs could be processed as block | Space: object requires documentation | |
679 | 874 | IDocs could not be processed successfully | Space: object requires documentation | |
680 | 875 | IDocs should not be transferred for processing | Space: object requires documentation | |
681 | 876 | No more IDocs available for post-processing | Space: object requires documentation | |
682 | 877 | Status set by error handling for IDoc packet | Space: object requires documentation | |
683 | 878 | IDocs set to status '30' successfully | Space: object requires documentation | |
684 | 879 | IDocs could not be set to status '30' | Space: object requires documentation | |
685 | 880 | Incorrect selection of MASS_RSEOUT00 | Space: object requires documentation | |
686 | 881 | IDocs set to status '03' successfully | Space: object requires documentation | |
687 | 882 | IDocs could not be set to status '03' | Space: object requires documentation | |
688 | 883 | IDocs marked for deletion | Space: object requires documentation | |
689 | 884 | IDocs should not be marked for deletion | Space: object requires documentation | |
690 | 885 | IDocs could not be marked for deletion | Space: object requires documentation | |
691 | 886 | Command file could be started | Space: object requires documentation | |
692 | 887 | Command file could not be started | Space: object requires documentation | |
693 | 888 | Command file could be started, but IDocs still have old status | Space: object requires documentation | |
694 | 889 | Restart not possible because port definition is missing | Space: object requires documentation | |
695 | 890 | The IDoc number & is not available in the database. | Space: object requires documentation | |
696 | 891 | The IDoc number & is not an outgoing IDoc | Space: object requires documentation | |
697 | 892 | Deletion not possible, a status record must be written in control record. | Space: object requires documentation | |
698 | 893 | The IDoc number must not be 0 or initial. | Space: object requires documentation | |
699 | 894 | The entered status is not valid for the inbound status | Space: object requires documentation | |
700 | 895 | The status record was stored in file &. | Space: object requires documentation | |
701 | 896 | The port entered is not a file port. | Space: object requires documentation | |
702 | 897 | No port entered. | Space: object requires documentation | |
703 | 898 | No file entered. | Space: object requires documentation | |
704 | 899 | No outbound IDoc is available in the system. | Space: object requires documentation |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |