Message Number list used by SAP ABAP Class /TDAG/CP_IMDSCL_PROC_SUPPLMDS (Process Class for Supplier MDS)
SAP ABAP Class /TDAG/CP_IMDSCL_PROC_SUPPLMDS (Process Class for Supplier MDS) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | /TDAG/CPM_IMPORT - 017 | Cannot assign organization unit &1 to any suppliers | |
2 | Message Number | /TDAG/CPM_MANAGER - 007 | You are not authorized to start the import | |
3 | Message Number | /TDAG/CPM_MANAGER - 009 | You are not authorized for specification management | |
4 | Message Number | /TDAG/CP_IMDS - 169 | MDS structure data import into &1 (&2, &3) | |
5 | Message Number | /TDAG/CP_IMDS - 167 | Rejecting MDS (&1, &2) | |
6 | Message Number | /TDAG/CP_IMDS - 175 | Cannot perform action; communication to IMDS is currently running | |
7 | Message Number | /TDAG/CP_IMDS - 185 | Supplier MDS ID &1: current MDS data is newer (no update) | |
8 | Message Number | /TDAG/CP_IMDS - 186 | Supplier MDS ID &1 rec. &2: current recipient data is newer (no update) | |
9 | Message Number | /TDAG/CP_IMDS - 191 | Assigned specification contains a different module ID | |
10 | Message Number | /TDAG/CP_IMDS - 191 | Assigned specification contains a different module ID | |
11 | Message Number | /TDAG/CP_IMDS - 192 | Assigned specification contains same module ID but a higher version | |
12 | Message Number | /TDAG/CP_IMDS - 192 | Assigned specification contains same module ID but a higher version | |
13 | Message Number | /TDAG/CP_IMDS - 193 | Material category of assigned specification differs to the MDS type | |
14 | Message Number | /TDAG/CP_IMDS - 193 | Material category of assigned specification differs to the MDS type | |
15 | Message Number | /TDAG/CP_IMDS - 194 | MDS is in recipient status &1 | |
16 | Message Number | /TDAG/CP_IMDS - 195 | The MDS supplier organization is not mapped to a supplier record | |
17 | Message Number | /TDAG/CP_IMDS - 204 | Request ID &1: current request data is newer (no update) | |
18 | Message Number | /TDAG/CP_IMDS - 205 | IMDS request file import (&1 : &2) | |
19 | Message Number | /TDAG/CP_IMDS - 206 | Request imported from file &1 | |
20 | Message Number | /TDAG/CP_IMDS - 207 | Could not find any request records | |
21 | Message Number | /TDAG/CP_IMDS - 208 | Request does not contain request ID | |
22 | Message Number | /TDAG/CP_IMDS - 218 | Do you really want to import MDS &1? | |
23 | Message Number | /TDAG/CP_IMDS - 227 | In synchronous mode, only one MDS record is allowed to be imported | |
24 | Message Number | /TDAG/CP_IMDS - 229 | Cannot perform action; MDS structure was already imported | |
25 | Message Number | /TDAG/CP_IMDS - 166 | Accepting MDS (&1, &2) | |
26 | Message Number | /TDAG/CP_IMDS - 018 | Error when loading the file from DMS; file was not loaded | |
27 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
28 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
29 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
30 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
31 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
32 | Message Number | /TDAG/CP_IMDS - 040 | Error while creating the application log | |
33 | Message Number | /TDAG/CP_IMDS - 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) | |
34 | Message Number | /TDAG/CP_IMDS - 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) | |
35 | Message Number | /TDAG/CP_IMDS - 145 | IMDS system is not configured | |
36 | Message Number | /TDAG/CP_IMDS - 145 | IMDS system is not configured | |
37 | Message Number | /TDAG/CP_IMDS - 151 | Specification assignment changed to &1 (&2 : &3) | |
38 | Message Number | /TDAG/CP_IMDS - 152 | MDS record with different module ID was already assigned | |
39 | Message Number | /TDAG/CP_IMDS - 153 | MDS record with same module ID but higher version was already assigned | |
40 | Message Number | /TDAG/CP_IMDS - 157 | Material category of assigned specification does not match MDS type | |
41 | Message Number | /TDAG/CP_IMDS - 158 | IMDS file import (&1 : &2) | |
42 | Message Number | /TDAG/CP_IMDS - 159 | MDS imported from file &1. | |
43 | Message Number | /TDAG/CP_IMDS - 160 | IMDS organization &1 does not exist in organization table | |
44 | Message Number | /TDAG/CP_IMDS - 169 | MDS structure data import into &1 (&2, &3) | |
45 | Message Number | /TDAG/CP_IMDS_RES - 143 | Attribute 'RecipPartNo' missing in recipient data |