SAP ABAP Message Class /TDAG/CP_IMDS (Message Class for IMDS)
Basic Data
Hierarchy
☛
TDAGBCA (Software Component) TechniData Basic Components
⤷ EHS (Application Component) Environment, Health and Safety
⤷ /TDAG/CP_IMDS (Package) IMDS Advanced Interface Integration
⤷ EHS (Application Component) Environment, Health and Safety
⤷ /TDAG/CP_IMDS (Package) IMDS Advanced Interface Integration
Attributes
Message class | /TDAG/CP_IMDS | |
Short Description | Message Class for IMDS | |
Changed On | 20141109 | |
Last Changed At | 212225 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | System failure: &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | Data set does not exist: &1 | The short text describes the object sufficiently | |
3 | 002 | Data set is locked by user &3 | Space: object requires documentation | |
4 | 004 | Data set with initial primary key found in table &1 | The short text describes the object sufficiently | |
5 | 005 | Inconsistent root GUIDs; parent and child entry must have same root GUID | Space: object requires documentation | |
6 | 006 | Data set that you want to create already exists | Space: object requires documentation | |
7 | 007 | Cannot change data set because there are missing locks | The short text describes the object sufficiently | |
8 | 008 | Foreign key is missing in parent table; check database entries | Space: object requires documentation | |
9 | 009 | MDS contains different root GUIDs to corresponding chapter 4 data | Space: object requires documentation | |
10 | 010 | Missing primary key in table &1 | The short text describes the object sufficiently | |
11 | 011 | Mandatory field is initial | Space: object requires documentation | |
12 | 012 | No data was found for the entered search criteria | The short text describes the object sufficiently | |
13 | 013 | Cannot display document (document number &1) | The short text describes the object sufficiently | |
14 | 014 | Cannot display application log (log handle &1) | The short text describes the object sufficiently | |
15 | 015 | Characteristic &1 is of type "Phrase" but the value is not | The short text describes the object sufficiently | |
16 | 016 | Property type &1 is unknown | The short text describes the object sufficiently | |
17 | 017 | Error when storing the file in DMS; file was not stored | Space: object requires documentation | |
18 | 018 | Error when loading the file from DMS; file was not loaded | Space: object requires documentation | |
19 | 019 | You requested a GUID that does not exist; check your entry | Space: object requires documentation | |
20 | 020 | &1, &2, &3, &4 | The short text describes the object sufficiently | |
21 | 021 | A specification could not be locked | The short text describes the object sufficiently | |
22 | 022 | Specification &1 locked | The short text describes the object sufficiently | |
23 | 023 | MatNo: &1, ModuleID: &2, ModuleVers: &3 | The short text describes the object sufficiently | |
24 | 024 | Error reading specification (RECN: &1) | The short text describes the object sufficiently | |
25 | 030 | An INSERT statement into the database failed; database table: &1 | The short text describes the object sufficiently | |
26 | 031 | A DELETE statement on the database failed; database table: &1, GUID: &2 | The short text describes the object sufficiently | |
27 | 032 | An UPDATE statement on the database failed; database table: &1, GUID: &2 | The short text describes the object sufficiently | |
28 | 040 | Error while creating the application log | The short text describes the object sufficiently | |
29 | 041 | Loading the XML viewer failed | The short text describes the object sufficiently | |
30 | 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) | The short text describes the object sufficiently | |
31 | 100 | -------- Messages for Customer / Supplier MDS Center ------------------- | The short text describes the object sufficiently | |
32 | 101 | Could not select an organization | The short text describes the object sufficiently | |
33 | 102 | Save successfully performed | The short text describes the object sufficiently | |
34 | 103 | Recipient &1 (&2) was already added to the current MDS | The short text describes the object sufficiently | |
35 | 104 | Recipient must not be the same as the own company (&1) | The short text describes the object sufficiently | |
36 | 105 | Refresh successfully performed | The short text describes the object sufficiently | |
37 | 106 | Save to IMDS successfully performed | The short text describes the object sufficiently | |
38 | 107 | MDS successfully proposed | The short text describes the object sufficiently | |
39 | 108 | Recipient cannot be same as own organization (&1) | The short text describes the object sufficiently | |
40 | 109 | Your own MDS is currently not assigned to a specification | The short text describes the object sufficiently | |
41 | 110 | Could not find your own IMDS company | Space: object requires documentation | |
42 | 111 | Contact person (&1) for org. unit (&2) is not in IMDS address management | Space: object requires documentation | |
43 | 112 | Org. unit (&1) is not in IMDS adress management | Space: object requires documentation | |
44 | 113 | Own MDS sent in edit mode (&1, &2 : &3) | The short text describes the object sufficiently | |
45 | 114 | Recipient company ID not supplied | The short text describes the object sufficiently | |
46 | 115 | 'Part Index', 'Designer E-Mail' and 'Standard Index' fields are mandatory | Space: object requires documentation | |
47 | 116 | Parse Error: &1 | The short text describes the object sufficiently | |
48 | 117 | Release Error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
49 | 118 | Release Warning: &1 &2 &3 &4 | The short text describes the object sufficiently | |
50 | 119 | Result file imported (&1 : &2) | The short text describes the object sufficiently | |
51 | 120 | Messages in result file handling (&1 : &2) | The short text describes the object sufficiently | |
52 | 121 | Own MDS proposed to customer (&1, &2 : &3) | The short text describes the object sufficiently | |
53 | 122 | MDS &1 cannot be proposed in status &2 | The short text describes the object sufficiently | |
54 | 123 | No recipient or recipient status is not suitable for propose | The short text describes the object sufficiently | |
55 | 124 | MDS &1 cannot be saved in edit mode in status &2 | The short text describes the object sufficiently | |
56 | 125 | Contact person not supplied | The short text describes the object sufficiently | |
57 | 126 | No outgoing template specified | The short text describes the object sufficiently | |
58 | 127 | Outgoing template &1 does not exist | The short text describes the object sufficiently | |
59 | 128 | Define a document type in outgoing template &1 | Space: object requires documentation | |
60 | 129 | Define an application in outgoing template &1 | Space: object requires documentation | |
61 | 130 | Define a report generation function in outgoing template &1 | Space: object requires documentation | |
62 | 131 | Supplied buffer mode &1 for MDS record &2 is not supported | The short text describes the object sufficiently | |
63 | 132 | MDS &1 cannot be sent to a customer in status &2 | The short text describes the object sufficiently | |
64 | 133 | No recipient or recipient status is not suitable for sending to customer | The short text describes the object sufficiently | |
65 | 134 | Only one recipient allowed for "Send to Customer" activity | The short text describes the object sufficiently | |
66 | 135 | MDS sent to customer (&1, &2, &3) | The short text describes the object sufficiently | |
67 | 136 | MDS released (&1, &2, &3) | The short text describes the object sufficiently | |
68 | 137 | MDS successfully sent to customer | The short text describes the object sufficiently | |
69 | 138 | MDS record &1 does not exist in buffer | The short text describes the object sufficiently | |
70 | 139 | No valid identifier for reference material (SUBID: &1) | Space: object requires documentation | |
71 | 140 | MDS record &1 does not exist in the database but in the buffer | The short text describes the object sufficiently | |
72 | 141 | Outgoing template &1 not defined | The short text describes the object sufficiently | |
73 | 142 | The entered specification (&1) does not exist | The short text describes the object sufficiently | |
74 | 143 | Product structure of specification &1 does not conform with IMDS | Space: object requires documentation | |
75 | 144 | Cannot create application log for MDS record &1 | The short text describes the object sufficiently | |
76 | 145 | IMDS system is not configured | Space: object requires documentation | |
77 | 146 | MDS was rejected | The short text describes the object sufficiently | |
78 | 147 | MDS was accepted | The short text describes the object sufficiently | |
79 | 148 | No MDS selected for import | The short text describes the object sufficiently | |
80 | 149 | Import of MDS structure successfully started | The short text describes the object sufficiently | |
81 | 150 | Import aborted; no MDSs were selected or allowed to be imported | The short text describes the object sufficiently | |
82 | 151 | Specification assignment changed to &1 (&2 : &3) | The short text describes the object sufficiently | |
83 | 152 | MDS record with different module ID was already assigned | The short text describes the object sufficiently | |
84 | 153 | MDS record with same module ID but higher version was already assigned | The short text describes the object sufficiently | |
85 | 154 | Error occured in result file processing; see previous messages | The short text describes the object sufficiently | |
86 | 155 | MDS successfully published | The short text describes the object sufficiently | |
87 | 156 | MDS &1 cannot be published in status &2 | The short text describes the object sufficiently | |
88 | 157 | Material category of assigned specification does not match MDS type | The short text describes the object sufficiently | |
89 | 158 | IMDS file import (&1 : &2) | The short text describes the object sufficiently | |
90 | 159 | MDS imported from file &1. | The short text describes the object sufficiently | |
91 | 160 | IMDS organization &1 does not exist in organization table | Space: object requires documentation | |
92 | 161 | MDS &1 cannot be accepted in status &2 | The short text describes the object sufficiently | |
93 | 162 | MDS &1 cannot be rejected in status &2 | The short text describes the object sufficiently | |
94 | 163 | MDS published (&1, &2, &3) | The short text describes the object sufficiently | |
95 | 164 | Error creating IMDS BAdI &1 | The short text describes the object sufficiently | |
96 | 165 | IMDS batch client RFC failure | Space: object requires documentation | |
97 | 166 | Accepting MDS (&1, &2) | The short text describes the object sufficiently | |
98 | 167 | Rejecting MDS (&1, &2) | The short text describes the object sufficiently | |
99 | 168 | MDS successfully copied | The short text describes the object sufficiently | |
100 | 169 | MDS structure data import into &1 (&2, &3) | The short text describes the object sufficiently | |
101 | 170 | Unable to read MDS with node ID &1 | The short text describes the object sufficiently | |
102 | 171 | Could not find MDS in buffer | The short text describes the object sufficiently | |
103 | 172 | Failed to open the compliance workbench in simulation mode | The short text describes the object sufficiently | |
104 | 173 | Failed to import the MDS in simulation mode | The short text describes the object sufficiently | |
105 | 174 | Cannot perform action; import of MDS structure is currently running | The short text describes the object sufficiently | |
106 | 175 | Cannot perform action; communication to IMDS is currently running | The short text describes the object sufficiently | |
107 | 176 | Releasing the MDS internally (&1, &2, &3) | The short text describes the object sufficiently | |
108 | 177 | MDS &1 cannot be internally released in status &2 | The short text describes the object sufficiently | |
109 | 178 | MDS successfully internally released | The short text describes the object sufficiently | |
110 | 179 | No head of product structure for normalization variant &1 (Spec &2) | The short text describes the object sufficiently | |
111 | 180 | MDS upload successfully processed; new status is &1 | The short text describes the object sufficiently | |
112 | 181 | Recipient &1 and &2 are assigned to the same company (&3) | The short text describes the object sufficiently | |
113 | 182 | Recipient &1 cannot be deleted in status &2 | The short text describes the object sufficiently | |
114 | 183 | Own MDS ID &1: current MDS data is newer (no update) | The short text describes the object sufficiently | |
115 | 184 | Own MDS ID &1 rec. &2: current recipient data is newer (no update) | The short text describes the object sufficiently | |
116 | 185 | Supplier MDS ID &1: current MDS data is newer (no update) | The short text describes the object sufficiently | |
117 | 186 | Supplier MDS ID &1 rec. &2: current recipient data is newer (no update) | The short text describes the object sufficiently | |
118 | 187 | Result file not (yet) available | The short text describes the object sufficiently | |
119 | 188 | Deleting recipients (&1, &2) | The short text describes the object sufficiently | |
120 | 189 | Data was successfully submitted to IMDS | The short text describes the object sufficiently | |
121 | 190 | An MDS already exists for this specification | The short text describes the object sufficiently | |
122 | 191 | Assigned specification contains a different module ID | The short text describes the object sufficiently | |
123 | 192 | Assigned specification contains same module ID but a higher version | The short text describes the object sufficiently | |
124 | 193 | Material category of assigned specification differs to the MDS type | The short text describes the object sufficiently | |
125 | 194 | MDS is in recipient status &1 | The short text describes the object sufficiently | |
126 | 195 | The MDS supplier organization is not mapped to a supplier record | The short text describes the object sufficiently | |
127 | 196 | A request already exists for this specification | The short text describes the object sufficiently | |
128 | 197 | Result file processing was canceled (no file entries exist) | The short text describes the object sufficiently | |
129 | 198 | Selected org. ID is not assigned to the assigned supplier | The short text describes the object sufficiently | |
130 | 199 | Request &1 for MDS &2 cannot be deleted in request status &3 | The short text describes the object sufficiently | |
131 | 200 | Organization &1 is not defined as own organization | The short text describes the object sufficiently | |
132 | 201 | Specification with sub ID &1 does not exist or is not active | The short text describes the object sufficiently | |
133 | 202 | Organization with org. ID &1 does not exist or is not active | The short text describes the object sufficiently | |
134 | 203 | Contact person with pers. ID &1 does not exist or is not active | The short text describes the object sufficiently | |
135 | 204 | Request ID &1: current request data is newer (no update) | The short text describes the object sufficiently | |
136 | 205 | IMDS request file import (&1 : &2) | The short text describes the object sufficiently | |
137 | 206 | Request imported from file &1 | The short text describes the object sufficiently | |
138 | 207 | Could not find any request records | The short text describes the object sufficiently | |
139 | 208 | Request does not contain request ID | The short text describes the object sufficiently | |
140 | 209 | Request &1 for MDS &2 cannot be created in request status &3 | The short text describes the object sufficiently | |
141 | 210 | Request &1 for MDS &2 cannot be modified in request status &3 | The short text describes the object sufficiently | |
142 | 211 | Sending supplier request (&1, &2) | The short text describes the object sufficiently | |
143 | 212 | Request &1 cannot be rejected in status &2 | The short text describes the object sufficiently | |
144 | 213 | Request rejected (&1, &2, &3) | The short text describes the object sufficiently | |
145 | 214 | IMDS types do not match (&1 <> &2) | The short text describes the object sufficiently | |
146 | 215 | Data sheet of substance &1 cannot be assigned to request | Space: object requires documentation | |
147 | 216 | Request &1 successfully unassigned | The short text describes the object sufficiently | |
148 | 217 | Request unassigned (&1 : &2) | The short text describes the object sufficiently | |
149 | 218 | Do you really want to import MDS &1? | The short text describes the object sufficiently | |
150 | 219 | Request assigned (&1, &2 : &3) | The short text describes the object sufficiently | |
151 | 220 | You must enter a contact person for data sheets | The short text describes the object sufficiently | |
152 | 221 | You can only switch to module if no recipients are assigned | The short text describes the object sufficiently | |
153 | 222 | Nothing to upload to IMDS | Space: object requires documentation | |
154 | 223 | Cannot perform action; MDS/Module &1 is exported to IMDS | The short text describes the object sufficiently | |
155 | 224 | Deleting supplier request (&1, &2) | The short text describes the object sufficiently | |
156 | 225 | Cannot perform action; MDS/Module is not exported to IMDS | The short text describes the object sufficiently | |
157 | 226 | Worklist management created a new version of customer MDS | The short text describes the object sufficiently | |
158 | 227 | In synchronous mode, only one MDS record is allowed to be imported | The short text describes the object sufficiently | |
159 | 228 | IMDS version identifier in specification &1 is not valid | The short text describes the object sufficiently | |
160 | 229 | Cannot perform action; MDS structure was already imported | The short text describes the object sufficiently |
History
Last changed on/by | 20141109 | SAP | |
SAP Release Created in | 200_600 |