IDOC_ADAPTER - Nachrichten f�r den IDoc-Adapter
The following messages are stored in message class IDOC_ADAPTER: Nachrichten f�r den IDoc-Adapter.
It is part of development package SIDOC_ADAPTER in software component BC-XI-IS. This development package consists of objects that can be grouped under "IDoc Adapter for Message Broker".
It is part of development package SIDOC_ADAPTER in software component BC-XI-IS. This development package consists of objects that can be grouped under "IDoc Adapter for Message Broker".
Message Nr ▲ | Message Text |
|---|---|
| 000 | * Messages for the IDoc Adapter in the Integration Server |
| 099 | &1 |
| 100 | -->> Messages FM IDOC_INBOUND_XMB <<-- |
| 101 | Inbound adapter: IDoc control record table does not contain any entries |
| 102 | Inbound IDoc adapter: IDoc data record table does not contain any entries |
| 103 | IDoc adapter inbound channel: No data records exist for IDoc number &1 |
| 104 | IDoc adapter inbound: Sender port is initial |
| 105 | IDoc adapter inbox: IDoc sender partner is initial |
| 106 | IDoc adapter inbound channel: Error &1 occurred in the IS pipeline |
| 107 | IDoc adapter inbox: IDoc type in control record not set |
| 108 | IDoc adapter inbox: Error when converting to UTF-8 |
| 110 | IDoc MDMP interface only supported in central XI |
| 111 | Error in configuration query for central Integration Server |
| 112 | IDoc MDMP interface not supported for IDoc type &1 |
| 115 | NO_ACL_PERMISSION: &1 &2 &3 |
| 116 | NO_RUN_PERMISSION: &1 |
| 117 | NO_ACL_AGREEM_PERMISSION: &1 &2 &3 |
| 120 | IDoc_Adapter: Segment Limitation &1 > &2 |
| 150 | -->> Messages FM IDX_IDOC_TO_XML <<-- |
| 151 | Transaction IDX1: Port &1, client &2, RFC destination &3 contain errors |
| 152 | Metadata EDISDEF for port &1, IDoc type &2 and CIM type &3 not maintained |
| 153 | Metadata EDSAPPL for port &1, IDoc type &2 and CIM type &3 not maintained |
| 154 | Port &1 Client &2: IDoc &3 does not contain an IDoc type or CIM type |
| 155 | EDISDEF: Port &1 segment def. &2 in IDoc type &3 CIM type &4 do not exist |
| 156 | Segment reduction with Release &1: No EDISDEF metadata |
| 200 | -->> Messages FM IDX_XML_TO_IDOC <<-- |
| 201 | iXML toolkit: Internal Error |
| 202 | XML parser: Error in row &1 column &2, error &3 |
| 203 | MSGGUID &1: Tag &3 found instead of tag &2 |
| 205 | IDoc XML data record: In segment &1 attribute &3 occurred instead of &2 |
| 207 | XML IDoc conversion: No known segments identified |
| 208 | IDoc adapter: IDoc &1 exists twice in IDoc XML |
| 209 | MSGGUID &1: Control record must start with tag EDI_DC40, not &2 |
| 210 | IDoc adapter outbound channel: Structure of logical receiver &1 incorrect |
| 211 | Error during the internal UTF-8 conversion from XString to string |
| 215 | Error during segment alignment &1 for data record number &2 |
| 216 | MSGGUID &1: Syntax of segment start &2 incorrect |
| 217 | Unknown field &2 found in segment &1 |
| 218 | Unknown segment &1 found |
| 250 | -->> Messages FM IDX_OUTBOUND_MB <<-- |
| 251 | Only asynchronous processing supported for IDoc adapter outbound processg |
| 301 | No inconsistencies found in metadata |
| 310 | IDX2: Metadata loaded for port &1; use another port |
| 311 | IDX1: Data maintained for port &1; use another port |
| 315 | IDX1: No RFC destination maintained for port &1 |
| 316 | IDX1: Port &1 RFC destination &2: Error while loading metadata |
| 400 | * Error in structure information read/find/delete |
| 401 | Entries could not be deleted, error when deleting |
| 402 | Entries were deleted |
| 403 | No entries exist for the specified selections |
| 404 | No IDoc type passed |
| 405 | The passed RFC destination '&1' does not exist |
| 406 | The passed RFC destination '&1' has the wrong type |
| 407 | Communication Error: '&1' |
| 408 | No structure information could be found |
| 409 | Special segment version could not be determined |
| 410 | Structure information not reloaded |
| 411 | You do not have authorization to display this data |
| 412 | You do not have authorization to change this data |
| 413 | You do not have authorization to create this data |
| 414 | You do not have authorization to delete this data |
| 418 | To display a structure you must first select an IDoc type |
| 419 | Select an IDoc type to copy the link |
| 420 | Select an IDoc type link |
| 421 | Enter a port name |
| 422 | Specify a target port name |
| 423 | IDoc type copied successfully |
| 424 | Meta data already loaded for this port. Delete this data first |
| 425 | Select a line |
| 426 | Mandatory node '&1' missing in structure &2 &3 |
| 427 | Segment '&1', segment number '&2' not correct in structure &3 &4 |
| 432 | Enter a valid SAP release |
| 433 | Metadata for port '&1' not yet loaded |
| 434 | Only one segment definition can exist for each release. Change entry |
| 450 | * Error message for online maintenance |
| 451 | Enter a value for field '&1' |
| 452 | Enter a numerical value for the client |
| 453 | Entry deleted |
| 454 | Entry was made |
| 455 | No RFC destination is maintained for the port '&1' |
| 456 | Structure information loaded successfully |
| 457 | Structure information not loaded; '&1' missing |
| 458 | Structure information not loaded |
| 459 | Entry could not be added |
| 460 | Port already exists and cannot be added |
| 461 | Segment versions could not be read |
| 462 | Entries saved |
| 500 | * Error messages for IDoc display in Integration Server |
| 501 | No message selected |
| 551 | Select the lines you want to save |
| 552 | Logical partner cannot be left empty; check the proposal |
| 553 | Logical partner &1 already exists with partner &2/&3/&4 |
| 554 | No partner could be found with these selection criteria |
| 555 | IDoc adapter: Port &1 with client &2 and RFC destination &3 created |
| 560 | &1: Could not determine code page with &2 &3 &4 |
| 601 | No service for system &1, client &2 in Integration Directory |
| 602 | Partner & could not be converted |
| 603 | System not configured as central Integration Server |
| 604 | IDoc adapter inbound channel not called: IDoc type &1 in exception table |
| 605 | Field SNDPOR=&1 does not equal 'SAP' + System ID |
| 610 | Conversion obsolete, maintain service/party in Integration Directory |
| 615 | Error in &1: &2 |
| 620 | Partner &1 could not be converted |
| 630 | No IDoc packaging because parameter TUNING EO_INBOUND_TO_OUTBOUND = 0 |
| 640 | Copy Sender from Payload: Sender Is Missing in Payload |
| 641 | Copy Receiver from Payload: Receiver Is Missing in Payload |
| 651 | Changed data record saved in database |
| 652 | New assignment saved |
| 653 | Complete the logical partner field |
| 654 | Entry with the same key already exists |
| 655 | Logical partner must be unique for the receiver |
| 656 | Select a partner entry |
| 657 | Enter a valid IDoc partner |
| 658 | Client can only contain the numbers 0..9 |
| 659 | You do not have authorization for transaction IDX4 |
| 660 | You do not have authorization to change entries |
| 661 | You do not have authorization for monitor IDX5 |
| 662 | You do not have authorization to delete entries |
| 663 | You do not have authorization to create new entries |
| 664 | No queue entries exist for the inbound tRFC |
| 665 | User & is not authorized for message processing |
| 701 | IDoc syntax error: ALEAUDIT IDoc number & does not contain segment &1 |
| 702 | Syntax error: Mandatory segment E1ADHDR missing in ALEAUD01 IDoc &1 |
| 703 | Syntax error: Mandatory segment E1STATE missing in ALEAUD01 IDoc &1 |
| 704 | ALEAUDIT not possible for IDoc &1; message no longer exists |
| 810 | No information found for & messages |
| 820 | Destination & does not exist |
| 830 | Destination & is not an R/3 destination (of type '3') |
| 840 | Error &3 for the remote call of method &1 in system &2, message &4 |
| 850 | No RFC destination found for system with port &1 and client &2 |