SAP ABAP Message Class IDOC_ADAPTER (Messages for the IDoc Adapter)

Basic Data

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-XI-IS (Application Component) Integration Server
     ⤷ SIDOC_ADAPTER (Package) IDoc Adapter for Message Broker

Attributes

Message class	IDOC_ADAPTER
Short Description	Messages for the IDoc Adapter
Changed On	20130531
Last Changed At	091403

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	* Messages for the IDoc Adapter in the Integration Server	Space: object requires documentation	☐
2	099	&1	The short text describes the object sufficiently	☐
3	100	-->> Messages FB IDOC_INBOUND_XMB <<--	Space: object requires documentation	☐
4	101	IDoc adapter inbound: IDoc control record table contains no entries	Space: object requires documentation	☐
5	102	IDoc adapter inbound: IDoc data record table contains no entries	Space: object requires documentation	☐
6	103	IDoc adapter inbound channel: No data records exist for IDoc number &1	Space: object requires documentation	☐
7	104	IDoc adapter inbound: Sender port is initial	Space: object requires documentation	☐
8	105	IDoc adapter inbox: IDoc sender partner is initial	Space: object requires documentation	☐
9	106	IDoc adapter inbound channel: Error &1 occurred in the IS pipeline	Space: object requires documentation	☐
10	107	IDoc adapter inbox: IDoc type in control record not set	Space: object requires documentation	☐
11	108	IDoc adapter inbox: Error when converting to UTF-8	Space: object requires documentation	☐
12	110	IDoc MDMP interface only supported in central XI	The short text describes the object sufficiently	☐
13	111	Error in configuration query for central Integration Server	The short text describes the object sufficiently	☐
14	112	IDoc MDMP interface not supported for IDoc type &1	The short text describes the object sufficiently	☐
15	115	NO_ACL_PERMISSION: &1 &2 &3	The short text describes the object sufficiently	☐
16	116	NO_RUN_PERMISSION: &1	The short text describes the object sufficiently	☐
17	117	NO_ACL_AGREEM_PERMISSION: &1 &2 &3	The short text describes the object sufficiently	☐
18	120	IDoc_Adapter: Segment Limitation &1 > &2	The short text describes the object sufficiently	☐
19	150	-->> Messages FB IDX_IDOC_TO_XML <<--	Space: object requires documentation	☐
20	151	Transaction IDX1: Port &1, client &2, RFC destination &3 contain errors	Space: object requires documentation	☐
21	152	Metadata EDISDEF for port &1, IDoc type &2 and CIM type &3 not maintained	Space: object requires documentation	☐
22	153	Metadata EDSAPPL for port &1, IDoc type &2 and CIM type &3 not maintained	Space: object requires documentation	☐
23	154	Port &1 Client &2: IDoc &3 does not contain an IDoc type or CIM type	Space: object requires documentation	☐
24	155	EDISDEF: Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist	Space: object requires documentation	☐
25	200	-->> Messages FB IDX_XML_TO_IDOC <<--	Space: object requires documentation	☐
26	201	iXML toolkit: Internal Error	Space: object requires documentation	☐
27	202	XML parser: Error in row &1 column &2, error &3	Space: object requires documentation	☐
28	203	MSGGUID &1: Tag &3 found instead of tag &2	Space: object requires documentation	☐
29	205	IDoc XML data record: In segment &1 attribute &3 occurred instead of &2	Space: object requires documentation	☐
30	207	XML IDoc conversion: No known segments identified	Space: object requires documentation	☐
31	208	IDoc adapter: IDoc &1 exists twice in IDoc XML	Space: object requires documentation	☐
32	209	MSGGUID &1: Control record must start with tag EDI_DC40, not &2	Space: object requires documentation	☐
33	210	IDoc adapter outbound channel: Structure of logical receiver &1 incorrect	Space: object requires documentation	☐
34	211	Error during the internal UTF-8 conversion from XString to string	Space: object requires documentation	☐
35	215	Error during segment alignment &1 for data record number &2	Space: object requires documentation	☐
36	216	MSGGUID &1: Syntax of segment start &2 incorrect	The short text describes the object sufficiently	☐
37	217	Unknown field &2 found in segment &1	The short text describes the object sufficiently	☐
38	218	Unknown segment &1 found	The short text describes the object sufficiently	☐
39	250	-->> Messages FB IDX_OUTBOUND_MB <<--	Space: object requires documentation	☐
40	251	Only asynchronous processing supported for IDoc adapter outbound processg	Space: object requires documentation	☐
41	301	No inconsistencies found in metadata	The short text describes the object sufficiently	☐
42	310	IDX2: Metadata loaded for port &1; use another port	The short text describes the object sufficiently	☐
43	311	IDX1: Data maintained for port &1; use another port	The short text describes the object sufficiently	☐
44	315	IDX1: No RFC destination maintained for port &1	The short text describes the object sufficiently	☐
45	316	IDX1: Port &1 RFC destination &2: Error while loading metadata	The short text describes the object sufficiently	☐
46	400	* Error in structure information read/find/delete	Space: object requires documentation	☐
47	401	Entries could not be deleted, error when deleting	Space: object requires documentation	☐
48	402	Entries deleted	Space: object requires documentation	☐
49	403	No entries exist for the specified selections	Space: object requires documentation	☐
50	404	No IDoc type passed	Space: object requires documentation	☐
51	405	The transferred RFC destination '&1' does not exist	Space: object requires documentation	☐
52	406	The transferred RFC destination '&1' is the wrong type	Space: object requires documentation	☐
53	407	Communication Error: '&1'	Space: object requires documentation	☐
54	408	No structure information could be found	Space: object requires documentation	☐
55	409	Special segment version could not be determined	Space: object requires documentation	☐
56	410	Structure information not reloaded	Space: object requires documentation	☐
57	411	You do not have authorization to display this data	Space: object requires documentation	☐
58	412	You do not have authorization to change this data	Space: object requires documentation	☐
59	413	You do not have authorization to create this data	Space: object requires documentation	☐
60	414	You do not have authorization to delete this data	Space: object requires documentation	☐
61	418	To display a structure you must first select an IDoc type	Space: object requires documentation	☐
62	419	Select an IDoc type to copy the link	Space: object requires documentation	☐
63	420	Select an IDoc type link	Space: object requires documentation	☐
64	421	Enter a port name	Space: object requires documentation	☐
65	422	Specify a target port name	Space: object requires documentation	☐
66	423	IDoc type copied successfully	Space: object requires documentation	☐
67	424	Meta data already loaded for this port. Delete this data first	Space: object requires documentation	☐
68	425	Select a line	Space: object requires documentation	☐
69	426	Obligatory node '&1' missing in structure &2 &3	Space: object requires documentation	☐
70	427	Segment '&1', segment number '&2' not correct in structure &3 &4	Space: object requires documentation	☐
71	432	Enter a valid SAP release	Space: object requires documentation	☐
72	433	Metadata for port '&1' not yet loaded	Space: object requires documentation	☐
73	434	Only one segment definition can exist for each release. Change entry	Space: object requires documentation	☐
74	450	* Error message for online maintenance	Space: object requires documentation	☐
75	451	Enter a value for field '&1'	Space: object requires documentation	☐
76	452	Enter a numerical value for the client	Space: object requires documentation	☐
77	453	Entry deleted	Space: object requires documentation	☐
78	454	Entry was made	Space: object requires documentation	☐
79	455	No RFC destination is maintained for the port '&1'	Space: object requires documentation	☐
80	456	Structure information loaded successfully	Space: object requires documentation	☐
81	457	Structure information not loaded; '&1' missing	Space: object requires documentation	☐
82	458	Structure information not loaded	Space: object requires documentation	☐
83	459	Entry could not be added	Space: object requires documentation	☐
84	460	Port already exists and cannot be added	Space: object requires documentation	☐
85	461	Segment versions could not be read	Space: object requires documentation	☐
86	462	Entries saved	The short text describes the object sufficiently	☐
87	500	* Error messages for IDoc display in Integration Server	Space: object requires documentation	☐
88	501	No message selected	Space: object requires documentation	☐
89	551	Select the lines you want to save	Space: object requires documentation	☐
90	552	Logical partner cannot be left empty; check the proposal	Space: object requires documentation	☐
91	553	Logical partner &1 already exists with partner &2/&3/&4	Space: object requires documentation	☐
92	554	No partner could be found with these selection criteria	Space: object requires documentation	☐
93	555	IDoc adapter: Port &1 with client &2 and RFC destination &3 created	Space: object requires documentation	☐
94	560	&1: Could not determine code page with &2 &3 &4	Space: object requires documentation	☐
95	601	No service for system &1, client &2 in Integration Directory	Space: object requires documentation	☐
96	602	Partner & could not be converted	Space: object requires documentation	☐
97	603	System not configured as central Integration Server	Space: object requires documentation	☐
98	604	IDoc adapter inbound channel not called: IDoc type &1 in exception table	Space: object requires documentation	☐
99	605	Field SNDPOR=&1 does not equal 'SAP' + System ID	Space: object requires documentation	☐
100	610	Conversion obsolete, maintain service/party in Integration Directory	Space: object requires documentation	☐
101	615	Error in &1: &2	The short text describes the object sufficiently	☐
102	620	Partner &1 could not be converted	The short text describes the object sufficiently	☐
103	630	No IDoc packaging because parameter TUNING EO_INBOUND_TO_OUTBOUND = 0	Space: object requires documentation	☐
104	640	Copy Sender from Payload: Sender Is Missing in Payload	The short text describes the object sufficiently	☐
105	641	Copy Receiver from Payload: Receiver Is Missing in Payload	The short text describes the object sufficiently	☐
106	651	Changed data record saved in database	Space: object requires documentation	☐
107	652	New assignment saved	Space: object requires documentation	☐
108	653	Complete the logical partner field	Space: object requires documentation	☐
109	654	Entry with the same key already exists	Space: object requires documentation	☐
110	655	Logical partner must be unique for the receiver	Space: object requires documentation	☐
111	656	Select a partner entry	Space: object requires documentation	☐
112	657	Enter a valid IDoc partner	Space: object requires documentation	☐
113	658	Client can only contain the numbers 0..9	Space: object requires documentation	☐
114	659	You do not have authorization for transaction IDX4	Space: object requires documentation	☐
115	660	You do not have authorization to change entries	Space: object requires documentation	☐
116	661	You do not have authorization for monitor IDX5	Space: object requires documentation	☐
117	662	You do not have authorization to delete entries	Space: object requires documentation	☐
118	663	You do not have authorization to create new entries	Space: object requires documentation	☐
119	664	No queue entries exist for the inbound tRFC	Space: object requires documentation	☐
120	665	User & is not authorized for message processing	The short text describes the object sufficiently	☐
121	701	IDoc syntax error: ALEAUDIT IDoc number & contains no segment &1	Space: object requires documentation	☐
122	702	Syntax error: Obligatory Segment E1ADHDR missing in ALEAUD01 IDoc &1	Space: object requires documentation	☐
123	703	Syntax error: Obligatory Segment E1STATE missing in ALEAUD01 IDoc &1	Space: object requires documentation	☐
124	704	ALEAUDIT not possible for IDoc &1, message no longer exists	Space: object requires documentation	☐
125	810	No information found for & messages	The short text describes the object sufficiently	☐
126	820	Destination & does not exist	The short text describes the object sufficiently	☐
127	830	Destination & is not an R/3 destination (of type '3')	The short text describes the object sufficiently	☐
128	840	Error &3 for the remote call of method &1 in system &2, message &4	The short text describes the object sufficiently	☐
129	850	No RFC destination found for system with port &1 and client &2	The short text describes the object sufficiently	☐

History

Last changed on/by	20130531	SAP
SAP Release Created in	620