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