SAP ABAP Message Class B1 (ALE group messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE (Package) Application Link Enabling
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE (Package) Application Link Enabling
Attributes
Message class | B1 | |
Short Description | ALE group messages | |
Changed On | 20130531 | |
Last Changed At | 115938 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 00 | No entry in table & for key & & & | ||
2 | 000 | ***** Messages for input and outbound processing ***** | ||
3 | 001 | No IDoc type maintained for base type & and extension type & | ||
4 | 002 | Transport contains control data to be distributed - please distribute | Space: object requires documentation | |
5 | 003 | Could not determine recipients for message type & | ||
6 | 004 | A separate logical system is not defined for client & | ||
7 | 005 | & &, &, &. | Space: object requires documentation | |
8 | 006 | &, &, &, & | Space: object requires documentation | |
9 | 007 | Segment type & does not exist in message type & | ||
10 | 008 | Mandatory segment & in message type & cannot be filtered | ||
11 | 009 | Partner profile missing for recipient & & &, message type & | Space: object requires documentation | |
12 | 01 | Objects not in T777I do not have an infotype | ||
13 | 010 | Position the Cursor Correctly | ||
14 | 011 | Interface changed for message type &1: Settings reset | Space: object requires documentation | |
15 | 012 | Message type & does not exist | ||
16 | 013 | Message type & exists already | Space: object requires documentation | |
17 | 014 | Database error when storing in EDMSG | ||
18 | 015 | Database error when storing in EDIMSG | Space: object requires documentation | |
19 | 016 | Database error when storing in EDIMSGT | ||
20 | 017 | Database error when storing in EDIMAP | ||
21 | 018 | Port & is not an RFC port, or RFC destination is missing | ||
22 | 019 | Error when calling asynchronous Remote Function Call | ||
23 | 02 | Infotype " " is only for objects without infotypes | ||
24 | 020 | Database error occurred when storing in BDSER | ||
25 | 021 | No data for entity & | Space: object requires documentation | |
26 | 022 | Inconsistent IDocs passed: Data records or control records missing. | ||
27 | 023 | Class type &, receiving system &: no list maintained | ||
28 | 024 | Object type & not maintained for message type & | ||
29 | 025 | Distribution model posted successfully | Space: object requires documentation | |
30 | 026 | Object type & cannot be read for message type & from segment type & | ||
31 | 027 | No classification object maintained for message type & | ||
32 | 028 | Database error when storing in BDPNT | ||
33 | 029 | No distribution class type exists for classification object & | ||
34 | 030 | ***** Messages for application input ***** | ||
35 | 031 | No (active) partner profile: sender & & &, message type & | Space: object requires documentation | |
36 | 032 | No process code exists for sender & and message type & | ||
37 | 033 | No function module for input process code & | ||
38 | 034 | No parameters found for function module & | ||
39 | 035 | Maximum no. of repetitions exceeded | ||
40 | 036 | IDocs in packet do not match | Space: object requires documentation | |
41 | 037 | Packet contains no IDocs | Space: object requires documentation | |
42 | 038 | & master IDocs set up for message type & | Space: object requires documentation | |
43 | 039 | & communication IDoc(s) generated for message type & | Space: object requires documentation | |
44 | 040 | User & has no authorization for message type & in ALE inbound | Space: object requires documentation | |
45 | 041 | Table MASTER_IDOC_DATA is empty | ||
46 | 042 | Direct call started | ||
47 | 043 | Task & started with workflow ID & | ||
48 | 044 | Incorrect function module & called up | ||
49 | 045 | Application function module & terminated with invalid exception. | ||
50 | 046 | Task & could not be started. | ||
51 | 047 | Process & could not be started. | ||
52 | 048 | Process & started with ID &. | ||
53 | 049 | More than one IDoc transferred | Space: object requires documentation | |
54 | 050 | ***** Messages for failed Select Singles ***** | ||
55 | 051 | IDoc included in IDoc packet containing an error: transfer it separately | Space: object requires documentation | |
56 | 052 | Message type included in request | Space: object requires documentation | |
57 | 053 | Filter object type & not permitted with message type & | ||
58 | 054 | Control data object & does not exist | Space: object requires documentation | |
59 | 055 | Message type & does not exist | ||
60 | 056 | Database error when storing in Table TBD10 | ||
61 | 057 | Database error when storing in Table TBD12 | ||
62 | 058 | Database error when storing in Table TBD13 | ||
63 | 059 | Database error when storing in Table TBDME | ||
64 | 060 | Database error when storing data in Table & | ||
65 | 061 | The customer model in HR-ORG could not be deleted | Space: object requires documentation | |
66 | 062 | Error when assigning numbers to HR-ORG objects | Space: object requires documentation | |
67 | 063 | & request IDocs created for message type & | Space: object requires documentation | |
68 | 064 | Remote Function Call destination could not be found | ||
69 | 065 | Connection to other system could not be established | ||
70 | 066 | Messages have been created during processing (last was displayed) | Space: object requires documentation | |
71 | 067 | Number of IDocs: total &, dispatched &, still open (tRFC queue) & | Space: object requires documentation | |
72 | 068 | Place the cursor on a subsystem | ||
73 | 069 | Filter object already assigned | ||
74 | 070 | Internal error: Program &, command &, argument & | Space: object requires documentation | |
75 | 071 | More than one IDoc selected | The short text describes the object sufficiently | |
76 | 072 | Place the cursor on a message type | ||
77 | 073 | Place the cursor on a filter object | ||
78 | 074 | Distribution model is being processed | ||
79 | 075 | Function & is not available in this system, termination | Space: object requires documentation | |
80 | 076 | No object type for lists maintained for message type & | ||
81 | 077 | This IDoc was forwarded to receiver & & &. | Space: object requires documentation | |
82 | 078 | Check your entry | ||
83 | 079 | Message type & included in request & | ||
84 | 080 | ***** Messages for RBDTBDA1 ***** | ||
85 | 081 | Change pointer generation deactivated | ||
86 | 082 | Change pointer generation activated | ||
87 | 083 | No data could be selected. | ||
88 | 084 | Database error occurred when storing in table TBDMS | Space: object requires documentation | |
89 | 085 | Error occurred when assigning a number for a change pointer | ||
90 | 086 | External partner system &: functionality not available | Space: object requires documentation | |
91 | 087 | Partner system & is an R/2 system: functionality not available | Space: object requires documentation | |
92 | 088 | RFC destination & does not exist | Space: object requires documentation | |
93 | 089 | Partner profile & & & & does not exist | Space: object requires documentation | |
94 | 090 | IDoc type could not be determined for the IDoc | Space: object requires documentation | |
95 | 091 | Receiver of IDoc is its own logical system | Space: object requires documentation | |
96 | 092 | Start Transaction & for the check | Space: object requires documentation | |
97 | 093 | Model & cannot be maintained in own system | ||
98 | 094 | Message type not permitted, because no ownership for model & | Space: object requires documentation | |
99 | 095 | Segment & does not exist for message type & | Space: object requires documentation | |
100 | 096 | Indicator cannot be selected | Space: object requires documentation | |
101 | 097 | Changes cannot be made to the control data distribution in this system | ||
102 | 098 | Tool could not be started - please enter call parameters | Space: object requires documentation | |
103 | 099 | & | ||
104 | 10 | F key must be specified | ||
105 | 100 | Linked object: &, && | ||
106 | 101 | Message type & does not exist | ||
107 | 102 | Required segment & cannot be deactivated | ||
108 | 103 | Segment & has already been deactivated completely | ||
109 | 104 | No IDoc type found for message type & | Space: object requires documentation | |
110 | 105 | Message type & exists already | ||
111 | 106 | Reduction for message type & saved | ||
112 | 107 | Higher-level segment deactivated | ||
113 | 108 | Table & for message type & exists already in EDIMAP | ||
114 | 109 | Please choose an processing type. | ||
115 | 11 | This combination is not allowed | ||
116 | 110 | Reference message type may not have reference | ||
117 | 111 | Generation of change pointers for & activated in client & | ||
118 | 112 | Reduction for message type & deleted | ||
119 | 113 | Generation of change pointers for & deactivated in client & | ||
120 | 114 | Change pointers for message type & active in client & | ||
121 | 115 | Message type & already being processed | ||
122 | 116 | An IDoc without a message type was passed to the ALE layer | Space: object requires documentation | |
123 | 117 | Place the cursor on a valid line and field | Space: object requires documentation | |
124 | 118 | The IDoc type for this message must not be reduced | Space: object requires documentation | |
125 | 119 | Message & is not in valid name range | ||
126 | 120 | Recipient & & & not permissible for this IDoc | ||
127 | 121 | There is no data maintained in the reduction pool for message type & | ||
128 | 122 | A server group should be specified with parallel processing | Space: object requires documentation | |
129 | 123 | No assignment for & company code & to a & company code. | ||
130 | 124 | For & business area & no assignment to a & business area. | ||
131 | 125 | You do not have the authorization for the action | ||
132 | 126 | Foreground processing and parallel processing are not possible together | Space: object requires documentation | |
133 | 127 | No partner profiles (message control) maintained | ||
134 | 128 | A message type could not be (uniquely) identified | ||
135 | 129 | No recipient found for message type & in the ALE model | ||
136 | 130 | Too many recipients found for message type & in the ALE model | ||
137 | 131 | Wrong partner type & | ||
138 | 132 | Select packet size larger than 0 | The short text describes the object sufficiently | |
139 | 133 | IDoc type has not been entered for message type & | Space: object requires documentation | |
140 | 134 | Change pointer creation is currently deactivated | ||
141 | 135 | Please maintain ALE Customizing via the IMG | ||
142 | 136 | All event couplings were activated. | ||
143 | 137 | You have selected all data records. Did you intend to do this? | Space: object requires documentation | |
144 | 138 | The tool cannot be executed on your frontend. | ||
145 | 139 | No data relevant to audit were selected. | Space: object requires documentation | |
146 | 140 | Error when locking the audit statistics for & & &. | ||
147 | 141 | Database error when writing status records for the status &. | ||
148 | 142 | A change period must be specified. | ||
149 | 143 | Number range for change pointer has not been maintained. | ||
150 | 144 | Message type & cannot be reduced | ||
151 | 145 | Message type & is not relevant to reduction | Space: object requires documentation | |
152 | 146 | The change pointer target should not be changed manually | Space: object requires documentation | |
153 | 147 | Selection Period for AUDIT IDocs: &1 &2 -> &3 &4 | Space: object requires documentation | |
154 | 148 | Customer distribution model & does not exist | ||
155 | 149 | Customer distribution model & successfully deleted | ||
156 | 150 | ***** Error messages in area of serialization ***** | ||
157 | 151 | Object & &: Overtaking process between systems | ||
158 | 152 | System error occurred when writing to table BDSE | ||
159 | 153 | Model & is currently being edited by & | ||
160 | 154 | Warning! You have not done the checkout with the current model | ||
161 | 155 | Message type & is not within the permitted SAP name range | ||
162 | 156 | Error locking change pointer for message type &. | ||
163 | 157 | Message type & cannot be sent with change pointers | ||
164 | 158 | No parties are interested in the selected data | Space: object requires documentation | |
165 | 159 | IDoc must be processed later; expected: &; current: & | Space: object requires documentation | |
166 | 160 | System error has occurred writing data to table BDRGIN | Space: object requires documentation | |
167 | 161 | Data in table & has been changed and logged in SYSLOG | Space: object requires documentation | |
168 | 162 | Changing the registry can interrupt the data transfer | Space: object requires documentation | |
169 | 163 | Data could not be entered in table &. (Does entry already exist?) | Space: object requires documentation | |
170 | 164 | Data in table & could not be deleted. | Space: object requires documentation | |
171 | 165 | System error has occurred writing data to table BDRGOUT. | Space: object requires documentation | |
172 | 166 | Please mark at least one option (outbound and/or inbound) | Space: object requires documentation | |
173 | 167 | No changes made (don't need to save) | Space: object requires documentation | |
174 | 168 | & entries in the registry table & have been deleted/ SYSLOG log | Space: object requires documentation | |
175 | 169 | Change pointers for message type &1 are being migrated | Space: object requires documentation | |
176 | 170 | ********* Messages for control data ********************************** | Space: object requires documentation | |
177 | 171 | Choose 'Utilities -> Comparison' in the following table maintenance view | Space: object requires documentation | |
178 | 172 | Report & is not available in this system, you cannot run it. | Space: object requires documentation | |
179 | 173 | Data has already been maintained by & and therefore can only be displayed | Space: object requires documentation | |
180 | 174 | System error occurred while writing to table BDEOIO_OUT | The short text describes the object sufficiently | |
181 | 175 | System error occurred while writing to table BDEOIO_IN | The short text describes the object sufficiently | |
182 | 176 | Subsequent IDOC already processed; expected: &; current: & | Space: object requires documentation | |
183 | 177 | Invalid ID for sequence processing | Space: object requires documentation | |
184 | 195 | ***** Messages for direct model maintenance ***** | Space: object requires documentation | |
185 | 198 | Logical system & must not be deleted | Space: object requires documentation | |
186 | 199 | Logical system & must not be deleted | Space: object requires documentation | |
187 | 20 | Please check entry & & & in table & | ||
188 | 200 | Model view & already exists | Space: object requires documentation | |
189 | 201 | Place the cursor on a model view | Space: object requires documentation | |
190 | 202 | Sending system must be different to receiving system | Space: object requires documentation | |
191 | 203 | Method & has already been added | Space: object requires documentation | |
192 | 204 | Method & has already been defined in the model view & | Space: object requires documentation | |
193 | 205 | Place the cursor on a method | Space: object requires documentation | |
194 | 206 | Distribution model has been saved | Space: object requires documentation | |
195 | 207 | Distribution model is being edited by user & (You can only display it) | Space: object requires documentation | |
196 | 208 | This function is not available for this node | Space: object requires documentation | |
197 | 209 | Input help is not available for the filter object type & | Space: object requires documentation | |
198 | 210 | Method & cannot be filtered | Space: object requires documentation | |
199 | 211 | Filter object has already been added | Space: object requires documentation | |
200 | 212 | No filter has been defined for method & | Space: object requires documentation | |
201 | 213 | Distribution model has not been changed | Space: object requires documentation | |
202 | 214 | Message type & has already been added | Space: object requires documentation | |
203 | 215 | Message type & has already been defined in the model view & | Space: object requires documentation | |
204 | 216 | Place the cursor on a message type | Space: object requires documentation | |
205 | 217 | No filter available for message type & | Space: object requires documentation | |
206 | 218 | No further filter available for message type & | Space: object requires documentation | |
207 | 219 | No filter has been defined for message type & | Space: object requires documentation | |
208 | 220 | Reference to message type & has already been defined | Space: object requires documentation | |
209 | 221 | End date cannot be earlier than the start date | Space: object requires documentation | |
210 | 222 | The valid time period overlaps with that of the model view & | Space: object requires documentation | |
211 | 223 | Classes are defined in a separate Customizing transaction | Space: object requires documentation | |
212 | 224 | First save the distribution model | Space: object requires documentation | |
213 | 225 | Model view & does not exist and has been deleted in target systems | Space: object requires documentation | |
214 | 226 | Method & has not been assigned a message type | Space: object requires documentation | |
215 | 227 | You are not authorized to carry out this action | Space: object requires documentation | |
216 | 228 | Model view has not been specified | Space: object requires documentation | |
217 | 229 | Maintenance systems for model view & are not the same | Space: object requires documentation | |
218 | 230 | Method & has already been defined in the model view & | Space: object requires documentation | |
219 | 231 | Message type & has already been defined in model view & | Space: object requires documentation | |
220 | 232 | The distribution model is currently being processed | Space: object requires documentation | |
221 | 233 | Model view & has been created | Space: object requires documentation | |
222 | 234 | Model view & has been changed | Space: object requires documentation | |
223 | 235 | Model view & has been deleted | Space: object requires documentation | |
224 | 236 | Model view & must not be maintained in your own system | Space: object requires documentation | |
225 | 237 | You are not authorized to create the model view & | Space: object requires documentation | |
226 | 238 | You are not authorized to change the model view & | Space: object requires documentation | |
227 | 239 | Client and server must be different systems | Space: object requires documentation | |
228 | 240 | You are not authorized to delete the model view & | Space: object requires documentation | |
229 | 241 | You are not authorized to transport model view & | Space: object requires documentation | |
230 | 242 | You are not authorized to distribute the model view & | Space: object requires documentation | |
231 | 243 | Distribution model has been edited by user & | Space: object requires documentation | |
232 | 244 | Object & is already defined in the model view & | Space: object requires documentation | |
233 | 245 | Distribution via classes for object & has already been defined | Space: object requires documentation | |
234 | 246 | Reference to method & has already been defined | Space: object requires documentation | |
235 | 247 | Model view & already exists and will be completely overwritten | Space: object requires documentation | |
236 | 248 | Define the conversion of the logical systems for copying | Space: object requires documentation | |
237 | 249 | This message type belongs to object method &.&. | Space: object requires documentation | |
238 | 250 | ***** Error messages for "manual input" method ***** | ||
239 | 251 | IDoc number & does not exist in the database | Space: object requires documentation | |
240 | 252 | Function module not allowed: & | Space: object requires documentation | |
241 | 253 | IDoc & has not been edited | Space: object requires documentation | |
242 | 254 | Error during application input | ||
243 | 255 | IDoc successfully processed by the application | Space: object requires documentation | |
244 | 256 | Previous status & unsuitable | ||
245 | 257 | IDoc has been flagged for deletion | Space: object requires documentation | |
246 | 258 | No event found to trigger | ||
247 | 259 | No object type found for event | ||
248 | 260 | Error when opening IDoc: IDoc locked | Space: object requires documentation | |
249 | 261 | Error when opening IDoc: IDoc does not exist | Space: object requires documentation | |
250 | 262 | Error when opening IDoc: IDoc number is invalid | Space: object requires documentation | |
251 | 263 | Error when reading IDoc: IDoc number is invalid | Space: object requires documentation | |
252 | 264 | Error when reading IDoc: no data | Space: object requires documentation | |
253 | 265 | Error when writing IDoc status: IDoc number is invalid | Space: object requires documentation | |
254 | 266 | Error writing IDoc status: Database error | Space: object requires documentation | |
255 | 267 | Error when writing IDoc status: Invalid status | Space: object requires documentation | |
256 | 268 | Error when writing IDoc status: No status record exists | Space: object requires documentation | |
257 | 269 | Error when closing IDoc: IDoc not opened | Space: object requires documentation | |
258 | 270 | Error when closing IDoc: Database error | Space: object requires documentation | |
259 | 271 | Error when closing IDoc: Incorrect parametrization | Space: object requires documentation | |
260 | 272 | Error when closing IDoc: Status not set | Space: object requires documentation | |
261 | 273 | Error: Incorrect IDoc status value | Space: object requires documentation | |
262 | 274 | Caution: & IDocs have been selected | Space: object requires documentation | |
263 | 275 | Error writing IDOC status: IDoc locked | Space: object requires documentation | |
264 | 276 | More than one IDoc in packet: Application supports single processing only | Space: object requires documentation | |
265 | 277 | Error when opening IDoc: IDoc already opened | Space: object requires documentation | |
266 | 278 | IDoc &: status & cannot be processed | Space: object requires documentation | |
267 | 279 | The IDocs have no data records | Space: object requires documentation | |
268 | 280 | The IDocs do not exist in the database | Space: object requires documentation | |
269 | 281 | IDocs not specified | Space: object requires documentation | |
270 | 282 | Error: No IDocs to be processed | Space: object requires documentation | |
271 | 283 | There is no ALE link object defined. | ||
272 | 284 | Link object not in IDOC. | ||
273 | 285 | You are not authorized to display/edit IDoc & | Space: object requires documentation | |
274 | 286 | Server group & could not be initialized | Space: object requires documentation | |
275 | 287 | Number of maximum attempts to start parallel processes has been exceeded | Space: object requires documentation | |
276 | 288 | & of & IDocs could be transferred in parallel for processing | Space: object requires documentation | |
277 | 300 | ***** Error messages in area 'ALE error handling' ***** | ||
278 | 301 | IDoc & does not exist, processing not possible | Space: object requires documentation | |
279 | 302 | No details exist for message | ||
280 | 303 | Error when processing IDoc & | Space: object requires documentation | |
281 | 304 | IDoc & flagged for deletion | Space: object requires documentation | |
282 | 305 | IDoc & already processed, processing not possible | Space: object requires documentation | |
283 | 306 | Status set within ALE/EDI error handling | ||
284 | 307 | Status reset after editing IDoc | Space: object requires documentation | |
285 | 308 | IDoc & can be passed to the port | Space: object requires documentation | |
286 | 309 | IDoc & successfully passed to the port | Space: object requires documentation | |
287 | 310 | IDoc & can be tranferred to the application | Space: object requires documentation | |
288 | 311 | IDoc & successfully passed to the application | Space: object requires documentation | |
289 | 312 | More IDocs created from IDoc & | Space: object requires documentation | |
290 | 313 | IDoc & successfully processed | Space: object requires documentation | |
291 | 314 | IDoc flagged for deletion | Space: object requires documentation | |
292 | 315 | More IDocs have been created from the IDoc | Space: object requires documentation | |
293 | 316 | No status records exist for IDoc &, processing not possible | Space: object requires documentation | |
294 | 317 | Report has reset status | Space: object requires documentation | |
295 | 318 | Resetting the status may result in data inconsistency | Space: object requires documentation | |
296 | 350 | ***** More messages for input ***** | ||
297 | 351 | Errors when compiling version: Target structure & & does not match IDoc | Space: object requires documentation | |
298 | 352 | IDoc has wrong status | Space: object requires documentation | |
299 | 353 | Parameter & missing in container of task & | ||
300 | 354 | Version & of process code & not allowed for ALE | ||
301 | 355 | No object for requested IDoc selected for sending | Space: object requires documentation | |
302 | 356 | Account group in the IDoc is different | Space: object requires documentation | |
303 | 357 | Status records with status 51 after status 53 | ||
304 | 358 | No status record was passed to ALE by the application | ||
305 | 359 | No active event coupling for & . & found, no error work items | Space: object requires documentation | |
306 | 360 | Status was set automatically | Space: object requires documentation | |
307 | 38 | An editing module must be specified | ||
308 | 40 | Field & does not belong to structure & of infotype & | ||
309 | 400 | ***** Messages for ALE Customizing ***** | ||
310 | 401 | Object class & does not exist | ||
311 | 402 | Table & for object class & does not exist | ||
312 | 403 | Table & is not an active table | ||
313 | 404 | Field & does not exist in table & | ||
314 | 405 | Application object type & is not planned | ||
315 | 406 | Assignment not allowed | ||
316 | 407 | Segment type & deactivated for message type & | ||
317 | 408 | Field & in segment type & deactivated for message type & | ||
318 | 409 | A check table has not been defined for field & in table & | Space: object requires documentation | |
319 | 41 | Structure to infotype & not found | ||
320 | 411 | Object type & may only be assigned to fields from one segment type | ||
321 | 412 | Segment type & not defined for message type & | ||
322 | 413 | Field & in segment type & does not exist | Space: object requires documentation | |
323 | 414 | Conversion rule & does not exist | ||
324 | 415 | Conversion rule & for segment type & does not exist | ||
325 | 416 | Object type & is assigned to fields from more than one segment type | ||
326 | 417 | Required segment & may not be filtered | ||
327 | 418 | Segment type & does not exist | ||
328 | 419 | Segment type & does not exist in active form | ||
329 | 42 | Relationship & is unknown | ||
330 | 420 | Selected function not implemented for message type & | ||
331 | 421 | Function not possible for the selected line | ||
332 | 422 | Logical system & does not exist | ||
333 | 423 | You are logged on to partner system & | Space: object requires documentation | |
334 | 424 | Maintenance transaction & not defined in partner system & | ||
335 | 425 | Purchasing organization & does not exist | ||
336 | 426 | Vendor & does not exist | ||
337 | 427 | Material & does not exist | ||
338 | 428 | RFC destination & does not exist | ||
339 | 429 | Specify the RFC destination for logical system & | ||
340 | 430 | Sales organization & does not exist | ||
341 | 431 | Distribution channel & does not exist | ||
342 | 432 | Order type & does not exist | ||
343 | 433 | Partner status & does not exist | ||
344 | 434 | Language & does not exist | ||
345 | 435 | Output mode & does not exist | ||
346 | 436 | Processing & is not defined | ||
347 | 437 | The maintenance transaction & is not defined in own system & | ||
348 | 438 | No application object type planned for the function module | ||
349 | 439 | Cross-system checking is active. | ||
350 | 44 | Entries for external object types are not allowed (acc. to table T77EO) | ||
351 | 440 | Cross-system checking is inactive. | ||
352 | 441 | There are no inspection results available for the selected line. | ||
353 | 442 | There are no receiver systems defined in the distribution model | Space: object requires documentation | |
354 | 443 | Select at least one system. | ||
355 | 444 | The table for the listing data for message type & is not defined. | Space: object requires documentation | |
356 | 445 | Distribution-relevant class type for table & is not defined. | Space: object requires documentation | |
357 | 446 | Class & is not defined for class type &. | Space: object requires documentation | |
358 | 447 | To display the test results choose 'Edit -> Detail' | Space: object requires documentation | |
359 | 448 | ***** Messages for the conversion pre-production => production ***** | Space: object requires documentation | |
360 | 449 | Table &: & of & entries in field & converted (client-independent) | Space: object requires documentation | |
361 | 45 | Symbols entered are not allowed | ||
362 | 450 | Table &: & of & entries in field & converted (client-dependent) | Space: object requires documentation | |
363 | 451 | The logical system & is already allocated to another system | ||
364 | 452 | The logical system & is not taken into account in any conversion | ||
365 | 453 | The logical system name &1 has been converted to name &2 in client &3 | Space: object requires documentation | |
366 | 454 | The logical system & has not yet been defined | Space: object requires documentation | |
367 | 455 | The logical system name & already exists | Space: object requires documentation | |
368 | 456 | The new logical system name & is the same as the old name & | Space: object requires documentation | |
369 | 457 | Error creating program & | Space: object requires documentation | |
370 | 458 | Syntax error in program & line & | Space: object requires documentation | |
371 | 459 | Conversion of logical system name & for name & in client & | Space: object requires documentation | |
372 | 46 | Entries in the field Ext are allowed in * lines 01-12 only | ||
373 | 460 | ***** Messages for ALE Recovery Tool ***** | Space: object requires documentation | |
374 | 461 | No system selected | Space: object requires documentation | |
375 | 462 | No documentation is available for object & in language &. | Space: object requires documentation | |
376 | 463 | Please choose the participating systems first. | Space: object requires documentation | |
377 | 464 | Please check system settings before starting the process. | Space: object requires documentation | |
378 | 465 | The processing type of some IDocs has not been defined. | Space: object requires documentation | |
379 | 466 | IDoc & no longer exists in system &. | Space: object requires documentation | |
380 | 467 | The process "Determine recovery objects" has been started in system &. | Space: object requires documentation | |
381 | 468 | System & has been reset to the status on & at &. | Space: object requires documentation | |
382 | 469 | An error has occurred when checking IDoc dispatch for system &. | Space: object requires documentation | |
383 | 47 | Profile ID 'O' (object-oriented) or 'S' (status-oriented) allowed | ||
384 | 470 | An error has occurred during message transmission. | Space: object requires documentation | |
385 | 471 | A tRFC entry with ID && has been deleted in system &. | Space: object requires documentation | |
386 | 472 | No data could be selected for partner system &. | Space: object requires documentation | |
387 | 473 | ALE recovery tool converts status | Space: object requires documentation | |
388 | 474 | No log found | Space: object requires documentation | |
389 | 476 | Could not determine any tables | The short text describes the object sufficiently | |
390 | 477 | Read the online documentation before carrying out the transaction | Space: object requires documentation | |
391 | 478 | No logical system name has been defined for client & | Space: object requires documentation | |
392 | 479 | Table &: & of & entries in field & converted (client-dependent) | Space: object requires documentation | |
393 | 480 | ***** Messages for BAPIs <-> ALE generating tool ***** | Space: object requires documentation | |
394 | 481 | BAPI &.& does not exist in the system | Space: object requires documentation | |
395 | 482 | Reference type & is not a structure and therefore it is not allowed | Space: object requires documentation | |
396 | 483 | For the message type & there is no IDoc type & | Space: object requires documentation | |
397 | 484 | Only some of the objects in the interface have been released | Space: object requires documentation | |
398 | 485 | The release of the interface has been partly reset | Space: object requires documentation | |
399 | 486 | The objects in the interface have been released | Space: object requires documentation | |
400 | 487 | The release of the interface has been reset | Space: object requires documentation | |
401 | 488 | Reset of data filtering deactivates all filter functions | Space: object requires documentation | |
402 | 489 | Version &2 of segment &3 released for release &1 | Space: object requires documentation | |
403 | 49 | Color/shape value must be specified | ||
404 | 490 | Segment & is not a BAPI segment | Space: object requires documentation | |
405 | 491 | The BAPI does not support packet processing in the current release | Space: object requires documentation | |
406 | 492 | The ALE outbound interface is incomplete | Space: object requires documentation | |
407 | 493 | The inbound ALE interface is incomplete | Space: object requires documentation | |
408 | 494 | Parameter & in the function module has no reference field/structure | Space: object requires documentation | |
409 | 495 | **** Object & does not belong to the selected category ***** | Space: object requires documentation | |
410 | 496 | Method & of object & has not yet been released. | Space: object requires documentation | |
411 | 497 | Process has been cancelled by user | Space: object requires documentation | |
412 | 498 | You cannot use the tool for dialog method & | Space: object requires documentation | |
413 | 499 | Message type & is not available in the system | Space: object requires documentation | |
414 | 50 | Line 001 is missing for event & | ||
415 | 500 | The IDoc interface is not complete for message type & | Space: object requires documentation | |
416 | 501 | BAPI & has been called successfully | Space: object requires documentation | |
417 | 502 | No existing function module for object & and method & | Space: object requires documentation | |
418 | 503 | Message type & already exists in system | Space: object requires documentation | |
419 | 504 | Packet & is not available in the System | Space: object requires documentation | |
420 | 505 | Function group & does not exist in system | Space: object requires documentation | |
421 | 506 | For object & the method & does not exist | Space: object requires documentation | |
422 | 507 | There is not an ALE interface for object & and method & | Space: object requires documentation | |
423 | 508 | Function module & does not exist | Space: object requires documentation | |
424 | 509 | For object & and method & the message type & already exists | Space: object requires documentation | |
425 | 51 | Infotype must be specified | ||
426 | 510 | syntax error in line & of function module & | Space: object requires documentation | |
427 | 511 | The BAPI must have a RETURN parameter | Space: object requires documentation | |
428 | 512 | & does not exist | Space: object requires documentation | |
429 | 513 | & has been released and cannot be deleted | Space: object requires documentation | |
430 | 514 | & has been deleted | Space: object requires documentation | |
431 | 515 | & has been generated | Space: object requires documentation | |
432 | 516 | The field & of structure & has more than 1000 characters | Space: object requires documentation | |
433 | 517 | Predecessor & exists | Space: object requires documentation | |
434 | 518 | & already exists | Space: object requires documentation | |
435 | 519 | & & | Space: object requires documentation | |
436 | 52 | Function code must be specified | ||
437 | 520 | & is the current version and has not been generated | Space: object requires documentation | |
438 | 521 | IDoc type & already exists in packet & | Space: object requires documentation | |
439 | 522 | Internal syntax error in template &, line & | Space: object requires documentation | |
440 | 523 | Function module & already exists in group &. | Space: object requires documentation | |
441 | 524 | & does not exist and has not been deleted | Space: object requires documentation | |
442 | 525 | Changes in segment & for new definition are not compatible | Space: object requires documentation | |
443 | 526 | & already exists and has not been generated | Space: object requires documentation | |
444 | 527 | An error has occurred assigning data (&) | Space: object requires documentation | |
445 | 528 | & is still being used and has not been deleted | Space: object requires documentation | |
446 | 529 | & has not been generated. Further processing is not possible | Space: object requires documentation | |
447 | 53 | Infotype & is not allowed for object type & | ||
448 | 530 | * Messages for the program generating coding for mapping and conversion | Space: object requires documentation | |
449 | 531 | The structure & could not be read | Space: object requires documentation | |
450 | 532 | Currency amount passed with more than & digits after decimal point | Space: object requires documentation | |
451 | 533 | The field & has already been assigned to the SAP code | Space: object requires documentation | |
452 | 534 | The input field has an incorrect domain or an incorrect data type | Space: object requires documentation | |
453 | 535 | Function module & already exists | Space: object requires documentation | |
454 | 536 | Currency amount & & in field & could not be converted | Space: object requires documentation | |
455 | 537 | & initial v., currency amount & in & was transferred without a currency | Space: object requires documentation | |
456 | 538 | BAPI field contains SAP code. You cannot enter a value. | Space: object requires documentation | |
457 | 539 | No ISO code found for the country key & in the field & | Space: object requires documentation | |
458 | 54 | Relationship & is not allowed between object types & and & ->F1 | ||
459 | 540 | No ISO code found for the currency key & in field & | Space: object requires documentation | |
460 | 541 | No ISO code found for the quantity unit & in field & | Space: object requires documentation | |
461 | 542 | No ISO code found for the language key & in field & | Space: object requires documentation | |
462 | 543 | SAP code: Please assign ISO code field on the detail screen | Space: object requires documentation | |
463 | 544 | Currency amount: Assign currency fields/parameters on the detail screen | Space: object requires documentation | |
464 | 545 | Function module & has been created | Space: object requires documentation | |
465 | 546 | No country key found for the ISO code & in field & | Space: object requires documentation | |
466 | 547 | No currency key found for ISO code & in field & | Space: object requires documentation | |
467 | 548 | No unit of measure found for ISO code & in field & | Space: object requires documentation | |
468 | 549 | No language key found for ISO code & in field & | Space: object requires documentation | |
469 | 55 | Please enter an external object type | ||
470 | 550 | An RFC destination could not be specified for the logical system & | Space: object requires documentation | |
471 | 551 | No internal key found for the PSP element & in field & | Space: object requires documentation | |
472 | 552 | No external key found for the PSP element & in field & | Space: object requires documentation | |
473 | 553 | No internal key found for project definition & in field & | Space: object requires documentation | |
474 | 554 | No external key found for project definition & in field & | Space: object requires documentation | |
475 | 555 | No RFC destination could be determined for the method call. | Space: object requires documentation | |
476 | 556 | Queue name for rule & cannot be set up | The short text describes the object sufficiently | |
477 | 557 | Message ID could not be created (error during CREATE_UUID) | The short text describes the object sufficiently | |
478 | 56 | Please enter a valid type for the related object | ||
479 | 560 | Get details from previous status records with status & | Space: object requires documentation | |
480 | 561 | Cannot process IDocs with syntax errors | Space: object requires documentation | |
481 | 57 | Please enter a valid relationship | ||
482 | 60 | Please specify program and editing routine | ||
483 | 600 | ***** Messages for CPIC communication to R/2 ***** | ||
484 | 601 | RFC destination & for port & is not available | ||
485 | 602 | No STIMEX received, for details refer to R/2 system log or R/2 EDI log | ||
486 | 603 | No acknowledgement received, details: R/2 system log or R/2 EDI log | ||
487 | 604 | No connection to SAP gateway (TXCOM dest. &); for details, SAP system log | Space: object requires documentation | |
488 | 605 | No connection to R/2 (TXCOM dest. &); for details, see SAP system log | Space: object requires documentation | |
489 | 606 | Connection terminated (TXCOM dest. &); details, see R/2 or SAP system log | Space: object requires documentation | |
490 | 607 | R/2 reports incorrect transfer, automatic repetition | ||
491 | 608 | R/2 rejects logon, for details refer to R/2 system log | ||
492 | 609 | Local error in R/2, error code returned: & | ||
493 | 610 | RFC destination &: Parameter & is not maintained | ||
494 | 611 | Segment type &, version &: No segment name found | ||
495 | 620 | ***** Messages for CCMS Monitoring ***** | Space: object requires documentation | |
496 | 621 | There are no suitable transaction IDs | Space: object requires documentation | |
497 | 622 | Internal error in & code &, action could not be carried out. | Space: object requires documentation | |
498 | 623 | Status & and direction & are not compatible | Space: object requires documentation | |
499 | 624 | & TIDs found for this monitoring object but threshold value is & | Space: object requires documentation | |
500 | 625 | Select a work area also | Space: object requires documentation | |
501 | 626 | & IDocs for this monitoring object found but threshold value is & | Space: object requires documentation | |
502 | 627 | Dependent entries in the detail table have also been deleted | Space: object requires documentation | |
503 | 628 | Monitoring object & does not yet exist or has not been specified | Space: object requires documentation | |
504 | 629 | Monitor object for determining key figure via IDocs of specified criteria | Space: object requires documentation | |
505 | 630 | & open change pntrs found for this monitor object - threshold value is & | Space: object requires documentation | |
506 | 631 | Number of IDocs for the defined selection criteria | Space: object requires documentation | |
507 | 632 | Number of open change pointers using the defined selection criteria | Space: object requires documentation | |
508 | 633 | Values <> 0 require a complex selection (see long text) | Space: object requires documentation | |
509 | 634 | Collective nodes for ALE monitoring objects of logical system | Space: object requires documentation | |
510 | 635 | Number of IDocs change pointers IDocs with the defined selection criteria | Space: object requires documentation | |
511 | 636 | Number of tRFC calls to IDocs with the defined selection criteria | Space: object requires documentation | |
512 | 638 | ALE CCMS Monitor: & IDocs in tRFC queue but threshold value is & | Space: object requires documentation | |
513 | 639 | Problem with CCMS runtime monitoring: function & | Space: object requires documentation | |
514 | 650 | ***** _Messages for Modelling ***** | Space: object requires documentation | |
515 | 651 | Filter object type & is not valid | Space: object requires documentation | |
516 | 652 | Reference to message type & for filter object type & is not valid | Space: object requires documentation | |
517 | 653 | Reference to method & for filter object type & is not valid | Space: object requires documentation | |
518 | 654 | Reference to message type & is not valid | Space: object requires documentation | |
519 | 655 | Distribution using classes is not allowed | Space: object requires documentation | |
520 | 656 | System & occurs as the target system several times | Space: object requires documentation | |
521 | 657 | Partner systems must not match in BD64 &1 &2 &3 &4 | The short text describes the object sufficiently | |
522 | 660 | ***** Messages for the Conversion of Logical System Names ***** | Space: object requires documentation | |
523 | 661 | Log for test run: &1 -> &2 in system &3 (initiator &4) | Space: object requires documentation | |
524 | 662 | Log for conversion: &1 -> &2 in system &3 (initiator &4) | Space: object requires documentation | |
525 | 663 | Maintain another subroutine for program &1 | Space: object requires documentation | |
526 | 664 | Table buffer in server synchronized after conversion | Space: object requires documentation | |
527 | 665 | Data inconsistency when running program &1, form routine &2 | Space: object requires documentation | |
528 | 666 | Converting the logical system name & to the name & | Space: object requires documentation | |
529 | 667 | A Process is Running for Test Run &1 -> &2 | Space: object requires documentation | |
530 | 668 | Another Process is Running for Conversion &1 -> &2 | Space: object requires documentation | |
531 | 675 | No authorization for navigation | Space: object requires documentation | |
532 | 676 | RFC destination &1 cannot be accessed under the name &2 | Space: object requires documentation | |
533 | 677 | RFC destination &1 currently not accessible | Space: object requires documentation | |
534 | 678 | Select a valid node | Space: object requires documentation | |
535 | 679 | Conversion can only be started after the test run | Space: object requires documentation | |
536 | 680 | The functions are not available in system &1 | Space: object requires documentation | |
537 | 681 | The logical system name & has been used by client & | Space: object requires documentation | |
538 | 682 | The new logical system name & is assigned to the current client & | Space: object requires documentation | |
539 | 683 | Existence check can only be activated for the test run | Space: object requires documentation | |
540 | 684 | Synchronize table buffer in server & after the conversion | Space: object requires documentation | |
541 | 685 | Table &1 not selected for conversion | Space: object requires documentation | |
542 | 686 | Field &1 in table &2 already contains the name &3 | Space: object requires documentation | |
543 | 687 | Error in field &1 of table &2. Manual correction required. | Space: object requires documentation | |
544 | 688 | An Error has Occurred in Program &1 | Space: object requires documentation | |
545 | 689 | Table &1 was not relevant for conversion | Space: object requires documentation | |
546 | 690 | &1 Entry/Entries in Field &2 of Table &3 Have Been Converted | Space: object requires documentation | |
547 | 691 | &1 entry/ies in field &2 of table &3 are for conversion | Space: object requires documentation | |
548 | 692 | New entry &1 has been entered in field &2 of table &3 | Space: object requires documentation | |
549 | 693 | New entry &1 has been entered in field &2 of table &3 | Space: object requires documentation | |
550 | 694 | Partner profile for &1 &2 &3 has been deactivated | Space: object requires documentation | |
551 | 695 | Error when scheduling the batch job for conversion in system &1 | Space: object requires documentation | |
552 | 696 | Table &1 was processed by a parallel process | The short text describes the object sufficiently | |
553 | 697 | The processs is executed in the background (&1 &2) in system &3 | Space: object requires documentation | |
554 | 698 | No processing available for object &1 | Space: object requires documentation | |
555 | 699 | Table &1 is excluded from the conversion | Space: object requires documentation | |
556 | 700 | ***** Messages for XPRA programs ***** | ||
557 | 701 | The report & was executed successfully. | Space: object requires documentation | |
558 | 702 | Application: & | ||
559 | 703 | Database error occurred when reading table &. | ||
560 | 704 | Database error occurred when writing table &. | ||
561 | 710 | *** Messages for XPRA RBDXBDLT | ||
562 | 711 | Class type & does not exist in client & | ||
563 | 712 | Mo message types were found for the classification object & | ||
564 | 713 | Application ALE (cross-application), client & | ||
565 | 714 | & & & & | ||
566 | 715 | Client &: Validity for the ALE distribution model has been initialized | Space: object requires documentation | |
567 | 72 | Please specify one object ID only | ||
568 | 730 | ***Messages for block processing change pointers | Space: object requires documentation | |
569 | 731 | Setting the block size of message type & has failed | Space: object requires documentation | |
570 | 732 | Incorrect status for block processing with message type & | Space: object requires documentation | |
571 | 733 | Resetting block size for message type & has failed | Space: object requires documentation | |
572 | 750 | **************** Messages for serialized distribution ********** | Space: object requires documentation | |
573 | 751 | Serialization group & does not exist | Space: object requires documentation | |
574 | 752 | Error has occurred scheduling check job | Space: object requires documentation | |
575 | 753 | Serialization group & is being dispatched | Space: object requires documentation | |
576 | 754 | IDocs in serialization group & are still in the tRFC queue | Space: object requires documentation | |
577 | 755 | An error has occurred creating/dispatching the control IDoc | Space: object requires documentation | |
578 | 756 | & IDoc(s) of message type & have been sent | Space: object requires documentation | |
579 | 757 | Message type & has not been specififed for serialization group & | Space: object requires documentation | |
580 | 758 | Message types have not been assigned to the serialization group & | Space: object requires documentation | |
581 | 759 | Check job has been scheduled for serialization group & for &, & | Space: object requires documentation | |
582 | 760 | Error has occurred when determining receiver for SERDAT | Space: object requires documentation | |
583 | 761 | No receiver exists for the group & in the distribution model | Space: object requires documentation | |
584 | 762 | Inbound processing for serialization group & is not defined | Space: object requires documentation | |
585 | 770 | ** Messages for assigning RFC destinations to logical systems | Space: object requires documentation | |
586 | 771 | There is already an entry for this key. | Space: object requires documentation | |
587 | 772 | Please select a logical system | Space: object requires documentation | |
588 | 773 | User is editing the assignments. (You can only display them). | Space: object requires documentation | |
589 | 774 | Please select an RFC destination | Space: object requires documentation | |
590 | 775 | An RFC destination has already been assigned for method &.& | Space: object requires documentation | |
591 | 776 | Entry & does not exist. Check spelling | Space: object requires documentation | |
592 | 777 | Error has occurred making remote call to method & in system & | Space: object requires documentation | |
593 | 778 | Error &3 for the remote call of method &1 in system &2, message &4 | Space: object requires documentation | |
594 | 800 | **************** API message for receiver determination ***************** | Space: object requires documentation | |
595 | 801 | There is no filter object type for filter message type & | Space: object requires documentation | |
596 | 802 | The business object type for message type & does not exist | Space: object requires documentation | |
597 | 803 | No function module has been assigned to the business object type & | Space: object requires documentation | |
598 | 804 | Object & with object ID & has not been found | Space: object requires documentation | |
599 | 805 | Filter object &1 is missing for determining receiver of message type &2 | Space: object requires documentation | |
600 | 806 | Message type & is dependent on itself | Space: object requires documentation | |
601 | 807 | Filter object &1 is not valid for the BAPI table parameter &2. | Space: object requires documentation | |
602 | 808 | Filter object &1 is not valid for BAPI (&2,&3) | Space: object requires documentation | |
603 | 809 | BAPI (&1, &2) is self-dependent | Space: object requires documentation | |
604 | 810 | Filter object &1 is missing for determining receiver of BAPI (&1, &2) | Space: object requires documentation | |
605 | 811 | More than one receiving system has been specified for the BAPI (&1, &2) | Space: object requires documentation | |
606 | 860 | ********** Messages for maintaining hierarchy of BAPI parameters ****** | Space: object requires documentation | |
607 | 861 | Tables &1 and &2 have no shared field reference. | Space: object requires documentation | |
608 | 862 | Please position the cursor on one table parameter | Space: object requires documentation | |
609 | 863 | The hierarchy for the BAPI (&1, &2) already exists. | Space: object requires documentation | |
610 | 864 | No hierarchy for BAPI (&1, &2) exists. | Space: object requires documentation | |
611 | 865 | Tables &1 and &2 do not have a shared reference field | Space: object requires documentation | |
612 | 866 | Table parameter &1 already exists in the hierarchy | Space: object requires documentation | |
613 | 867 | Hierarchy has been saved. | Space: object requires documentation | |
614 | 868 | Error has occurred when write-accessing database table TBD19. | Space: object requires documentation | |
615 | 869 | Hierarchy has been deleted | Space: object requires documentation | |
616 | 870 | Note: The ALE interface must be regenerated afterwards | Space: object requires documentation | |
617 | 871 | The hierarchy has not been modified | Space: object requires documentation | |
618 | 872 | You have not selected field references | Space: object requires documentation | |
619 | 873 | Parameter & does not have parent parameters | Space: object requires documentation | |
620 | 874 | You cannot modify the hierarchy. Refer to the long text. | Space: object requires documentation | |
621 | 875 | Hierarchy has not been created | Space: object requires documentation | |
622 | 876 | The table parameter & is not available in the BAPI interface. | Space: object requires documentation | |
623 | 877 | Child parameter &1 is not assigned to parent parameter &2. | Space: object requires documentation | |
624 | 878 | All the BAPI table parameters in the hierarchy have already been used. | Space: object requires documentation | |
625 | 879 | Name of external structure too long for function module generation | Space: object requires documentation | |
626 | 880 | ISO code & is not assigned to a country key | ||
627 | 881 | Country key & has no ISO code | ||
628 | 882 | ISO code & is not assigned to a currency key in the valid time period | Space: object requires documentation | |
629 | 883 | Currency key & does not have an ISO code | Space: object requires documentation | |
630 | 884 | Unit of measure & has no ISO code | ||
631 | 885 | Language key & does not have an ISO code | Space: object requires documentation | |
632 | 886 | ISO code & has not been assigned to a language key | Space: object requires documentation | |
633 | 887 | For the ISO code &1 there is more than one SAP currency code for ALE | Space: object requires documentation | |
634 | 888 | For the ISO code &1 there is no unique SAP currency code for ALE | Space: object requires documentation | |
635 | 889 | For the currency code &1 ALE communication is not allowed | Space: object requires documentation | |
636 | 890 | You must select a node | Space: object requires documentation | |
637 | 891 | The operation cannot be carried out with this node type | Space: object requires documentation | |
638 | 892 | Processing not possible - use Transaction SM58 | Space: object requires documentation | |
639 | 893 | No IDocs could be selected | Space: object requires documentation | |
640 | 894 | The initialization of the logical system has failed | Space: object requires documentation | |
641 | 895 | Display of logical system & is not implemented | Space: object requires documentation | |
642 | 896 | Error communicating with system & | Space: object requires documentation | |
643 | 897 | No IDoc has been selected | Space: object requires documentation | |
644 | 898 | Error in namespace prefixes of function; see long text | Space: object requires documentation | |
645 | 899 | Name of internal structure too long for function module generation | Space: object requires documentation | |
646 | 90 | Please specify a valid value | ||
647 | 91 | The default position taken from T77S0 already exists in T528B | ||
648 | 999 | & & & & |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |