B1 SAP Message Class - Nachrichten der ALE-Gruppe

B1 is a standard message class available within your SAP system (depending on your versionand release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.

MESSAGE I00(B1).

Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages

Message class details can be viewed directly within your SAP system by entering the object name B1 into the relevant SAP transaction such as SE91 or SE80.

00 No entry in table & for key & & &
000 ***** Messages for input and outbound processing *****
001 No IDoc type maintained for base type & and extension type &




002 Transport contains control data to be distributed - please distribute
003 Could not determine recipients for message type &
004 A separate logical system is not defined for client &
005 & &, &, &.
006 &, &, &, &
007 Segment type & does not exist in message type &
008 Mandatory segment & in message type & cannot be filtered
009 Partner profile missing for recipient & & &, message type &
01 Objects not in T777I do not have an infotype
010 Position the Cursor Correctly
011 Interface changed for message type &1: Settings reset
012 Message type & does not exist
013 Message type & exists already
014 Database error when storing in EDMSG
015 Database error when storing in EDIMSG
016 Database error when storing in EDIMSGT
017 Database error when storing in EDIMAP
018 Port & is not an RFC port, or RFC destination is missing
019 Error when calling asynchronous Remote Function Call
02 Infotype " " is only for objects without infotypes
020 Database error occurred when storing in BDSER
021 No data for entity &
022 Inconsistent IDocs passed: Data records or control records missing.
023 Class type &, receiving system &: no list maintained
024 Object type & not maintained for message type &
025 Distribution model posted successfully
026 Object type & cannot be read for message type & from segment type &
027 No classification object maintained for message type &
028 Database error when storing in BDPNT



029 No distribution class type exists for classification object &
030 ***** Messages for application input *****
031 No (active) partner profile: sender & & &, message type &
032 No process code exists for sender & and message type &
033 No function module for input process code &
034 No parameters found for function module &
035 Maximum no. of repetitions exceeded
036 IDocs in packet do not match
037 Packet contains no IDocs
038 & master IDocs set up for message type &
039 & communication IDoc(s) generated for message type &
040 User & has no authorization for message type & in ALE inbound
041 Table MASTER_IDOC_DATA is empty
042 Direct call started
043 Task & started with workflow ID &
044 Incorrect function module & called up
045 Application function module & terminated with invalid exception.
046 Task & could not be started.
047 Process & could not be started.
048 Process & started with ID &.
049 More than one IDoc transferred
050 ***** Messages for failed Select Singles *****
051 IDoc included in IDoc packet containing an error: transfer it separately
052 Message type included in request
053 Filter object type & not permitted with message type &
054 Control data object & does not exist
055 Message type & does not exist
056 Database error when storing in Table TBD10
057 Database error when storing in Table TBD12
058 Database error when storing in Table TBD13
059 Database error when storing in Table TBDME
060 Database error when storing data in Table &
061 The customer model in HR-ORG could not be deleted
062 Error when assigning numbers to HR-ORG objects
063 & request IDocs created for message type &
064 Remote Function Call destination could not be found
065 Connection to other system could not be established
066 Messages have been created during processing (last was displayed)
067 Number of IDocs: total &, dispatched &, still open (tRFC queue) &
068 Place the cursor on a subsystem
069 Filter object already assigned
070 Internal error: Program &, command &, argument &
071 More than one IDoc selected
072 Place the cursor on a message type
073 Place the cursor on a filter object
074 Distribution model is being processed
075 Function & is not available in this system, termination
076 No object type for lists maintained for message type &
077 This IDoc was forwarded to receiver & & &.



078 Check your entry
079 Message type & included in request &
080 ***** Messages for RBDTBDA1 *****
081 Change pointer generation deactivated
082 Change pointer generation activated
083 No data could be selected.
084 Database error occurred when storing in table TBDMS
085 Error occurred when assigning a number for a change pointer
086 External partner system &: functionality not available
087 Partner system & is an R/2 system: functionality not available
088 RFC destination & does not exist
089 Partner profile & & & & does not exist
090 IDoc type could not be determined for the IDoc
091 Receiver of IDoc is its own logical system
092 Start Transaction & for the check
093 Model & cannot be maintained in own system
094 Message type not permitted, because no ownership for model &
095 Segment & does not exist for message type &
096 Indicator cannot be selected
097 Changes cannot be made to the control data distribution in this system
098 Tool could not be started - please enter call parameters
099 &
10 F key must be specified
100 Linked object: &, &&
101 Message type & does not exist
102 Required segment & cannot be deactivated
103 Segment & has already been deactivated completely
104 No IDoc type found for message type &
105 Message type & exists already
106 Reduction for message type & saved
107 Higher-level segment deactivated
108 Table & for message type & exists already in EDIMAP
109 Please choose an processing type.
11 This combination is not allowed
110 Reference message type may not have reference
111 Generation of change pointers for & activated in client &
112 Reduction for message type & deleted
113 Generation of change pointers for & deactivated in client &
114 Change pointers for message type & active in client &


115 Message type & already being processed
116 An IDoc without a message type was passed to the ALE layer
117 Place the cursor on a valid line and field
118 The IDoc type for this message must not be reduced
119 Message & is not in valid name range
120 Recipient & & & not permissible for this IDoc
121 There is no data maintained in the reduction pool for message type &
122 A server group should be specified with parallel processing
123 No assignment for & company code & to a & company code.
124 For & business area & no assignment to a & business area.
125 You do not have the authorization for the action
126 Foreground processing and parallel processing are not possible together
127 No partner profiles (message control) maintained
128 A message type could not be (uniquely) identified
129 No recipient found for message type & in the ALE model
130 Too many recipients found for message type & in the ALE model
131 Wrong partner type &
132 Select packet size larger than 0
133 IDoc type has not been entered for message type &
134 Change pointer creation is currently deactivated
135 Please maintain ALE Customizing via the IMG
136 All event couplings were activated.
137 You have selected all data records. Did you intend to do this?
138 The tool cannot be executed on your frontend.
139 No data relevant to audit were selected.
140 Error when locking the audit statistics for & & &.
141 Database error when writing status records for the status &.
142 A change period must be specified.
143 Number range for change pointer has not been maintained.
144 Message type & cannot be reduced
145 Message type & is not relevant to reduction
146 The change pointer target should not be changed manually
147 Selection Period for AUDIT IDocs: &1 &2 -> &3 &4
148 Customer distribution model & does not exist
149 Customer distribution model & successfully deleted
150 ***** Error messages in area of serialization *****
151 Object & &: Overtaking process between systems
152 System error occurred when writing to table BDSE
153 Model & is currently being edited by &
154 Warning! You have not done the checkout with the current model
155 Message type & is not within the permitted SAP name range
156 Error locking change pointer for message type &.
157 Message type & cannot be sent with change pointers
158 No parties are interested in the selected data
159 IDoc must be processed later; expected: &; current: &
160 System error has occurred writing data to table BDRGIN
161 Data in table & has been changed and logged in SYSLOG
162 Changing the registry can interrupt the data transfer
163 Data could not be entered in table &. (Does entry already exist?)
164 Data in table & could not be deleted.
165 System error has occurred writing data to table BDRGOUT.
166 Please mark at least one option (outbound and/or inbound)
167 No changes made (don't need to save)
168 & entries in the registry table & have been deleted/ SYSLOG log
169 Change pointers for message type &1 are being migrated
170 ********* Messages for control data **********************************
171 Choose 'Utilities -> Comparison' in the following table maintenance view
172 Report & is not available in this system, you cannot run it.
173 Data has already been maintained by & and therefore can only be displayed
174 System error occurred while writing to table BDEOIO_OUT
175 System error occurred while writing to table BDEOIO_IN
176 Subsequent IDOC already processed; expected: &; current: &
177 Invalid ID for sequence processing
195 ***** Messages for direct model maintenance *****
198 Logical system & must not be deleted
199 Logical system & must not be deleted
20 Please check entry & & & in table &
200 Model view & already exists
201 Place the cursor on a model view
202 Sending system must be different to receiving system
203 Method & has already been added
204 Method & has already been defined in the model view &
205 Place the cursor on a method
206 Distribution model has been saved
207 Distribution model is being edited by user & (You can only display it)
208 This function is not available for this node
209 Input help is not available for the filter object type &
210 Method & cannot be filtered
211 Filter object has already been added
212 No filter has been defined for method &
213 Distribution model has not been changed
214 Message type & has already been added
215 Message type & has already been defined in the model view &
216 Place the cursor on a message type
217 No filter available for message type &
218 No further filter available for message type &
219 No filter has been defined for message type &
220 Reference to message type & has already been defined
221 End date cannot be earlier than the start date
222 The valid time period overlaps with that of the model view &
223 Classes are defined in a separate Customizing transaction
224 First save the distribution model
225 Model view & does not exist and has been deleted in target systems
226 Method & has not been assigned a message type
227 You are not authorized to carry out this action
228 Model view has not been specified
229 Maintenance systems for model view & are not the same
230 Method & has already been defined in the model view &
231 Message type & has already been defined in model view &
232 The distribution model is currently being processed
233 Model view & has been created
234 Model view & has been changed
235 Model view & has been deleted
236 Model view & must not be maintained in your own system
237 You are not authorized to create the model view &
238 You are not authorized to change the model view &
239 Client and server must be different systems
240 You are not authorized to delete the model view &
241 You are not authorized to transport model view &
242 You are not authorized to distribute the model view &
243 Distribution model has been edited by user &
244 Object & is already defined in the model view &
245 Distribution via classes for object & has already been defined
246 Reference to method & has already been defined
247 Model view & already exists and will be completely overwritten
248 Define the conversion of the logical systems for copying
249 This message type belongs to object method &.&.
250 ***** Error messages for "manual input" method *****
251 IDoc number & does not exist in the database
252 Function module not allowed: &
253 IDoc & has not been edited
254 Error during application input
255 IDoc successfully processed by the application
256 Previous status & unsuitable
257 IDoc has been flagged for deletion
258 No event found to trigger
259 No object type found for event
260 Error when opening IDoc: IDoc locked
261 Error when opening IDoc: IDoc does not exist
262 Error when opening IDoc: IDoc number is invalid
263 Error when reading IDoc: IDoc number is invalid
264 Error when reading IDoc: no data
265 Error when writing IDoc status: IDoc number is invalid
266 Error writing IDoc status: Database error
267 Error when writing IDoc status: Invalid status
268 Error when writing IDoc status: No status record exists
269 Error when closing IDoc: IDoc not opened
270 Error when closing IDoc: Database error
271 Error when closing IDoc: Incorrect parametrization
272 Error when closing IDoc: Status not set
273 Error: Incorrect IDoc status value
274 Caution: & IDocs have been selected
275 Error writing IDOC status: IDoc locked
276 More than one IDoc in packet: Application supports single processing only
277 Error when opening IDoc: IDoc already opened
278 IDoc &: status & cannot be processed
279 The IDocs have no data records
280 The IDocs do not exist in the database
281 IDocs not specified
282 Error: No IDocs to be processed
283 There is no ALE link object defined.
284 Link object not in IDOC.
285 You are not authorized to display/edit IDoc &
286 Server group & could not be initialized
287 Number of maximum attempts to start parallel processes has been exceeded
288 & of & IDocs could be transferred in parallel for processing
300 ***** Error messages in area 'ALE error handling' *****
301 IDoc & does not exist, processing not possible
302 No details exist for message
303 Error when processing IDoc &
304 IDoc & flagged for deletion
305 IDoc & already processed, processing not possible
306 Status set within ALE/EDI error handling
307 Status reset after editing IDoc
308 IDoc & can be passed to the port
309 IDoc & successfully passed to the port
310 IDoc & can be tranferred to the application
311 IDoc & successfully passed to the application
312 More IDocs created from IDoc &
313 IDoc & successfully processed
314 IDoc flagged for deletion
315 More IDocs have been created from the IDoc
316 No status records exist for IDoc &, processing not possible
317 Report has reset status
318 Resetting the status may result in data inconsistency
350 ***** More messages for input *****
351 Errors when compiling version: Target structure & & does not match IDoc
352 IDoc has wrong status
353 Parameter & missing in container of task &
354 Version & of process code & not allowed for ALE
355 No object for requested IDoc selected for sending
356 Account group in the IDoc is different
357 Status records with status 51 after status 53
358 No status record was passed to ALE by the application
359 No active event coupling for & . & found, no error work items
360 Status was set automatically
38 An editing module must be specified
40 Field & does not belong to structure & of infotype &
400 ***** Messages for ALE Customizing *****
401 Object class & does not exist
402 Table & for object class & does not exist
403 Table & is not an active table
404 Field & does not exist in table &
405 Application object type & is not planned
406 Assignment not allowed
407 Segment type & deactivated for message type &
408 Field & in segment type & deactivated for message type &
409 A check table has not been defined for field & in table &
41 Structure to infotype & not found
411 Object type & may only be assigned to fields from one segment type
412 Segment type & not defined for message type &
413 Field & in segment type & does not exist
414 Conversion rule & does not exist
415 Conversion rule & for segment type & does not exist
416 Object type & is assigned to fields from more than one segment type
417 Required segment & may not be filtered
418 Segment type & does not exist
419 Segment type & does not exist in active form
42 Relationship & is unknown
420 Selected function not implemented for message type &
421 Function not possible for the selected line
422 Logical system & does not exist
423 You are logged on to partner system &
424 Maintenance transaction & not defined in partner system &
425 Purchasing organization & does not exist
426 Vendor & does not exist
427 Material & does not exist
428 RFC destination & does not exist
429 Specify the RFC destination for logical system &
430 Sales organization & does not exist
431 Distribution channel & does not exist
432 Order type & does not exist
433 Partner status & does not exist
434 Language & does not exist
435 Output mode & does not exist
436 Processing & is not defined
437 The maintenance transaction & is not defined in own system &
438 No application object type planned for the function module
439 Cross-system checking is active.
44 Entries for external object types are not allowed (acc. to table T77EO)
440 Cross-system checking is inactive.
441 There are no inspection results available for the selected line.
442 There are no receiver systems defined in the distribution model
443 Select at least one system.
444 The table for the listing data for message type & is not defined.
445 Distribution-relevant class type for table & is not defined.
446 Class & is not defined for class type &.
447 To display the test results choose 'Edit -> Detail'
448 ***** Messages for the conversion pre-production => production *****
449 Table &: & of & entries in field & converted (client-independent)
45 Symbols entered are not allowed
450 Table &: & of & entries in field & converted (client-dependent)
451 The logical system & is already allocated to another system
452 The logical system & is not taken into account in any conversion
453 The logical system name &1 has been converted to name &2 in client &3
454 The logical system & has not yet been defined
455 The logical system name & already exists
456 The new logical system name & is the same as the old name &
457 Error creating program &
458 Syntax error in program & line &
459 Conversion of logical system name & for name & in client &
46 Entries in the field Ext are allowed in * lines 01-12 only
460 ***** Messages for ALE Recovery Tool *****
461 No system selected
462 No documentation is available for object & in language &.
463 Please choose the participating systems first.
464 Please check system settings before starting the process.
465 The processing type of some IDocs has not been defined.
466 IDoc & no longer exists in system &.
467 The process "Determine recovery objects" has been started in system &.
468 System & has been reset to the status on & at &.
469 An error has occurred when checking IDoc dispatch for system &.
47 Profile ID 'O' (object-oriented) or 'S' (status-oriented) allowed
470 An error has occurred during message transmission.
471 A tRFC entry with ID && has been deleted in system &.
472 No data could be selected for partner system &.
473 ALE recovery tool converts status
474 No log found
476 Could not determine any tables
477 Read the online documentation before carrying out the transaction
478 No logical system name has been defined for client &
479 Table &: & of & entries in field & converted (client-dependent)
480 ***** Messages for BAPIs <-> ALE generating tool *****
481 BAPI &.& does not exist in the system
482 Reference type & is not a structure and therefore it is not allowed
483 For the message type & there is no IDoc type &
484 Only some of the objects in the interface have been released
485 The release of the interface has been partly reset
486 The objects in the interface have been released
487 The release of the interface has been reset
488 Reset of data filtering deactivates all filter functions
489 Version &2 of segment &3 released for release &1
49 Color/shape value must be specified
490 Segment & is not a BAPI segment
491 The BAPI does not support packet processing in the current release
492 The ALE outbound interface is incomplete
493 The inbound ALE interface is incomplete
494 Parameter & in the function module has no reference field/structure
495 **** Object & does not belong to the selected category *****
496 Method & of object & has not yet been released.
497 Process has been cancelled by user
498 You cannot use the tool for dialog method &
499 Message type & is not available in the system
50 Line 001 is missing for event &
500 The IDoc interface is not complete for message type &
501 BAPI & has been called successfully
502 No existing function module for object & and method &
503 Message type & already exists in system
504 Packet & is not available in the System
505 Function group & does not exist in system
506 For object & the method & does not exist
507 There is not an ALE interface for object & and method &
508 Function module & does not exist
509 For object & and method & the message type & already exists
51 Infotype must be specified
510 syntax error in line & of function module &
511 The BAPI must have a RETURN parameter
512 & does not exist
513 & has been released and cannot be deleted
514 & has been deleted
515 & has been generated
516 The field & of structure & has more than 1000 characters
517 Predecessor & exists
518 & already exists
519 & &
52 Function code must be specified
520 & is the current version and has not been generated
521 IDoc type & already exists in packet &
522 Internal syntax error in template &, line &
523 Function module & already exists in group &.
524 & does not exist and has not been deleted
525 Changes in segment & for new definition are not compatible
526 & already exists and has not been generated
527 An error has occurred assigning data (&)
528 & is still being used and has not been deleted
529 & has not been generated. Further processing is not possible
53 Infotype & is not allowed for object type &
530 * Messages for the program generating coding for mapping and conversion
531 The structure & could not be read
532 Currency amount passed with more than & digits after decimal point
533 The field & has already been assigned to the SAP code
534 The input field has an incorrect domain or an incorrect data type
535 Function module & already exists
536 Currency amount & & in field & could not be converted
537 & initial v., currency amount & in & was transferred without a currency
538 BAPI field contains SAP code. You cannot enter a value.
539 No ISO code found for the country key & in the field &
54 Relationship & is not allowed between object types & and & ->F1
540 No ISO code found for the currency key & in field &
541 No ISO code found for the quantity unit & in field &
542 No ISO code found for the language key & in field &
543 SAP code: Please assign ISO code field on the detail screen
544 Currency amount: Assign currency fields/parameters on the detail screen
545 Function module & has been created
546 No country key found for the ISO code & in field &
547 No currency key found for ISO code & in field &
548 No unit of measure found for ISO code & in field &
549 No language key found for ISO code & in field &
55 Please enter an external object type
550 An RFC destination could not be specified for the logical system &
551 No internal key found for the PSP element & in field &
552 No external key found for the PSP element & in field &
553 No internal key found for project definition & in field &
554 No external key found for project definition & in field &
555 No RFC destination could be determined for the method call.
556 Queue name for rule & cannot be set up
557 Message ID could not be created (error during CREATE_UUID)
56 Please enter a valid type for the related object
560 Get details from previous status records with status &
561 Cannot process IDocs with syntax errors
57 Please enter a valid relationship
60 Please specify program and editing routine
600 ***** Messages for CPIC communication to R/2 *****
601 RFC destination & for port & is not available
602 No STIMEX received, for details refer to R/2 system log or R/2 EDI log
603 No acknowledgement received, details: R/2 system log or R/2 EDI log
604 No connection to SAP gateway (TXCOM dest. &); for details, SAP system log
605 No connection to R/2 (TXCOM dest. &); for details, see SAP system log
606 Connection terminated (TXCOM dest. &); details, see R/2 or SAP system log
607 R/2 reports incorrect transfer, automatic repetition
608 R/2 rejects logon, for details refer to R/2 system log
609 Local error in R/2, error code returned: &
610 RFC destination &: Parameter & is not maintained
611 Segment type &, version &: No segment name found
620 ***** Messages for CCMS Monitoring *****
621 There are no suitable transaction IDs
622 Internal error in & code &, action could not be carried out.
623 Status & and direction & are not compatible
624 & TIDs found for this monitoring object but threshold value is &
625 Select a work area also
626 & IDocs for this monitoring object found but threshold value is &
627 Dependent entries in the detail table have also been deleted
628 Monitoring object & does not yet exist or has not been specified
629 Monitor object for determining key figure via IDocs of specified criteria
630 & open change pntrs found for this monitor object - threshold value is &
631 Number of IDocs for the defined selection criteria
632 Number of open change pointers using the defined selection criteria
633 Values <> 0 require a complex selection (see long text)
634 Collective nodes for ALE monitoring objects of logical system
635 Number of IDocs change pointers IDocs with the defined selection criteria
636 Number of tRFC calls to IDocs with the defined selection criteria
638 ALE CCMS Monitor: & IDocs in tRFC queue but threshold value is &
639 Problem with CCMS runtime monitoring: function &
650 ***** _Messages for Modelling *****
651 Filter object type & is not valid
652 Reference to message type & for filter object type & is not valid
653 Reference to method & for filter object type & is not valid
654 Reference to message type & is not valid
655 Distribution using classes is not allowed
656 System & occurs as the target system several times
657 Partner systems must not match in BD64 &1 &2 &3 &4
660 ***** Messages for the Conversion of Logical System Names *****
661 Log for test run: &1 -> &2 in system &3 (initiator &4)
662 Log for conversion: &1 -> &2 in system &3 (initiator &4)
663 Maintain another subroutine for program &1
664 Table buffer in server synchronized after conversion
665 Data inconsistency when running program &1, form routine &2
666 Converting the logical system name & to the name &
667 A Process is Running for Test Run &1 -> &2
668 Another Process is Running for Conversion &1 -> &2
675 No authorization for navigation
676 RFC destination &1 cannot be accessed under the name &2
677 RFC destination &1 currently not accessible
678 Select a valid node
679 Conversion can only be started after the test run
680 The functions are not available in system &1
681 The logical system name & has been used by client &
682 The new logical system name & is assigned to the current client &
683 Existence check can only be activated for the test run
684 Synchronize table buffer in server & after the conversion
685 Table &1 not selected for conversion
686 Field &1 in table &2 already contains the name &3
687 Error in field &1 of table &2. Manual correction required.
688 An Error has Occurred in Program &1
689 Table &1 was not relevant for conversion
690 &1 Entry/Entries in Field &2 of Table &3 Have Been Converted
691 &1 entry/ies in field &2 of table &3 are for conversion
692 New entry &1 has been entered in field &2 of table &3
693 New entry &1 has been entered in field &2 of table &3
694 Partner profile for &1 &2 &3 has been deactivated
695 Error when scheduling the batch job for conversion in system &1
696 Table &1 was processed by a parallel process
697 The processs is executed in the background (&1 &2) in system &3
698 No processing available for object &1
699 Table &1 is excluded from the conversion
700 ***** Messages for XPRA programs *****
701 The report & was executed successfully.
702 Application: &
703 Database error occurred when reading table &.
704 Database error occurred when writing table &.
710 *** Messages for XPRA RBDXBDLT
711 Class type & does not exist in client &
712 Mo message types were found for the classification object &
713 Application ALE (cross-application), client &
714 & & & &
715 Client &: Validity for the ALE distribution model has been initialized
72 Please specify one object ID only
730 ***Messages for block processing change pointers
731 Setting the block size of message type & has failed
732 Incorrect status for block processing with message type &
733 Resetting block size for message type & has failed
750 **************** Messages for serialized distribution **********
751 Serialization group & does not exist
752 Error has occurred scheduling check job
753 Serialization group & is being dispatched
754 IDocs in serialization group & are still in the tRFC queue
755 An error has occurred creating/dispatching the control IDoc
756 & IDoc(s) of message type & have been sent
757 Message type & has not been specififed for serialization group &
758 Message types have not been assigned to the serialization group &
759 Check job has been scheduled for serialization group & for &, &
760 Error has occurred when determining receiver for SERDAT
761 No receiver exists for the group & in the distribution model
762 Inbound processing for serialization group & is not defined
770 ** Messages for assigning RFC destinations to logical systems
771 There is already an entry for this key.
772 Please select a logical system
773 User is editing the assignments. (You can only display them).
774 Please select an RFC destination
775 An RFC destination has already been assigned for method &.&
776 Entry & does not exist. Check spelling
777 Error has occurred making remote call to method & in system &
778 Error &3 for the remote call of method &1 in system &2, message &4
800 **************** API message for receiver determination *****************
801 There is no filter object type for filter message type &
802 The business object type for message type & does not exist
803 No function module has been assigned to the business object type &
804 Object & with object ID & has not been found
805 Filter object &1 is missing for determining receiver of message type &2
806 Message type & is dependent on itself
807 Filter object &1 is not valid for the BAPI table parameter &2.
808 Filter object &1 is not valid for BAPI (&2,&3)
809 BAPI (&1, &2) is self-dependent
810 Filter object &1 is missing for determining receiver of BAPI (&1, &2)
811 More than one receiving system has been specified for the BAPI (&1, &2)
860 ********** Messages for maintaining hierarchy of BAPI parameters ******
861 Tables &1 and &2 have no shared field reference.
862 Please position the cursor on one table parameter
863 The hierarchy for the BAPI (&1, &2) already exists.
864 No hierarchy for BAPI (&1, &2) exists.
865 Tables &1 and &2 do not have a shared reference field
866 Table parameter &1 already exists in the hierarchy
867 Hierarchy has been saved.
868 Error has occurred when write-accessing database table TBD19.
869 Hierarchy has been deleted
870 Note: The ALE interface must be regenerated afterwards
871 The hierarchy has not been modified
872 You have not selected field references
873 Parameter & does not have parent parameters
874 You cannot modify the hierarchy. Refer to the long text.
875 Hierarchy has not been created
876 The table parameter & is not available in the BAPI interface.
877 Child parameter &1 is not assigned to parent parameter &2.
878 All the BAPI table parameters in the hierarchy have already been used.
879 Name of external structure too long for function module generation
880 ISO code & is not assigned to a country key
881 Country key & has no ISO code
882 ISO code & is not assigned to a currency key in the valid time period
883 Currency key & does not have an ISO code
884 Unit of measure & has no ISO code
885 Language key & does not have an ISO code
886 ISO code & has not been assigned to a language key
887 For the ISO code &1 there is more than one SAP currency code for ALE
888 For the ISO code &1 there is no unique SAP currency code for ALE
889 For the currency code &1 ALE communication is not allowed
890 You must select a node
891 The operation cannot be carried out with this node type
892 Processing not possible - use Transaction SM58
893 No IDocs could be selected
894 The initialization of the logical system has failed
895 Display of logical system & is not implemented
896 Error communicating with system &
897 No IDoc has been selected
898 Error in namespace prefixes of function; see long text
899 Name of internal structure too long for function module generation
90 Please specify a valid value
91 The default position taken from T77S0 already exists in T528B
999 & & & & .