SAP ABAP Message Class E0 (SAP EDI messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Attributes
Message class | E0 | |
Short Description | SAP EDI messages | |
Changed On | 20140121 | |
Last Changed At | 103715 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | ---> Error messages from the partner profiles | ||
2 | 002 | Please maintain the master data for the partner first | Space: object requires documentation | |
3 | 003 | Function module & does not exist | Space: object requires documentation | |
4 | 004 | Please choose a process type defined for EDI | Space: object requires documentation | |
5 | 005 | Report & does not exist | Space: object requires documentation | |
6 | 006 | Please specify the name for the logical host destination | Space: object requires documentation | |
7 | 007 | Specify the name of the command file | Space: object requires documentation | |
8 | 008 | Please enter a permitted value for trigger | ||
9 | 009 | Please maintain the directory and file or function module | Space: object requires documentation | |
10 | 01 | Enter subgroup | ||
11 | 010 | Please maintain the directory and file or function module | Space: object requires documentation | |
12 | 011 | Please maintain the directory and file or function module | Space: object requires documentation | |
13 | 012 | Port type '&' is not supported for file interface | Space: object requires documentation | |
14 | 013 | Interchange method '&' is not supported for file interface | Space: object requires documentation | |
15 | 014 | Specify the path name of the command files | Space: object requires documentation | |
16 | 015 | Please maintain the master data check routines first | Space: object requires documentation | |
17 | 016 | Interchange method '&' is not supported for asynchronous RFC | Space: object requires documentation | |
18 | 017 | Port type '&' not supported for asynchronous RFC | ||
19 | 018 | Port name '&' cannot be assigned online | Space: object requires documentation | |
20 | 019 | Enter directory and name of command file | Space: object requires documentation | |
21 | 02 | Subgroup & not maintained | ||
22 | 020 | --> Error texts for function group EDI2 | ||
23 | 021 | EDI: Process code inbound '&' is not available | Space: object requires documentation | |
24 | 022 | EDI: Error process code '&' is not available | Space: object requires documentation | |
25 | 023 | EDI: Obsolete entry for process code system '&' | Space: object requires documentation | |
26 | 024 | IDoc display canceled due to technical problems | Space: object requires documentation | |
27 | 025 | EDI: Wrong direction & for inbound IDoc & | Space: object requires documentation | |
28 | 026 | EDI: Incorrect status & for inbound IDoc & | Space: object requires documentation | |
29 | 027 | This file is not within a valid logical path | Space: object requires documentation | |
30 | 028 | This directory is not within a valid logical path | Space: object requires documentation | |
31 | 029 | IDoc type &1 cannot be processed by &2 &3 | Space: object requires documentation | |
32 | 03 | In year & company & in Bet.version & does not belong to subgroup &. | ||
33 | 030 | --> Error texts for function group EDI3 | ||
34 | 031 | Port '&' does not exist in the table of port descriptions | Space: object requires documentation | |
35 | 032 | Port '&' does not exist in the table of port descriptions | ||
36 | 033 | Port transferred with incorrect port type | Space: object requires documentation | |
37 | 034 | Not all IDocs should go to same port | Space: object requires documentation | |
38 | 035 | Function module & is not RFC-compatible | Space: object requires documentation | |
39 | 036 | EDI: IDoc '&' was created and and forwarded for transmission | ||
40 | 037 | '&' IDocs selected | Space: object requires documentation | |
41 | 038 | No authorization for writing to this file | Space: object requires documentation | |
42 | 039 | Function module & does not exist | Space: object requires documentation | |
43 | 04 | Company & not maintained | ||
44 | 040 | --> Error texts for the exceptions of function group EDIP | ||
45 | 041 | Inbound partner profile is not available | Space: object requires documentation | |
46 | 042 | No entry for partner function '&' in table TPAR | Space: object requires documentation | |
47 | 043 | Outbound partner profile is not available | Space: object requires documentation | |
48 | 044 | No outbound profile available for partner no. '&', partner type '&' | Space: object requires documentation | |
49 | 045 | IDoc '&' was created and forwarded for transmission | Space: object requires documentation | |
50 | 046 | No EDI partner profile found for IDoc '&' | Space: object requires documentation | |
51 | 047 | IDoc '&' could not be processed further | Space: object requires documentation | |
52 | 048 | IDoc could not be written to file | Space: object requires documentation | |
53 | 049 | Additional data record '&' does not exist | Space: object requires documentation | |
54 | 05 | Name of subgroup & not maintained | ||
55 | 050 | Segment &1 was added by the application. | Space: object requires documentation | |
56 | 051 | EDI: Field & in control record with value '&' is invalid | Space: object requires documentation | |
57 | 052 | IDoc content changed by application before saving | Space: object requires documentation | |
58 | 053 | Conversion of GTIN to material number not unique | Space: object requires documentation | |
59 | 054 | IDoc number is blank (please check data) | Space: object requires documentation | |
60 | 055 | EDI: IDoc '&' has not been opened (OPEN) | Space: object requires documentation | |
61 | 056 | EDI: Error while assigning IDoc number | Space: object requires documentation | |
62 | 057 | EDI: Error during database insert/update in table EDIDC | Space: object requires documentation | |
63 | 058 | EDI: Invalid parameter combination | ||
64 | 059 | EDI: Key part of record is incomplete | Space: object requires documentation | |
65 | 06 | In year & no companies belong to subgroup & in version &. | ||
66 | 060 | EDI: After DOCUMENT_OPEN_FOR_PROCESS, DOCUMENT_STATUS_SET is missing | Space: object requires documentation | |
67 | 061 | EDI: IDOC '&' is currently locked | Space: object requires documentation | |
68 | 062 | EDI: IDoc '&' does not exist (please check data) | Space: object requires documentation | |
69 | 063 | EDI: IDoc ID '&' is invalid | Space: object requires documentation | |
70 | 064 | EDI: Data records are not numbered sequentially | Space: object requires documentation | |
71 | 065 | EDI: Data record '&' does not exist | Space: object requires documentation | |
72 | 066 | EDI: Status value '&' is invalid | Space: object requires documentation | |
73 | 067 | EDI: Field & in status record with value '&' is invalid | Space: object requires documentation | |
74 | 068 | EDI: Component '&' is not active | ||
75 | 069 | EDI: IDoc ID is blank | Space: object requires documentation | |
76 | 07 | Error in year: Lower limit (&) greater than upper limit (&) ! | ||
77 | 070 | EDI: Table passed to EDI_SEGMENTS_ADD_BLOCK is empty. | Space: object requires documentation | |
78 | 071 | EDI: Table passed to EDI_STATUS_ADD_BLOCK is empty | Space: object requires documentation | |
79 | 072 | EDI: Syntax error in IDoc (mandatory segment missing) | ||
80 | 073 | EDI: Syntax error in IDoc (too many repetitions of a group) | ||
81 | 074 | EDI: Syntax error in IDoc (too few repetitions of a group) | ||
82 | 075 | EDI: Syntax error in IDoc (too many repetitions of a segment) | ||
83 | 076 | EDI: Syntax error in IDoc (too few repetitions of a segment) | ||
84 | 077 | EDI: Syntax error in IDoc (hierarchy level is invalid) | ||
85 | 078 | EDI: Syntax error in IDoc (segment cannot be identified) | ||
86 | 079 | EDI: Syntax error in IDoc (mandatory group missing) | ||
87 | 08 | Error in period: Lower limit (&) greater than upper limit (&)! | ||
88 | 080 | Segments should have been inserted, but have been rejected. | Space: object requires documentation | |
89 | 081 | EDI: Insert w/o check (error assigning IDoc number) | Space: object requires documentation | |
90 | 082 | EDI: Insert without check (error in structure '&') | ||
91 | 083 | Error at '&' for structure '&' | Space: object requires documentation | |
92 | 084 | Error at OPEN '&' (check file) | Space: object requires documentation | |
93 | 085 | Error at READ '&' (check file) | Space: object requires documentation | |
94 | 086 | Error at DELETE '&' (check file) | Space: object requires documentation | |
95 | 087 | First record in inbound file is invalid (please check file) | Space: object requires documentation | |
96 | 088 | Process code '&' for error handling is not available | Space: object requires documentation | |
97 | 089 | ------> continues from 360 | ||
98 | 090 | --> Error texts for EDI outbound processing (others from 300) | ||
99 | 091 | Outbound process code '&' is not available | Space: object requires documentation | |
100 | 092 | No IDoc is ready for processing | Space: object requires documentation | |
101 | 093 | IDoc '&' could not be processed | Space: object requires documentation | |
102 | 094 | Process (workflow object) could not be generated | Space: object requires documentation | |
103 | 095 | Error while processing IDoc '&' (no mail address found) | Space: object requires documentation | |
104 | 096 | IDoc was added and file generated | Space: object requires documentation | |
105 | 097 | IDoc '&' added | Space: object requires documentation | |
106 | 098 | IDoc added and EDI subsystem triggered | Space: object requires documentation | |
107 | 099 | Error at OPEN '&&' (check path name) | Space: object requires documentation | |
108 | 10 | Version & not maintained! | ||
109 | 100 | Message texts for RSEIDOC2 ********************************************** | ||
110 | 101 | You have the first selected IDoc again | Space: object requires documentation | |
111 | 102 | You already have the last selected IDoc | Space: object requires documentation | |
112 | 103 | You are holding the first selected status record again | Space: object requires documentation | |
113 | 104 | You are already holding the last selected status record | Space: object requires documentation | |
114 | 105 | No IDoc selected | Space: object requires documentation | |
115 | 106 | No status record was selected | Space: object requires documentation | |
116 | 107 | No status record exists for the selected IDocs | Space: object requires documentation | |
117 | 108 | Selected IDoc is still locked | Space: object requires documentation | |
118 | 109 | Select a node first | Space: object requires documentation | |
119 | 11 | In subgroup & version & not maintained! | ||
120 | 110 | EDI: IDoc has more than & syntax errors | Space: object requires documentation | |
121 | 111 | EDI: IDoc & has syntax errors | Space: object requires documentation | |
122 | 112 | EDI: IDoc '&' is already open in process mode | Space: object requires documentation | |
123 | 113 | No IDocs selected | Space: object requires documentation | |
124 | 114 | First data record for IDoc is already displayed | Space: object requires documentation | |
125 | 115 | Last data record for IDoc is already displayed | Space: object requires documentation | |
126 | 116 | EDI: Inconsistency in fields of the control record | Space: object requires documentation | |
127 | 117 | EDI: Inconsistency in the parameter combination | Space: object requires documentation | |
128 | 118 | EDI: No status records for IDoc '&' | Space: object requires documentation | |
129 | 119 | EDI: IDoc '&' cannot be deleted | Space: object requires documentation | |
130 | 12 | No authorization for companies belonging to subgroup & ! | ||
131 | 120 | --> Error texts for inbound status processing | ||
132 | 121 | Error at OPEN '&' (check file) | Space: object requires documentation | |
133 | 122 | Error positioning cursor on last processed record | Space: object requires documentation | |
134 | 123 | Last IDoc number could not be determined (number range) | Space: object requires documentation | |
135 | 124 | IDoc number '&' in status record '&' is invalid | Space: object requires documentation | |
136 | 125 | Status record & is invalid (TABNAM: '&') | Space: object requires documentation | |
137 | 126 | Error in DOCUMENT_OPEN for IDoc '&' | Space: object requires documentation | |
138 | 127 | Error in DOCUMENT_STATUS_SET for IDoc '&' | Space: object requires documentation | |
139 | 128 | Error in DOCUMENT_CLOSE for IDoc '&' | Space: object requires documentation | |
140 | 129 | Error in SO_OBJECT_SEND for IDoc '&' | Space: object requires documentation | |
141 | 13 | Please enter the fiscal year! | ||
142 | 130 | Error in PARTNER_READ_OUTGOING_USER for IDoc '&' | Space: object requires documentation | |
143 | 131 | Error in SEGMENT_GET_NEXT for IDoc '&' | Space: object requires documentation | |
144 | 132 | Error reading port table for port '&' | Space: object requires documentation | |
145 | 133 | Error for Remote Function Call with port '&' | Space: object requires documentation | |
146 | 134 | Error while setting status for IDoc '&' | Space: object requires documentation | |
147 | 135 | Error at INSERT or UPDATE, table EDFI2 | Space: object requires documentation | |
148 | 136 | IDoc '&' set to status '&' | Space: object requires documentation | |
149 | 137 | Error at READ '&' (check file) | Space: object requires documentation | |
150 | 138 | Delete when deleting status file '&' after successful processing | Space: object requires documentation | |
151 | 139 | Error in status processing at DELETE for path & in table EDFI2 | Space: object requires documentation | |
152 | 14 | Please specify the item's lower limit! | ||
153 | 140 | Process code '&' for status record processing is not available | Space: object requires documentation | |
154 | 141 | Status '&' does not exist in list of status values | Space: object requires documentation | |
155 | 142 | Inconsistency in processing status file '&1' (index &2) | Space: object requires documentation | |
156 | 143 | Task & for status record processing has errors | Space: object requires documentation | |
157 | 144 | Invalid value for process type & for status record processing | Space: object requires documentation | |
158 | 145 | Work item/workflow & could not be started | Space: object requires documentation | |
159 | 146 | DELETE error for file '&1' with key '&2' | Space: object requires documentation | |
160 | 147 | Warning: this maintenance function is only for SAP development | Space: object requires documentation | |
161 | 148 | Configuration was not saved | Space: object requires documentation | |
162 | 149 | Configuration was saved | Space: object requires documentation | |
163 | 150 | --- Messages RSEIDOC0 | ||
164 | 151 | Please choose Create, Read or Process | ||
165 | 152 | Please choose a database or file | ||
166 | 153 | Specify file | Space: object requires documentation | |
167 | 154 | Please do not make entries for deactivated items | ||
168 | 155 | Specify IDoc number | Space: object requires documentation | |
169 | 156 | Please choose 'From start' or 'From segment' | ||
170 | 157 | Please specify the segment name | ||
171 | 158 | Choose Display only with Read | ||
172 | 159 | No entry in IDOCSYN for basic type & | Space: object requires documentation | |
173 | 160 | No configuration selected | Space: object requires documentation | |
174 | 161 | No entry in EDISYN for basic type & and extension & | Space: object requires documentation | |
175 | 162 | No data was changed | Space: object requires documentation | |
176 | 163 | Error messages from new RSEIDOC2 | Space: object requires documentation | |
177 | 164 | This IDoc cannot be edited | Space: object requires documentation | |
178 | 165 | This IDoc is saved as the original of an edited document | Space: object requires documentation | |
179 | 166 | Changes to the IDoc are written to the database | Space: object requires documentation | |
180 | 167 | You do not have authorization to edit IDocs | Space: object requires documentation | |
181 | 168 | You do not have authorization to execute program RSEIDOC2 | Space: object requires documentation | |
182 | 169 | You do not have authorization for selected IDoc | Space: object requires documentation | |
183 | 170 | Internal error occurred reading structure of segment '&' | Space: object requires documentation | |
184 | 171 | No error message available | Space: object requires documentation | |
185 | 172 | No status information available | Space: object requires documentation | |
186 | 173 | No previous status is available | Space: object requires documentation | |
187 | 174 | No subsequent status is available | Space: object requires documentation | |
188 | 175 | Function "Long text" can only be executed for SAP error messages | Space: object requires documentation | |
189 | 176 | Select a valid segment | Space: object requires documentation | |
190 | 177 | Select a segment number less than or equal to & | Space: object requires documentation | |
191 | 178 | Enter a segment number greater than 0 | Space: object requires documentation | |
192 | 179 | No previous data record available | ||
193 | 180 | No next data record available | ||
194 | 181 | Inbound IDocs cannot be reset manually | Space: object requires documentation | |
195 | 182 | Last status is not "syntax error" | ||
196 | 183 | Changed control record was saved | Space: object requires documentation | |
197 | 184 | Changed data record was saved | Space: object requires documentation | |
198 | 185 | --> Message texts for MSEIDOC1 | ||
199 | 186 | Specify search criterion | Space: object requires documentation | |
200 | 187 | Restrict number of IDocs to carry out full text search | Space: object requires documentation | |
201 | 188 | Segment '&' not created or activated - field display not possible | ||
202 | 189 | ----> Message texts for EDI statistics and FUGR EDIU | Space: object requires documentation | |
203 | 190 | Database error &1 during access to file 'EDICONF' | ||
204 | 191 | '& from' must be earlier or the same as '& to' | Space: object requires documentation | |
205 | 192 | Invalid value for & page: & | Space: object requires documentation | |
206 | 193 | Default values saved for user '&' in current client | ||
207 | 194 | First or last page reached already | Space: object requires documentation | |
208 | 195 | Selection '&' reset | ||
209 | 196 | Default values could not be saved | ||
210 | 197 | Date / time '&' noted as time limit | ||
211 | 198 | You have no change authorization | ||
212 | 199 | Default values were not transferred | Space: object requires documentation | |
213 | 200 | ---> Message texts for RSEIDOC1 | ||
214 | 201 | Unable to create full file name '&' (no output) | ||
215 | 202 | File '&' already exists - overwrite after confirmation | ||
216 | 203 | File '&' could not be opened | ||
217 | 204 | Output was written to file '&' | ||
218 | 205 | File '&' could not be opened - trying to open '&' | ||
219 | 206 | Error - segment '&' does not exist | Space: object requires documentation | |
220 | 207 | IDoc type & does not exist | Space: object requires documentation | |
221 | 208 | Enter your selection | Space: object requires documentation | |
222 | 209 | Error - IDoc '&' does not exist in version '&' | Space: object requires documentation | |
223 | 210 | ----> Message texts for RSEIDOC3 | ||
224 | 211 | Error during output of structure of IDoc type tables | ||
225 | 212 | Error during reading of fields for segment & for IDoc type & | ||
226 | 213 | Error during output of fields for segment & for IDoc type & | ||
227 | 214 | Error in funct.mod. "GET_FIELDTAB" in prog. RSEIDOC3 for table/segment & | ||
228 | 215 | Error - No texts available for table/segment & (check table) | ||
229 | 216 | Error - No fields available for table/segment & (check table) | ||
230 | 217 | Error - Table/segment & is not known/not active (check table) | ||
231 | 218 | No syntax entries available for basic type & | Space: object requires documentation | |
232 | 219 | Syntax for basic type & and extension & could not be found | Space: object requires documentation | |
233 | 220 | Segment & in Release & unknown, output is terminated | Space: object requires documentation | |
234 | 221 | Error during creation of ITAB in "SET_ENDS" for IDoc type & | ||
235 | 222 | Error during output of IDoc type & | ||
236 | 223 | Error outputting attributes for & | ||
237 | 224 | Selection criteria specified do not give a result | ||
238 | 225 | No file name defined for file output | ||
239 | 226 | You have no authorization for & | ||
240 | 227 | Enter your selection | Space: object requires documentation | |
241 | 228 | Enter your selection | Space: object requires documentation | |
242 | 229 | Selection criteria specified do not give a result | ||
243 | 230 | ---> Messages for SAPMSED0 (maintain partner profiles) continue from 600 | ||
244 | 231 | Choose a valid line | ||
245 | 232 | Partner was read | ||
246 | 233 | Partner was changed | Space: object requires documentation | |
247 | 234 | Partner was created | Space: object requires documentation | |
248 | 235 | No entries available | ||
249 | 236 | Invalid combination of partner type and partner role | Space: object requires documentation | |
250 | 237 | Partner role & not found | Space: object requires documentation | |
251 | 238 | Partner function is not always required for partner type & | Space: object requires documentation | |
252 | 239 | Global parameters could not be locked | Space: object requires documentation | |
253 | 240 | Global parameters are locked by user &1 | Space: object requires documentation | |
254 | 241 | EDI: IDoc '&' does not exist; see long text for details | Space: object requires documentation | |
255 | 242 | The sender had the code page: '&'. | Space: object requires documentation | |
256 | 243 | Please select a language | Space: object requires documentation | |
257 | 244 | Partner &3/&2 locked by user &1 | Space: object requires documentation | |
258 | 245 | Unable to lock partner | Space: object requires documentation | |
259 | 246 | This partner has not been created yet | Space: object requires documentation | |
260 | 247 | Table/view &2 is locked by &1 | Space: object requires documentation | |
261 | 248 | Port name could not be assigned | Space: object requires documentation | |
262 | 249 | Port could not be saved | Space: object requires documentation | |
263 | 250 | ---> Messages of module pool MSEIDOC0 | ||
264 | 251 | Maintain port definition '&1' for the SAP System | Space: object requires documentation | |
265 | 252 | Error opening file '&1' | Space: object requires documentation | |
266 | 253 | Please enter different names for source file and target file | Space: object requires documentation | |
267 | 254 | You do not have authorization for &2 for ports of type &1 | Space: object requires documentation | |
268 | 255 | No default values could be determined from port description &1 | Space: object requires documentation | |
269 | 256 | --> Message texts for EDI authorization checks | ||
270 | 257 | You do not have authorization for &2 for function &1 | Space: object requires documentation | |
271 | 258 | You do not have authorization for &2 for function &1 | ||
272 | 259 | You do not have authorization for &2 for function &1 | ||
273 | 260 | No error log available | Space: object requires documentation | |
274 | 261 | You do not have authorization for &2 for function &1 | ||
275 | 262 | Message control is not active in your system | Space: object requires documentation | |
276 | 263 | --->Messages of module pool SAPMSED2 | Space: object requires documentation | |
277 | 265 | Port '&' is not of type 'file' | ||
278 | 266 | Could not find code page for receiving system | Space: object requires documentation | |
279 | 268 | In output mode 1 and 2 of the partner further processing is standard | Space: object requires documentation | |
280 | 269 | Port type Internet no longer supported (see OSS note 315083) | Space: object requires documentation | |
281 | 270 | --> Error message FUGR EDI0 | ||
282 | 271 | IDoc sent as SAPmail to user & | Space: object requires documentation | |
283 | 272 | No text messages transferred | ||
284 | 273 | No SAP user maintained for partner '& & &' | Space: object requires documentation | |
285 | 275 | & IDoc(s) added and written to & file(s) | Space: object requires documentation | |
286 | 276 | &1 IDoc(s) added | Space: object requires documentation | |
287 | 277 | &1 IDoc(s) added and further processing started | Space: object requires documentation | |
288 | 278 | Could not send IDoc immediately | Space: object requires documentation | |
289 | 280 | > Messages for IDoc info system | ||
290 | 281 | Selected selection criteria do not give a result | Space: object requires documentation | |
291 | 283 | >>>> IDoc inbound processing | Space: object requires documentation | |
292 | 284 | The file & to be deleted could not be found in the file system | Space: object requires documentation | |
293 | 285 | Error reading first record to be processed from file & | ||
294 | 286 | IDoc file copied and transferred to inbound processing | Space: object requires documentation | |
295 | 287 | IDoc file transferred to inbound processing | Space: object requires documentation | |
296 | 288 | Status report transferred to status processing | Space: object requires documentation | |
297 | 289 | Attempt to read file & from the end (see long text!) | Space: object requires documentation | |
298 | 290 | --> Messages for RSEHRORG (conversion of Office user to HR ORG user) | ||
299 | 291 | & has already been created in HR-ORG | ||
300 | 292 | & could not be created as an information type (&) | Space: object requires documentation | |
301 | 293 | & is not known as an SAP user | Space: object requires documentation | |
302 | 294 | Port '&' is not permitted for this inbound processing. | Space: object requires documentation | |
303 | 295 | Please start with the smaller segment number | Space: object requires documentation | |
304 | 296 | Enter a real interval | Space: object requires documentation | |
305 | 297 | IDoc & to document & could not be processed | Space: object requires documentation | |
306 | 298 | EDI: Error during name conversion for IDOC '&' | ||
307 | 300 | --> EDI outbound processing error texts | ||
308 | 301 | EDI: Process code '&' for error handling is not available | Space: object requires documentation | |
309 | 302 | EDI: Invalid processing mode | Space: object requires documentation | |
310 | 303 | IDoc '&' has syntax error | Space: object requires documentation | |
311 | 304 | EDI: Name of segment '&' could not be converted | Space: object requires documentation | |
312 | 305 | EDI: Port '&' is not of type which writes to a file | ||
313 | 306 | EDI: Output mode '&' is invalid | ||
314 | 307 | EDI: Function module '&' does not exist | ||
315 | 308 | EDI: Message was saved and processed as inbound IDoc | Space: object requires documentation | |
316 | 309 | EDI: This type of processing is not supported for transmission medium 'A' | ||
317 | 310 | --> Messages for 'IDoc list' | Space: object requires documentation | |
318 | 311 | Too many values for graphic 'message types': & (max. &) | Space: object requires documentation | |
319 | 312 | Default values saved as global values in current client | ||
320 | 313 | Switching to display '&/&' not recommended due to dataset! | Space: object requires documentation | |
321 | 315 | --> Messages for status processing | Space: object requires documentation | |
322 | 316 | Error while receiving status from file '&' | Space: object requires documentation | |
323 | 317 | The length & of status record & is too large for version of port & | Space: object requires documentation | |
324 | 318 | The length & of status record & is too small for version of port & | Space: object requires documentation | |
325 | 319 | IDoc has incorrect status (&) for inbound processing | ||
326 | 320 | ---> Error messages for function group 0EDL | ||
327 | 321 | EDI: Entry for path '&' deleted | Space: object requires documentation | |
328 | 322 | EDI: Entry for path '&' already deleted | Space: object requires documentation | |
329 | 324 | --> Messages WE46 | Space: object requires documentation | |
330 | 325 | Enter a Valid Process Code | Space: object requires documentation | |
331 | 326 | Process Code & Already Exists | Space: object requires documentation | |
332 | 330 | ---> Error messages for function group EDI6 | ||
333 | 331 | EDI: No entry for partner function '&' in table TPAR | Space: object requires documentation | |
334 | 332 | EDI: Partner profile not available | Space: object requires documentation | |
335 | 333 | EDI: Partner profile not active | Space: object requires documentation | |
336 | 334 | EDI: Partner profile only available as template | Space: object requires documentation | |
337 | 335 | EDI: Partner profile outbound process code not available | Space: object requires documentation | |
338 | 336 | EDI: Partner profile outbound logical message not available | Space: object requires documentation | |
339 | 337 | EDI: Partner profile inbound not available | Space: object requires documentation | |
340 | 338 | EDI: Partner profile without full specification of party to be notified | Space: object requires documentation | |
341 | 339 | Enter a valid value for the package size | Space: object requires documentation | |
342 | 340 | Enter an existing segment version | Space: object requires documentation | |
343 | 341 | Enter a valid partner type | Space: object requires documentation | |
344 | 342 | Enter a permissible partner number | Space: object requires documentation | |
345 | 344 | --> Messages for WE05/WE07 | Space: object requires documentation | |
346 | 345 | No error message for IDoc number: & | Space: object requires documentation | |
347 | 346 | Display was refreshed | Space: object requires documentation | |
348 | 347 | Invalid cursor position | Space: object requires documentation | |
349 | 348 | No data available | Space: object requires documentation | |
350 | 349 | No data could be selected | Space: object requires documentation | |
351 | 350 | --> EDI error messages for general port maintenance | ||
352 | 351 | Select a port type | Space: object requires documentation | |
353 | 352 | Select a port | Space: object requires documentation | |
354 | 353 | This port already exists, cannot be created | Space: object requires documentation | |
355 | 354 | Buffer number may not be larger than & | Space: object requires documentation | |
356 | 355 | Buffer number may not be lower than & | Space: object requires documentation | |
357 | 356 | Buffer number must be greater than & | Space: object requires documentation | |
358 | 357 | Enter name and title for folder in the Workplace | Space: object requires documentation | |
359 | 358 | '&' is not a file in directory '&' | Space: object requires documentation | |
360 | 359 | Executability cannot be tested | Space: object requires documentation | |
361 | 360 | --> Other errors in inbound processing | ||
362 | 361 | EDI: Status '&' does not exist in the list of status values | Space: object requires documentation | |
363 | 362 | EDI: No process code entered for status '&' | Space: object requires documentation | |
364 | 363 | EDI: Name of segment '&' could not be converted | Space: object requires documentation | |
365 | 364 | EDI: Work item '&' generated or started | Space: object requires documentation | |
366 | 365 | EDI: Workflow '&' created | Space: object requires documentation | |
367 | 366 | EDI: Transfer to ALE level carried out | Space: object requires documentation | |
368 | 367 | EDI: Error transferring to ALE level | ||
369 | 368 | EDI: Error occurred processing document '&' | ||
370 | 369 | EDI: Incorrect direction for inbound processing | ||
371 | 370 | EDI: File '&' will not be processed again | ||
372 | 371 | EDI: error during database insert in table EDIDS | ||
373 | 372 | First record is not an IDoc control record (please check file) | Space: object requires documentation | |
374 | 373 | IDoc inbound: Container definition for task & has errors | ||
375 | 374 | Event for starting inbound processing was not triggered | Space: object requires documentation | |
376 | 375 | Error when reading data from file &. | Space: object requires documentation | |
377 | 376 | No IDocs selected | Space: object requires documentation | |
378 | 377 | --> Error - complete control tables | Space: object requires documentation | |
379 | 378 | Enter an ID (&) | Space: object requires documentation | |
380 | 379 | For entry, access 'Function module for ALE-EDI inbound processing' | Space: object requires documentation | |
381 | 380 | 'Processing with trigger inbound' is only possible for FM version 3.0 | Space: object requires documentation | |
382 | 381 | '&' is not an SAP Business Workflow task | Space: object requires documentation | |
383 | 382 | '&' is not a process until Release 2.2 | Space: object requires documentation | |
384 | 383 | '&' is not a supported logical message | Space: object requires documentation | |
385 | 384 | Selected process is not a task (single-step task) | Space: object requires documentation | |
386 | 385 | Selected process is not a workflow (multistep task) | Space: object requires documentation | |
387 | 386 | Only work item for exception handling is supported for 3.0a | Space: object requires documentation | |
388 | 387 | Please save the new entries first | Space: object requires documentation | |
389 | 388 | Database error changing text for process code '&' language '&' | Space: object requires documentation | |
390 | 389 | Database error deleting text for process code '&' language '&' | Space: object requires documentation | |
391 | 390 | Database error inserting text for process code '&' language '&' | Space: object requires documentation | |
392 | 391 | Database error updating inbound process code | Space: object requires documentation | |
393 | 392 | ID type '&' not valid for this system | Space: object requires documentation | |
394 | 393 | Function cannot be executed in this system | Space: object requires documentation | |
395 | 394 | Problems locking/unlocking text table | Space: object requires documentation | |
396 | 395 | Choose a code | Space: object requires documentation | |
397 | 396 | Choose an option | Space: object requires documentation | |
398 | 397 | This code already exists, it cannot be created | Space: object requires documentation | |
399 | 398 | Please save the new entries first | Space: object requires documentation | |
400 | 399 | Enter a process code | Space: object requires documentation | |
401 | 400 | Entry in outbound table not found | Space: object requires documentation | |
402 | 401 | Entry in partner table already exists | Space: object requires documentation | |
403 | 402 | Database error inserting in partner table | Space: object requires documentation | |
404 | 403 | Please check parameters | Space: object requires documentation | |
405 | 404 | Entry in outbound table already exists | Space: object requires documentation | |
406 | 405 | Database error reading from EDPP1 | Space: object requires documentation | |
407 | 406 | Partner not found in partner table | Space: object requires documentation | |
408 | 407 | Entry in outbound table already exists | Space: object requires documentation | |
409 | 408 | Database error inserting in outbound table | Space: object requires documentation | |
410 | 409 | Entry in outbound table was not found | Space: object requires documentation | |
411 | 410 | Database error reading from EDP12 | ||
412 | 411 | Database error reading from EDP13 | ||
413 | 412 | Entry in inbound table already exists | Space: object requires documentation | |
414 | 413 | Database error inserting in inbound table | Space: object requires documentation | |
415 | 414 | Entry in inbound table not found | Space: object requires documentation | |
416 | 415 | Partner is inactive - only active partners can be used | Space: object requires documentation | |
417 | 416 | Partner serves as template - only active partners can be used | Space: object requires documentation | |
418 | 417 | Entry for &, partner type & is not available | ||
419 | 418 | Partner &, partner type & is still inactive | ||
420 | 419 | Partner &, partner type & only serves as a template | ||
421 | 420 | Please enter a valid receiver port | Space: object requires documentation | |
422 | 421 | Please enter a correct partner status | Space: object requires documentation | |
423 | 422 | Please enter a valid value for the test flag | Space: object requires documentation | |
424 | 423 | Please enter a valid partner type | Space: object requires documentation | |
425 | 424 | Please enter a valid partner number | Space: object requires documentation | |
426 | 425 | Please enter a valid value for the archive flag | Space: object requires documentation | |
427 | 426 | Please enter a valid value for the receiver type | Space: object requires documentation | |
428 | 427 | Please enter a valid language | Space: object requires documentation | |
429 | 428 | Please enter a valid partner functin | Space: object requires documentation | |
430 | 429 | Please enter a valid application | Space: object requires documentation | |
431 | 430 | Please enter a valid output type | Space: object requires documentation | |
432 | 431 | Please enter a valid value for the change indicator | Space: object requires documentation | |
433 | 432 | Enter a valid process code | Space: object requires documentation | |
434 | 433 | Please enter a valid logical message | Space: object requires documentation | |
435 | 434 | Enter a valid basic type | Space: object requires documentation | |
436 | 435 | Please enter a valid value for the syntax check | Space: object requires documentation | |
437 | 436 | Please enter a valid value for inbound processing | Space: object requires documentation | |
438 | 437 | Please enter a valid value for dialog/background | Space: object requires documentation | |
439 | 438 | Please enter a valid value for the IDoc type | Space: object requires documentation | |
440 | 439 | Please enter a valid value for the output mode | Space: object requires documentation | |
441 | 440 | Enter a valid extension | Space: object requires documentation | |
442 | 441 | Enter a valid combination of basic type and extension | Space: object requires documentation | |
443 | 442 | Enter a valid message type assignment | Space: object requires documentation | |
444 | 443 | Segment definition & of segment & not released | Space: object requires documentation | |
445 | 444 | Segment definition & is not released | Space: object requires documentation | |
446 | 445 | Segment type & already exists | Space: object requires documentation | |
447 | 446 | No segment definition found for segment & | Space: object requires documentation | |
448 | 447 | Internal error in FM & object & | ||
449 | 448 | IDoc type & does not have any fields | ||
450 | 449 | IDoc type & is not active | ||
451 | 450 | Segment type & could not be found | Space: object requires documentation | |
452 | 451 | Segment assignment was saved | ||
453 | 452 | Segment definition & cannot be assigned to segment type & | Space: object requires documentation | |
454 | 453 | Segment length greater than 1000 bytes | ||
455 | 454 | Segment & released | ||
456 | 455 | Enter valid development class | Space: object requires documentation | |
457 | 456 | Segment name released - can no longer be changed | ||
458 | 457 | Segment & not found | Space: object requires documentation | |
459 | 458 | Segment & does not contain any fields | ||
460 | 459 | Segment was changed, please save first | Space: object requires documentation | |
461 | 460 | Segment name & already exists | Space: object requires documentation | |
462 | 461 | Changes to SAP segment not allowed | Space: object requires documentation | |
463 | 462 | Data was saved | ||
464 | 463 | Name range reserved for IDoc segments - maintenance via EDI development | ||
465 | 464 | Segment definition & cannot be deleted | Space: object requires documentation | |
466 | 465 | New segment definition & will be created | Space: object requires documentation | |
467 | 466 | Object & already exists in Dictionary | Space: object requires documentation | |
468 | 467 | Please assign different names to the segment type and segment name | ||
469 | 468 | Name & must begin with & | Space: object requires documentation | |
470 | 469 | Please avoid underscores in segment names | Space: object requires documentation | |
471 | 470 | Segment definition & created | Space: object requires documentation | |
472 | 471 | Segment definition & not created as unchanged compared to predecessor | Space: object requires documentation | |
473 | 472 | Segment definition & saved | Space: object requires documentation | |
474 | 473 | Segment type & created | Space: object requires documentation | |
475 | 474 | Segment definition & deleted | Space: object requires documentation | |
476 | 475 | Segment definition & could not be deleted | ||
477 | 476 | Object & does not conform to the naming convention | Space: object requires documentation | |
478 | 477 | Not possible to cancel release | ||
479 | 478 | Integration system for development class & is & | ||
480 | 479 | Data element & for segment documentation unknown in Dictionary | Space: object requires documentation | |
481 | 480 | Structure is still being used in | Space: object requires documentation | |
482 | 481 | & could not be activated | ||
483 | 482 | &, &, and & activated | Space: object requires documentation | |
484 | 483 | Database error writing & | Space: object requires documentation | |
485 | 484 | Please activate the IDoc types first | ||
486 | 485 | Table entries were saved | Space: object requires documentation | |
487 | 486 | Segment definition & has already been released | Space: object requires documentation | |
488 | 487 | Activation state of & could not be determined | Space: object requires documentation | |
489 | 488 | Data element & for segment structure is not active in Dictionary | Space: object requires documentation | |
490 | 489 | Data element & was not found in Dictionary | Space: object requires documentation | |
491 | 490 | Access to & rejected | Space: object requires documentation | |
492 | 491 | Error accessing & | Space: object requires documentation | |
493 | 492 | Lines contents transferred to the clipboard | Space: object requires documentation | |
494 | 493 | Make an entry in all required fields | Space: object requires documentation | |
495 | 494 | Field name & already available | Space: object requires documentation | |
496 | 495 | Processing canceled | ||
497 | 496 | Segment is currently locked by user & | Space: object requires documentation | |
498 | 497 | Segment could not be locked | Space: object requires documentation | |
499 | 498 | Fields for & could not be read | ||
500 | 499 | Release flag for SAP segments cannot be deleted | Space: object requires documentation | |
501 | 50 | Trading partner field is blank! | ||
502 | 500 | Segment has development class '&' and integration system '&' | Space: object requires documentation | |
503 | 501 | Object class & is not known | Space: object requires documentation | |
504 | 502 | Name & is invalid | ||
505 | 503 | Function module & was not executed | ||
506 | 504 | Object & not found | ||
507 | 505 | Object not specified | Space: object requires documentation | |
508 | 506 | Development class of segment '&' is not known | ||
509 | 507 | Segment & was deleted | Space: object requires documentation | |
510 | 508 | Data element for segment documentation & is not active | Space: object requires documentation | |
511 | 509 | Domain & could not be checked | Space: object requires documentation | |
512 | 51 | Transaction type field is blank! | ||
513 | 510 | Valid data types for & are: CHAR, CLNT, CUKY, DATS, LANG, NUMC, TIMS | Space: object requires documentation | |
514 | 511 | List of segment definitions is not up to date | ||
515 | 512 | Structure & in Dictionary activated | ||
516 | 513 | Segment & could not be released | Space: object requires documentation | |
517 | 514 | Release of segment type & successful | ||
518 | 515 | All segment definitions for segment type & have already been released | ||
519 | 516 | Segment type & unknown | Space: object requires documentation | |
520 | 517 | Segment name & not in Dictionary | ||
521 | 518 | Release flag cannot be changed | Space: object requires documentation | |
522 | 519 | No released segment definition & found | ||
523 | 520 | Release of segment type & reset | ||
524 | 521 | Name range conflict: Development class '&' | ||
525 | 522 | Segment & already released | ||
526 | 523 | Segment & already activated | ||
527 | 524 | Segment definition & could not be activated | ||
528 | 525 | Segment & activated | ||
529 | 526 | Segment type & not used in any IDoc type | Space: object requires documentation | |
530 | 527 | No active segment definition | Space: object requires documentation | |
531 | 528 | No segment definition available | Space: object requires documentation | |
532 | 529 | Release indicator can now be changed | Space: object requires documentation | |
533 | 530 | New segments have development class '&' and integration system '&' | ||
534 | 531 | No data field could be found with these options | Space: object requires documentation | |
535 | 532 | Documentation on control record (EDI_DC) could not be found | ||
536 | 533 | Documentation on data record (EDI_DD) could not be found | ||
537 | 534 | Documentation on status record (EDI_DS) could not be found | ||
538 | 535 | Segment name & already being used | ||
539 | 536 | Segment is still used | Space: object requires documentation | |
540 | 537 | Unknown development class '&' | ||
541 | 538 | Development class '&' is not transport-relevant | ||
542 | 539 | Segment definition & is from the current Release | Space: object requires documentation | |
543 | 540 | Entry & in & could not be deleted | Space: object requires documentation | |
544 | 541 | Entries & in & could not be deleted | Space: object requires documentation | |
545 | 542 | Description for & saved | Space: object requires documentation | |
546 | 543 | Saving of description for & terminated | Space: object requires documentation | |
547 | 544 | No description for & found | ||
548 | 545 | Segment type & flagged for transport | Space: object requires documentation | |
549 | 546 | Change in task & of transport & flagged | ||
550 | 547 | Segment definition was not saved, since unchanged or initial | Space: object requires documentation | |
551 | 548 | Length & of field & adapted to length & of application data element | ||
552 | 549 | Conflict development class - IDoc type name range | ||
553 | 550 | --> Error generating port name | ||
554 | 551 | Error during internal number assignment for port names | Space: object requires documentation | |
555 | 552 | Error during insert in port table | Space: object requires documentation | |
556 | 553 | Logical destination '&' is assigned to file port '&' | Space: object requires documentation | |
557 | 554 | Maintain the address for the port | Space: object requires documentation | |
558 | 555 | RFC destination '&' not known | Space: object requires documentation | |
559 | 556 | Host destination '&' not known | Space: object requires documentation | |
560 | 557 | Choose another name! Name range reserved! | Space: object requires documentation | |
561 | 558 | Error in internal number assignment for tRFC ports | Space: object requires documentation | |
562 | 559 | '&' is not a function module | Space: object requires documentation | |
563 | 560 | An error process for process code '&' will be generated | ||
564 | 561 | EDI/ALE: The system tried to send an error message | ||
565 | 562 | Function module has not yet been entered under 'Generate file name' | ||
566 | 563 | Type '&' of logical destination & is incompatible with port type '&' | Space: object requires documentation | |
567 | 564 | Select another port name. Assign different type to port name. | ||
568 | 565 | No test possible because directory is empty. | Space: object requires documentation | |
569 | 566 | File cannot be opened | Space: object requires documentation | |
570 | 567 | '&' is an executable file in directory & | Space: object requires documentation | |
571 | 568 | Access to directory possible from current application server | ||
572 | 569 | '&' is not an executable file in directory & | Space: object requires documentation | |
573 | 570 | --> Messages from function group EDIT | ||
574 | 571 | Processing canceled by user | Space: object requires documentation | |
575 | 572 | Basic IDoc type &2 cannot be used | Space: object requires documentation | |
576 | 573 | Extension & is not linked to any basic IDoc types | Space: object requires documentation | |
577 | 574 | --> Messages for 'Active monitoring of IDoc processing' | Space: object requires documentation | |
578 | 575 | Invalid value for status group &; Use F4 Help | Space: object requires documentation | |
579 | 576 | Date restrictions have not been entered correctly; see long text | ||
580 | 577 | Missing entry for field 'Status group' | ||
581 | 578 | User/organizational unit is invalid or does not exist | ||
582 | 579 | Action was terminated by user | ||
583 | 580 | Start time is after the end time -> No selection possible | Space: object requires documentation | |
584 | 581 | Basic IDoc type & could not be found | Space: object requires documentation | |
585 | 582 | Extension & could not be found | Space: object requires documentation | |
586 | 583 | No free number found for new IDoc type | Space: object requires documentation | |
587 | 584 | Unable to obtain a number for &/& | ||
588 | 585 | No combination possible: Segment type & occurs twice | ||
589 | 586 | No combination possible: No reference segment type & | ||
590 | 587 | Interval & for number range & not found | Space: object requires documentation | |
591 | 588 | Interval & for number range & is not internal | Space: object requires documentation | |
592 | 589 | Number range & not found | Space: object requires documentation | |
593 | 590 | --> Status processing via IDoc type SYSTAT01 | Space: object requires documentation | |
594 | 591 | Errors occurred during updating of IDoc | ||
595 | 592 | IDoc & could not be updated | ||
596 | 593 | The IDoc was marked for deletion using task '&' | ||
597 | 594 | Error occurred during processing of IDoc | ||
598 | 595 | --> Active monitoring of IDoc processing | Space: object requires documentation | |
599 | 596 | Error situation found by evaluation | ||
600 | 597 | No error situation determined by evaluation | ||
601 | 598 | Triggering event & caused an error | Space: object requires documentation | |
602 | 599 | Enter a valid value | ||
603 | 60 | No document information for this line! | ||
604 | 600 | --> Further messages for SAPMSED0 (partner profile) (orig. from 230) | ||
605 | 601 | Partner already exists | Space: object requires documentation | |
606 | 602 | No entry available for Message Control | Space: object requires documentation | |
607 | 603 | Port with destination & already exists | Space: object requires documentation | |
608 | 604 | An EDI port already exists for this destination | Space: object requires documentation | |
609 | 605 | Logical destination already exists | Space: object requires documentation | |
610 | 606 | Please enter a value for package size | Space: object requires documentation | |
611 | 607 | Please enter a valid version | ||
612 | 608 | Processing not possible (&) | Space: object requires documentation | |
613 | 609 | Only display possible (&) | Space: object requires documentation | |
614 | 610 | Exception & at TR_TASK_OVERVIEW | ||
615 | 611 | Saving of correction system rejected, exception & | ||
616 | 612 | Receiver port & does not exist | ||
617 | 613 | Partner &/& deleted | Space: object requires documentation | |
618 | 614 | You do not have authorization to display this partner | ||
619 | 615 | Object ID & is unknown (please observe upper/lower case) | ||
620 | 616 | Object type & is not known | Space: object requires documentation | |
621 | 617 | Folder &2 (&1) is unknown | ||
622 | 618 | Object &, ID & is unknown | ||
623 | 619 | A subsystem cannot be started for this port | Space: object requires documentation | |
624 | 620 | Possible entries (F4) not available for this parameter | Space: object requires documentation | |
625 | 621 | Development class & is not known | Space: object requires documentation | |
626 | 622 | Please enter a valid SAP Release | Space: object requires documentation | |
627 | 623 | Link between log. message & and IDoc type does not exist | Space: object requires documentation | |
628 | 624 | Object type &, ID & unknown (please observe upper/lower case) | ||
629 | 625 | Partner profile &/& created | Space: object requires documentation | |
630 | 626 | Please enter a valid SAP Release | Space: object requires documentation | |
631 | 627 | Please enter a valid SAP Release | Space: object requires documentation | |
632 | 628 | Please enter a valid SAP Release | Space: object requires documentation | |
633 | 629 | Segment definitions missing for release &1/&3 | Space: object requires documentation | |
634 | 630 | ---> Messages from the module pool SAPMSED5 (IDocs) | ||
635 | 631 | No description for & found | ||
636 | 632 | Object type & is not known | ||
637 | 633 | IDoc type & has not yet been created | Space: object requires documentation | |
638 | 634 | & is a basic IDoc type | Space: object requires documentation | |
639 | 635 | Basic IDoc type & and extension & have not yet been combined | Space: object requires documentation | |
640 | 636 | Select a basic IDoc type for extension & | Space: object requires documentation | |
641 | 637 | & already exists | Space: object requires documentation | |
642 | 638 | & could not be copied | Space: object requires documentation | |
643 | 639 | & has already been released, only display possible | Space: object requires documentation | |
644 | 640 | & is an extension | Space: object requires documentation | |
645 | 641 | & is an IDoc type | Space: object requires documentation | |
646 | 642 | This action is not possible for IDoc types | Space: object requires documentation | |
647 | 643 | Missing segment definitions marked | Space: object requires documentation | |
648 | 644 | SAP may not edit extensions | Space: object requires documentation | |
649 | 645 | & is an extended basic IDoc type and can only be displayed | Space: object requires documentation | |
650 | 646 | Predecessor has not been released | Space: object requires documentation | |
651 | 647 | Choose a valid line | Space: object requires documentation | |
652 | 648 | Please enter a template | Space: object requires documentation | |
653 | 649 | Basic IDoc type & not found | Space: object requires documentation | |
654 | 650 | Extension & not found | Space: object requires documentation | |
655 | 651 | Extension not possible: Segment type & occurs twice | Space: object requires documentation | |
656 | 652 | Extension not possible: Reference segment & missing | Space: object requires documentation | |
657 | 653 | Enter a name | Space: object requires documentation | |
658 | 654 | Extension not possible: & not released | Space: object requires documentation | |
659 | 655 | & does not exist in IDoc type | Space: object requires documentation | |
660 | 656 | & has been released - cannot be deleted | Space: object requires documentation | |
661 | 657 | Extension & is not linked to any basic IDoc types | Space: object requires documentation | |
662 | 658 | Basic IDoc type & has no extensions | Space: object requires documentation | |
663 | 659 | Data saved | Space: object requires documentation | |
664 | 660 | Data saved but warning messages displayed | Space: object requires documentation | |
665 | 661 | Assigned name is longer than & characters | Space: object requires documentation | |
666 | 662 | Development object &2 is locked by user &1 | Space: object requires documentation | |
667 | 663 | Development object could not be locked | Space: object requires documentation | |
668 | 664 | & already has successor & | Space: object requires documentation | |
669 | 665 | & generated, only display possible | Space: object requires documentation | |
670 | 666 | This action cannot be used for extensions | Space: object requires documentation | |
671 | 667 | & has not been released yet | ||
672 | 668 | No short text available for & | Space: object requires documentation | |
673 | 669 | The basic type & cannot be created as a successor to & | Space: object requires documentation | |
674 | 670 | & already has successor & | Space: object requires documentation | |
675 | 671 | This combination already exists as & | Space: object requires documentation | |
676 | 672 | Combination not possible: & not released | Space: object requires documentation | |
677 | 673 | Saving is not possible, type contains no segments | Space: object requires documentation | |
678 | 674 | & is consistent | ||
679 | 675 | Save extension | Space: object requires documentation | |
680 | 676 | & contains no segments, no combination possible | ||
681 | 677 | Predecessor & comes from current release | Space: object requires documentation | |
682 | 678 | Enter linked basic type | Space: object requires documentation | |
683 | 679 | Predecessor & was generated, no creation possible | Space: object requires documentation | |
684 | 680 | ---> Messages from function group EDIF (IDoc type <-> tree structure) | ||
685 | 681 | No attributes available for segment type & | Space: object requires documentation | |
686 | 682 | No parent segment types found for segment type & | ||
687 | 683 | Segment cannot be repaired, no Dictionary structures available | ||
688 | 685 | & not found | Space: object requires documentation | |
689 | 686 | Activity canceled | Space: object requires documentation | |
690 | 687 | Unknown software component '&' | The short text describes the object sufficiently | |
691 | 688 | Number range & is not internal | ||
692 | 689 | Number range & not found | ||
693 | 690 | Number of requested numbers is 0 | ||
694 | 691 | Error inserting IDOCVRS for & | ||
695 | 692 | The name & contains a character that is not permitted | Space: object requires documentation | |
696 | 693 | & has already been released | Space: object requires documentation | |
697 | 694 | & was released | Space: object requires documentation | |
698 | 695 | No description found for & | Space: object requires documentation | |
699 | 696 | No segment types in the clipboard | Space: object requires documentation | |
700 | 697 | Segment type(s) transferred to the clipboard | Space: object requires documentation | |
701 | 698 | & has not been released | Space: object requires documentation | |
702 | 699 | & has successor & | Space: object requires documentation | |
703 | 700 | Release for & cancelled | Space: object requires documentation | |
704 | 701 | & has a predecessor which has not been released | Space: object requires documentation | |
705 | 702 | Predecessor entry not found in the IDoc type list | Space: object requires documentation | |
706 | 703 | Version for segment type & could not be created | ||
707 | 704 | No successor found for & | Space: object requires documentation | |
708 | 705 | Object type & is not known | Space: object requires documentation | |
709 | 706 | Client & does not exist | Space: object requires documentation | |
710 | 707 | Not possible to transport in client & | Space: object requires documentation | |
711 | 708 | & included in order/task & | Space: object requires documentation | |
712 | 709 | Message type & is unknown | ||
713 | 710 | Basic IDoc type & is unknown | Space: object requires documentation | |
714 | 711 | Extension & is unknown | Space: object requires documentation | |
715 | 712 | Basic IDoc type & and extension & are not combined | Space: object requires documentation | |
716 | 713 | Basic IDoc type & not released | Space: object requires documentation | |
717 | 714 | Segment type & is not used in IDoc types | Space: object requires documentation | |
718 | 715 | Segment type & not found | ||
719 | 716 | You are editing an object in the SAP name range | Space: object requires documentation | |
720 | 717 | & has not been released yet | Space: object requires documentation | |
721 | 718 | You are creating an object in the customer name range | Space: object requires documentation | |
722 | 721 | & is used with basic IDoc type, please see long text | Space: object requires documentation | |
723 | 722 | & is not consistent, please see long text | Space: object requires documentation | |
724 | 723 | & is not within a valid value set | ||
725 | 724 | --> Status processing | ||
726 | 725 | IDoc no. & was set to status 68 | ||
727 | 726 | Event for error during status processing could not be triggered | Space: object requires documentation | |
728 | 727 | IDoc no. & was processed successfully | ||
729 | 728 | Errors while processing IDoc no. & | ||
730 | 729 | IDoc no. & already has status 68 | ||
731 | 730 | --> Messages about docu tools | ||
732 | 731 | For Release & no segment definition could be found for segment type & | ||
733 | 732 | Test: & & | ||
734 | 734 | Enter a valid view | Space: object requires documentation | |
735 | 735 | >>> IDoc: CPI-C data transfer with R/2 System <<< | ||
736 | 736 | IDoc transfer: Error while connection to R/2 System was being closed | ||
737 | 737 | IDoc transfer: Logon to R/2 System failed | ||
738 | 738 | Error during reading of logical destination &. | ||
739 | 739 | IDoc transfer: CPI-C error - error while data was being received | ||
740 | 740 | IDoc transfer: CPI-C error - error while sending data | ||
741 | 741 | IDoc transfer: & data is incorrect | ||
742 | 742 | IDoc transfer: Data flow not correct | ||
743 | 743 | IDoc transfer: Length given is not correct | ||
744 | 744 | IDoc transfer: First record is not an IDoc control record | ||
745 | 745 | IDoc inbox: Temporary IDoc number list could not be read | ||
746 | 746 | IDoc status records could not be received by R/2 System | ||
747 | 747 | IDoc: No. of objects received is different from no. of objects sent | ||
748 | 748 | IDoc transfer: CPI-C error - error while closing connection | ||
749 | 749 | IDoc can be ignored - error during transfer from R/2 System | ||
750 | 750 | >>> EDI: Messages for function group EDIG | ||
751 | 751 | Segment type & is already used in & & | Space: object requires documentation | |
752 | 752 | Segment type & invalid | Space: object requires documentation | |
753 | 753 | Please enter a valid value in the field 'Mandatory segment' (' '/'X') | Space: object requires documentation | |
754 | 754 | Please specify valid values for 'Min.number' and 'Max.number' | Space: object requires documentation | |
755 | 755 | Name of segment type must begin with & | Space: object requires documentation | |
756 | 756 | Name of segment type must begin with & | Space: object requires documentation | |
757 | 757 | Segment type(s) cannot be deleted - & occurs in predecessor IDoc type & | Space: object requires documentation | |
758 | 758 | Segment type(s) cannot be inserted at the beginning of the IDoc type & | Space: object requires documentation | |
759 | 759 | Type & is not a valid node type for segments in structure tree (internal) | Space: object requires documentation | |
760 | 760 | Extension segment type(s) will be inserted as child segment type(s) of & | Space: object requires documentation | |
761 | 761 | No attributes for reference segments in extensions | Space: object requires documentation | |
762 | 762 | Invalid value for reference segment flag in attributes: & (internal) | Space: object requires documentation | |
763 | 763 | Please insert cut reference segment as reference segment | Space: object requires documentation | |
764 | 764 | Cut extension segment cannot be inserted as reference segment | Space: object requires documentation | |
765 | 765 | Segment type & cannot be inserted for compatibility reasons | Space: object requires documentation | |
766 | 766 | Segment & cannot be inserted as it would appear twice when combined | Space: object requires documentation | |
767 | 767 | Name of first segment cannot be changed for successors | Space: object requires documentation | |
768 | 768 | A child seg. cannot be inserted - level of parent node would be changed | ||
769 | 769 | Segment attributes changed in a way not allowed - level would be changed | Space: object requires documentation | |
770 | 770 | Invalid segment type & - name must begin with & or & | Space: object requires documentation | |
771 | 771 | Development object & was deleted | Space: object requires documentation | |
772 | 772 | IDoc type & could not be deleted fully | Space: object requires documentation | |
773 | 773 | Extension & cannot be deleted - used with basic IDoc type | Space: object requires documentation | |
774 | 774 | Extension & could not be deleted completely | Space: object requires documentation | |
775 | 775 | Basic IDoc type & cannot be deleted - used with extension | Space: object requires documentation | |
776 | 776 | Basic IDoc type & could not be deleted completely | Space: object requires documentation | |
777 | 777 | Segment type & is already used in one extension | Space: object requires documentation | |
778 | 778 | First extension segment of reference segment cannot be changed | Space: object requires documentation | |
779 | 779 | Names of segment types of the predecessor IDoc type cannot be changed | Space: object requires documentation | |
780 | 780 | & is not a valid reference segment for compatibility reasons | Space: object requires documentation | |
781 | 781 | Segment & is already used in one extension | Space: object requires documentation | |
782 | 782 | Segment & is used as reference segment in one extension | Space: object requires documentation | |
783 | 783 | Segment & is not permitted as reference segment | Space: object requires documentation | |
784 | 784 | Segment & already used in & & as reference segment | Space: object requires documentation | |
785 | 785 | Segment & not found | Space: object requires documentation | |
786 | 786 | Segment & version & not found | ||
787 | 787 | Segment name is blank | ||
788 | 788 | Segment type is blank | Space: object requires documentation | |
789 | 789 | Segment &, Release & not found | Space: object requires documentation | |
790 | 790 | Segment name is blank | Space: object requires documentation | |
791 | 791 | ---> Other messages for process codes | ||
792 | 792 | No reassignment since another branch has not been selected | Space: object requires documentation | |
793 | 793 | Please select one code for reassignment | Space: object requires documentation | |
794 | 794 | The code 'EDIS' is reserved as a status process code | Space: object requires documentation | |
795 | 795 | Please select a version of the function module | Space: object requires documentation | |
796 | 798 | Reference segments cannot be deleted from here | Space: object requires documentation | |
797 | 799 | Segments cannot be inserted here | Space: object requires documentation | |
798 | 800 | EDI: Entry '&' missing in table '&' | Space: object requires documentation | |
799 | 802 | ---> Other messages for RSEIDOC2 | ||
800 | 803 | An error occurred reading the structure of segment '&' | Space: object requires documentation | |
801 | 804 | An error occurred reading the structure of segment '&' | Space: object requires documentation | |
802 | 805 | Only documents in the current system can be displayed | ||
803 | 806 | 'DISPLAY' method is not supported for object type '&' | ||
804 | 807 | Select a record to be displayed | ||
805 | 808 | No data records flagged as containing errors are available | ||
806 | 809 | The IDoc was marked for deletion using task '&' | ||
807 | 810 | An application document was created manually from the IDoc | ||
808 | 811 | Select a data record for this function | ||
809 | 812 | Select a status record for this function | ||
810 | 813 | User profiles indicates no tree display may be used for IDoc | ||
811 | 814 | The IDoc was marked for deletion using task '&' | Space: object requires documentation | |
812 | 815 | Unlogged error during inbound processing | ||
813 | 816 | Processing restarted. Please complete processing of step. | ||
814 | 817 | IDoc '&' sent via Internet | Space: object requires documentation | |
815 | 818 | IDoc inbound procg: Work item & started | Space: object requires documentation | |
816 | 819 | --> Further messages from segment editor SAPMSED3 | ||
817 | 820 | Not possible to switch to change mode | Space: object requires documentation | |
818 | 821 | System profile could not be read | ||
819 | 822 | Change not allowed | Space: object requires documentation | |
820 | 823 | Change to & not included in transport request, action terminated | Space: object requires documentation | |
821 | 824 | No authorization to change & | Space: object requires documentation | |
822 | 825 | Segment & saved | Space: object requires documentation | |
823 | 826 | Segment definition & placed in transport request | Space: object requires documentation | |
824 | 827 | Inactive structures will be activated in data repository | ||
825 | 828 | Please place the cursor on a data element field | Space: object requires documentation | |
826 | 829 | Do not use segment editor now. System is working... | Space: object requires documentation | |
827 | 830 | Activated segment definition & not released | ||
828 | 831 | Segment type & assigned successfully to segment definition & | Space: object requires documentation | |
829 | 832 | Segment type & assigned to segment definition & with errors | Space: object requires documentation | |
830 | 833 | Release/release reversal of segment definitions performed correctly | Space: object requires documentation | |
831 | 834 | Error in release/resetting release | Space: object requires documentation | |
832 | 835 | Segment definition & already active | ||
833 | 836 | No released segment definition available | ||
834 | 837 | Descriptions saved correctly | Space: object requires documentation | |
835 | 838 | Error while saving descriptions | Space: object requires documentation | |
836 | 839 | Create not allowed | Space: object requires documentation | |
837 | 840 | -> Messages for view maintenance EDIFCT | ||
838 | 841 | Combination of basic IDoc type & and extension & is invalid | Space: object requires documentation | |
839 | 843 | Please make an entry in field '&' | Space: object requires documentation | |
840 | 845 | >>> Cont.: IDoc: CPI-C data transfer with R/2 System <<< (733-749) | ||
841 | 846 | No new mailbag number could be assigned | ||
842 | 847 | Port '&' does not exist in the table of port descriptions | ||
843 | 848 | IDoc inbox: Temporary IDoc number status could not be deleted | Space: object requires documentation | |
844 | 849 | Status record outbox: Temporary IDoc number list not deleted | ||
845 | 850 | IDoc transfer: Logon to R/2 System failed (no confirmation) | ||
846 | 851 | IDoc transfer: Logon to R/2 System failed (no confirmation) | ||
847 | 852 | IDoc inb.procg from R/2: Error during lock of temporary numbers | Space: object requires documentation | |
848 | 853 | IDoc transfer: No authorization for CPI-C communication | Space: object requires documentation | |
849 | 855 | ---> Other messages FuGr EDI1 | ||
850 | 856 | EDI: Not all table entries of IDoc '&' could be deleted | Space: object requires documentation | |
851 | 857 | EDI: IDoc number is not unique, IDoc not reloaded | Space: object requires documentation | |
852 | 858 | EDI: IDoc '&' could not be reloaded | Space: object requires documentation | |
853 | 859 | EDI: Key fields are not unique, IDoc saved anyway | ||
854 | 860 | EDI: No range selected | Space: object requires documentation | |
855 | 861 | EDI: Range could not be selected | Space: object requires documentation | |
856 | 865 | >>> Messages for relationships between R/2 IDocs and other IDocs | Space: object requires documentation | |
857 | 866 | IDoc was created in R/2 System with the number & | Space: object requires documentation | |
858 | 867 | No application document was posted in the R/2 System for the IDoc | Space: object requires documentation | |
859 | 868 | An application document was posted in the R/2 System for the IDoc | Space: object requires documentation | |
860 | 869 | An application document was posted in the R/2 System for the IDoc | Space: object requires documentation | |
861 | 870 | --> Messages for mass activation of partner profiles RSEMASSA | ||
862 | 871 | >>> Messages during IDoc inbound processing <<< | Space: object requires documentation | |
863 | 872 | You can enter a test port for testing inbound processing. | Space: object requires documentation | |
864 | 873 | File ending '.XML' for file & is reserved for XML files. | Space: object requires documentation | |
865 | 874 | IDoc inbound processing: No file name could be determined | ||
866 | 875 | IDoc inbound: Task for inbound processing contains errors | ||
867 | 876 | IDoc inbound: Work item/workflow & could not be created | Space: object requires documentation | |
868 | 877 | IDoc can be ignored - error during inbound processing | ||
869 | 878 | The file name must contain at least one valid character. | Space: object requires documentation | |
870 | 879 | File & does not contain any data with IDocs. | Space: object requires documentation | |
871 | 880 | --> Messages for EDI XPRAs | ||
872 | 881 | Table '&' was filled (& entries) | ||
873 | 882 | Error filling table & | ||
874 | 883 | Beginning of conversion of partner profiles and syntax tables | ||
875 | 884 | End of conversion of partner profiles and syntax tables | ||
876 | 885 | No SAP users for the following Office users: | ||
877 | 886 | Office user & (client &) | ||
878 | 887 | Unknown message type & for partner & | ||
879 | 888 | Application: CA-EDI client: & | ||
880 | 890 | --> Messages for RSEIDOC2 | Space: object requires documentation | |
881 | 891 | Search in control records was unsuccessful | Space: object requires documentation | |
882 | 892 | Search in data records was unsuccessful | Space: object requires documentation | |
883 | 893 | You do not have authorization to execute program & | Space: object requires documentation | |
884 | 894 | & IDocs have been selected. Search data records... | Space: object requires documentation | |
885 | 895 | & IDocs were found | Space: object requires documentation | |
886 | 896 | &1 of &2 IDocs have been searched and &3 have been selected | Space: object requires documentation | |
887 | 897 | Preparing list output... | Space: object requires documentation | |
888 | 898 | No system entry found for DEVTYPE | ||
889 | 899 | The search in the archive info structure was unsuccessful | Space: object requires documentation | |
890 | 900 | --> Messages for EDI XPRAs | Space: object requires documentation | |
891 | 901 | Processing of table & successful | ||
892 | 902 | Table & was filled | ||
893 | 903 | Error during update of table & | ||
894 | 904 | Error filling table & | ||
895 | 905 | Beginning of conversion of partner profiles and syntax tables | ||
896 | 906 | End of conversion of partner profiles and syntax tables |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |