Skip to Content
If you didn’t know about it already,

working in a global community requires ‘openness’ to different people and cultures.

If you didn’t know about it already,

communicating in an open environment requires ‘acceptability’ to different languages and systems.

If you didn’t know about it already,

becoming a part of SAP’s partnering eco-system requires both ‘openness’ and ‘acceptability’.

If you didn’t know about it already,

I am talking about Unicode testing!

That means that the SAP Integration and Certification Center (ICC) has started to test for these unique qualities in the product integrations we certify. A system is Unicode, in the business lingo, represents openness to multi-languages it interacts with. The technical jargon equates to START {non-ASCII char input via XML syntax returns valid results || outputs} END.

Since the majority of SAP applications, systems, and SAP NetWeaver all run on Unicode, it would make sense that SAP partners’ certified product integrations are Unicode enabled as well. Therefore, the ICC has started to include Unicode supportability as one of its items during our certification tests. Let me be clear … it is not mandatory to support Unicode, but since the current and future SAP releases will be Unicode only, we only anticipate that our customers will expect to have certified Unicode integrations.

How can I generate Unicode test data?

It is not necessary to have meaningful data. The strings are created with “foreign” Unicode characters (e.g. সুকুমার রায়, , äÕÑÊ ÝÊÍ Úáی ÎÇä, சிவாஜி கனேசன்). To enter Unicode data, you can either turn on the Language Toolbar in the Windows Taskbar and write text with the keyboard or you can use some from an Internet page to copy and paste the Unicode characters. Here are some sites:

http://www.i18nguy.com/unicode-example.html
http://www-306.ibm.com/software/globalization/topics/unicode/unicode_samples.html

How is the testing done?

During the test procedure, we will generate the necessary Unicode data in the SAP applications. If the test is conducted on your landscape (e.g. ABAP, EP-BP, PCA, etc.) then you should add some Unicode data there. The testing of the Unicode-enabled integration scenarios is done exactly the same way as before; However, for at least one test case, you will use Unicode characters and check that they are transferred and/or displayed correctly. Contact the ICC if you have any questions: https://www.benchmarking.sap.com/cgi-bin/qwebcorporate.dll?idx=B6EM96.

And, one last time! If you didn’t know about it already, Unicode supportability will be mentioned on the certificate as an additional certified function and will also shown be  in SAP’s online catalogs about your company’s certified product. Since we interact in a global area, let’s ensure that our systems communicate globally through the means of Unicode acceptability!

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply