SAP Unicode White Paper

Roadmap to Unicode Conversion

Click To Download White Paper

Navigation

Poll

What are your plans for migration to Unicode for your SAP system?
Defer to and combine with the next SAP upgrade
0%
Defer to and combine with a hardware upgrade
33%
Defer until a business need for the JAVA stack forces the issue
0%
Defer as long as possible
0%
As soon as we can
67%
Total votes: 3

Who's online

There are currently 0 users and 1 guest online.
SAP Unicode

Realistically, what is your risk if you defer converting to Unicode?

If you read the Case for Unicode, you realize that you face a risk of data loss or corruption based on numerous warnings if you remain in a non-Unicode SAP environment. So what is your real risk? Click to read more.

Layering of risk

Short of an exhaustive data analysis in your current environment, it would be virtually impossible to quantify the risk. The only way for you to make the call as to your organization's exposure to potential data loss/corruption, is to analyze how many factors that are known risk contributors are present in your landscape, and then developing it into a risk profile.

Risk Components

Review the following risk components as to whether they are present in your landscape, and map it to the illustrative graph. If there is more than one system of the same component group, increment the component count.

  • JAVA components (eg. SAP Portal, Mobile Infrastructure etc...). SAP note 975768
  • MS-Office Integration (eg. MS Excel updates to SAP, BEX, etc...)
  • HTTP/HTML (eg. Portals, CRM etc...)
  • SOA - Service Oriented Architecture. SAP note 1358929
  • Technology differences (eg. interfaces from mainframes, unix, windows etc...)
  • Asian languages
  • XI/PI

       Non-Unicode Risk Model

The above is not intended to be quantitative, but is provided merely to be used as a guide to assist in providing perspective for your environment.