SAP ABAP Message Class E1 (Messages for IDoc Basis)

Basic Data

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-MID-ALE (Application Component) ALE Integration Technology
     ⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)

Attributes

Message class	E1
Short Description	Messages for IDoc Basis
Changed On	20141121
Last Changed At	124009

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	00	& & & &		☐
2	000	--> Messages XPRA 4.0	Space: object requires documentation	☐
3	001	**Start of conversion of IDoc basis tables	Space: object requires documentation	☐
4	002	**Conversion of ports (tables EDIPO and EDIPOI)	Space: object requires documentation	☐
5	003	**Conversion of global admin. data (table EDADM)	Space: object requires documentation	☐
6	004	**Conversion of segment type tables and segment definition tables	Space: object requires documentation	☐
7	005	**Conversion of basic IDoc types and extensions	Space: object requires documentation	☐
8	006	**Create links: process code <-> logical message	Space: object requires documentation	☐
9	007	Table & updated successfully (& entries)	Space: object requires documentation	☐
10	008	Error filling table &	Space: object requires documentation	☐
11	009	Error updating table &	Space: object requires documentation	☐
12	010	**Completion of customer-specific entries for DOCTYP (table EDI_CNVDOC)	Space: object requires documentation	☐
13	011	--> Messages XPRA 4.0c (and supplements for XPRA 4.0A)	Space: object requires documentation	☐
14	012	**Conversion of status customizing data (tables TEDS1,TEDS3)	Space: object requires documentation	☐
15	013	Error during update of table &	Space: object requires documentation	☐
16	014	Table & already completely filled	Space: object requires documentation	☐
17	015	$ has already been agreed in the partner. $ $ $ selected		☐
18	018	Fcode in SAP segment $SA (table TEDAS) is missing	Space: object requires documentation	☐
19	019	Wrong direction entered, please correct		☐
20	020	Please specify $		☐
21	030	--> Messages from the area status processing	Space: object requires documentation	☐
22	031	IDoc '&' has been set to status '30'.	Space: object requires documentation	☐
23	100	--> Messages from consistency check for partner profiles	Space: object requires documentation	☐
24	101	No entries for these selection criteria	Space: object requires documentation	☐
25	102	Consistency check for partner profiles	Space: object requires documentation	☐
26	103	System & Client &	Space: object requires documentation	☐
27	104	Date & Time &	Space: object requires documentation	☐
28	105	Partner profile &	Space: object requires documentation	☐
29	106	Header entry (table EDPP1)	Space: object requires documentation	☐
30	107	Recipient of notifications exists	Space: object requires documentation	☐
31	108	Unknown recipient: & &	Space: object requires documentation	☐
32	109	Correct partner status	Space: object requires documentation	☐
33	110	Invalid partner status: &	Space: object requires documentation	☐
34	111	Entry &	Space: object requires documentation	☐
35	112	Entries for Message Control (table EDP12)	Space: object requires documentation	☐
36	113	Logical message exists	Space: object requires documentation	☐
37	114	Logical message does not exist: &	Space: object requires documentation	☐
38	115	Process code (outbound) exists	Space: object requires documentation	☐
39	116	Process code (outbound) does not exist: &	Space: object requires documentation	☐
40	117	Entries for outbound processing (table EDP13)	Space: object requires documentation	☐
41	118	Port exists	Space: object requires documentation	☐
42	119	Port does not exist: &	Space: object requires documentation	☐
43	120	Packet size for asynchronous RFC has errors: &	Space: object requires documentation	☐
44	121	Output mode for asynchronous RFC is not permitted: &	Space: object requires documentation	☐
45	122	Basic type exists	Space: object requires documentation	☐
46	123	Basic type does not exist: &	Space: object requires documentation	☐
47	124	Extension exists	Space: object requires documentation	☐
48	125	Extension does not exist: &	Space: object requires documentation	☐
49	126	Link exists between logical message and IDoc type	Space: object requires documentation	☐
50	127	No link exists between logical message and IDoc type (EDIMSG)	Space: object requires documentation	☐
51	128	Entries for inbound processing (table EDP21)	Space: object requires documentation	☐
52	129	Process code (inbound) exists	Space: object requires documentation	☐
53	130	Process code (inbound) does not exist: &	Space: object requires documentation	☐
54	131	RC = &	Space: object requires documentation	☐
55	132	Outbound profile exists for this entry	Space: object requires documentation	☐
56	133	No outbound profile for this entry	Space: object requires documentation	☐
57	134	Message Control entry exists for this entry	Space: object requires documentation	☐
58	135	No Message Control entry for this entry	Space: object requires documentation	☐
59	136	View of IDoc type exists already	Space: object requires documentation	☐
60	137	Invalid partner number: &	Space: object requires documentation	☐
61	138	Message Control entry already exists	Space: object requires documentation	☐
62	139	The basis for the copy must be an incoming message.		☐
63	140	Translation set $, partner $, appl. ID $, comp. code $ exists (outbound)		☐
64	141	Translation set $ is entered for partner $, comp. code $ exists (inbound)		☐
65	142	Issue version (TEDAN) must be identical when copying.		☐
66	143	Allocation set $ saves		☐
67	144	Maximum $ repetitions allowed for group $.		☐
68	145	Maximum $ repetitions allowed for segment $.		☐
69	146	Error testing number segments and/or groups.		☐
70	147	Deletion not allowed.		☐
71	148	Position cursor on qualifier line.		☐
72	149	Screen $ for screen group $ not in table TEDIF.		☐
73	150	Combination of basic type and extension is possible	Space: object requires documentation	☐
74	151	Combination is not possible: & and &	Space: object requires documentation	☐
75	152	Specify screen name in field "screen".		☐
76	153	Screen change impossible.		☐
77	154	Message type $ not in table TEDAN.		☐
78	155	Table $ does not exist.		☐
79	156	Report $ does not exist.		☐
80	157	Fill either field or constant.		☐
81	158	Incomplete entry.		☐
82	159	Deviating standards not allowed (cf. TEDAN -> PF: 1).		☐
83	160	Copy basis is a non-SAP application (cf. TEDAN -> PF: 1).		☐
84	161	Copy basis is not a non-SAP application (cf. TEDAN -> PF: 1).		☐
85	162	Message type $ does not exist for EDI standard $.		☐
86	163	Issue $ does not exist for EDI standard $, message type $.		☐
87	164	Transaction code $ not in table STC.		☐
88	165	Entry not found in table TEDIM.		☐
89	166	String not found.		☐
90	167	Component $ ($) is not installed.		☐
91	168	Translation set already exists. Direction change is not allowed.		☐
92	169	Maintain table TEDSS (service segments) for EDI standard $.	Space: object requires documentation	☐
93	170	Translation set $ deleted		☐
94	171	Reference object $ copied		☐
95	172	Reference object $ does not exist		☐
96	177	Message type $ does not exist for EDI standard $		☐
97	178	Maintain message type for table TEDIF		☐
98	179	Allocation parameter $ exists, reference not possible		☐
99	200	--> Partner profiles (SAPLEDIPA)	Space: object requires documentation	☐
100	201	Enter a valid view	Space: object requires documentation	☐
101	202	Parameters for message control already used -> long text	Space: object requires documentation	☐
102	203	No IDocs created	Space: object requires documentation	☐
103	204	IDoc & created	Space: object requires documentation	☐
104	205	Several IDocs created (first IDoc: &)	Space: object requires documentation	☐
105	206	Enter an IDoc type	Space: object requires documentation	☐
106	207	Logical message & does not exist	Space: object requires documentation	☐
107	208	The display could not be updated	Space: object requires documentation	☐
108	209	Choose an entry	Space: object requires documentation	☐
109	210	No entries found that match selection criteria	Space: object requires documentation	☐
110	211	Outbound parameters are copied without Message Control -> Long text	Space: object requires documentation	☐
111	212	The selected entry could not be determined	Space: object requires documentation	☐
112	213	The packet size has been set to 1	Space: object requires documentation	☐
113	214	The display could not be updated	Space: object requires documentation	☐
114	215	Partner does not exist	Space: object requires documentation	☐
115	216	Partner type & does not exist, display only possible	Space: object requires documentation	☐
116	217	No Authorization to Display for Partner &, Partner Type &	Space: object requires documentation	☐
117	218	No Authorization to Change Partner Profile	Space: object requires documentation	☐
118	219	No Authorization to Create Partner Profile	Space: object requires documentation	☐
119	220	Mandatory composite data element is missing		☐
120	221	Invalid +/- sign position		☐
121	222	Invalid decimal point position		☐
122	223	Several decimal points		☐
123	224	Several +/- signs		☐
124	230	Segment not in standard data		☐
125	231	Segment on invalid position		☐
126	232	Mandatory segment is missing		☐
127	233	Invalid segment group repetition.		☐
128	234	Invalid segment repetition		☐
129	235	Segment not in the message type		☐
130	236	Segment in invalid sequence		☐
131	237	Invalid character after segment name		☐
132	240	Message type / version not in standard data		☐
133	250	--> Messages for repair programs	Space: object requires documentation	☐
134	251	You do not have authorization for this transaction	Space: object requires documentation	☐
135	252	You do not have authorization to execute this program	Space: object requires documentation	☐
136	270	--> Messages for the test suite	Space: object requires documentation	☐
137	271	No IDocs were processed	Space: object requires documentation	☐
138	272	IDoc & in status &: &	Space: object requires documentation	☐
139	273	Not all IDocs could be deleted	Space: object requires documentation	☐
140	274	Port & already exists	Space: object requires documentation	☐
141	275	Port & has been created	Space: object requires documentation	☐
142	276	Partner profile for partner &, partner type & has been created	Space: object requires documentation	☐
143	299	--->>> Error messages for log, subset development:		☐
144	300	--> Messages for port maintenance	Space: object requires documentation	☐
145	301	Enter to create a port name	Space: object requires documentation	☐
146	302	Port & already exists! Choose a different name!	Space: object requires documentation	☐
147	303	Logical directory '&' has not been defined!	Space: object requires documentation	☐
148	304	Rplcmnt character seq. must differ from special characters to be replaced	Space: object requires documentation	☐
149	305	To activate the conversion, you must first maintain the conversion table	Space: object requires documentation	☐
150	306	Rplcmnt character seq. '&' contains special character '&' to be replaced	Space: object requires documentation	☐
151	307	Special character to be replaced must not be left empty!	Space: object requires documentation	☐
152	308	'Generate port name' has been selected! Name is ignored!	Space: object requires documentation	☐
153	309	Special character '&' is replaced by a blank character! Check!	Space: object requires documentation	☐
154	310	--> Messages to message tree	Space: object requires documentation	☐
155	311	Message type & has not been assigned a process code in &	Space: object requires documentation	☐
156	312	Process code & is not used in the partner parameters	Space: object requires documentation	☐
157	313	Position the cursor on a process code for the where-used list	Space: object requires documentation	☐
158	314	Message type not found	Space: object requires documentation	☐
159	315	Port & is not used in partner profiles	Space: object requires documentation	☐
160	316	Port not found	Space: object requires documentation	☐
161	317	No port name entered for the search	Space: object requires documentation	☐
162	318	Port & has been deleted in the meantime by another user	Space: object requires documentation	☐
163	319	Port was incomplete and could not be saved!	Space: object requires documentation	☐
164	320	-> Messages status processing	Space: object requires documentation	☐
165	321	Inbound status for inbound IDocs not supported (IDoc no. & in file &)	Space: object requires documentation	☐
166	322	Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &)	Space: object requires documentation	☐
167	323	OPEN error CONVT_CODEPAGE_INIT for port & and file & for status inbound	Space: object requires documentation	☐
168	324	OPEN error CONVT_CODEPAGE_INIT occurs in directory entered	Space: object requires documentation	☐
169	325	Read error CONVT_CODEPAGE for status inbound from file &	Space: object requires documentation	☐
170	326	Further processing despite CONVT_CODEPAGE in status inbound from file &	Space: object requires documentation	☐
171	327	Also activate 'Continue despite conversion errors'	Space: object requires documentation	☐
172	328	Selected replacement indicator &1 does not exist in code page &2	Space: object requires documentation	☐
173	329	Code page &1 does not exist	The short text describes the object sufficiently	☐
174	330	Error occurred during check of replacement character	The short text describes the object sufficiently	☐
175	331	Inbound status for Aged IDocs not supported (IDocNr & in IDoc &)	The short text describes the object sufficiently	☐
176	332	Inbound status for Aged IDocs not supported (IDocNr & in file &)	The short text describes the object sufficiently	☐
177	333	Message type $ not found for issue $, EDI standard $.		☐
178	334	Controlling agency $ not found in table TEDSU.		☐
179	335	Subset identifier must be two-digit.		☐
180	336	No controlling agency maintained for EDI standard $, issue $.		☐
181	337	The attributes must not be changed.		☐
182	338	Translation set $ exists for this subset		☐
183	339	Select 'Delete' again to delete the subset		☐
184	340	No entry in TEDIC for $, issue $, DE $, code $.		☐
185	341	Association assigned code $ not found in table TEDSZ.		☐
186	342	No assosiation assigned code maintained for EDI standard $, issue $.		☐
187	343	Segment status '$' invalid for EDI standard $.		☐
188	344	'SAP' object must not be changed.		☐
189	345	Specified message type is not a subset.		☐
190	346	Please specify $		☐
191	351	Enter an IDoc type name	The short text describes the object sufficiently	☐
192	352	IDoc type & does not exist. Enter an existing one	The short text describes the object sufficiently	☐
193	353	Segment &1 does not exist in IDoc type &2	The short text describes the object sufficiently	☐
194	354	Specify current Basis approved release	The short text describes the object sufficiently	☐
195	355	Current and new approved release are identical; no conversion necessary	The short text describes the object sufficiently	☐
196	360	No entry found in table $.		☐
197	399	--->>> Error messages for partner agreements/communication		☐
198	400	Messages for MDMP Communication	The short text describes the object sufficiently	☐
199	401	Port & is not a tRFC port, no MDMP communication possible	Space: object requires documentation	☐
200	402	Code pages for tRFC port & could not be determined	Space: object requires documentation	☑
201	403	No definition for language fields maintained in segments	Space: object requires documentation	☑
202	404	No language maintained for RFC destination of port &	Space: object requires documentation	☑
203	405	IDoc with MDMP technology sent to tRFC port	The short text describes the object sufficiently	☐
204	406	No code page could be found for port & and language &	Space: object requires documentation	☐
205	407	Unicode settings in SM59 (destination &) are not correct	Space: object requires documentation	☐
206	408	Destination & is Unicode	Space: object requires documentation	☐
207	409	No valid language code page combination found (destination &)	Space: object requires documentation	☐
208	410	Destination (&, type 3; ABAP connection) does not exist	Space: object requires documentation	☐
209	411	Error while setting up connection (destination &)	Space: object requires documentation	☐
210	412	&1&2&3&4	The short text describes the object sufficiently	☐
211	413	Specified RFC destination does not have a logon language	Space: object requires documentation	☐
212	414	Destination system is not a Unicode system	Space: object requires documentation	☐
213	415	Destination system is not a non-Unicode system	Space: object requires documentation	☐
214	416	Destination used does not have type 3	Space: object requires documentation	☐
215	417	Ending cannot be empty; enter an ending first	The short text describes the object sufficiently	☐
216	418	Trigger file '&&' created	The short text describes the object sufficiently	☐
217	419	Could not create trigger file	The short text describes the object sufficiently	☐
218	420	Trigger file created, but IDocs still have old status	The short text describes the object sufficiently	☐
219	421	Trigger file created	The short text describes the object sufficiently	☐
220	422	Enter an ending for the handshake file first	The short text describes the object sufficiently	☐
221	423	Enter a logical destination first	The short text describes the object sufficiently	☐
222	424	No entry for standard $, $, message type $ in TEDEX		☐
223	425	Sales organization $ not in table TVKO		☐
224	426	Purchasing organization $ not in table T024E		☐
225	427	Company code $ not in table T001		☐
226	428	Only EDI standard 'E' is permitted		☐
227	430	Call no longer in bgRFC Monitor	The short text describes the object sufficiently	☐
228	431	qRFC communication with an external system	Space: object requires documentation	☐
229	432	Please specify the correct EDI standard		☐
230	433	Partner addresses already exist		☐
231	434	Partner addresses do not exist		☐
232	435	No new communications service was added		☐
233	436	Please specify the correct partner type		☐
234	440	Partner $ is not in the vendor master.		☐
235	441	Partner $ is not in the customer master.		☐
236	442	Partner communication addresses currently locked.		☐
237	443	Create new partner communication addresses.		☐
238	444	Partner identifications deleted in $.		☐
239	445	Sender identification $ $ exists for $ $		☐
240	446	No further communications services are available		☐
241	447	Partner communication addresses saved		☐
242	448	Partner communication addresses deleted		☐
243	449	Communication addresses for $ deleted. Please save		☐
244	450	Partner $ is not in the vendor master.		☐
245	451	Partner $ is not in the customer master.		☐
246	452	Separate communication addresses currently locked.		☐
247	453	Create new separate communication addresses.		☐
248	454	Separate identifications deleted in $.		☐
249	455	Recipient identification $ $ for $ available.		☐
250	456	Select 'Delete' again to delete communication addresses for $		☐
251	457	Separate communication addresses saved.		☐
252	458	Separate communication addresses deleted for $		☐
253	459	Please enter correct application ID.		☐
254	460	Syntax error during locking	Space: object requires documentation	☐
255	461	Please specify the correct EDI standard		☐
256	462	Bitte Angaben zu OrgId vollständig eingeben!		☐
257	463	Eigene Adressen bereits vorhanden!		☐
258	464	Eigene Adressen noch nicht vorhanden!		☐
259	480	$ message(s) set to status 'finished'.		☐
260	481	Please select messages		☐
261	482	$ message(s) printing.		☐
262	483	$ message(s) set to 'archived'. (-> PF1)		☐
263	485	--->>> Error messages for message archive		☐
264	489	--->>> Error messages for message archive		☐
265	490	Archive header(EDX2) for $ not found.		☐
266	491	Table EDX4 could not be read (data header).		☐
267	492	Message $ not found in archive (INDX,ED).		☐
268	493	Message $ found in archive (INDX,ED), but without data.		☐
269	494	Separators are incomplete.		☐
270	495	Table EDX3 could not be read (functional group header).		☐
271	496	Separators not found in archive or profiles.		☐
272	497	The message could not be interpreted.		☐
273	498	No matching message found in the archive		☐
274	499	--->>> Error messages for translator:		☐
275	500	Table TEDIA could not be read.		☐
276	501	Table TEDIE could not be read.		☐
277	502	Table TEDPC could not be read.		☐
278	503	Table TEDIK could not be read.		☐
279	504	Table TEDIF could not be read.		☐
280	506	Screen not in table TEDIF.		☐
281	507	Data contents is missing in field $1, segment path $2.		☐
282	508	Allocated segment path $ not in message.		☐
283	509	Allocated segment is missing in EDI message.		☐
284	511	Error entry reset	Space: object requires documentation	☐
285	512	Error entry not reset	Space: object requires documentation	☐
286	513	Error reading segment $.		☐
287	514	Document $ company code $ locked.		☐
288	515	No document available for selection		☐
289	516	Code conversion impossible for field $1, segment path $2.		☐
290	518	Message number $ not available.		☐
291	530	$ is missing		☐
292	531	$ is missing (segment groups are dependent on message type)		☐
293	532	Copy object $ not found in standard $, issue $.		☐
294	533	$ not available, but can be created		☐
295	534	Object already exists, will be overwritten by reference		☐
296	535	Structure OK		☐
297	536	$ empty		☐
298	537	Cursor not in correct position		☐
299	538	Cursor is within the selected block		☐
300	539	Please select a line		☐
301	540	$ $ is already in $		☐
302	541	Entries not saved. Select <PF3> to exit the display		☐
303	542	Segment starts with a group. Qualification impossible		☐
304	543	Message $ from standard $ cannot be changed		☐
305	544	Entries not saved. Press Enter to exit the transaction		☐
306	545	Object(s) saved		☐
307	546	Saving unnecessary, data unchanged		☐
308	547	For message type $, translation set $ exists		☐
309	548	This object cannot be changed		☐
310	549	Object not found, but can be created		☐
311	550	EDI standard object cannot be changed		☐
312	551	$ $ deleted		☐
313	552	Please specify $		☐
314	553	Object not deleted		☐
315	554	Data type is missing		☐
316	555	Length not specified		☐
317	556	Description is missing		☐
318	557	Status is missing		☐
319	558	Composite data element is empty		☐
320	559	Text for object is missing		☐
321	560	$ empty		☐
322	561	Save structure first		☐
323	562	Select 'Delete' again to delete $		☐
324	563	Issue $ from EDI standard $ currently being processed		☐
325	564	$ $ found in $ $		☐
326	565	Segment $ available in segment group $ (message $)		☐
327	566	EDI standard $ not allowed		☐
328	567	Issue contains invalid character		☐
329	568	All segments of message type $ were generated (TEDNA)		☐
330	569	Minimum length is larger than maximum length		☐
331	570	Coded data elements may have a maximum length of 17 characters		☐
332	571	Code $ does not have a minimum length ($)		☐
333	572	Code $ does not correspond to data type $		☐
334	573	1st segment must have status 'M' and a maximum usage '1'		☐
335	574	Data element is coded		☐
336	575	Structure error --> no generation		☐
337	576	Segment name must contain at least one letter		☐
338	600	Screen group $ not in table TEDAN		☐
339	601	Screen group $ not in table TSTC		☐
340	602	Screen $ not in table D020S.		☐
341	603	Screen group $ already exists. Select PF5 to add.		☐
342	604	Partner agreements not found (TEDPD)		☐
343	605	Enter Fcode.		☐
344	606	Alternative Fcode not filled.		☐
345	607	Field $ not in screen $.		☐
346	610	Fill LOOPMAX field		☐
347	611	Only a loop dynpro or position dynpro can be checked		☐
348	699	--->>> Error messages for transactor:		☐
349	700	Table EDUA could not be read.		☐
350	701	Table EDUB could not be read.		☐
351	702	Table EDUC could not be read.		☐
352	703	Table EDUD could not be read.		☐
353	704	Table EDSS could not be read.		☐
354	705	No partner profile for standard $4, direction $5		☐
355	706	No partner arrangement for standard $4		☐
356	708	Last segment in incoming transfer file : $		☐
357	709	Incoming transfer file $1 could not be read.		☐
358	710	EDI data could not be split up by segments (file $).		☐
359	712	EDI message could not be sent.		☐
360	713	No messages were sent.		☐
361	714	Segment $1 has syntax error.		☐
362	715	SF: The standard $1 is incorrect (syntax error)		☐
363	716	SF: Error creating the interchange.		☐
364	717	SF: Error creating the functional group.		☐
365	718	SF: Error creating the message.		☐
366	719	SF: Error transferring to the communication module/dataset.		☐
367	720	Incorrect reference number in segment $1.		☐
368	721	Data trailer $ is missing.		☐
369	722	Incorrect message reference in header/trailer		☐
370	723	Segment number does not correspond to the segment control counter.		☐
371	724	Invalid font for EDIFACT file $1.		☐
372	725	Functional group trailer $ is missing.		☐
373	726	Incorrect functional group reference in header/trailer		☐
374	727	Message number does not correspond to the data control counter.		☐
375	728	Incorrect interchange control reference in header/trailer		☐
376	729	Functional group number does not correspond to the control counter.		☐
377	730	Functional group header $ is missing.		☐
378	731	Segment $ is invalid after segment $.		☐
379	732	Interchange data trailer $ is missing.		☐
380	750	Error: data could not be sent.		☐
381	751	Error at 'COMMUNICATION'		☐
382	752	Error in the host workstation synchronization		☐
383	753	Error saving the data on the workstation		☐
384	754	Host-workstation connection terminated		☐
385	755	Invalid communications service/priority		☐
386	756	Error during passing of data in a dataset		☐
387	757	Read error of data from the dataset		☐
388	758	Error during download of data to the workstation		☐
389	759	Error during upload of data to the workstation		☐
390	760	Error transferring (messages have status 'translated')		☐
391	775	Segment to long (800 bytes max.)		☐
392	776	Password not recognized. File transfer not excepted		☐
393	777	Authority not recognized. File transfer not excepted		☐
394	778	Error in transactor-comm.module/dataset-synchronization		☐
395	779	Error in host WS log		☐
396	780	Header segment $1 not recognized. WS file not transfered		☐
397	781	Invalid syntax ID $1		☐
398	782	Error during data transfer		☐
399	799	--->>> Error messages for EDI processing (ESEL, TRA, ACT):		☐
400	800	Error exporting message $1 direction $2.		☐
401	801	Error importing message $1 direction $2.		☐
402	802	Number assignment not possible		☐
403	803	Internal table $ not created.		☐
404	804	Message was not processed (error in interchange)		☐
405	805	Interchange incorrect.		☐
406	807	Non-SAP-application: Key fields are not unique.		☐
407	810	Insert in table EDX2 incorrect.		☐
408	811	Insert in table EDX3 incorrect.		☐
409	812	Insert in table EDX4 incorrect.		☐
410	813	Error in update of table EDPB		☐
411	814	Error in update of table EDX2		☐
412	820	Table TEDX2 could not be read.		☐
413	821	Table EDX3 could not be read.		☐
414	822	Table TEDX4 could not be read.		☐
415	830	Table TEDPA could not be read.		☐
416	831	Partner profile for $5 $6 $7 is not available		☐
417	832	Translation set $1 is not available		☐
418	833	Message type $2 does not exist		☐
419	834	No entry available in table EDX2.		☐
420	835	No entry found in table EDX3.		☐
421	836	No entry found in table EDX4.		☐
422	837	Partner agreement does not exist for $1		☐
423	838	Error in document selection/translation		☐
424	839	No entry exists for message type $1 in table TEDZW		☐
425	840	No entry found for standard $ in table TEDPG		☐
426	841	No entry found for field $ in table TEDPG		☐
427	850	Error $ during close of batch input session $		☐
428	851	During Insert Batch Input Sessin $: error $, Tcode $		☐
429	852	Error $ for $ $ during open of batch input session $		☐
430	869	--->>> SAPcomm <<-----------------------------------------------------		☐
431	870	Debugging: rc= & : &.		☐
432	871	Error ( & ) during spool read		☐
433	872	Undocumented spool error: &		☐
434	873	Error( & ) during status update (open spool & & ).		☐
435	874	Error ( & ) during status update (close spool & & ).		☐
436	875	Error ( & ) during print of a received message (open & &)		☐
437	876	Error( & ) during print of a received message (close & &)		☐
438	877	SAP user & is not a SAPoffice user		☐
439	878	Error during allocation of SAP name to SAPoffice name for SA name &		☐
440	879	Message for & / & could not be sent: & &		☐
441	880	Message &.& could not be transfered to the SAPcomm server		☐
442	881	Incoming message undeliverable, redirected to & via SAPmail		☐
443	882	SAP user & has no & authorization		☑
444	883	CPI-C 'receive' error &		☐
445	884	Upload status incomplete (Error in status &)		☐
446	885	Upload document is incomplete (Error in status &)		☐
447	886	Unable to read spool		☐
448	887	Spool entry &.& is an invalid SAPcomm request		☐
449	888	Message for & / & could not be sent by &		☐
450	889	Spool entries &.& could not be refreshed (&)		☐
451	899	--->>> Error messages for message type development:		☐
452	900	$ is missing.		☐
453	901	$ is missing. (segment groups are dependent on message type).		☐
454	902	Copy object $ not found in standard $, issue $.		☐
455	903	$ not available, but can be created		☐
456	904	Object already exists, will be overwritten by reference		☐
457	905	Structure OK		☐
458	906	$ empty		☐
459	907	Cursor not in correct position.		☐
460	908	Cursor is within the selected block.		☐
461	909	Select desired line.		☐
462	910	$ $ already exists in $		☐
463	911	Entries not saved. Select <PF3> to quit the display.		☐
464	912	Segment starts with a group. Qualification impossible.		☐
465	913	Message $ from standard $ cannot be changed.		☐
466	914	Entries not saved. Press Enter to quit the transaction.		☐
467	915	Object(s) saved.		☐
468	916	Saving unnecessary, data unchanged		☐
469	917	For message type $ translation set $ exists		☐
470	918	This object cannot be changed		☐
471	919	Object not found, but can be created		☐
472	920	EDI standard object cannot be changed		☐
473	921	$ $ deleted		☐
474	922	Please specify $.		☐
475	923	Object not deleted		☐
476	924	Data type is missing		☐
477	925	Length not specified		☐
478	926	Description is missing		☐
479	927	Status is missing		☐
480	928	Composite data element is empty.		☐
481	929	Text for object is missing		☐
482	930	$ empty		☐
483	931	Save structure first.		☐
484	932	Select 'Delete' again to delete $		☐
485	933	Issue $ from EDI standard $ currently being processed		☐
486	934	$ $ found in $ $.		☐
487	935	Segment $ available in segment group $ (message $).		☐
488	936	EDI standard $ not allowed.		☐
489	937	Issue contains invalid character.		☐
490	938	All segments of message type $ were generated (TEDNA).		☐
491	939	Minimum length is larger than maximum length.		☐
492	940	Coded data elements may have a maximum length of 17 characters.		☐
493	941	Code $ does not have a minimum length ($)		☐
494	942	Code $ does not correspond to data type $		☐
495	943	1st segment must have status 'M' and a maximum usage '1'.		☐
496	944	Data element is coded.		☐
497	945	Structure error --> no generation		☐
498	946	Segment name must contain at least one letter		☐

History

Last changed on/by	20141121	SAP
SAP Release Created in