EHPRC_CP_IMDS - Message Class for IMDS
The following messages are stored in message class EHPRC_CP_IMDS: Message Class for IMDS.
It is part of development package EHPRC_CP_IMDS in software component EHS-MGM-PRC. This development package consists of objects that can be grouped under "IMDS Advanced Interface Communication".
It is part of development package EHPRC_CP_IMDS in software component EHS-MGM-PRC. This development package consists of objects that can be grouped under "IMDS Advanced Interface Communication".
Message Nr ▲ | Message Text |
|---|---|
| 000 | System failure: &1 &2 &3 &4 |
| 001 | Data set does not exist: &1 |
| 002 | Data set is locked by user &3 |
| 004 | Data set with initial primary key found in table &1 |
| 005 | Inconsistent root GUIDs; parent and child entry must have same root GUID |
| 006 | Data set that you want to create already exists |
| 007 | Cannot change data set because there are missing locks |
| 008 | Foreign key not found in parent table; contact system admin |
| 009 | Different root GUIDs; see long text |
| 010 | Entry without primary key in table &1 |
| 011 | Mandatory field is initial |
| 012 | No data found for the entered search criteria |
| 013 | Cannot display document (document number &1) |
| 014 | Cannot display application log (log handle &1) |
| 015 | Characteristic &1 is of type "Phrase" but the value is not |
| 016 | Property type &1 is unknown |
| 017 | Error while storing the file in DMS; file was not stored |
| 018 | Error while loading the file from DMS; file was not loaded |
| 019 | GUID does not exist; check your entry |
| 020 | &1, &2, &3, &4 |
| 021 | Cannot lock specification |
| 022 | Specification &1 locked |
| 023 | MatNo: &1, ModuleID: &2, ModuleVers: &3 |
| 024 | Error reading specification (RECN: &1) |
| 030 | INSERT statement in the database failed; database table: &1 |
| 031 | DELETE statement in the database failed; database table: &1, GUID: &2 |
| 032 | UPDATE statement in the database failed; database table: &1, GUID: &2 |
| 040 | Error while creating the application log |
| 041 | Loading the XML viewer failed |
| 042 | No log handle in MDS entry (GUID: &1, SUBID: &2) |
| 049 | |
| 050 | No compliance data object found for specification &1 |
| 051 | No compliance data object found for material &1 |
| 052 | No specification ID found for CDO key &1 |
| 053 | |
| 065 | No IMDS Node ID exists for the component |
| 066 | No IMDS Node ID exists for basic material &1 |
| 067 | Multiple CDOs found for IMDS Node ID &1 |
| 100 | -------- Messages for Customer / Supplier MDS Center ------------------- |
| 101 | Could not select an organization |
| 102 | Saved |
| 103 | Recipient &1 (&2) already added to the current MDS |
| 104 | Recipient cannot be the same as the own company (&1) |
| 105 | Refreshed |
| 106 | Saved to IMDS |
| 107 | MDS proposed |
| 108 | Recipient cannot be the same as own organization (&1) |
| 109 | Your own MDS is currently not assigned to a specification |
| 110 | Cannot find your own IMDS company |
| 111 | Contact person (&1) for org. unit (&2) is not in IMDS address management |
| 112 | Org. unit (&1) is not in IMDS address management |
| 113 | Own MDS sent in edit mode (Customer:&1, &2 : &3) |
| 114 | Recipient company ID not supplied |
| 115 | 'Part Index', 'Designer E-Mail' and 'Standard Index' fields are mandatory |
| 116 | Parse Error: &1 |
| 117 | Release Error: &1 &2 &3 &4 |
| 118 | Release Warning: &1 &2 &3 &4 |
| 119 | Result file imported (&1 : &2) |
| 120 | Messages in result file handling (&1 : &2) |
| 121 | Own MDS proposed to customer (Customer:&1, &2 : &3) |
| 122 | MDS &1 cannot be proposed in status &2 |
| 123 | No recipient or recipient status is not suitable for propose |
| 124 | MDS &1 cannot be saved in edit mode in status &2 |
| 125 | Contact person not supplied |
| 126 | No outgoing template specified |
| 127 | Outgoing template &1 does not exist |
| 128 | Define a document type in outgoing template &1 |
| 129 | Define an application in outgoing template &1 |
| 130 | Define a report generation function in outgoing template &1 |
| 131 | Supplied buffer mode &1 for MDS record &2 is not supported |
| 132 | MDS &1 cannot be sent to a customer in status &2 |
| 133 | No recipient or recipient status is not suitable for sending to customer |
| 134 | Only one recipient allowed for "Send to Customer" activity |
| 135 | MDS sent to customer (Customer:&1, &2, &3) |
| 136 | MDS released (&1, &2, &3) |
| 137 | MDS successfully sent to customer |
| 138 | MDS record &1 does not exist in buffer |
| 139 | No valid identifier for reference material (SUBID: &1) |
| 140 | MDS record &1 does not exist in the database but in the buffer |
| 141 | Outgoing template &1 not defined |
| 142 | Entered specification (&1) does not exist |
| 143 | Product structure of specification &1 does not conform with IMDS |
| 144 | Cannot create application log for MDS record &1 |
| 145 | IMDS system is not configured |
| 146 | MDS rejected |
| 147 | MDS accepted |
| 148 | No MDS selected for import |
| 149 | Import of MDS structure successfully started |
| 150 | Import aborted; no MDSs were selected or allowed to be imported |
| 151 | Specification assignment changed to &1 (&2 : &3) |
| 152 | MDS record with different module ID was already assigned |
| 153 | MDS record with same module ID but higher version was already assigned |
| 154 | Error occured in result file processing; see previous messages |
| 155 | MDS published |
| 156 | MDS &1 cannot be published in status &2 |
| 157 | Material category of assigned specification does not match MDS type |
| 158 | IMDS file import (&1 : &2) |
| 159 | MDS imported from file &1 |
| 160 | IMDS organization &1 does not exist in organization table |
| 161 | Cannot accept MDS &1 in status &2 |
| 162 | Cannot reject MDS &1 in status &2 |
| 163 | MDS published (&1, &2, &3) |
| 164 | Error while creating IMDS BAdI &1 |
| 165 | Check IMDS batch client connection; file transfer via RFC failed |
| 166 | Accepting MDS (&1, &2) |
| 167 | Rejecting MDS (&1, &2) |
| 168 | MDS copied |
| 169 | MDS structure data import into &1 (&2, &3) |
| 170 | Unable to read MDS with node ID &1 |
| 171 | Cannot find MDS in buffer |
| 172 | Failed to open the compliance workbench in simulation mode |
| 173 | Failed to import the MDS in simulation mode |
| 174 | Cannot perform action; import of MDS structure is currently running |
| 175 | Cannot perform action; communication to IMDS is currently running |
| 176 | Releasing the MDS internally (&1, &2, &3) |
| 177 | MDS &1 cannot be internally released in status &2 |
| 178 | MDS internally released |
| 179 | No head of product structure for normalization variant &1 (Spec &2) |
| 180 | MDS upload processed; new status is &1 |
| 181 | Recipient &1 and &2 are assigned to the same company (&3) |
| 182 | Cannot delect recipient &1 in status &2 |
| 183 | Own MDS ID &1: current MDS data is newer (no update) |
| 184 | Own MDS ID &1 rec. &2: current recipient data is newer (no update) |
| 185 | Supplier MDS ID &1: current MDS data is newer (no update) |
| 186 | Supplier MDS ID &1 rec. &2: current recipient data is newer (no update) |
| 187 | Result file not available |
| 188 | Deleting recipients (&1, &2) |
| 189 | Data submitted to IMDS |
| 190 | An MDS already exists for this specification |
| 191 | Assigned specification contains a different module ID |
| 192 | Assigned specification contains same module ID but a higher version |
| 193 | Material category of assigned specification differs to the MDS type |
| 194 | MDS is in recipient status &1 |
| 195 | MDS supplier organization is not mapped to a supplier record |
| 196 | Request already exists for this specification |
| 197 | Result file processing was canceled; no file entries exist |
| 198 | Selected org. ID is not assigned to the assigned supplier |
| 199 | Request &1 for MDS &2 cannot be deleted in request status &3 |
| 200 | Organization &1 is not defined as own organization |
| 201 | Specification with sub ID &1 does not exist or is not active |
| 202 | Organization with org. ID &1 does not exist or is not active |
| 203 | Contact person with pers. ID &1 does not exist or is not active |
| 204 | Request ID &1: current request data is newer (no update) |
| 205 | IMDS request file import (&1 : &2) |
| 206 | Request imported from file &1 |
| 207 | Cannot find any request records |
| 208 | Request does not contain request ID |
| 209 | Request &1 for MDS &2 cannot be created in request status &3 |
| 210 | Request &1 for MDS &2 cannot be modified in request status &3 |
| 211 | Sending supplier request (&1, &2) |
| 212 | Request &1 cannot be rejected in status &2 |
| 213 | Request rejected (Customer:&1, &2, &3) |
| 214 | IMDS types do not match (&1 <> &2) |
| 215 | Data sheet of substance &1 cannot be assigned to request |
| 216 | Request &1 unassigned |
| 217 | Request unassigned (&1 : &2) |
| 218 | Do you really want to import MDS &1? |
| 219 | Request assigned (Customer:&1, &2 : &3) |
| 220 | You must enter a contact person for data sheets |
| 221 | You can only switch to module if no recipients are assigned |
| 222 | Nothing to upload to IMDS |
| 223 | Cannot perform action; MDS/Module &1 is exported to IMDS |
| 224 | Deleting supplier request (&1, &2) |
| 225 | Cannot perform action; MDS/Module is not exported to IMDS |
| 226 | Worklist management created a new version of customer MDS |
| 227 | In synchronous mode, only one MDS record is allowed to be imported |
| 228 | IMDS version identifier in specification &1 is not valid |
| 229 | Cannot perform action; MDS structure for MDS &1 was already imported |
| 230 | IMDS batch client is not configured; MDS center functions are restricted |
| 231 | MDS center functions are restricted; maintain a valid IMDS system |
| 232 | Do you want to unassign material &1 from request? |
| 233 | Messages returned when reading own MDS: |
| 234 | Messages returned when writing own MDS: |
| 235 | Messages returned when reading supplier MDS: |
| 236 | Messages returned when writing supplier MDS: |
| 237 | Display not possible because MDS &1 is not mapped to a compliance object |
| 238 | Cannot perform action; import for MDS &1 is currently running |
| 239 | Enter mandatory company ID |
| 240 | Recipient part number &1 and supplier code &2 already used for MDS ID &3 |
| 241 | Current import status of MDS &1 does not permit import |
| 242 | MDS not found; import not possible |
| 243 | MDS &1 (&2) references the preliminary MDS &3 (&4) |
| 244 | MACSI number and eMail of designer are mandatory when sending a MDS to &1 |
| 245 | The system did not find any data that matches your selection criteria |