Message Number list used by SAP ABAP Class /TDAG/CP_IMDSCL_PROC_CUSTMDS (Release an MDS internally)
SAP ABAP Class /TDAG/CP_IMDSCL_PROC_CUSTMDS (Release an MDS internally) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | /TDAG/CPM_EXPORT - 025 | Specification &1: result &2 for check &3 is not allowed (export type &4) | |
2 | Message Number | /TDAG/CPM_EXPORT - 024 | Specification &1: compliance check &2 for export type &3 is missing | |
3 | Message Number | /TDAG/CPM_MANAGER - 007 | You are not authorized to start the import | |
4 | Message Number | /TDAG/CP_IMDS - 192 | Assigned specification contains same module ID but a higher version | |
5 | Message Number | /TDAG/CP_IMDS - 158 | IMDS file import (&1 : &2) | |
6 | Message Number | /TDAG/CP_IMDS - 191 | Assigned specification contains a different module ID | |
7 | Message Number | /TDAG/CP_IMDS - 191 | Assigned specification contains a different module ID | |
8 | Message Number | /TDAG/CP_IMDS - 184 | Own MDS ID &1 rec. &2: current recipient data is newer (no update) | |
9 | Message Number | /TDAG/CP_IMDS - 183 | Own MDS ID &1: current MDS data is newer (no update) | |
10 | Message Number | /TDAG/CP_IMDS - 181 | Recipient &1 and &2 are assigned to the same company (&3) | |
11 | Message Number | /TDAG/CP_IMDS - 180 | MDS upload successfully processed; new status is &1 | |
12 | Message Number | /TDAG/CP_IMDS - 175 | Cannot perform action; communication to IMDS is currently running | |
13 | Message Number | /TDAG/CP_IMDS - 172 | Failed to open the compliance workbench in simulation mode | |
14 | Message Number | /TDAG/CP_IMDS - 171 | Could not find MDS in buffer | |
15 | Message Number | /TDAG/CP_IMDS - 169 | MDS structure data import into &1 (&2, &3) | |
16 | Message Number | /TDAG/CP_IMDS - 169 | MDS structure data import into &1 (&2, &3) | |
17 | Message Number | /TDAG/CP_IMDS - 159 | MDS imported from file &1. | |
18 | Message Number | /TDAG/CP_IMDS - 229 | Cannot perform action; MDS structure was already imported | |
19 | Message Number | /TDAG/CP_IMDS - 192 | Assigned specification contains same module ID but a higher version | |
20 | Message Number | /TDAG/CP_IMDS - 193 | Material category of assigned specification differs to the MDS type | |
21 | Message Number | /TDAG/CP_IMDS - 193 | Material category of assigned specification differs to the MDS type | |
22 | Message Number | /TDAG/CP_IMDS - 204 | Request ID &1: current request data is newer (no update) | |
23 | Message Number | /TDAG/CP_IMDS - 205 | IMDS request file import (&1 : &2) | |
24 | Message Number | /TDAG/CP_IMDS - 206 | Request imported from file &1 | |
25 | Message Number | /TDAG/CP_IMDS - 207 | Could not find any request records | |
26 | Message Number | /TDAG/CP_IMDS - 208 | Request does not contain request ID | |
27 | Message Number | /TDAG/CP_IMDS - 215 | Data sheet of substance &1 cannot be assigned to request | |
28 | Message Number | /TDAG/CP_IMDS - 217 | Request unassigned (&1 : &2) | |
29 | Message Number | /TDAG/CP_IMDS - 218 | Do you really want to import MDS &1? | |
30 | Message Number | /TDAG/CP_IMDS - 223 | Cannot perform action; MDS/Module &1 is exported to IMDS | |
31 | Message Number | /TDAG/CP_IMDS - 225 | Cannot perform action; MDS/Module is not exported to IMDS | |
32 | Message Number | /TDAG/CP_IMDS - 227 | In synchronous mode, only one MDS record is allowed to be imported | |
33 | Message Number | /TDAG/CP_IMDS - 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) | |
34 | Message Number | /TDAG/CP_IMDS - 000 | System failure: &1 &2 &3 &4 | |
35 | Message Number | /TDAG/CP_IMDS - 000 | System failure: &1 &2 &3 &4 | |
36 | Message Number | /TDAG/CP_IMDS - 000 | System failure: &1 &2 &3 &4 | |
37 | Message Number | /TDAG/CP_IMDS - 000 | System failure: &1 &2 &3 &4 | |
38 | Message Number | /TDAG/CP_IMDS - 018 | Error when loading the file from DMS; file was not loaded | |
39 | Message Number | /TDAG/CP_IMDS - 022 | Specification &1 locked | |
40 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
41 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
42 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
43 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
44 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
45 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
46 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
47 | Message Number | /TDAG/CP_IMDS - 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) | |
48 | Message Number | /TDAG/CP_IMDS - 157 | Material category of assigned specification does not match MDS type | |
49 | Message Number | /TDAG/CP_IMDS - 103 | Recipient &1 (&2) was already added to the current MDS | |
50 | Message Number | /TDAG/CP_IMDS - 104 | Recipient must not be the same as the own company (&1) | |
51 | Message Number | /TDAG/CP_IMDS - 108 | Recipient cannot be same as own organization (&1) | |
52 | Message Number | /TDAG/CP_IMDS - 126 | No outgoing template specified | |
53 | Message Number | /TDAG/CP_IMDS - 127 | Outgoing template &1 does not exist | |
54 | Message Number | /TDAG/CP_IMDS - 128 | Define a document type in outgoing template &1 | |
55 | Message Number | /TDAG/CP_IMDS - 129 | Define an application in outgoing template &1 | |
56 | Message Number | /TDAG/CP_IMDS - 130 | Define a report generation function in outgoing template &1 | |
57 | Message Number | /TDAG/CP_IMDS - 145 | IMDS system is not configured | |
58 | Message Number | /TDAG/CP_IMDS - 145 | IMDS system is not configured | |
59 | Message Number | /TDAG/CP_IMDS - 151 | Specification assignment changed to &1 (&2 : &3) | |
60 | Message Number | /TDAG/CP_IMDS - 152 | MDS record with different module ID was already assigned | |
61 | Message Number | /TDAG/CP_IMDS - 153 | MDS record with same module ID but higher version was already assigned |