image
Write no Evil?
Background to the weblog: While attending the ASUG/Sapphire US 2006 event, I happened upon an interesting discussion at one of the SAP NetWeaver exhibit booths (or ‘pods’ as we call them at SAP – something out of invasion of the body snatchers don’t you think?) I was staffing. The discussion started out simply enough about implementing additional capabilities of SAP NetWeaver and the approach that the customer should take. The discussion wound its way to the part about staffing the project itself – this is where I was asked by the customer if it was worth hiring SAP NetWeaver certified consultants for the project. From SAP’s perspective, the answer is always ‘Yes’ to this question. Now this is where the conversation got more philosophical as the customer stated that while he liked the idea of a consultant having a certain quality level of knowledge. An observation from the customer was that the certification itself did not always ensure that the consultant was competent -“How could some consultants actually get certified when they obviously did not have the basic understanding of the product area they were meant to have specialized in?”. There are probably a large number of reasons you could argue why this could be, so I was pleased to see that this customer had rigorous interviewing techniques to reduce this risk of hiring a consultant who know less than his staff. Following this conversation, while talking to colleagues on the SDN pod (yes, we use alien technology to clone our SDN staff – it explains a lot!) about some of the challenges of moderating SDN forums, one of my colleagues mentioned that he was having some challenges in his area, specifically the BI related forums, with multiple postings of requests for certification questions and the responses. He said that he had started to remove some of the postings but had received feedback from some SDN posters that this was censorship and he should stop. As further background, the SDN community guidelines state "We reserve the right to remove any postings (although we have no duty to do so)." So this leads to the philosophical discussion?
Should SDN editors and moderators have the right to control content posted on SDN? Is this censorship?
Completely taking off my SAP Employee hat here, I personally have strong beliefs in the freedom of speech and against censorship in almost every form but unfortunately its not a black and white subject and needs intelligent discussion, agreement, and some enforceable rules. The subject of this weblog is not to talk about censorship vs. freedom of speech in the general context (there are numerous newsgroups on the web that cover this already) but the specific topic of whether SDN editors and moderators should remove content that they deem questionable or harmful. Of course this now leads down the whole rat-hole of what does “questionable” or “harmful” actually mean? So for this blog I want to limit the discussion to that of the certification questions postings (and answers!) on the forums in SDN. I think this is a relatively safe discussion for SDN and relevant to most people who use SDN without opening up a very very large can of worms. In addition I do not want to open the discussion in the specific merits of the actual certifications themselves as that is a weblog in itself and something someone else might want to post on! It is not an easy topic to get your hands around so I’ll pose a few questions to think about: • Is it ethical for people to post certification examination questions and answers on SDN forums? • Is this cheating or simple information sharing or are the posters cheaters or information sharers? • Do such postings diminish the certification test itself? • Would you feel comfortable hiring a consultant if you knew that they could have cheated on their certification tests? • Do you see the SAP NetWeaver certifications as valuable achievements that people should work hard for? • Should SAP change the certification test questions more frequently? • Should SDN forum moderators remove such postings on SDN? • Is there any difference between removing these posts and removing blatantly incorrect information from SDN? • Should fellow community forum posters self police the forums and add postings requesting the posters not do this? Would self policing work? • Does it make a difference if the moderators removing these posting are SAP employees or not? • Do inaction or removal actions by SDN forum moderators on these postings diminish the SDN community as a whole? • Or does the presence of such postings diminish the integrity of the community? image OR image You may or may not have made up your mind when thinking about these questions. This blogger’s opinion is that we should remove such postings and specifically prohibit such postings in the community guidelines - other communities do control content too (see below). I have not removed any postings as of yet but there are a multitude of them already in the forums. Obviously this does not holistically solve this problem as there are other non–SDN SAP forums on the web where these individuals could go to post but I believe it does improve the SDN community itself by reducing ‘unethical’ actions by individuals. In addition I believe that everyone benefits when we have highly ethical and trained/certified consultants and users to work with. If we do exercise content control, where is the tipping point if we start adding more content restrictions to an open community? Even Google, whose corporate philosophy is “Do No Evil” has wrestled with this one and implemented at its discretion the ability to edit content on newsgroups set up by individuals (I will avoid the whole Chinese censorship issue immediately as this is a highly political discussion and not really a topic for SDN). Below is an extract from its terms and policies: Google's Rights. "... If Google discovers Content that does not appear to conform to the Terms of Service, Google may investigate and determine in good faith and in its sole discretion whether to remove the Content..." During my limited research for this blog I found newsgroups with answers to the questions for my state’s driving examination! Now this is really scary that people may be out there without having learnt the laws. Obviously SAP Certification exams are not as life endangering as this example but it does bring some of the arguments into perspective… Maybe I should be suspicious of people who have passed both and drive really badly… or am I including myself there??? :-) Got to love this WWW, you find examples for everything! We could produce handbooks for these people too!! image So there you have it, I hope you found this thought-provoking and something worth reading? I look forward to the comments posted. All the best, “Write no Evil” Mike (A SDN forum moderator, SDN community volunteer, former SAP consultant and SAP customer)

The next step in the transition to Unicode at SAP is just around the corner – actually sneaking in with the New Year while we are partying. So what delights does 2007 bring us?

 

As of the end of 2006, all new releases of SAP NetWeaver and SAP applications based on SAP NetWeaver will only be available for installation based on Unicode.


This next step on the road to Unicode is probably an obvious one for those observant globalization readers of SDN and the SAP Service Marketplace but this now puts a definitive stake in the ground in regard to what and when. Before we go into details, it might help to know a little background about the SAP globalization solutions for supporting representation of multiple language character combinations:


  • The first step for SAP was to work on the Unicode standard itself with other technology companies. We had prior SAP workaround stop gap solutions but Unicode was the ultimate goal. Once Unicode was defined and implemented, SAP delivered versions on all SAP applications that supported Unicode.

  • The second step was to provide robust and productized conversion tools for all application, whether the source is a single code, a blended code page, or an MDMP based application (much better than delivering fragile and pre-production quality tools, don’t you think? ;-) ).

  • The next step was to phase out the older workaround technologies used to support multi-language requirements prior to Unicode. ‘Blended code pages’ were de-supported with the release of SAP NetWeaver Application Server 6.10 (and therefore for SAP applications based on SAP NetWeaver AS 6.10 or higher). New MDMP installations for SAP R/3/mySAP ERP were not possible starting with the release of mySAP ERP 2004. Finally MDMP is no longer supported as of mySAP ERP 2005 - only single code pages and Unicode (to view a weblog on this click Globalization: End of full support for MDMP implementations)

  • The latest step is that all new applications and SAP NetWeaver capabilities will only be built and delivered as Unicode solutions (example of these applications include SAP NetWeaver Exchange infrastructure, SAP NetWeaver Master Data Management, any J2EE based SAP applications, etc)


 

So this brings us to today and the announcement covered in this weblog. So what are the important points of the Unicode customer announcement and what does it mean to you:


1. Every SAP Customer was sent a letter in April 2006 notifying them of this change. It is a possibility that this letter did not reach the system administrators/landscape architects in your company - it is probably sitting on the desk of someone who signed the SAP contract and is still wondering what Unicode and bits are but afraid to ask anyone. Yes, this the same person who gets the regular shipments of service release CDs, all requested SAP Applications CD shipments, and is invariably always on holiday when you desperately need to get that CD for the installation. But I digress; you can find a copy of the letter at this link: Customer letter
Please note that there is also information in the customer letter about the de-support of 32 bit for new SAP installations! My colleague Matt Kangas has an informative and entertaining weblog on that topic… you can access this Will You Still Love Me When I'm 64?. 64 bit processing is a real asset for delivering Unicode solutions.

2. This change only really effects NEW installations of SAP NetWeaver and SAP applications based on SAP NetWeaver that were previously available with non-Unicode installation options (e.g. mySAP xxx business suite applications, SAP xApps, and the BI and (ABAP) AS capabilities of SAP NetWeaver). Remember only the ABAP stack supported single code pages in the past - J2EE is only Unicode.

3. Existing installations of SAP NetWeaver and SAP applications based on SAP NetWeaver that were based on single code pages can be upgraded to the new releases WITHOUT having to convert to Unicode. This is really cool as it protects your existing investments and you can live in the non Unicode world for a little longer. Please do remember that MDMP will not be an option for mySAP ERP customers… this solution was de-supported as of the mySAP ERP 2005 release!

4. For those administrators worried about processes that require some of the installation tools (i.e. those much loved system copies that you are asked to do much too often!), SAP will still deliver tools to enable you to do this for single code page based system. I guess some administrators would prefer that we did not make the tools available. That way they could tell the business users to tidy up their own data and not rely on system copies to provide refreshes for them! :-)

5. For clarification - Unicode does not simultaneously translate from one spoken language to another (You’d be surprising how often this is asked!).
Another additional clarification - contrary to some popular beliefs Unicode is not the name of a small, yellow, leechlike fish that is probably the oddest thing in the Universe. That is another globalization solution from far away in future whose species was hijacked by a translation tool (I hope Mr. Adam’s estate is getting royalties!). Just in case there was some confusion or misplaced beliefs in this area, check out this Link for more information on the other globalization solution for your amusement.

6. Customers can convert to Unicode now assuming that they are on the minimum supported Unicode releases and do not have to wait for the delivery of all new releases of SAP NetWeaver and SAP applications based on SAP NetWeaver after 2007. SAP strongly recommends that customer's consider Unicode conversions in the short term as a per-active step and to potentially reduce the need for further resources and monetary costs further down the road as you systems grow.

So there you have it, a whirlwind tour of the upcoming changes for SAP NetWeaver and applications built on SAP NetWeaver from the end of 2006 onward.

“Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.” … So I hope the weblog was somewhat informative and good, otherwise you may have read it before I finished it…

All the best,
Mike.

We at SAP have had a lot of questions concerning the ongoing support of 'Multi Display, Multi Processing' (MDMP) for our future mySAP ERP releases. Hopefully I can clarify this question and provide you with information that enables you to plan your future mySAP ERP rollout and requirements for multiple languages.

 

Some background:

MDMP was the solution SAP developed for support of combinations of multiple code pages in one system prior to the availability of unicode database support. MDMP effectively enabled an SAP ERP system to be installed with a non-unicode database, and to support connections to the ERP application by users with language combinations not supported by a single code page.

Example: support of one ERP system with English, French, Japanese, and Chinese.

MDMP implementations implemented strict rules and restrictions(*) in order to ensure data consistency and avoid data corruption.

MDMP was only supported for SAP R/3, SAP R/3 Enterprise, and mySAP ERP applications. No other SAP applications or SAP NetWeaver components support MDMP.

Future of MDMP:

MDMP was a short term solution delivered to customers until unicode was released for SAP ERP applications. Once unicode was released, MDMP was not recommended to customers. Therefore SAP strongly recommends utilizing unicode versions of SAP ERP for multi-language solutions that require multiple codepages.

Note: Unicode is supported from SAP R/3 Enterprise onwards

For those ERP customers already running MDMP, SAP has clarified the ongoing support of MDMP in a letter to customers:

MDMP will no longer be fully supported from mySAP ERP 2005 onwards:

From mySAP ERP 2005 onwards SAP can only warrant for consistent data in installations with mixed languages (more than one code page) if the whole system is based on Unicode.

In cases where customers want to use MDMP from mySAP ERP 2005 onwards, SAP strongly recommends to involve an experienced SAP consultant, but SAP disclaims all responsibility for

Any damages or losses of (productive) data and Interruption of or restrictions for scenarios in mixed environments (E.g. Unicode <-> MDMP - systems)

Unless such damages are attributable to SAP&#146;s willful misconduct or gross negligence.

 

Conversion from MDMP to Unicode:

SAP provides migration tools and services to support the conversion of non-unicode and MDMP systems to unicode. For more information please consult the unicode home page on the SAP Service Marketplace.

Further information:

For more information please consult the following info sources:

SAP Unicode home page:    http://service.sap.com/unicode

>SAP note: 741821

*- Since the potential risks are extremely complex depending on a given scenario, interfaces and data exchange, a general list covering ALL potential possibilities of data corruption is not feasible to cover.

 

 

 

May 2006: Update on globalization support:


SAP has announced that as of 2007, there will no longer be shipments of non-unicode installation kits for new releases of applications that run on SAP NetWeaver or SAP NetWeaver itself. More information can be found in this Single code page SAP systems heading towards history - Unicode Only Future! (Single code page SAP systems heading towards history - Unicode Only Future!)

 

 

 

I hope you find this useful

All the best,

Mike