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
⤷
⤷
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 | System failure: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 2 | Data set does not exist: &1 | The short text describes the object sufficiently | ||
| 3 | Data set is locked by user &3 | Space: object requires documentation | ||
| 4 | Data set with initial primary key found in table &1 | The short text describes the object sufficiently | ||
| 5 | Inconsistent root GUIDs; parent and child entry must have same root GUID | Space: object requires documentation | ||
| 6 | Data set that you want to create already exists | Space: object requires documentation | ||
| 7 | Cannot change data set because there are missing locks | The short text describes the object sufficiently | ||
| 8 | Foreign key is missing in parent table; check database entries | Space: object requires documentation | ||
| 9 | MDS contains different root GUIDs to corresponding chapter 4 data | Space: object requires documentation | ||
| 10 | Missing primary key in table &1 | The short text describes the object sufficiently | ||
| 11 | Mandatory field is initial | Space: object requires documentation | ||
| 12 | No data was found for the entered search criteria | The short text describes the object sufficiently | ||
| 13 | Cannot display document (document number &1) | The short text describes the object sufficiently | ||
| 14 | Cannot display application log (log handle &1) | The short text describes the object sufficiently | ||
| 15 | Characteristic &1 is of type "Phrase" but the value is not | The short text describes the object sufficiently | ||
| 16 | Property type &1 is unknown | The short text describes the object sufficiently | ||
| 17 | Error when storing the file in DMS; file was not stored | Space: object requires documentation | ||
| 18 | Error when loading the file from DMS; file was not loaded | Space: object requires documentation | ||
| 19 | You requested a GUID that does not exist; check your entry | Space: object requires documentation | ||
| 20 | &1, &2, &3, &4 | The short text describes the object sufficiently | ||
| 21 | A specification could not be locked | The short text describes the object sufficiently | ||
| 22 | Specification &1 locked | The short text describes the object sufficiently | ||
| 23 | MatNo: &1, ModuleID: &2, ModuleVers: &3 | The short text describes the object sufficiently | ||
| 24 | Error reading specification (RECN: &1) | The short text describes the object sufficiently | ||
| 25 | An INSERT statement into the database failed; database table: &1 | The short text describes the object sufficiently | ||
| 26 | A DELETE statement on the database failed; database table: &1, GUID: &2 | The short text describes the object sufficiently | ||
| 27 | An UPDATE statement on the database failed; database table: &1, GUID: &2 | The short text describes the object sufficiently | ||
| 28 | Error while creating the application log | The short text describes the object sufficiently | ||
| 29 | Loading the XML viewer failed | The short text describes the object sufficiently | ||
| 30 | No log handle in MDS entry (GUID: &1, SUBID: &2) | The short text describes the object sufficiently | ||
| 31 | -------- Messages for Customer / Supplier MDS Center ------------------- | The short text describes the object sufficiently | ||
| 32 | Could not select an organization | The short text describes the object sufficiently | ||
| 33 | Save successfully performed | The short text describes the object sufficiently | ||
| 34 | Recipient &1 (&2) was already added to the current MDS | The short text describes the object sufficiently | ||
| 35 | Recipient must not be the same as the own company (&1) | The short text describes the object sufficiently | ||
| 36 | Refresh successfully performed | The short text describes the object sufficiently | ||
| 37 | Save to IMDS successfully performed | The short text describes the object sufficiently | ||
| 38 | MDS successfully proposed | The short text describes the object sufficiently | ||
| 39 | Recipient cannot be same as own organization (&1) | The short text describes the object sufficiently | ||
| 40 | Your own MDS is currently not assigned to a specification | The short text describes the object sufficiently | ||
| 41 | Could not find your own IMDS company | Space: object requires documentation | ||
| 42 | Contact person (&1) for org. unit (&2) is not in IMDS address management | Space: object requires documentation | ||
| 43 | Org. unit (&1) is not in IMDS adress management | Space: object requires documentation | ||
| 44 | Own MDS sent in edit mode (&1, &2 : &3) | The short text describes the object sufficiently | ||
| 45 | Recipient company ID not supplied | The short text describes the object sufficiently | ||
| 46 | 'Part Index', 'Designer E-Mail' and 'Standard Index' fields are mandatory | Space: object requires documentation | ||
| 47 | Parse Error: &1 | The short text describes the object sufficiently | ||
| 48 | Release Error: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 49 | Release Warning: &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 50 | Result file imported (&1 : &2) | The short text describes the object sufficiently | ||
| 51 | Messages in result file handling (&1 : &2) | The short text describes the object sufficiently | ||
| 52 | Own MDS proposed to customer (&1, &2 : &3) | The short text describes the object sufficiently | ||
| 53 | MDS &1 cannot be proposed in status &2 | The short text describes the object sufficiently | ||
| 54 | No recipient or recipient status is not suitable for propose | The short text describes the object sufficiently | ||
| 55 | MDS &1 cannot be saved in edit mode in status &2 | The short text describes the object sufficiently | ||
| 56 | Contact person not supplied | The short text describes the object sufficiently | ||
| 57 | No outgoing template specified | The short text describes the object sufficiently | ||
| 58 | Outgoing template &1 does not exist | The short text describes the object sufficiently | ||
| 59 | Define a document type in outgoing template &1 | Space: object requires documentation | ||
| 60 | Define an application in outgoing template &1 | Space: object requires documentation | ||
| 61 | Define a report generation function in outgoing template &1 | Space: object requires documentation | ||
| 62 | Supplied buffer mode &1 for MDS record &2 is not supported | The short text describes the object sufficiently | ||
| 63 | MDS &1 cannot be sent to a customer in status &2 | The short text describes the object sufficiently | ||
| 64 | No recipient or recipient status is not suitable for sending to customer | The short text describes the object sufficiently | ||
| 65 | Only one recipient allowed for "Send to Customer" activity | The short text describes the object sufficiently | ||
| 66 | MDS sent to customer (&1, &2, &3) | The short text describes the object sufficiently | ||
| 67 | MDS released (&1, &2, &3) | The short text describes the object sufficiently | ||
| 68 | MDS successfully sent to customer | The short text describes the object sufficiently | ||
| 69 | MDS record &1 does not exist in buffer | The short text describes the object sufficiently | ||
| 70 | No valid identifier for reference material (SUBID: &1) | Space: object requires documentation | ||
| 71 | MDS record &1 does not exist in the database but in the buffer | The short text describes the object sufficiently | ||
| 72 | Outgoing template &1 not defined | The short text describes the object sufficiently | ||
| 73 | The entered specification (&1) does not exist | The short text describes the object sufficiently | ||
| 74 | Product structure of specification &1 does not conform with IMDS | Space: object requires documentation | ||
| 75 | Cannot create application log for MDS record &1 | The short text describes the object sufficiently | ||
| 76 | IMDS system is not configured | Space: object requires documentation | ||
| 77 | MDS was rejected | The short text describes the object sufficiently | ||
| 78 | MDS was accepted | The short text describes the object sufficiently | ||
| 79 | No MDS selected for import | The short text describes the object sufficiently | ||
| 80 | Import of MDS structure successfully started | The short text describes the object sufficiently | ||
| 81 | Import aborted; no MDSs were selected or allowed to be imported | The short text describes the object sufficiently | ||
| 82 | Specification assignment changed to &1 (&2 : &3) | The short text describes the object sufficiently | ||
| 83 | MDS record with different module ID was already assigned | The short text describes the object sufficiently | ||
| 84 | MDS record with same module ID but higher version was already assigned | The short text describes the object sufficiently | ||
| 85 | Error occured in result file processing; see previous messages | The short text describes the object sufficiently | ||
| 86 | MDS successfully published | The short text describes the object sufficiently | ||
| 87 | MDS &1 cannot be published in status &2 | The short text describes the object sufficiently | ||
| 88 | Material category of assigned specification does not match MDS type | The short text describes the object sufficiently | ||
| 89 | IMDS file import (&1 : &2) | The short text describes the object sufficiently | ||
| 90 | MDS imported from file &1. | The short text describes the object sufficiently | ||
| 91 | IMDS organization &1 does not exist in organization table | Space: object requires documentation | ||
| 92 | MDS &1 cannot be accepted in status &2 | The short text describes the object sufficiently | ||
| 93 | MDS &1 cannot be rejected in status &2 | The short text describes the object sufficiently | ||
| 94 | MDS published (&1, &2, &3) | The short text describes the object sufficiently | ||
| 95 | Error creating IMDS BAdI &1 | The short text describes the object sufficiently | ||
| 96 | IMDS batch client RFC failure | Space: object requires documentation | ||
| 97 | Accepting MDS (&1, &2) | The short text describes the object sufficiently | ||
| 98 | Rejecting MDS (&1, &2) | The short text describes the object sufficiently | ||
| 99 | MDS successfully copied | The short text describes the object sufficiently | ||
| 100 | MDS structure data import into &1 (&2, &3) | The short text describes the object sufficiently | ||
| 101 | Unable to read MDS with node ID &1 | The short text describes the object sufficiently | ||
| 102 | Could not find MDS in buffer | The short text describes the object sufficiently | ||
| 103 | Failed to open the compliance workbench in simulation mode | The short text describes the object sufficiently | ||
| 104 | Failed to import the MDS in simulation mode | The short text describes the object sufficiently | ||
| 105 | Cannot perform action; import of MDS structure is currently running | The short text describes the object sufficiently | ||
| 106 | Cannot perform action; communication to IMDS is currently running | The short text describes the object sufficiently | ||
| 107 | Releasing the MDS internally (&1, &2, &3) | The short text describes the object sufficiently | ||
| 108 | MDS &1 cannot be internally released in status &2 | The short text describes the object sufficiently | ||
| 109 | MDS successfully internally released | The short text describes the object sufficiently | ||
| 110 | No head of product structure for normalization variant &1 (Spec &2) | The short text describes the object sufficiently | ||
| 111 | MDS upload successfully processed; new status is &1 | The short text describes the object sufficiently | ||
| 112 | Recipient &1 and &2 are assigned to the same company (&3) | The short text describes the object sufficiently | ||
| 113 | Recipient &1 cannot be deleted in status &2 | The short text describes the object sufficiently | ||
| 114 | Own MDS ID &1: current MDS data is newer (no update) | The short text describes the object sufficiently | ||
| 115 | Own MDS ID &1 rec. &2: current recipient data is newer (no update) | The short text describes the object sufficiently | ||
| 116 | Supplier MDS ID &1: current MDS data is newer (no update) | The short text describes the object sufficiently | ||
| 117 | Supplier MDS ID &1 rec. &2: current recipient data is newer (no update) | The short text describes the object sufficiently | ||
| 118 | Result file not (yet) available | The short text describes the object sufficiently | ||
| 119 | Deleting recipients (&1, &2) | The short text describes the object sufficiently | ||
| 120 | Data was successfully submitted to IMDS | The short text describes the object sufficiently | ||
| 121 | An MDS already exists for this specification | The short text describes the object sufficiently | ||
| 122 | Assigned specification contains a different module ID | The short text describes the object sufficiently | ||
| 123 | Assigned specification contains same module ID but a higher version | The short text describes the object sufficiently | ||
| 124 | Material category of assigned specification differs to the MDS type | The short text describes the object sufficiently | ||
| 125 | MDS is in recipient status &1 | The short text describes the object sufficiently | ||
| 126 | The MDS supplier organization is not mapped to a supplier record | The short text describes the object sufficiently | ||
| 127 | A request already exists for this specification | The short text describes the object sufficiently | ||
| 128 | Result file processing was canceled (no file entries exist) | The short text describes the object sufficiently | ||
| 129 | Selected org. ID is not assigned to the assigned supplier | The short text describes the object sufficiently | ||
| 130 | Request &1 for MDS &2 cannot be deleted in request status &3 | The short text describes the object sufficiently | ||
| 131 | Organization &1 is not defined as own organization | The short text describes the object sufficiently | ||
| 132 | Specification with sub ID &1 does not exist or is not active | The short text describes the object sufficiently | ||
| 133 | Organization with org. ID &1 does not exist or is not active | The short text describes the object sufficiently | ||
| 134 | Contact person with pers. ID &1 does not exist or is not active | The short text describes the object sufficiently | ||
| 135 | Request ID &1: current request data is newer (no update) | The short text describes the object sufficiently | ||
| 136 | IMDS request file import (&1 : &2) | The short text describes the object sufficiently | ||
| 137 | Request imported from file &1 | The short text describes the object sufficiently | ||
| 138 | Could not find any request records | The short text describes the object sufficiently | ||
| 139 | Request does not contain request ID | The short text describes the object sufficiently | ||
| 140 | Request &1 for MDS &2 cannot be created in request status &3 | The short text describes the object sufficiently | ||
| 141 | Request &1 for MDS &2 cannot be modified in request status &3 | The short text describes the object sufficiently | ||
| 142 | Sending supplier request (&1, &2) | The short text describes the object sufficiently | ||
| 143 | Request &1 cannot be rejected in status &2 | The short text describes the object sufficiently | ||
| 144 | Request rejected (&1, &2, &3) | The short text describes the object sufficiently | ||
| 145 | IMDS types do not match (&1 <> &2) | The short text describes the object sufficiently | ||
| 146 | Data sheet of substance &1 cannot be assigned to request | Space: object requires documentation | ||
| 147 | Request &1 successfully unassigned | The short text describes the object sufficiently | ||
| 148 | Request unassigned (&1 : &2) | The short text describes the object sufficiently | ||
| 149 | Do you really want to import MDS &1? | The short text describes the object sufficiently | ||
| 150 | Request assigned (&1, &2 : &3) | The short text describes the object sufficiently | ||
| 151 | You must enter a contact person for data sheets | The short text describes the object sufficiently | ||
| 152 | You can only switch to module if no recipients are assigned | The short text describes the object sufficiently | ||
| 153 | Nothing to upload to IMDS | Space: object requires documentation | ||
| 154 | Cannot perform action; MDS/Module &1 is exported to IMDS | The short text describes the object sufficiently | ||
| 155 | Deleting supplier request (&1, &2) | The short text describes the object sufficiently | ||
| 156 | Cannot perform action; MDS/Module is not exported to IMDS | The short text describes the object sufficiently | ||
| 157 | Worklist management created a new version of customer MDS | The short text describes the object sufficiently | ||
| 158 | In synchronous mode, only one MDS record is allowed to be imported | The short text describes the object sufficiently | ||
| 159 | IMDS version identifier in specification &1 is not valid | The short text describes the object sufficiently | ||
| 160 | 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 |