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