BI Unicode Conversion impact on Microsft office tools

Hello Friends,
The BI version is BI 7.0, but we are using both Bex 3.x and Bex 7.0.BI 7.0 is being Unicode converted.
Questions
Does Unicode conversion have any impact on running the new/existing reports in 3.x and 7.x
Does Unicode conversion have any impact on running the new/existing WAD reports.
Does Unicode conversion have any impact on any of the Microsoft office products used by BI.
Thanks!

Since Excel is the starting point for BEx Analyzer, Excel 2007 would need to be tested. In BEx Web, if you have Excel as a save as option for queries, you will need to test that too. It also requires that the .NET Framework 3.0 be on the end user machine.
See [OSS Note 1013201|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1013201]

Similar Messages

  • UNICODE conversion of Siebel Database- Impact on interface

    Hi All,
    This is regarding the impacts on Interfaces after Siebel database UNICODE conversion.
    We are planning to do a UNICODE conversion of the Siebel database.In the current landscape we have Siebel interacting with multiple application which are non UNICODE.
    Majority of the interfaces(outbound/inbound) are batch interfaces which either use file or PL/SQL + EIM for the data transfer.
    We have the following queries about the impact on the Interfaces post conversion
    1) the Interfaces which are outbound from siebel to non -unicode database what will be impact on these interface.
    2) For the above mentioned interfaces do we need to do some conversion of data before it gets loaded to non unicode database.
    3) for the inbound interfaces will the siebel unicode data base will allow the data which is flowing from non unicode database.
    Could you please guide me with your experiences which will help us in planning this conversion.
    Do let us know if there must to consider points for Siebel database unicode conversions
    Thanks,
    Ashutosh

    Ashutosh,
    Did you already start on the Unicode conversion?
    We contacted Oracle, but so far they only said we need to go through a workshop where we can estimate the impact on the interfaces.
    Since we need to do a cost/benefit analyses before we decide to do this, it's hard to do so when you don't know the impact on the interfaces.
    In our case we use EIM, Web Services, MSMQ (XML) and flat files.
    Anyone with experience with a conversion to Unicode and impact on interfaces?
    Ji Yong

  • Unicode conversion & SAP Office functionality.

    Hi All,
    We are in a process of combined upgrade & Unicode coversion. Our source release is 4.6C and we are going for "SAP NetWeaver 7.0 Application Server ABAP including SAP Enhancement Package 01 ". As per CU&UC guide in "Component-specific Requirements" there is SAP office related requirement.
    I have gone through sap note 691407, 690074 and I understand that from the release 4.6C SAP will not loger enhance it as some of the components are not unicode enable.
    I query is
    1) How to find out whether we are productively using SAP offce in our system and which of these components wil not be available after unicode conversion.
    2) What exactly will happen after unicode conversion to these fuctionalities.
    Please reply.
    Regards

    Hi Nikhil,
    I do not think you will find a detailed list of functionality which works.
    As far as I remember, the 'deprecation status' of sophisticated SAP Office functions (e.g. SAPMAPI) is more than 8 years old ...
    Therefore I do not see another option than testing your scenarios and find out which functionality still works (this might be also caused by the upgrade, not only Unicode).
    Best regards,
    Nils Buerckel
    SAP AG

  • Print Servers Impact after unicode conversion

    Hi
    We are performing an CUUC from 4.6C to ECC 6.0
    Our customer has around 4-5 windows special print servers which are used for chinese, japanese, korean printing..etc.
    After the upgrade & unicode conversion
    - Do we still need to use all these 4-5 special print servers for each languages seperatly? or
    - We shall consolidate all these print servers into one print server? Or
    - We don't need to have any print servers, all the print queues can be pointed to unix print queues and then to the printers directly.
    Kindly advise
    Thanks & Regards
    Senthil

    I would think you could consolidate the print servers, but you still need the separate printers/device types in SAP. We use a single print server for EN/DE/ZH but have different SAP printers (usinging different device types) for EN/DE & ZH printers.

  • Combined Upgrade and Unicode conversion of Sap 4.6C to ECC6.0

    Hello all,
    my project team intends to carry out a combined upgrade and unicode conversion of an SAP ERP 4.6C system with MDMP to ECC6.0 (no enhancement package). The system is running on Oracle 10.2.
    In preparation for this upgrade, I have gone through the SAP notes 928729, 54801.
    We need to get a rough estimate of the entire downtime so as to alert our end users. From the CU&UC documentation in 928729, I read up note 857081. However the program in this note cannot be used to estimate the downtime as my system is < SAP netweaver 6.20.
    Is there any other SAP note or tool or program that I can use to estimate the downtime for the entire CU&UC? Thanks a lot!

    Hi,
    Combined upgrade depend upon number of factors like database size, resources on the server and optimization. In order to get idea of how much downtime, it will take, I would suggest you to do combined upgrade and unicode conversion on sandbox system which should be the replica of your production system. And try to optimize it. From there you can get approx. downtime required.
    Also, please read combined upgrade and unicode conversion guides on  http://service.sap.com/unicode@sap
    Thanks
    Sunny

  • Unicode conversion in situ

    Hi SCN,
    I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
    However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
    What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
    This seems logically problematic as you need a target system to import to.
    I can imagine a process along these lines though...:
    1. Take SAP layer offline
    2. Run full backup of system
    3. Export system
    4. Drop database* (to make clean ready for new import)
    5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
    6. ....and continue to run import into that database
    7. Complete Unicode conversion process
    However the big issue here for me is
    (a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
    (b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
    Any input/discussion on these points would be very welcome.
    Regards, doonan_79

    FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
    Allowing for parallel export/import, but going back to the original configured host to complete the process.

  • How to go for Unicode conversion?

    Hi All,
    Presently i'm upgrading my SAP 4.7 system (6.2 WAS) in to ERP 2004 (6.40 WAS), which is an non-unicode upgrade.
    Now should i first complete Unicode conversion or apply the latest SP stack.
    Also please tell me how this Support pack will affect me in Unicode conversion?
    Order of this steps will be really helpful for smooth flow of work
    Thanks in Advance

    If you have already completed your upgrade, the best practice would be to install the SP stack first in order to have the latest updates available for the unicode migration tools.  Then proceed with the unicode migration.  There are slight differences in the process between support packages where you may have to create a migration program manually in an older support package and the very same migration program is included in the later support package.  SAP publishes separate unicode migration guides, based on the support package level, due to these updates.

  • Error with PS text after Unicode conversion

    Hi, we are having problem after doing unicode conversion with special
    character not displayed correctly in a Web interface. In SAP
    (transaction CN04) everything is OK, but if the PS text is displayed
    through a Web interface (BSP for instance) some characters are
    displayed wrong. One of these characters is the apostrophe in French
    language ('). Is there an available tool to perform a conversion of
    existing PS text after performing unicode upgrade ?

    Hima ... try this
    http://<server>/Lighthammer/JCOProxy?Mode=Reset

  • Unicode Conversion

    Hi ,
           We are into the initial phase of upgradation from 4.6 to ECC6 .
    ineed  some of the questions below ...
    1.    what is mean by unicode conversion ?
    2.    in an object example reoprt or script or bdc or module pool objects what are      need to be done to convert it as ab unicode object ?
    3.    next is after working on the unicode object we need to work on the spoue objects .what is mean by that ?
    could you guys can clear my dought for the above mentioned question ?
    thanks,
    vinay

    plz go through the following links.....
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5546db3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55470b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55473b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55476b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5547cb3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5547fb3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55482b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55485b3dc11d5993800508b6b8b11/content.htm
    The Link will be helpful to you.
    Re: Upgrade 4.6 to ECC - What are the responsibilites
    regarding Unicode influence in Standard programs
    Very good document:
    http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
    You need to use the transaction UCCHECK.
    The report documentation is here
    ABAP Unicode Scan Tool UCCHECK
    You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
    Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
    Selection of Objects:
    The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
    PROG Report
    CLAS Class
    FUGR Function groups
    FUGX Function group (with customer include, customer area)
    FUGS Function group (with customer include, SAP area)
    LDBA Logical Database
    CNTX Context
    TYPE Type pool
    INTF Interface
    Only Examine Programs with Non-Activated Unicode Flag
    By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
    Only Objects with TADIR Entry
    By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
    Exclude Packages $*
    By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
    Display Modified SAP Programs Also
    By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
    Maximum Number of Programs:
    To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
    Call transaction SAMT
    Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
    For further information refer to documentation for transaction SAMT.
    Displaying Points that Cannot Be Analyzed Statically
    If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
    To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
    Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
    Applikation-Specific Checks
    These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
    View Maintenance
    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
    UPLOAD/DOWNLOAD
    The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
    Plzz Reward if it is useful

  • Performance during Unicode Conversion

    Hello,
    currently we are planning to do a Unicode Conversion on a Linux/MaxDB System.
    The DB has a size of approx. 350 GB. The system runs on Fujitsu-Siemens FlexFrame hardware.
    One problem is that during a test conversion the export of the DB took more than 24 hours.
    This seems too much regarding the DB size.
    We know that filesystem and RAM and CPUs influence the export duration.
    What possibilities do we have to tune the export with "software" tools?
    - table splitting
    For example: Our largest table has ~26GB datasize.
    How do we split this table?
    In 10 parts or in 20 or in 200?
    If you could please post your experiences.
    Regards, Michael

    I don´t wanna discourage you but I´m not sure if splitting that single table will help alot.
    The problem with this combination is the fact, that the MaxDB database reads data block-by-block, means, exeucting single I/Os for each block to read. Given that fact and the fact, that each I/O will be ran over an NFS (with the known latency) it´s unlikely that you will get much more speed out of this.
    The problem is NOT the speed between the NAS and the database server, if you will look on the network traffic you will see, that there´s plenty left. The problem is the latency on the client side (the database server) when you put your files on NFS.
    I can export a 250 GB database in under 3 hours (admittedly - without UC conversion) using a direct fibrechannel connection (so non-NFS) so the database itself is certainly not the problem, it´s the combination of the usage of NFS (no matter if v2 or v3) and the way the MaxDB database reads data.
    I´ve been involved in a likewise project and with a NetApp specialist and some in-depth tuning we were able to gain 15 - 20 % speed but not more.
    Markus

  • Error during Unicode Conversion at DDNTF table

    Hello
    We are doing a Unicode Conversion for our CRT systems. This system now
    is a SAP CRM 7.0 SR1 ABAP.
    We have performed preparatory steps (SPUMG, checks, updating R3load,
    R3ldctl, R3szchk, dboralib, ...),
    but when we start Import process we get an error in SAPSDIC package.
    The error looks like:
    *************************+
    (RTF) ########## WARNING ###########
    Without ORDER BY PRIMARY KEY the exported data may be unusable
    for some databases
    (EXP) INFO: table DDNTF will be exported with sorting
    (RSCP) ERROR: 'DDNTF' in UMGCCTL: Guess has illegal value.
    (RSCP) WARN: DDNTF: Missing in UMGSTAT,
    ERROR in nametab conversion
    conversion of nametab table 'DDNTF ':
    rscpMCStartTab: rc = 128
    (CNV) ERROR: data conversion failed. rc = 2
    (DB) INFO: disconnected from DB
    /usr/sap/CRT/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/CRT/SYS/exe/run/R3load: END OF LOG: 20091229193651
    Any idea??
    Thanks in advance
    Regards

    Yes I executed this Report using Menu Tool Bar.
    The first execution gave me some errors regarding some tables existing at database level but  not in DDIC. We ignored this errrors because those tables are not important.
    But the last try, we decided solve this inconsistencies deleteting those tables at database level, repeting report RADUCNT (in this case no errors appeared) and repeting the export with the same error..
    Now, we have seen in Tabscript STATUS of SPUMG there are some errors regarding DDNTF inconsistency found at table control. Reason 4.  But this reason means that faillback codepage missing at table control for this table. But as far I know, I can't fill failbak field for this kind of table...
    So know I'm reseting SPUMG, and reestarting again..
    But I don't understand what is the problem
    In a few minutes I will you inform about results
    Meanwhile is anybody have any suggestion or idea... please let me know
    Thanks!

  • MDMP unicode conversion - Vocabulary maintenace

    Hello,
              W have upgraded 4.5B MDMP system to ECC4 EHP4 and now we are in process of unicode conversion.
    please advice on as specified below.
    In SPUMG Scan process, we have completed the following scans:
    a) Tables without language Info
    b) Tables with Ambiguous language Info
    c) Indx Analysis
    For maintaining vocabulary  we have implemented notes 756534 &  756535, 871541. and Tables with language are also scanned. While handling vocabulary the system has displays 539158 with duplicates and 189314 when duplicates are discarded, which doesnot assigened any languages. We have 9 acive languages.
    As per Unicode conversion document i left out with only 2 more option a) HInt management b) Manual assignment
    How to handle this? is this a normal situation or any correction can be done?
    Thanks and Regards
    Vinay

    Hi Vinay,
    This Thread belongs to the Unicode forum:
    Internationalization and Unicode
    In my opinion one of the best and most efficient possibility to reduce the number of words
    is to make use of hints. Please follow the  Unicode Conversion Guide and SAP note 1034188.
    Application colleagues should be contacted in order to find proper hints.
    Please also note that report umg_vocabulary_statistic or um4_vocabulary_statistic is the best tool to evaluate tables for hint processing.
    And the rest of the vocab, which can not be assigned by the hints method or by the SAP notes you mentioned, need to be assigned by native speakers (manual effort !).
    As you can see, SPUMG is NOT just a tool to be executed by Basis staff.
    It needs in deed collaboration between Basis, Application and native speakers.
    And it should be clear that the duration of the scans can be quite high - therefore a trial & error approach will take time (especially for large systems).
    Best regards,
    Nils Buerckel
    SAP AG

  • Please guide me on unicode conversion

    Hi All,
    Presently we are having 4.7ee,oracle and win 2003 and aix..
    Our client is planning for unicode conversion...Please help me in preparing for unicode conversion..In the form of guids...screen shots...in and out of the unicode conversion process....
    Thanks in Advance,
    Kasperr.

    Some useful links -
    Making ABAP Programs Unicode Enabled
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30781270-bc11-2a10-2a8d-f890e25e87ca
    Translation Tools for Translators
    http://help.sap.com/saphelp_nw04/helpdata/en/77/5719d2492011d1894a0000e829fbbd/frameset.htm
    Code Pages
    http://help.sap.com/abapdocu/en/ABENCODEPAGE_GLOSRY.htm
    http://help.sap.com/abapdocu/en/ABAPSET_LOCALE.htm
    Hope you benefit from it!
    Cheers,
    Varna

  • Unicode conversion  after upgrade

    I am well aware that sap recommends to convert  to unicode first before converting to 2004s. however  does anyone know what any consiequences would be of waiting to do it until after ther upgrade. Our landscape is very simple, we do not plan to immediately integrate new tools, and we don't have the abundance of code pages someone here mentioned (nor do we use foreign currencies). so with that said, are there any known consequences to simply doing the unicode conversion  after upgrading from 3 to BI7?

    > Let's take the system user table for example:
    > (USER, NAME , SURNAME, ADDRESS).
    >
    > USER1 | שלום | עליכם | יקרים |
    > USER2 | %%$% | אלי | #$$%#$ |
    > USER3| #$%#$% | $##%$#%| $#%#$$%%#
    I would say that those entries were not correctly specified in your vocabulary as being Hebrew - OR
    Addresses have another speciality, they have a "creation language" field (LANGU_CREA). That field may be wrong filled if you e. g. create the user with an english logon and then change the user data to Hebrew (with Hebrew characters). The entry in the LANGU_CREA field however stays english. If you use that field now to decide the conversion of the addresse it will be converted wrong and you see gibberish.
    Markus

  • UNICODE CONVERSION urgent

    Hi friends,
    can any one send the commom errors in unicode conversion project?

    Hi ,
    Hope it will help you,
    The Link will be helpful to you.
    Re: Upgrade 4.6 to ECC - What are the responsibilites
    regarding Unicode influence in Standard programs
    Very good document:
    http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
    You need to use the transaction UCCHECK.
    The report documentation is here
    ABAP Unicode Scan Tool UCCHECK
    You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
    Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
    Selection of Objects:
    The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
    PROG Report
    CLAS Class
    FUGR Function groups
    FUGX Function group (with customer include, customer area)
    FUGS Function group (with customer include, SAP area)
    LDBA Logical Database
    CNTX Context
    TYPE Type pool
    INTF Interface
    Only Examine Programs with Non-Activated Unicode Flag
    By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
    Only Objects with TADIR Entry
    By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
    Exclude Packages $*
    By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
    Display Modified SAP Programs Also
    By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
    Maximum Number of Programs:
    To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
    Call transaction SAMT
    Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
    For further information refer to documentation for transaction SAMT.
    Displaying Points that Cannot Be Analyzed Statically
    If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
    To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
    Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
    Applikation-Specific Checks
    These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
    View Maintenance
    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
    UPLOAD/DOWNLOAD
    The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
    Thanks
    Jagadeesh.G

Maybe you are looking for