Menu

SAP Message Class E1

Nachrichten für IDoc-Basis

Recommended Now

All-new Echo Dot Smart speaker with Alexa

This bundle includes Echo Dot (3rd Gen) Charcoal and Philips Hue White A19 Medium Lumen Smart Bulb, 1100 Lumens. Built in Smart Home hub. Ask Alexa to control Zigbee-compatible devices. No additional Philips Hue hub required. Two choices for easy smart lighting - Start setting the mood with Hue Smart bulbs and your Echo device, supporting up to 5 Hue Bluetooth & Zigbee smart bulbs. Add the Hue Hub for whole-home smart lighting (up to 50 light points) and bonus features.

Check it out on amazon.com →

The Message Class E1 (Nachrichten für IDoc-Basis) is a standard Message Class in SAP ERP and is part of the package SED.

Technical Information

Message Class E1
Short Text Nachrichten für IDoc-Basis
Package SED

Messages

ID Language Text
000 D
001 D **Beginn der Umsetzung der Tabellen der IDoc-Basis
002 D **Umsetzung der Ports (Tabellen EDIPO und EDIPOI)
003 D **Umsetzung der globalen Admin.daten (Tabelle EDADM)
004 D **Umsetzung der Segmenttyp- und Segmentdefinitionstabellen
005 D **Umsetzung der Basis-Idoctypen und Erweiterungen
006 D **Erstellung Verknüpfungen Vorgangscode <-> logische Nachricht
007 D Tabelle & wurde erfolgreich aktualisiert (& Einträge)
008 D Fehler beim Füllen der Tabelle &
009 D Fehler beim Aktualisieren der Tabelle &
010 D **Füllen der kundeneigenen Einträge für DOCTYP (Tabelle EDI_CNVDOC)
011 D
012 D **Umsetzung der Status-Customizing-Daten (Tabellen TEDS1,TEDS3)
013 D Fehler bei Update der Tabelle &
014 D Tabelle & bereits vollständig gefüllt
030 D
031 D Das IDoc '&' wurde auf Status '30' gesetzt.
100 D
101 D Keine Einträge für diese Selektionskriterien vorhanden
102 D Konsistenzprüfung für Partnervereinbarungen
103 D System & Mandant &
104 D Datum & Uhrzeit &
105 D Partnervereinbarung &
106 D Kopfeintrag (Tabelle EDPP1)
107 D Empfänger von Benachrichtigungen existiert
108 D Unbekannter Empfänger: & &
109 D Korrekter Partnerstatus
110 D Ungültiger Partnerstatus: &
111 D Eintrag &
112 D Einträge zur Nachrichtensteuerung (Tabelle EDP12)
113 D Logische Nachricht existiert
114 D Logische Nachricht existiert nicht: &
115 D Vorgangscode (Ausgang) existiert
116 D Vorgangscode (Ausgang) existiert nicht: &
117 D Einträge zur Ausgangsverarbeitung (Tabelle EDP13)
118 D Port existiert
119 D Port existiert nicht: &
120 D Paketgröße für asynchronen RFC fehlerhaft: &
121 D Ausgabemodus für asynchronen RFC nicht zugelassen: &
122 D Basistyp existiert
123 D Basistyp existiert nicht: &
124 D Erweiterung existiert
125 D Erweiterung existiert nicht: &
126 D Verknüpfung zwischen log. Nachricht und IDoc-Typ existiert
127 D Verknüpfung zwischen log. Nachricht und IDoc-Typ existiert nicht (EDIMSG)
128 D Einträge zur Eingangsverarbeitung (Tabelle EDP21)
129 D Vorgangscode (Eingang) existiert
130 D Vorgangscode (Eingang) existiert nicht: &
131 D RC = &
132 D Ausgangsvereinbarung für diesen Eintrag existiert
133 D Ausgangsvereinbarung für diesen Eintrag fehlt
134 D Nachrichtensteuerungseintrag für diesen Eintrag existiert
135 D Nachrichtensteuerungseintrag für diesen Eintrag fehlt
136 D View auf IDoc-Typ existiert
137 D Ungültige Partnernummer: &
138 D Nachrichtensteuerungseintrag existiert bereits
150 D Kombination aus Basistyp und Erweiterung ist möglich
151 D Kombination ist nicht möglich: & und &
200 D
201 D Bitte geben Sie eine gültige Sicht ein
202 D Parameter für Nachrichtensteuerung werden bereits verwendet -> Langtext
203 D Es wurden keine IDocs erstellt
204 D IDoc & wurde erstellt
205 D Es wurden mehrere IDocs erstellt (Erstes IDoc: &)
206 D Bitte geben Sie einen IDoc-Typen ein
207 D Logische Nachricht & existiert nicht
208 D Die Anzeige konnte nicht aktualisiert werden
209 D Bitte einen Eintrag auswählen
210 D Es wurden keine Einträge gemäß Selektion gefunden
211 D Ausgangsparameter werden ohne Nachrichtensteuerung kopiert -> Langtext
212 D Der markierte Eintrag konnte nicht ermittelt werden
213 D Die Packetgröße wurde auf 1 gesetzt
214 D Die Anzeige konnte nicht aktualisiert werden
215 D Partner existiert nicht
216 D Partnerart & existiert nicht, nur Anzeige möglich
217 D Keine Berechtigung zur Anzeige für Partner &, Partnerart &
218 D Keine Berechtigung zum Ändern der Partnervereinbarung
219 D Keine Berechtigung zum Anlegen der Partnervereinbarung
250 D
251 D Sie haben keine Berechtigung für diese Transaktion
252 D Sie haben keine Berechtigung zum Ausführen von diesem Programm
270 D
271 D Es wurden keine IDocs verarbeitet
272 D IDoc & im Status &: &
273 D Nicht alle IDocs konnten gelöscht werden
274 D Port & existiert bereits
275 D Port & wurde angelegt
276 D Partnervereinbarung für Partner &, Partnerart & wurde angelegt
300 D
301 D Bitte geben Sie zum Anlegen einen Portnamen ein
302 D Port & existiert bereits ! Bitte anderen Namen wählen !
303 D Logisches Verzeichnis '&' ist nicht definiert!
304 D Ersatzzeichenfolge muß verschieden sein von zu ersetzendem Sonderzeichen
305 D Für Einschalten der Umsetzung bitte zuerst Umsetztabelle pflegen
306 D Ersatzzeichenfolge '&' enthält zu ersetzendes Sonderzeichen '&'
307 D Zu ersetzendes Sonderzeichen darf nicht leer sein!
308 D 'Portnamen generieren' ist ausgewählt worden! Name wird ignoriert !
309 D Sonderzeichen '&' wird durch Leerzeichen ersetzt! Bitte prüfen!
310 D
311 D Dem Nachrichtentyp & ist im & kein Vorgangscode zugeordnet
312 D Der Vorgangscode & wird in den Partnervereinbarungen nicht verwendet
313 D Für den Verwendungsnachweis bitte auf einen Vorgangscode positionieren
314 D Nachrichtentyp nicht gefunden
315 D Der Port & wird in den Partnervereinbarungen nicht verwendet
316 D Port nicht gefunden
317 D Kein Portname für Suche angegeben
318 D Der Port & wurde in der Zwischenzeit von einem anderen Benutzer gelöscht
319 D Port war unvollständig und konnte nicht gesichert werden !
320 D -> Nachrichten Statusverarbeitung
321 D Statuseingang für Eingangs-IDocs nicht unterstützt (IDocNr & in Datei &)
322 D Statuseingang für Eingangs-IDocs nicht unterstützt (IDocNr & in IDoc &)
323 D OPEN-Fehler CONVT_CODEPAGE_INIT für Port & und Datei & bei Statuseingang
324 D OPEN-Fehler CONVT_CODEPAGE_INIT tritt im angegebenen Verzeichnis auf
325 D Lesefehler CONVT_CODEPAGE beim Statuseingang aus Datei &
326 D Weiterverarbeitung trotz CONVT_CODEPAGE beim Statuseingang aus Datei &
327 D Bitte 'weiter trotz Konvertierungsfehlern' auch aktivieren
400 D Meldungen für MDMP-Kommunikation
401 D Port & ist kein tRFC-Port, keine MDMP-Kommunikation möglich
402 D Codepages für den tRFC-Port & konnten nicht ermittelt werden
403 D Keine Definition der Sprachenfelder in den Segmenten gepflegt
404 D Für die RFC-Destination des Ports & ist keine Sprache gepflegt
405 D IDoc mit MDMP-Technik an tRFC-Port gesendet
406 D Es konnte keine Codepage für den Port & und Sprache & ermittelt werden.
407 D Die Unicode Einstellungen in der SM59 (Destination &) stimmen nicht.
408 D Destination & ist Unicode
409 D Keine gültige Sprach-Codepage Kombination gefunden (Destination &).
410 D Destination (&, Typ 3, ABAP-Verbindung) existiert nicht
411 D Fehler beim Verbindungsaufbau (Destination &).
412 D &1&2&3&4
413 D Die hinterlegte RFC-Destination hat keine Anmeldesprache
414 D Zielsystem ist kein Unicodesystem
415 D Zielsystem ist kein Nicht-Unicodesystem
416 D Die benutzte Destination ist nicht vom Typ 3
431 D qRFC-Kommunikation mit einem externen System
000 E & & & &
001 E **Start of conversion of IDoc basis tables
002 E **Conversion of ports (tables EDIPO and EDIPOI)
003 E **Conversion of global admin. data (table EDADM)
004 E **Conversion of segment type tables and segment definition tables
005 E **Conversion of basic IDoc types and extensions
006 E **Create links: process code <-> logical message
007 E Table & updated successfully (& entries)
008 E Error filling table &
009 E Error updating table &
010 E **Completion of customer-specific entries for DOCTYP (table EDI_CNVDOC)
011 E
012 E **Conversion of status customizing data (tables TEDS1,TEDS3)
013 E Error during update of table &
014 E Table & already completely filled
015 E $ has already been agreed in the partner. $ $ $ selected
018 E Fcode in SAP segment $SA (table TEDAS) is missing
019 E Wrong direction entered, please correct
020 E Please specify $
030 E
031 E IDoc '&' has been set to status '30'.
100 E
101 E No entries for these selection criteria
102 E Consistency check for partner profiles
103 E System & Client &
104 E Date & Time &
105 E Partner profile &
106 E Header entry (table EDPP1)
107 E Recipient of notifications exists
108 E Unknown recipient: & &
109 E Correct partner status
110 E Invalid partner status: &
111 E Entry &
112 E Entries for Message Control (table EDP12)
113 E Logical message exists
114 E Logical message does not exist: &
115 E Process code (outbound) exists
116 E Process code (outbound) does not exist: &
117 E Entries for outbound processing (table EDP13)
118 E Port exists
119 E Port does not exist: &
120 E Packet size for asynchronous RFC has errors: &
121 E Output mode for asynchronous RFC is not permitted: &
122 E Basic type exists
123 E Basic type does not exist: &
124 E Extension exists
125 E Extension does not exist: &
126 E Link exists between logical message and IDoc type
127 E No link exists between logical message and IDoc type (EDIMSG)
128 E Entries for inbound processing (table EDP21)
129 E Process code (inbound) exists
130 E Process code (inbound) does not exist: &
131 E RC - &
132 E Outbound profile exists for this entry
133 E No outbound profile for this entry
134 E Message Control entry exists for this entry
135 E No Message Control entry for this entry
136 E View of IDoc type exists already
137 E Invalid partner number: &
138 E Message Control entry already exists
139 E The basis for the copy must be an incoming message.
140 E Translation set $, partner $, appl. ID $, comp. code $ exists (outbound)
141 E Translation set $ is entered for partner $, comp. code $ exists (inbound)
142 E Issue version (TEDAN) must be identical when copying.
143 E Allocation set $ saves
144 E Maximum $ repetitions allowed for group $.
145 E Maximum $ repetitions allowed for segment $.
146 E Error testing number segments and/or groups.
147 E Deletion not allowed.
148 E Position cursor on qualifier line.
149 E Screen $ for screen group $ not in table TEDIF.
150 E Combination of basic type and extension is possible
151 E Combination is not possible: & and &
152 E Specify screen name in field 'screen'.
153 E Screen change impossible.
154 E Message type $ not in table TEDAN.
155 E Table $ does not exist.
156 E Report $ does not exist.
157 E Fill either field or constant.
158 E Incomplete entry.
159 E Deviating standards not allowed (cf. TEDAN -> PF: 1).
160 E Copy basis is a non-SAP application (cf. TEDAN -> PF: 1).
161 E Copy basis is not a non-SAP application (cf. TEDAN -> PF: 1).
162 E Message type $ does not exist for EDI standard $.
163 E Issue $ does not exist for EDI standard $, message type $.
164 E Transaction code $ not in table STC.
165 E Entry not found in table TEDIM.
166 E String not found.
167 E Component $ ($) is not installed.
168 E Translation set already exists. Direction change is not allowed.
169 E Maintain table TEDSS (service segments) for EDI standard $.
170 E Translation set $ deleted
171 E Reference object $ copied
172 E Reference object $ does not exist
177 E Message type $ does not exist for EDI standard $
178 E Maintain message type for table TEDIF
179 E Allocation parameter $ exists, reference not possible
200 E
201 E Enter a valid view
202 E Parameters for message control already used -> long text
203 E No IDocs created
204 E IDoc & created
205 E Several IDocs created (first IDoc: &)
206 E Enter an IDoc type
207 E Logical message & does not exist
208 E The display could not be updated
209 E Choose an entry
210 E No entries found that match selection criteria
211 E Outbound parameters are copied without Message Control -> Long text
212 E The selected entry could not be determined
213 E The packet size has been set to 1
214 E The display could not be updated
215 E Partner does not exist
216 E Partner type & does not exist, display only possible
217 E No Authorization to Display for Partner &, Partner Type &
218 E No Authorization to Change Partner Profile
219 E No Authorization to Create Partner Profile
220 E Mandatory composite data element is missing
221 E Invalid +/- sign position
222 E Invalid decimal point position
223 E Several decimal points
224 E Several +/- signs
230 E Segment not in standard data
231 E Segment on invalid position
232 E Mandatory segment is missing
233 E Invalid segment group repetition.
234 E Invalid segment repetition
235 E Segment not in the message type
236 E Segment in invalid sequence
237 E Invalid character after segment name
240 E Message type / version not in standard data
250 E
251 E You do not have authorization for this transaction
252 E You do not have authorization to execute this program
270 E
271 E No IDocs were processed
272 E IDoc & in status &: &
273 E Not all IDocs could be deleted
274 E Port & already exists
275 E Port & has been created
276 E Partner profile for partner &, partner type & has been created
299 E
300 E
301 E Enter to create a port name
302 E Port & already exists! Choose a different name!
303 E Logical directory '&' has not been defined!
304 E Rplcmnt character seq. must differ from special characters to be replaced
305 E To activate the conversion, you must first maintain the conversion table
306 E Rplcmnt character seq. '&' contains special character '&' to be replaced
307 E Special character to be replaced must not be left empty!
308 E 'Generate port name' has been selected! Name is ignored!
309 E Special character '&' is replaced by a blank character! Check!
310 E
311 E Message type & has not been assigned a process code in &
312 E Process code & is not used in the partner parameters
313 E Position the cursor on a process code for the where-used list
314 E Message type not found
315 E Port & is not used in partner profiles
316 E Port not found
317 E No port name entered for the search
318 E Port & has been deleted in the meantime by another user
319 E Port was incomplete and could not be saved!
320 E -> Messages status processing
321 E Inbound status for inbound IDocs not supported (IDoc no. & in file &)
322 E Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &)
323 E OPEN error CONVT_CODEPAGE_INIT for port & and file & for status inbound
324 E OPEN error CONVT_CODEPAGE_INIT occurs in directory entered
325 E Read error CONVT_CODEPAGE for status inbound from file &
326 E Further processing despite CONVT_CODEPAGE in status inbound from file &
327 E Also activate 'Continue despite conversion errors'
328 E Select 'Save' again to save the subset incompletely
329 E Select 'Back' again to end the transaction without saving.
330 E Subset already exists with subset identifier $.
331 E Issue $ not found for EDI standard $.
332 E No codes have been chosen
333 E Message type $ not found for issue $, EDI standard $.
334 E Controlling agency $ not found in table TEDSU.
335 E Subset identifier must be two-digit.
336 E No controlling agency maintained for EDI standard $, issue $.
337 E The attributes must not be changed.
338 E Translation set $ exists for this subset
339 E Select 'Delete' again to delete the subset
340 E No entry in TEDIC for $, issue $, DE $, code $.
341 E Association assigned code $ not found in table TEDSZ.
342 E No assosiation assigned code maintained for EDI standard $, issue $.
343 E Segment status '$' invalid for EDI standard $.
344 E 'SAP' object must not be changed.
345 E Specified message type is not a subset.
346 E Please specify $
360 E No entry found in table $.
399 E
400 E Messages for MDMP Communication
401 E Port & is not a tRFC port, no MDMP communication possible
402 E Could not determine code pages for tRFC port &
403 E Language fields not defined in segments
404 E No language defined for RFC destination of port &
405 E IDoc with MDMP technology sent to tRFC port
406 E Could not determine code page for port &1 and language &2
407 E Unicode settings in transaction SM59 (destination &) are incorrect
408 E Destination & is a Unicode destination
409 E No valid language-code page combination found (destination &)
410 E Destination (&, type 3, ABAP connection) does not exist
411 E Connection error (destination &)
412 E &1&2&3&4
413 E Specified RFC destination does not have a logon language
414 E Destination system is not a Unicode system
415 E Destination system is not a non-Unicode system
416 E Destination used does not have type 3
417 E Message type $, issue $ were deselected.
418 E Translation set $ deselected, message type $, issue $ selected
419 E Message type $, issue, $ deselected, issue $ selected
420 E Message type $, issue $ deselected, translation set $ selected
421 E $ $ $ already selected for translation set $ (translation sets).
422 E $ $ $ is already selected (message types).
423 E Data variant $ invalid.
424 E No entry for standard $, $, message type $ in TEDEX
425 E Sales organization $ not in table TVKO
426 E Purchasing organization $ not in table T024E
427 E Company code $ not in table T001
428 E Only EDI standard 'E' is permitted
430 E Error reading ( $ ).
431 E qRFC communication with an external system
432 E Please specify the correct EDI standard
433 E Partner addresses already exist
434 E Partner addresses do not exist
435 E No new communications service was added
436 E Please specify the correct partner type
440 E Partner $ is not in the vendor master.
441 E Partner $ is not in the customer master.
442 E Partner communication addresses currently locked.
443 E Create new partner communication addresses.
444 E Partner identifications deleted in $.
445 E Sender identification $ $ exists for $ $
446 E No further communications services are available
447 E Partner communication addresses saved
448 E Partner communication addresses deleted
449 E Communication addresses for $ deleted. Please save
450 E Partner $ is not in the vendor master.
451 E Partner $ is not in the customer master.
452 E Separate communication addresses currently locked.
453 E Create new separate communication addresses.
454 E Separate identifications deleted in $.
455 E Recipient identification $ $ for $ available.
456 E Select 'Delete' again to delete communication addresses for $
457 E Separate communication addresses saved.
458 E Separate communication addresses deleted for $
459 E Please enter correct application ID.
460 E Syntax error during locking
461 E Please specify the correct EDI standard
462 E Bitte Angaben zu OrgId vollständig eingeben!
463 E Eigene Adressen bereits vorhanden!
464 E Eigene Adressen noch nicht vorhanden!
480 E $ message(s) set to status 'finished'.
481 E Please select messages
482 E $ message(s) printing.
483 E $ message(s) set to 'archived'. (-> PF1)
485 E
489 E
490 E Archive header(EDX2) for $ not found.
491 E Table EDX4 could not be read (data header).
492 E Message $ not found in archive (INDX,ED).
493 E Message $ found in archive (INDX,ED), but without data.
494 E Separators are incomplete.
495 E Table EDX3 could not be read (functional group header).
496 E Separators not found in archive or profiles.
497 E The message could not be interpreted.
498 E No matching message found in the archive
499 E
500 E Table TEDIA could not be read.
501 E Table TEDIE could not be read.
502 E Table TEDPC could not be read.
503 E Table TEDIK could not be read.
504 E Table TEDIF could not be read.
506 E Screen not in table TEDIF.
507 E Data contents is missing in field $1, segment path $2.
508 E Allocated segment path $ not in message.
509 E Allocated segment is missing in EDI message.
511 E Error entry reset
512 E Error entry not reset
513 E Error reading segment $.
514 E Document $ company code $ locked.
515 E No document available for selection
516 E Code conversion impossible for field $1, segment path $2.
518 E Message number $ not available.
530 E $ is missing
531 E $ is missing (segment groups are dependent on message type)
532 E Copy object $ not found in standard $, issue $.
533 E $ not available, but can be created
534 E Object already exists, will be overwritten by reference
535 E Structure OK
536 E $ empty
537 E Cursor not in correct position
538 E Cursor is within the selected block
539 E Please select a line
540 E $ $ is already in $
541 E Entries not saved. Select <PF3> to exit the display
542 E Segment starts with a group. Qualification impossible
543 E Message $ from standard $ cannot be changed
544 E Entries not saved. Press Enter to exit the transaction
545 E Object(s) saved
546 E Saving unnecessary, data unchanged
547 E For message type $, translation set $ exists
548 E This object cannot be changed
549 E Object not found, but can be created
550 E EDI standard object cannot be changed
551 E $ $ deleted
552 E Please specify $
553 E Object not deleted
554 E Data type is missing
555 E Length not specified
556 E Description is missing
557 E Status is missing
558 E Composite data element is empty
559 E Text for object is missing
560 E $ empty
561 E Save structure first
562 E Select 'Delete' again to delete $
563 E Issue $ from EDI standard $ currently being processed
564 E $ $ found in $ $
565 E Segment $ available in segment group $ (message $)
566 E EDI standard $ not allowed
567 E Issue contains invalid character
568 E All segments of message type $ were generated (TEDNA)
569 E Minimum length is larger than maximum length
570 E Coded data elements may have a maximum length of 17 characters
571 E Code $ does not have a minimum length ($)
572 E Code $ does not correspond to data type $
573 E 1st segment must have status 'M' and a maximum usage '1'
574 E Data element is coded
575 E Structure error --> no generation
576 E Segment name must contain at least one letter
600 E Screen group $ not in table TEDAN
601 E Screen group $ not in table TSTC
602 E Screen $ not in table D020S.
603 E Screen group $ already exists. Select PF5 to add.
604 E Partner agreements not found (TEDPD)
605 E Enter Fcode.
606 E Alternative Fcode not filled.
607 E Field $ not in screen $.
610 E Fill LOOPMAX field
611 E Only a loop dynpro or position dynpro can be checked
699 E
700 E Table EDUA could not be read.
701 E Table EDUB could not be read.
702 E Table EDUC could not be read.
703 E Table EDUD could not be read.
704 E Table EDSS could not be read.
705 E No partner profile for standard $4, direction $5
706 E No partner arrangement for standard $4
708 E Last segment in incoming transfer file : $
709 E Incoming transfer file $1 could not be read.
710 E EDI data could not be split up by segments (file $).
712 E EDI message could not be sent.
713 E No messages were sent.
714 E Segment $1 has syntax error.
715 E SF: The standard $1 is incorrect (syntax error)
716 E SF: Error creating the interchange.
717 E SF: Error creating the functional group.
718 E SF: Error creating the message.
719 E SF: Error transferring to the communication module/dataset.
720 E Incorrect reference number in segment $1.
721 E Data trailer $ is missing.
722 E Incorrect message reference in header/trailer
723 E Segment number does not correspond to the segment control counter.
724 E Invalid font for EDIFACT file $1.
725 E Functional group trailer $ is missing.
726 E Incorrect functional group reference in header/trailer
727 E Message number does not correspond to the data control counter.
728 E Incorrect interchange control reference in header/trailer
729 E Functional group number does not correspond to the control counter.
730 E Functional group header $ is missing.
731 E Segment $ is invalid after segment $.
732 E Interchange data trailer $ is missing.
750 E Error: data could not be sent.
751 E Error at 'COMMUNICATION'
752 E Error in the host workstation synchronization
753 E Error saving the data on the workstation
754 E Host-workstation connection terminated
755 E Invalid communications service/priority
756 E Error during passing of data in a dataset
757 E Read error of data from the dataset
758 E Error during download of data to the workstation
759 E Error during upload of data to the workstation
760 E Error transferring (messages have status 'translated')
775 E Segment to long (800 bytes max.)
776 E Password not recognized. File transfer not excepted
777 E Authority not recognized. File transfer not excepted
778 E Error in transactor-comm.module/dataset-synchronization
779 E Error in host WS log
780 E Header segment $1 not recognized. WS file not transfered
781 E Invalid syntax ID $1
782 E Error during data transfer
799 E
800 E Error exporting message $1 direction $2.
801 E Error importing message $1 direction $2.
802 E Number assignment not possible
803 E Internal table $ not created.
804 E Message was not processed (error in interchange)
805 E Interchange incorrect.
807 E Non-SAP-application: Key fields are not unique.
810 E Insert in table EDX2 incorrect.
811 E Insert in table EDX3 incorrect.
812 E Insert in table EDX4 incorrect.
813 E Error in update of table EDPB
814 E Error in update of table EDX2
820 E Table TEDX2 could not be read.
821 E Table EDX3 could not be read.
822 E Table TEDX4 could not be read.
830 E Table TEDPA could not be read.
831 E Partner profile for $5 $6 $7 is not available
832 E Translation set $1 is not available
833 E Message type $2 does not exist
834 E No entry available in table EDX2.
835 E No entry found in table EDX3.
836 E No entry found in table EDX4.
837 E Partner agreement does not exist for $1
838 E Error in document selection/translation
839 E No entry exists for message type $1 in table TEDZW
840 E No entry found for standard $ in table TEDPG
841 E No entry found for field $ in table TEDPG
850 E Error $ during close of batch input session $
851 E During Insert Batch Input Sessin $: error $, Tcode $
852 E Error $ for $ $ during open of batch input session $
869 E
870 E Debugging: rc- & : &.
871 E Error ( & ) during spool read
872 E Undocumented spool error: &
873 E Error( & ) during status update (open spool & & ).
874 E Error ( & ) during status update (close spool & & ).
875 E Error ( & ) during print of a received message (open & &)
876 E Error( & ) during print of a received message (close & &)
877 E SAP user & is not a SAPoffice user
878 E Error during allocation of SAP name to SAPoffice name for SA name &
879 E Message for & / & could not be sent: & &
880 E Message &.& could not be transfered to the SAPcomm server
881 E Incoming message undeliverable, redirected to & via SAPmail
882 E SAP user & has no & authorization
883 E CPI-C 'receive' error &
884 E Upload status incomplete (Error in status &)
885 E Upload document is incomplete (Error in status &)
886 E Unable to read spool
887 E Spool entry &.& is an invalid SAPcomm request
888 E Message for & / & could not be sent by &
889 E Spool entries &.& could not be refreshed (&)
899 E
900 E $ is missing.
901 E $ is missing. (segment groups are dependent on message type).
902 E Copy object $ not found in standard $, issue $.
903 E $ not available, but can be created
904 E Object already exists, will be overwritten by reference
905 E Structure OK
906 E $ empty
907 E Cursor not in correct position.
908 E Cursor is within the selected block.
909 E Select desired line.
910 E $ $ already exists in $
911 E Entries not saved. Select <PF3> to quit the display.
912 E Segment starts with a group. Qualification impossible.
913 E Message $ from standard $ cannot be changed.
914 E Entries not saved. Press Enter to quit the transaction.
915 E Object(s) saved.
916 E Saving unnecessary, data unchanged
917 E For message type $ translation set $ exists
918 E This object cannot be changed
919 E Object not found, but can be created
920 E EDI standard object cannot be changed
921 E $ $ deleted
922 E Please specify $.
923 E Object not deleted
924 E Data type is missing
925 E Length not specified
926 E Description is missing
927 E Status is missing
928 E Composite data element is empty.
929 E Text for object is missing
930 E $ empty
931 E Save structure first.
932 E Select 'Delete' again to delete $
933 E Issue $ from EDI standard $ currently being processed
934 E $ $ found in $ $.
935 E Segment $ available in segment group $ (message $).
936 E EDI standard $ not allowed.
937 E Issue contains invalid character.
938 E All segments of message type $ were generated (TEDNA).
939 E Minimum length is larger than maximum length.
940 E Coded data elements may have a maximum length of 17 characters.
941 E Code $ does not have a minimum length ($)
942 E Code $ does not correspond to data type $
943 E 1st segment must have status 'M' and a maximum usage '1'.
944 E Data element is coded.
945 E Structure error --> no generation
946 E Segment name must contain at least one letter