Skip to Content

Easy DMS - problem with object linking (unicode client)

Hi Gurus,

I have a problem concerning linking a materialmaster to a DIR in a uniciode environment. I tested following scenarios:

1) Easy DMS 6.00 SP10 non unicode + non unicode Backend --> no problem

2) Easy DMS 6.00 SP10 non unicode + unicode Backend --> no problem

3) Easy DMS 6.00 SP10 unicode + non unicode Backend --> no problem

4) Easy DMS 6.00 SP10 unicode + unicode Backend --> problem

Following Problem appears in scenario 4:

Our Material Number Format is ______-____-___ (6 digits - 4 digits - 3 digits), "Lexicographical" is disabled, "Leading Zeros" is enabled.

When I type in material number "111111-2222-333" and press "check all objects and read description" Easy DMS reads the description for

111111-2222-333 but after that easy dms changes 111111-2222-333 to 000001-1111-122 and when I try to save the DIR it tells me that

000001-1111-122 is not a valid material master.

As I mentioned this only appears with the unicode client + unicode backend. Any Ideas?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Apr 08, 2008 at 01:50 PM

    Hi David,

    please tell us which version of EasyDMS you use currently. If you do not use EasyDMS 6.00 SP10 I would kindly ask you to see SAP note 1105699 and download this SP from the Service Marketplace.

    Further please check if you have maintained the object link customizing correclty in your backend system. Therefore please see the information in the SDN WIKI area for DMS under

    Best regards,


    P.S.: Please reward points for useful information.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Christoph,

      as mentioned above I use Easy DMS 6.00 SP10. I checked the customizing and it seems to be right.

      Objekt linking works fine within the GUI an while using the non unicode verison. The problem only

      appears while using the unicode version of Easy DMS with a unicode backend.

      We switched a second backend system from non-unicode to unicode and now I have the same problem here.

      Edited by: David Deeg on Apr 9, 2008 7:55 AM

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.