Enhancements In IMDS Release 14.1

The release of IMDS 14.1 has been planned for August 9, 2023, with the following enhancements.

There will be 8 enhancements in total in three different categories as follows:

Functional Changes:

1. Rejection reason in inbox/outbox search result and export
2. Search for SCIP Material Category by ID
3. The default selection of Org.-Unit in new MDSs

Check Changes:

4. No error when sending of MDSs with default contact
5. Error for inactive application codes
6. Error for editable references to hidden data

Master Data Changes:

7. Split AC 5(b)
8. Rename AC 8(f)(a) and 8(f)(b)

The following is the information about the preliminary IMDS release 14.1.

1. Rejection reason in inbox/outbox search result and export

The rejection reason will be displayed in both Inbox and Outbox search results for the parts whose status is ‘Rejected’ and ‘Modified’ in IMDS with a limit of 50 characters if the rejection reasons are too lengthy. However, the complete rejection reasons will be available in the generated file if exporting the search results in an Excel file.

2. Search for SCIP Material Category by ID

A new search parameter will be added to the dialog to add a SCIP Material Category to a material. This parameter will allow searching for a category directly by ID as the “Taric code” search parameter works for adding SCIP Article Categories to components.

3. The default selection of Org.-Unit in the new MDS

Whenever a user sends, proposes, publishes, or releases an MDS the org. unit will be assigned in the “Supplier data” tab and it will be stored as the user’s default Org Unit. If the user creates a new MDS the default Org Unit will be preselected automatically.

If the user has not yet sent, proposed, published, or released an MDS after IMDS Release 14.1, if they are no longer assigned to their current default Org Unit or if that Org Unit has

4. No error when sending of MDSs with default contact

No more error messages will be shown for MDSs with an assigned deactivated contact person if an active default contact person is available. So, the older MDSs can be proposed with no longer active contact persons instead of creating a new version.

5. Error for inactive application codes

To prevent the continued use of deactivated application codes, all warning messages related to an inactive application code will be converted to errors. The error will occur if the MDS contains a deactivated application code even if it is used within a referenced MDS. To clear up such an error, a new version must be created, and the affected references have to be replaced with the appropriate data.

6. Error for editable references to hidden data

There will be new error messages if direct references to hidden substances, standard MDSs, or application codes in editable MDSs. If so, hidden data must be replaced before releasing an MDS.

Since hidden data cannot be found and referenced in a new MDS/module, this only affects new versions of existing MDSs/modules referencing such data. If the hidden data referenced inside referenced MDSs or inside released MDSs will not result in any error or warning. And there is no change to deactivated data (substances, standard MDSs, or application codes) as references to those in editable MDSs already show an error message.

7. Split AC 5(b)

To comply with the latest version of ELV Annex II, the application code 5(b) will be split into two new application codes 5(b)(i) and 5(b)(ii). The existing application code 5(b) will be hidden, and the two new ones will be added:

Both new application codes will apply to the same substances and classifications as the previous one.

8.Rename AC 8(f)(a) and 8(f)(b)

To comply with the latest version of ELV Annex II, the application code 8(f)(a) and 8(f)(b) will be renamed to also contain the new identifier:

The new name will automatically be visible for all uses of these application codes. No further action is required.

Reference: https://public.mdsystem.com/documents/d/imds-public-pages/prel_release-information_14-1_en-pdf