Non-Unicode Support Post NetWeaver 2004s

Hi everyone,
Our site runs an existing non-unicode environment, and are aware that we can definetly upgrade our existing environments to NetWeaver 2004s (Basis 7.0).
However will SAP provide future upgrade kits for later releases of SAP (eg Basis 8.x and higher) for non-unicode environments.
Cheers
Shaun

Thanks Matt and Eddy for your replies.
I had already read the "blog" Matt, and Eddy I have spent a heap of time in the service market place reading everything thats available on unicode including oss notes.
However here is a snippit from the blog the Matt directed me too:
========================================================
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.
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 <b>little longer</b>.
========================================================
Note on "3." that is says at the end there "for a little longer". ... how long? too what release?
From what I have read so far it sounds like anything above NetWeaver Application Server 7.0 will require a unicode conversion.
Any comments??
Ideally I would like someone to just give me a yes/no answer.
Cheers
Shaun

Similar Messages

Problem publishing database contents from non-unicode to unicode system

Hello everyone!
We just set up a new SAP WAS based on Netweaver 2004 as a unicode system. Out problem now is that we have a content management system on our non-unicode system and that we are publishing the contents via rfc to the WAS unicode system to display the contents online. the contents are stored in our own database tables.
The problem thereby is that many texts pasted from microsoft word contain special characters like bullets, long minus or low-9 quotation marks which are not correctly displayed in the unicode system / on the website. we already found out that it has something to do with the codepage. the sap notes say we should use 1160 instead of 1100 and that the transaction SPUMG would be helpful. but we are not able to select any tables there.
so now we do not know what to do exactly. do we have to change something in our non-unicode system or do we have to conversion in our unicode system. and what happends if content containing special microsoft word characters is published after the spumg conversion? do we have to to this frequently?
We would be glad if anyone could help.
Thanks a lot!

Hi Martin,
thanks for your quick answer.
You got me right. We have a local non-Unicode SAP HCM Netweaver 2004 system running a self-developed web based content management system / wiki. The texts entered in the bsp application are stored in a string field in our database table. Actually we publish the contents to a WAS 6.20 non-Unicode system with the same database tables to provide the content via BSP for the public. Everything is working fine including the special characters.
Now we want to replace the WAS 6.20 non-Unicode system by a new WAS 7.0/2004 Unicode system. But when publishing the contents via the same RFC function module to the new system the special characters seem to be damaged. We are not able to replace them with abap commands and when they are displayed on the website we only see "boxes".
If I get you right we have to run SPUMG on our nw 2004 non-unicode productive hcm system, right? but isn't there a danger to damage existing contents?
Best regards,
Stefan

Unicode Conversion necessary before 2004s upgrade??

Hello,
Can anyone tell me if it is necessary to do an Unicode Conversion first before upgrading a BW system to BW 2004s?
The Portal we are going to use is unicode enabled.
So this raises the question: "Do we need an Unicode Conversion first?".
Regards,
Jos

Hello,
It's not necessary to do a unicode conversion for NW 2004s BI. We still support non-unicode systems for NW 2004s BI. This link explains the pro's and con's of staying on non-unicode for SAP NetWeaver BI.
http://service.sap.com/~sapidb/011000358700006750052002E
Regards,
Bryan

Printing of views without Netweaver 2004s (Solution 2)

Hallo,
after writing my post concerning a printing solution before NetWeaver2004s (Solution 1),
i will also share my knowledge concerning my own printing solution developed inside Web Dynpro.
The following example should only demonstrate how an implementation of a print renderer can be done
inside Web Dynpro while you can take influence of the generated output.
I had to develop the possibility of printing some views including some head infos and table data.
The application is localized into six languages.
First i had a look at Adobe Document Services, but it is quite uncomfortable using table output
(it seems to be better supported in NetWeaver 2004s), but the problems resists in the localized labels.
You have to implement each lable also as an computed attribute to use it inside Adobe or
you have to copy the template for each language and translate it beside the xlf files.
I needed a solution that does not generate additional needs to print views.
So i decided to write an own PrintRendererClass using the Runtime view and the mapped context.
The following szenario should only demonstrate how you can archieve such a solution.
The Solution needs two Context attributes:
<b>ViewPrinter</b> (holds the reference to the renderer class)
<b>ViewPrinterURL</b> (String that receives an URL handle for using inside a LinkToURL control)
The instantiation of the class takes place inside the wdDoModifyView:
public static void wdDoModifyView(IPrivateDetailsView wdThis, IPrivateDetailsView.IContextNode wdContext,
     com.sap.tc.webdynpro.progmodel.api.IWDView view, boolean firstTime) {
//@@begin wdDoModifyView
if (firstTime) {
     ViewPrinter vprt = wdContext.currentContextElement().getViewPrinter();
     vprt = new ViewPrinter(view, wdContext, WDClientUser.getLoggedInClientUser().getLocale());
     vprt.setTitle(vprt.getTextById("Headline"));
     vprt.addGroup("GroupCustomerorder");
     vprt.addTable("TablePositions");
     wdContext.currentContextElement().setViewPrinterURL(vprt.render());
//@@end
The RendererClass is only a framework for a big StringBuffer (xml) that uses methods to add
addtional output content to the string and finally generates a dynamic xhtml file.
The URL handle is returned at the end via vprt.render() and stored in the context attribute.
Inside the view you can use a LinkToURL control mapped to this context attribute,
which opens a new window with the generated xhtml file.
The most interessting parts are addGroup(uielementid) and addTable(uielementid).
The addGroup searches for a uielement with the given id and iterates through all entries.
For all found labels and their binded values output code will be added:
public void addGroup(String id) {
     // open group
     xml.append("<fieldset>");
     IWDGroup group = (IWDGroup) view.getElement(id);
     // get group header text
     String legend = group.getHeader().getText();
     xml.append("<legend>" + legend + "</legend>");
     // trace all elements
     for (Iterator iter = group.iterateChildren(); iter.hasNext();) {
          IWDUIElement uiEl = (IWDUIElement) iter.next();
          if (uiEl instanceof IWDLabel) {
               xml.append("<div>");
               this.addLabelWithValue(uiEl.getId());
               xml.append("</div>");
     // close group
     xml.append("</fieldset>");
For each found label the label and binded text should be printed out:
public void addLabelWithValue(String id) {
     // find given label (with value)
     IWDLabel lbl = (IWDLabel) view.getElement(id);
     if (lbl!=null) {
          xml.append("<label for="" + lbl.getLabelFor() + "">" +
               encodeHTML(lbl.getText(),true) + ": </label>");
          // find corresponding value
          IWDTextView txt = (IWDTextView) view.getElement(lbl.getLabelFor());
          if (txt!=null) {
               xml.append("<span id="" + lbl.getLabelFor() + "">" +
                    encodeHTML(txt.getText(),true) + "</span>");
The most interesting part is the generic output of a table:
public void addTable(String id) {
     // find given table
     IWDTable table = (IWDTable) view.getElement(id);
     String tableBindedDataSource = table.bindingOfDataSource(); // node "Positions"
     xml.append("<fieldset>")
          .append("<legend>" + table.getHeader().getText() + "</legend>");
     xml.append("<table summary="")
          .append(table.getHeader().getText())
          .append("">");
     xml.append("<thead><tr>");
     // use iterator
     ArrayList cellAlign = new ArrayList();
     ArrayList cellId = new ArrayList();
     int nrUsedColumns = 0;
     for (Iterator iter = table.iterateColumns(); iter.hasNext();) {
          IWDTableColumn col = (IWDTableColumn) iter.next();
          // check column id against blacklist
          if (!blackList.contains(col.getId())) {
               IWDTableCellEditor cellEditor = col.getTableCellEditor();
               // casting for supported uiwidgets
               String bindedColumnText = null;
               if (cellEditor instanceof IWDTextView) {
                    IWDTextView txt = (IWDTextView) cellEditor;
                    bindedColumnText = txt.bindingOfText(); // "TABLE.ATTRIBUTE"
               // add supported widgets to print
               if (bindedColumnText != null) {
                    // remove leading TABLE prefix (use only ATTRIBUTE)
                    String textId = bindedColumnText.substring(bindedColumnText.lastIndexOf('.')+1);
                    // get column alignment
                    String colAlign = col.getHAlign().toString().toLowerCase();
                    String classAlign = (colAlign.equalsIgnoreCase("auto"))
                         ? "" : " class="" + colAlign + """;
                    xml.append("<th" + classAlign + " scope="col" abbr="" + col.getHeader().getText() + "">")
                         .append(col.getHeader().getText())
                         .append("</th>");
                    // make column values for table body available
                    cellAlign.add(nrUsedColumns, colAlign);
                    cellId.add(nrUsedColumns, textId);
                    nrUsedColumns++;
     xml.append("</tr></thead>");
     // print out table body
     xml.append("<tbody>");
     // table corresponding context node
     IWDNode node = ((IWDNode)wdContext).getContext().getRootNode().
          getCurrentElement().node().getChildNode(tableBindedDataSource, 0);
     int tableSize = node.size();
     IWDNodeElement nodeEl = null;
     for (int i = 0; i < tableSize; i++) {
          xml.append("<tr>");
          nodeEl = node.getElementAt(i);
          for (int col = 0; col < nrUsedColumns; col++) {
               Object value = nodeEl.getAttributeValue(cellId.get(col).toString());
               String classAlign = (cellAlign.get(col).toString().equalsIgnoreCase("auto"))
                    ? "" : " class="" + cellAlign.get(col).toString() + """;
               xml.append("<td" + classAlign + ">"
                    + encodeHTML(this.getAttributeValue(value), true) + "</td>");
          xml.append("</tr>");
     xml.append("</tbody>");
     xml.append("</table>");
     xml.append("</fieldset>");
[code]
First we inspect all table columns to get the head labels and the used cell editors.
There is also support for a black list to allow skipping of columns that should not be printed.
Invisible columns are also printed, so you can add addtional table columns for printing that are
disabled for the browser. Also the alignment of the cell editor will be supported.
A second loop iterates over the table context depending the used columns.
To get the formatted values concerning their datatype i use the method getAttributeValue,
cause i think the formatting of mapped Context to the browser takes place in the deepest parts
of the Web Dynpro Renderer Task and is not accessible via API.
Therefore you have to implement formatters for all supported datatypes:
[code]
private String getAttributeValue(Object obj) {
     String txt = "";
     if (obj != null) {
          // String handling
          if (obj instanceof java.lang.String) {
               txt = obj.toString();
          // Date handling
          } else if (obj instanceof java.sql.Date) {
               DateFormat formater = DateFormat.getDateInstance(
                    DateFormat.SHORT, this.locale);
               txt = formater.format(obj);
          // BigDecimal handling
          } else if (obj instanceof java.math.BigDecimal) {
               DecimalFormat df =
                    (DecimalFormat)DecimalFormat.getInstance(this.locale);
               df.applyPattern( "0.######" );
               txt = df.format(obj);
          // Default Handling -> with debug output of Class Name
          } else {
               txt = "<span class="pointer red" title="" + obj.getClass().getName() +
                    "">" + obj.toString() + "</span>";
     return txt;
Here is the reason, why the class constructor needs a locale!
I try to format the output concerning the portal user language.
At the end you have to call the vprt.render() method to start creation of a new html ressource.
The method returns the ressource url as a string which is binded to a LinkToUrl control.
That's it.
The above solution only fullfills my needs concerning the project. I implemented only the
needed methods to print out groups and tables.
The table renderer skips all table columns that are not IWDTextView.
if you need addtional things like IWDProgressBar, you have to implement such a kind of renderer.
The solution is a nice way to generate printable content of views with the following benefits
Pro:
- Print out is Locale/Language dependend (Text, Date, ...)
- You can influence the print design via css
- You can implement your own controll renderer (like decorators)
- It works for SAP Net Weaver releases <= 2004s
Cons:
- To support all widgets, you have to implement them
(controls/widgets are growing with new service packs)
The functionallity shows how you can use the abstract api for iterating
through view elements and their mapped context in a generic way.
The solution is a plain structured class because i do not want to reimplement
the whole Widgets API for printing a view (not in the scope/budget of our customers).
If you are interessted in the working class file, please contact me.
Maybe this helps someone who has to do similarly things inside Web Dynpro
and does not want to reinvent the wheel.
Best wishes,
Holger Schaefer

Hi Holger,
This Solution helped me a lot. Thanks a lot.
Sreekanth

Webdynpro Application is not Deploying into Netweaver 2004s From NWDS CE

Hi,
I Developed Webdynpro Application in NWDS CE 7.1 SP5.
I Am using Netweaver 2004s AS JAVA .
After Deploying application i will get page can not be displayed and in the browser url is following below
http://localhost:-1/webdynpro/dispatcher/demo.sap.com/firstapp/FirstApp?SAPtestId=2
my actual port is 50000 but it gives -1.
and also i need one clarification NWDS CE 7.1 Applications Supports the Netweaver 2004s or
it requires Netweaver CE 7.1 AS JAVA.
We have to develop applications using webdynpro,mobile perspectives in NWDS CE 7.1 SP5
Is it Supports Netweaver 2004s.
Thanks
Subbarao

Hi
NetWeaver CE 7.1 uses Java 5 and so does the NWDS CE 7.1 by default. The server you have is NW 2004s SP 9 which runs on Java 1.4. So you simply can not build with Java 5 and deploy it to a server with JRE 1.4, you will get a class unsupported version error.
Next you are using NWDS CE 7.1 to connect to server 2004s. The architecture of the Java servers in SAP is changed. 2004s has SDM and dispatcher and a server process at its simplest form. In CE theres an ICM and server. (SDM & Dispatcher combined). You no more give the message port number when you set up the JEE server of NWDS 7.1 instead you would use instance number. When you register a NW 2004s server with NWDS 7.1 (instance numbers are available for 7.0 servers as well), the studio fails to find the deploy mechanism (SDM or ICM) hence you see a port -1.
Lastly the architecture of WebDynpro is greatly changed from NW 7.0 to NW 7.1 so dont even think of deployment to previous versions.
Regards
LNV

Can Unicode system have Non Unicode Database

i have installed Nw2004 Unicode .
But if i install NW2004 unicode the database is also unicode or not

Hi,
Unicode and non unicode depends on how many bytes are reserved at database
if itis 1byte it is non unicode supports only english and germany
2 bytes it is non-unicode
so the DB is created with an Unicode Characterset once you install sap as unicode system
Samrat

MAM 2.5 on NetWeaver 2004s

Can you please advise if MI Mobile Asset Management(MAM) 2.5 is supported on NetWeaver 2004s?
Thank you.

Hello,
Kindly see the 'Software Restrictions' section in the SAP note 945240. This note is the release restriction note for SAP Mobile Asset Management 2.5 SR4.
Regards,
Dilip

Unicode affected objects in BI NetWeaver 2004s

Hi All,
We are planning for a parallel upgrade and Unicode from BW 3.1c to BI NetWeaver 2004s.
How can we obtain the list of BW Objects that would be affected by Unicode. Is there any general t-code to get this list...
From BW point of view, what do we need to check while moving from a Non Unicode to Unicode system?
Thanks and Regards,
Vidhya.A

Hi Aravindaksshan,
The T-code UCCHECK, gives the details of Program thats affected by Unicode... but i want to know the list of BW Objects (Like Info Objects, Cube etc...) that are affected by Unicode...
Is there any Transaction to get this list...
Regards,
Vidhya

Post-process after the upgrade to non-Unicode

Hello all,
I'm doing a CU&UC and just completed the first part - non-Unicode.
Since it will be followed immediately by a Unicode conversion, do you really need to do all the post-upgrade tasks? And if not, which are the mandatory part?
Thanks again,
Terry

You can take the CU&UC Guide..... after upgrade and before unicode it's mandatory to do some steps, aall about unicode preparation.....after do it you can do the export....
Has you begun this????.
Regards,
Alfredo.

How to import Support Package 13(SAPKW70013) for SAP NetWeaver 2004s BI

Hi,
How to import Support Package 13 for SAP NetWeaver 2004s BI (BI Patch 13 or SAPKW70013)
Note no for that is : 1019055.
Thanks in Adavance,
Dushyant.

Hi,
RTC for BI 7.0 SAP_BW SP 13 is scheduled in CW 21, that is coming week, after that you should be able to download it from service market place.
@others: Dont get confused about SPS release with SP release. BI has intermediate release which is SP release, SPS is SP-Stack release (which is NetWeaver release).
SP 12 correspond to SPS 12 which is sceduled CW 21.
Hope this helps.
Best Regards,
Rajani

Reg Support Package in BI 7 Netweaver 2004s

Hi all,
This week My Basis people are going to install BI 7(Netweaver 2004s) in the system.
May I now Initially upto which support package is good like SAPKW70012..........or 13 or 14.......
Thanks in advance....
Praveen.K

Hi,
Pls go for SP 13.
SP 13
[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPKW70013]
http://service.sap.com/sp-stacks
Hope this helps,
Regards
CSM Reddy

SAP Best Practice For Unicode Upgrades - NetWeaver 2004s

Team SAP,
I have a customer that is starting to plan for a Unicode upgrade. The question from the customer is as follows:
What is the SAP Best Practice for Unicode Upgrades? They will be upgrading from a BW 3.5 System to NetWeaver 2004s, and their question is ... should they:
a) Perform the Unicode Upgrade At The Same Time As Their BW 3.5 > NetWeaver 2004s Upgrade, or
b) Perform NetWeaver 2004s Upgrade first, and then at a later date, perform the Unicode Upgrade?
Thank you in advance for any guidance or counsel you may be able to offer.
-M

Hi Michael,
Check these links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee7407a0-0501-0010-81ae-e329029b1074
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7e259990-0201-0010-6085-e7c5aec5af1d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5411d290-0201-0010-b49b-a6145fb16d15
Bye
Dinesh

Choosing unicode and non-unicode option in SAP Netweaver Mobile 7.1

Hi folks,
do we have the option of choosing a unicode or non-unicode format on installing SAP Netweaver mobile 7.1?
Can we communicate MI unicode system with non-unicode backend?
Let me know on where i can find more info related to this
Regards,
Kalyan

Hi Ankur,
you can also directly navigate to the mobile administrator using the web browser. The url is as follows:
http://host:port/sap/bc/webdynpro/sap/sdoe_administration?sap-language=EN
Host and port you have to adjust to your settings. These are the same settings you are using during synchronization on a client device.
Regards,
Stefan

SAP Netweaver 2004s SR2 Post Installation Guide

Hi Guys,
Plz send me SAP Netweaver 2004s SR2 Post Installation Guide.....
Email ID :- <email address removed by moderator>
Thanks in advance.
Regards,
Suresh.K

Dear Suresh ,
You can download from https://websmp102.sap-ag.de/instguides OR https://websmp102.sap-ag.de/installnw70
OR Directly from :
https://websmp102.sap-ag.de/~sapidb/011000358700004073122006E
Regards ,
Santosh

Does this select stmnt is supported by non unicode system?

hi all,
does this select stmnt is supported by non unicode system?
SELECT * FROM DD02L INTO TABLE I_TABL
                        WHERE TABNAME IN S_TABL
                        AND   AS4LOCAL = 'A'.
this select stmnt is going for dump in 4.6.
pls help me....
regards,
sri sri.

Hi,
It's working fine in both (unicode and non-unicode) systems,
TABLES: dd02l.
SELECT-OPTIONS:
s_name FOR dd02l-tabname.
DATA:
w_tabl TYPE dd02l,
i_tabl LIKE TABLE OF w_tabl.
SELECT *
FROM dd02l
INTO TABLE i_tabl
WHERE tabname IN s_name
   AND as4local = 'A'.
LOOP AT i_tabl INTO w_tabl.
WRITE:/
    w_tabl-tabname,
    w_tabl-tabclass.
ENDLOOP.
Regards
Adil
Edited by: Syed Abdul Adil on Jun 18, 2008 12:39 PM

Non-Unicode Support Post NetWeaver 2004s

Similar Messages

Maybe you are looking for