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

Similar Messages

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]

Unicode conversion in sap query

i need to whether unicode conversion is possible in sap query

Hi again
The point 2 is still not clear for me..
1. Should I put in the source code (256 lines) of the function module here, or should I just put in a reference to the Function module like:
FM convert_to_local_currency;
2. Where should I put in the import variables you refer to?
3. When I push "single test" of the Function module I get these import parameters:
CLIENT                          210
DATE
FOREIGN_AMOUNT
FOREIGN_CURRENCY
LOCAL_CURRENCY
RATE                            0
TYPE_OF_RATE                    M
READ_TCURR                      X
Is this the import parameters you are reffering to?
Best regards
Ellen

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

SAP Data File size considerably reduced after Unicode Conversion

Hello Experts
I have just performed a CUUC (Upgrade along with unicode conversion) from R/3 4.7 to ECC 6.0 EHP5. The data size that i earlier had was close to 463 GB (MSSQL MDF, LDF Files), after the data export to be converted to unicode the size was 45 GB (10% of actual data size, i feel this is normal after heterogeneous system copy), but after the import again the DATA file size is only 247 GB, is this normal ? or have i lost some data ? For ex, I tried checking tables like MSEG and the number of entries have reduced from 15,678,790 to 15,290,545.
Could you kindly let me know if there is a way to check from Basis perspective if i have not lost any data ? I have followed all the procedures as per SAP Standards.
Waiting for your quick reply.
Best Regards
Pritish

Hi Nicholas
Data is compressed during the new R3load procedure is understood, but why number of table entries have reduced is something which is still a question to me (in some cases increased as well) ? For example
                             Source          Target
STPO                  415,725          412,150
STKO                 126,710          126,141
PLAF                 74,671                   78,336
MDKP                 193,487          192,747
MDPB                 55,329                   63,557
Any suggestions or ideas ?
Best Regards
Pritish

Unicode Conversion for SAP BI

Hi
We are upgrading out SAP BW 3.1 system to SAP NW 7.0. We are also planning to do a Unicode conversion of the upgraded system.
Please let me know the following:
1. What extra tests we need to do for Unicode Conversion
2. If you have done a Unicode conversion, please share the errors that you have got after the conversion, and the possible solutions.
Best Regards,
Rajib

hi,
Please refer
SAP Note Number: 928729 : Combined Upgrade & Unicode Conversion (CU&UC)
https://wiki.sdn.sap.com/wiki/display/unicode/ChallengesinBIUnicodeconversion
Below is the link for R/3... but still will give you some insight.
/people/tikkana.akurati/blog/2009/02/27/combined-upgrade-and-unicode-conversion-cuuc-cutover-project-plan-execution
This will also help you understand more about unicode...
/docs/DOC-8284#section5 [original link is broken]
Hope this helps
Regards
Raj

Conversion of Remote Function module RFC_READ_TABLE from non unicode to uni

Hi,
Please can any one help me in the conversion of Remote function module RFC_READ_TABLE from non unicode to unicode.
please tell me procdure and syntax change.
Thanks in advance.
zubera

TABLE_ENTRIES_GET_VIA_RFC in unicode system
Data retrieved by JCO formatted incorrectly
Please give me reward points if it is useful...

SAP 4.7 Ext 110 Unicode Conversion

We are Currently on
SAP 4.7 EXT 110 on AIX 5.2 / Oracle 9.x
We are planning to Convert the Existing 4.7 System to Unicode. I'm aware that 4.7 is already in extended maintanence and it is recommended to Upgrade to ECC 6.0 Unicode. However the Business decision is to Convert the existing SAP 4.7 Ext 110 to Unicode.
a) What is the Approach for this?
b) Do I need an Complete Target hardware other than the Mock hardware. What i mean here is
                    whether I can use the existing hardware for DEV,QAS,PRD
                                                                      or
                     Purchase a New Hardware for DEV,QAS, PRD.
c) Please let me know if there are challenges in Converting SAP 4.7 Ext 110 system to Unicode. If yes please help me in understanding.

Dear Nils
If you can help me in understanding the Advantages & Disadvantages of Two sever method and Having a Parallel landscape for Unicode , would be helpful
Current Landscape : DEV,QAS,PRD
a) Two server method : SBX for Copy of PRD , SBU for Unicode conversion . No Parallel landscape
The Movement you convert your DEV to Unicode , DEV is Unicode and QA is non-Unicode and PRD as well.
Is there a risk here?
b) With a Parallel landscape NEWDEV,NEWQAS,NEWPRD
Can we use the NEWPRD for mock ?
a) Mock -NEWPRD can be used as SBX for Mock and NEWQA can used as SBU for Unicode conversion
b) DEV-> Copy DEV NEWPRD (SBX) and use NEWDEV as SBU for Unicode conversion
c) QAS-> Copy PRD to NewPRD(SBX) and Use NewQAS as SBU for Unicode conversion
d) Rehearsal Export from PRD and Import in NEW PRD with Unicode kernel
What is advantage and disadvantage/Risk in the above two approaches

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

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

Unicode Conversion Problems~

Dear Expert:
I tried to import SAP_BASIS 700_15 to Ecc6 after an upgrade ECC 6.0.
(The Unicode Conversion Guide told me to do some step but need to import the Basis package to 18)
but an error occured return code 8.
check the SAP note 822379 and it said:
SAPKB70011 - SAPKB70016
Symptom: After you import the Support Packages SAPKB70011, SAPKB70012, SAPKB70013, SAPKB70014, SAPKB70015, and SAPKB70016, syntax errors occur in the class CL_GUI_ALV_GRID because corrections from notes have been partially overwritten. This may cause important Basis functions (such as the background systems) to no longer work.
Solution: Before you import the specified Basis Support Packages, see the information in Note 1249184.
after I refer to the note and upload and implement the 1174095 as it said,and import the SAP_BASIS 700_15 again but the error still occured like below.
   R3TRFUGRSPOO was repaired in this system
   R3TRFUGRSPOO was repaired in this system
   R3TRCLASCL_GUI_ALV_GRID was repaired in this system
what should i do ?
Regards
Jack lee

Dear Expert:
after doing what you said.
a error occured as below:
Runtime Errors         SYNTAX_ERROR
Date and Time          03.09.2009 14:43:21
Short text
     Syntax error in program "SAPLKKBL ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLKKBL " in include "LKKBLF01
      " in
     line 238:
     "Activation ID "ALV_PRINT_PARAMS" is unknown."
thank you for your help~
Regards
Jack Lee

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

Create Text Files as Unicode in SAP 4.5

Hi Experts
Is there any way to generate generate/save text files in SAP 4.5?
Thanks

Hi There.
I would like to suggest,
In ECC 4.5, The function modules -
>
WS_UPLOAD and WS_DOWNLOAD are not obsolete as like in ECC 4.7 onwards, but you can use them. CL_GUI_FRONTEND_SERVICES is used in the recent versions.
But, In case for Unicode conversions, It is not possible in ECC 4.5.
As an alternative,
I suggest, you use the transfer from Internal table to Application Server using OPEN DATASET and CLOSE DATASET as described by Chandralekha.
I suggest, Use transaction code: CG3Y for transfer of file from application to presentation server.
For retrieving back from presentation server to Application server you can use------>
Transaction code -
> CG3Z.
Direct Text conversions are possible, just select from the list.
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

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

Unicode conversion and patching simultaneously

Hi All -
We are planning to convert our core ECC 6.0 system to Unicode this year as well as patch it to the latest support pack stack. In order to minimize regression testing time, we are going to do them both at the same time so the functional teams only have to test once.
The question is which order to perform the tasks in: convert to Unicode first, THEN patch, or patch, THEN convert? I'm not sure the order matters, but I can't find any definite documentation either way. Has anyone had any experience with this that they would be willing to share?
Thanks for your help!
Abby

Hi Abby,
this depends on what you mean by "patches" ?
Do you want to combine the Unicode conversion with applying support packages only ?
Or do you want to implement EhPs as well ?
If you go for EhPs, I would recommend to do this before the Unicode conversion. This is also the "normal" approach when combining an upgrade with a Unicode conversion.
In case of support packages only, both ways are possible (Unicode first and then SPs or vice versa) ...
By the way I assume you do not have an MDMP system - this would add some additional constraints ...
Best regards,
Nils Buerckel
SAP AG

Unicode conversion & SAP Office functionality.

Similar Messages

Maybe you are looking for