SAP ABAP Message Class /DSD/ME (DSD connector: messages)

Basic Data

Hierarchy

☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ LE-DSD-DC-CN (Application Component) DSD Connector
     ⤷ /DSD/ME (Package) DSD Connector

Attributes

Message class	/DSD/ME
Short Description	DSD connector: messages
Changed On	20130531
Last Changed At	104746

Messages

#	Message	Message Short Text	Documentation status	Authorization check
1	000	No function modules are maintained in table &2 for object &1	Space: object requires documentation	☐
2	001	Function module &1 does not exist for object &2	Space: object requires documentation	☐
3	002	No mapping rules are maintained for object &2	Space: object requires documentation	☐
4	003	Function module &1 was called incorrectly	Space: object requires documentation	☐
5	004	Function not available in current released	Space: object requires documentation	☐
6	005	Error when accessing the DSD connector database	Space: object requires documentation	☐
7	006	Error when converting data using function module &2	Space: object requires documentation	☐
8	007	Value &1 not permitted for field &2	Space: object requires documentation	☐
9	008	Error when accessing table &1 with key &2	Space: object requires documentation	☐
10	009	MDE object &1 is unknown	Space: object requires documentation	☐
11	010	No data found for tour &1	Space: object requires documentation	☐
12	011	Serious error: Structures of &1 and &2 are different	Space: object requires documentation	☐
13	012	Message type &1 is not supported	Space: object requires documentation	☐
14	013	No communication path maintained to data source	Space: object requires documentation	☐
15	014	Currently only "RFC" or "File" type ports are supported	Space: object requires documentation	☐
16	015	Tour &1 already exists	Space: object requires documentation	☐
17	016	Tour &1 cannot be deleted	Space: object requires documentation	☐
18	017	Function &1 is not supported in the control IDoc	Space: object requires documentation	☐
19	018	Error occurred when reading DSD files from the source system. See Log	Space: object requires documentation	☐
20	020	Port data from &1 have not been maintained sufficiently	Space: object requires documentation	☐
21	021	Enter an IDoc number	Space: object requires documentation	☐
22	022	No IDocs to process	Space: object requires documentation	☐
23	023	No entry in table &1 corresponds to the selection	Space: object requires documentation	☐
24	024	IDoc was processed successfully	Space: object requires documentation	☐
25	025	This direction is unknown	Space: object requires documentation	☐
26	026	Enter an object ID or a transfer number	Space: object requires documentation	☐
27	027	Data processing has already started. Incorrect procedure	Space: object requires documentation	☐
28	028	ISO code &1 is not assigned to a unit of measurement	Space: object requires documentation	☐
29	029	No clear assignment of ISO code &1 to SAP code	Space: object requires documentation	☐
30	030	Function module &1 does not exist	Space: object requires documentation	☐
31	031	Specified table is invalid. &1 &2	Space: object requires documentation	☐
32	032	Error during status update	Space: object requires documentation	☐
33	033	Check mapping rules in table &1	Space: object requires documentation	☐
34	034	Upload process has been already started	The short text describes the object sufficiently	☐
35	035	The tour has been already reset or removed	The short text describes the object sufficiently	☐
36	036	The tour has not been downloaded yet	The short text describes the object sufficiently	☐
37	037	The entered values are not allowed. Check via F4-help	The short text describes the object sufficiently	☐
38	038	Please enter a password!	The short text describes the object sufficiently	☐
39	039	The passwords specified must be identical	The short text describes the object sufficiently	☐
40	040	Shipment type is already assigned to a scenario.	The short text describes the object sufficiently	☐
41	041	Delivery type is already assigned to a scenario.	The short text describes the object sufficiently	☐
42	042	Order type is already assigned to a scenario.	The short text describes the object sufficiently	☐
43	043	Imported shipment number is empty.	The short text describes the object sufficiently	☐
44	044	Pricing Data Extractor returns error.	The short text describes the object sufficiently	☐
45	045	The entry in Data Readiness Table for driver &1 is locked.	The short text describes the object sufficiently	☐
46	046	Tour assignment for tour &1 failed after IDOC parsing.	The short text describes the object sufficiently	☐
47	047	Driver &1 is not assigned to any device yet.	The short text describes the object sufficiently	☐
48	048	Driver &1 is not correctly assigned.	The short text describes the object sufficiently	☐
49	049	Planning start date of tour &1 is empty.	The short text describes the object sufficiently	☐
50	050	Updating status of tour &1 failed.	The short text describes the object sufficiently	☐
51	051	Error when starting to download to device (MEUSER=&1)	The short text describes the object sufficiently	☐
52	052	Device(MEUSER=&1) is not assigned to any driver yet.	The short text describes the object sufficiently	☐
53	053	Error when finishing downloading to device (MEUSER=&1)	The short text describes the object sufficiently	☐
54	054	Error 5: Download of tour &1 failed due to I-Error in MI server.	Space: object requires documentation	☐
55	055	Error when starting to upload tour &1.	The short text describes the object sufficiently	☐
56	056	Error when finishing uploading tour &1.	The short text describes the object sufficiently	☐
57	057	Error 4: Upload of tour &1 failed due to I-Error in MI server.	Space: object requires documentation	☐
58	058	Error 3: Upload of tour &1 failed due to errors in DSD Connector table.	Space: object requires documentation	☐
59	059	Import parameter &1 of function module &2 is not correct.	The short text describes the object sufficiently	☐
60	060	Function module &1 returns error.	The short text describes the object sufficiently	☐
61	061	Deleting tour &1 failed.	The short text describes the object sufficiently	☐
62	062	Tour &1 does not exist in DSD Connector.	The short text describes the object sufficiently	☐
63	063	Resending tour &1 failed.	The short text describes the object sufficiently	☐
64	064	Changing status failed in manual upload of tour &1.	The short text describes the object sufficiently	☐
65	065	Information of driver &1 is not complete in DSD Connector.	Space: object requires documentation	☐
66	066	Calling Pricing Data Extractor failed.	The short text describes the object sufficiently	☐
67	070	Sales area check in backend customizing not activated -> MDSD not possibl	The short text describes the object sufficiently	☐
68	071	Upload failed: Tour &1 was already uploaded to the backend system	The short text describes the object sufficiently	☐
69	072	Already uploaded tour can be removed in the backend by TA /DSD/HH_RA_DELE	The short text describes the object sufficiently	☐
70	073	ME -> BE, Communication error RFC-Destination &1	Space: object requires documentation	☐
71	074	No data readiness, table /DSD/ME_DDR_STAT	Space: object requires documentation	☐
72	075	Reload activity type is not found	Space: object requires documentation	☐
73	076	Tour &1 already uploaded; Inbound terminated	The short text describes the object sufficiently	☐
74	077	Tour &1 already sent to device; Inbound terminated	The short text describes the object sufficiently	☐
75	078	Tour &1 already triggered to MW; Inbound terminated	The short text describes the object sufficiently	☐
76	079	Tour &1 upload to BE started; Inbound terminated	The short text describes the object sufficiently	☐
77	080	Tour &1 not downloaded to mobile device! ATP Check/Price Det.not possible	The short text describes the object sufficiently	☐
78	081	Tour &1 - Existing MW queue is locked - deletion not possible	The short text describes the object sufficiently	☐
79	082		The short text describes the object sufficiently	☐

History

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