Open/Modifiable transports before unicode conversion

Hi,
We are planning to convert our ERP 6.0 system to Unicode starting with our DEV environment. Is it manadatory to release the open/modifiable change requests (transports) before we start the export/import on our DEV system? This is an upgrade of the ERP system so I am thinking we do not need to. But need some confirmation.
Thanks.

Hi,
this is a second aspect.
Basically you ask whether it is possible to transport between a Unicode system (DEV) and a Non-Unicode system (QAS).
In most cases, this is possible. Please have a look at SAP note 1322715 > Point 9 for details.
Best regards,
Nils Buerckel

Similar Messages

Unicode Attribute - Necessary before Unicode Conversion?

We are about to upgrade to ECC 6.0 with a Unicode conversion.
I know that the "Unicode Checks Active" flag must be set in every
customer program in order for the code to run in an ECC 6.0 unicode environment.
My question is does this HAVE to be done before we do the unicode
conversion. What we would like to do is convert the system to ECC 6.0
with Unicode and then apply the transports which set the "Unicode
Checks Active" flag. Since some of these transports contain new
objects, we would prefer to upgrade to ECC 6.0, then convert to unicode
first and apply the transports afterwards, to reduce the risk of potentially needing to rerun
scans.
Ideally we would have cleared all this before the upgrade, but we only
found this issue in our test system after we had upgraded it.
Is this a bad plan?

Hi Chris,
it is not necessary to set the Unicode flag for programming objects in order to succeed with the technical Unicode conversion.
However please keep in mind that the programs without flag will not work in the Unicode environment (as you already stated).
Best regards,
Nils Buerckel
SAP AG

Should modifiable transports be released before the unicode conversion?

We are getting started on the unicode conversion soon in our DEV environment. Should we go ahead and release the open/modifiable transports before the conversion? IS there a reason for that? Since this is unlike an SAP upgrade, can we release them later after the conversion is complete. Any insight?
Thanks.

Hi,
I Suppose its not must , as i have done lot of language import with open transport request.
http://help.sap.com/saphelp_nw70/helpdata/en/a3/30ad5296b511d384bb0060975b04f3/frameset.htm
This one will help
Note 18601 - Frequently asked questions on language transport
Regards,
Edited by: Gagan Deep Kaushal on Nov 2, 2010 8:34 PM

Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Hallo All,
We perform CU&UC of R/3 4.6C sandbox system to the ERP 6.0 EHP5.
Currently the upgrade phase is completed and Unicode conversion should
be started (we are in the step "Additional Preparation Steps in NW 7.02
non-UC" in the CU&UC guide).
In various transactions (PFCG - Generating of profiles, SPAM/SAINT ) we
received an error "SAP characters 00367 and 00065 are not unique in
character set 1180". As a workaround we temporarily deleted Polish
language (PL) in program RSCPINST and activated (so only codepage 1100
was active). Currently we have activated the Polish language again.
In the source 4.6C system TMB (created by System Copy from productive
system PMB) there was also the configuration in RSCPINST of more than 1
codepage (1100, 1401) and in TCPDB table 1180 codepage was configured
(see attached pictures).
Our question :
How is it possible to avoid this situation in upgrades of following
system (IMB, QMB, PMB)? Could this configuration cause any
problems/inconsistencies during/after Unicode conversion export &
import ?
Regards Peter Gauer

Hello Nils,
After upgrade, before unicode conversion we got the following error message in PFCG, SAINT,..
"SAP characters 00367 and 00065 are not unique in character set 1180"
I got the information from T-Systems that they excluded polish languages out of RSCINST,
then codepage 1100 was used, than T-Systems added polish language again to have the original situation.
First message I got with the simulation (choose blank latin-1)
The required language combination is supported
only in Unicode systems
Please refer to SAP Note 73606.
Now I Choose: 4EU, EuropTranslit
and simulation showed no message above, but went to the next page.
see below
S e l e c t e d   S e t t i n g s :
Language(s):
EN (E) English
FR (F) French
DE (D) German
PL (L) Polish
ES (S) Spanish
Country code:
4EU    EuropTranslit
R e s u l t s :
Code page configuration type:
Non-Unicode - Single Code Page configuration
Processed language entry:
DEFLS
Language(s) and Corresponding Code Page(s):
EN (E) 1180   Transliteration from Latin-2 (...) to Latin-1
FR (F) 1180   Transliteration from Latin-2 (...) to Latin-1
DE (D) 1180   Transliteration from Latin-2 (...) to Latin-1
PL (L) 1180   Transliteration from Latin-2 (...) to Latin-1
ES (S) 1180   Transliteration from Latin-2 (...) to Latin-1
T a s k s :
Required OS locales and their current status:
Locale installed     = the locale is installed correctly
Set locale failed    = the locale needs to be corrected on the app server
citmb07_TMB_07       de_DE.ISO-8859-1               Locale installed
                     en_US.ISO-8859-1               Locale installed
                     fr_FR.ISO-8859-1               Locale installed
                     de_DE.ISO-8859-1               Locale installed
                     es_ES.ISO-8859-1               Locale installed
Required profile parameter modifications:
RSCPINST does NOT change the value of profile parameter.
Please check the value of below parameter(s) after activation.
1) Please update zcsa/installed_languages.
    e.g. Copy the new value and paste it into a field in transaction RZ10
New:                  DEFLS
Current (sorted):
citmb07_TMB_07       DEFLS
2) Please proceed with Check result for below parameter(s):
OK     Checked and no inconsistency found.
Regards Peter

Combined Upgrade and Unicode conversion question

Hello Everyone,
I will be performing combined Upgrade and Unicode conversion soon. Currently i have run Prepare and do not have any errors.
I have already run SPUMG consistency check and i do not have any errors there. Since this is Combined Upgrade and unicode conversion according to guide i do not need to do the Nametab conversion right now. But now if i go this place:
SPUMG -> Status -> Additional Information , i see a status with red for Unicode nametabs are not consistent or not up-to-date.
Please let me know if i can ignore this step and do the nametab conversion after upgrade is complete and before unicode conversion.
Thanks,
FBK

Please follow the instructions from the guides.
The Unicode nametabs will be generated automatically during the upgrade.
An additional check is integrated into the final preparation steps in the target releases.
Regards,
Ronald

SRM can not open attachment after unicode conversion

Hi,
Our system is SRM4.0, last week we do a unicode conversion project.
After we convert to unicode, some attachment in SC and PO can not be openned, these attachment file name include some chinese. If the attachment file name is all English, no problem to open it.
I think it is the cause by unicode conversion, do you have any idea what is the root of this problem?
Thanks.

Hi,
Please check in table :BBP_PDATT
If you have created a shopping cart with attachment. The attachment will be in the above table
Regards
G.Ganesh Kumar

Is it required to do Unicode conversion before applying NW70EhP1?

Hi,
I am going to apply NW70EhP1 in our BI system.
My BI system details is:
1. NW70 SP16
2. ABAP+JAVA Web AS
3. Non Unicode.
Is it mandatory to do Unicode conversion before applying NW70EhP1SP6 in our NW70SP16 non-unicode ABAP+JAVA BI system?
Thanks
Manoj
+91-9231524195

Hi Yu,
Thank you for your answer.
But in the market place in the below two locations Non-Unocoe kernel are not available. As my system is NW70 ABAP+JAVA and having BI Java component as well as Portal component I am worring that will these components work properly in non-unicode kernel or it is required to convert the system to unicode?
Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP NETWEAVER --> SAP EHP1 FOR SAP NETWEAVER 7.0 --> PORTAL ADD-ON SAP NW 7.0 EHP1 --> Required Product Versions --> SAP EHP1 FOR SAP NETWEAVER 7.0 - Enterprise Portal
Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP NETWEAVER --> SAP EHP1 FOR SAP NETWEAVER 7.0 --> Entry by Component --> BI Java
Thanks again..
Manoj

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

Alignment all out after unicode conversion

The system is now unicode compliant.
The purchase order, invoice that has Chinese text as line item are all printed out of alignment.
It had pushed the next field towards the right.
I understand it is becuase of the unicode character / bytes difference.
Can someone shared with me how can I modified the sapscript to get it back in alignment?
Please provide a sample.
Thanks
bye

Hi,
I have read the thread before. It doesn't help in my case.
To share it with you,
I realised that I can place a length field after the field.
Previously I could use &EKPO-TZX01(40)&. Now I had to remove it to &EKPO-TZX01&.
it works for some but not all sapscripts.
For those that doesn't work, I will have to changed it as well as setting the tab using a separate paragraph.
So much to change after this unicode conversion.
Thanks

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

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

Combined upgrade & Unicode conversion.

Hi
I need some suggestions for my concerns: I would appreciate, if you reply ASAP for below situations and actions.
Current system: HP unix DB: Oracle10.2.0.2
SAP 6.20 with SP 61, single code page
strategy: resource minimized.
Upgrading from 4.7 was 6.20 to ECC6.0 with CU & unicode conversion.
we ran UCCHECK and provide the list to ABAP, but they are not modifying now.
Mean while we started the preconversion steps for unicode conversion and completed. SPUMG.
Upgrade prepare is completed and currently in begining of down-time.
so far ABAP programs are not unicode complaint!!!
we don't know, when would they modify??
If we complete the upgrade and post upg steps for ecc 6.0 and
pre coversion steps for unicode.
is it a problem, if the ABAP programs are not modified yet, can it be done after conversion and before export???
or after import??
Your time is highly appreciated.
Thanks
creddy

Per CU&UC guide, you can do some conversions in parellel
and after upgrade, you have to perform preparation steps and then export, that is what i am following.
What you said is right for single code page conversion method.
upgrade first
unicode conversion second.
I am following CU&UC method.
Thanks
reddy

Updating TRDIR-UCCHECK for unicode conversion

Hi,
We are currently performing a unicode conversion on our R/3 and BW systems. There are a lot of programs that DO NOT require changes to be unicode-compliant but don't currently have the TRDIR-UCCHECK flag turned on. I know that the UCCHECK transaction provides the functionality to turn on this flag, but it requires that the programs be transported. I don't want to transport all those programs.
I found code in another thread (see below) that updates the flag by doing a read/insert on the program. My question.... is there a reason that I can't update the TRDIR-UCCHECK flag directly rather than performing read/insert?
Suggestions appreciated,
Kirsten
Code snippet from prior thread:
REPORT YTEST.
TABLES : TRDIR.
DATA : BEGIN OF IT_PROG OCCURS 0,
LINE(255) TYPE C,
END OF IT_PROG.
PARAMETERS : P_PROG TYPE TRDIR-NAME OBLIGATORY,
P_CHECK TYPE C.
SELECT SINGLE * FROM TRDIR INTO TRDIR WHERE NAME = P_PROG.
IF SY-SUBRC = 0.
READ REPORT P_PROG INTO IT_PROG.
IF SY-SUBRC = 0.
TRDIR-UCCHECK = P_CHECK.
INSERT REPORT P_PROG FROM IT_PROG STATE 'A' DIRECTORY ENTRY TRDIR .
ENDIF.
ENDIF.

REPORT YTEST.
TABLES : TRDIR.
DATA : BEGIN OF IT_PROG OCCURS 0,
LINE(255) TYPE C,
END OF IT_PROG.
PARAMETERS : P_PROG TYPE TRDIR-NAME OBLIGATORY,
P_CHECK TYPE C.
SELECT SINGLE * FROM TRDIR INTO TRDIR WHERE NAME = P_PROG.
IF SY-SUBRC = 0.
if TRDIR-UCCHECK = space
TRDIR-UCCHECK = P_CHECK.
modify trdir from trdir where NAME = P_PROG.
endif.
Just right this code .
This will solve the problem .
You also have a file of programs and give a file input to program and in the loop do a select n modify .
PLesae reward if useful.

Unicode Conversion check

Hello All,
We are doing Combined Upgrade and Unicode Conversion from 4.6C to ECC 6.0. We have listed all the Z programs and we need to do unicode conversion check for the same. Hence we have exported the Z programs and imported the same into our IDES server and completed the UCCHECK. But we were not able to activate the same as there are many references missing (example: Z tables). We planned for activating the Z programs in IDES server and use the corrected programs in the upgrade system. But we are not able to proceed due to activation problem
Could you please suggest any other alternative solution or best practise that needs to be followed? Should we upgrade our system to 6.20 / 6.40 Engine first for UCCHECK. Please suggest
Regards,
Anand

Hi ,
As per SAP bes practice there are 2 options
1) You copy and upgrade your SAP Basis 4.6c production system to at least WAS 6.10 (non-unicode) or higher. And here you can perform your preparation steps. You can call this system as UCCHECK system. This is the recommended option.
I had chosen it in my CUUC upgrade from 4.6c to ECC 6.0
2) Option 2 is you can install a sandbox system at lease on version 6.10(non-unicode) or higher. Note that if you choose this option you must make sure that the sandbox system should contain all DDIC objects that are used in Z programs or modified SAP programs.
Then create a transport with Z programs + modified SAP programs in your 4.6c system and import them in sandbox system.
now here you can perform your preparation steps.
Also I will recommend you please go through the CUUC guide. It will clear all your doubts.
Regards,
Sachin Rane.

MDMP: TWIN Upgrade + Unicode conversion

Hello ,
We have adopted twin upgrade and unicode conversion method and at present we are converting the twin system to unicode conversion.
In Twin system we have completed SPUMG 7 scans. Whether i need to run UMG_TWIN_CREATE_TRANSPORT now to save the results for twin preparation run or i need to perform this step after Additional preparatory step.
Kindly suggest
Regards
Vinay

Hi Vinay,
Excerpt from the UCG:
2.4 Final Preparation Steps
2.4.1 SPUMG Updates
If there is a time difference between the scan and the database export, it may happen that a new table has been created or a Support Package has brought a new table with it. In such a case, the preconversion must be rerun right before the export is carried out to ensure that the data change is reflected in the Export Control Table.
End excerpt
Hence this step is necessary in case of DB changes (e.g. new tables with or without content).
Therefore if you have significant changes, I would recommend to create the twin transport after this step.
However this step has to be repeated in the PRD system as well (see TU&UC-Guide) to reflect the changes between Twin and PRD system. In order to minimize downtime, the differences between the two systems should be small.
Best regards,
Nils Buerckel
SAP AG

Open/Modifiable transports before unicode conversion

Similar Messages

Maybe you are looking for