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