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

Similar Messages

Unicode conversion for ERP

Morning!
In that famous OSS note about unicode conversion, the attached guides are labeled
as NW unicode conversion guides.
-- ERP can use the same guides?
-- how about the unicode conversion for other products such as SM, SCM, CRM, etc.?
Thank you!

Hi,
Answer to both the questions would be Yes. The conversion guides are as per the Netweaver base release for any of the applications (ERP, SCM, SRM, CRM etc).
Eg, If converting a CRM 2005 Non-Unicode to Unicode, the guide SCP700SP<xx> would be relevant, because the Netweaver 700 SP<xx> is the base release for CRM 2005. Similarly for all applications.
Regards,
Srikishan

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 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 for ECC5 MDMP system

Hello,
We are planning to do Upgrade and Unicode conversion of ECC5 MDMP system to ECC6 EHP4 Unicode. We are adopting Combined upgrade and Unicode conversion strategy to minimise the downtime.
In source version ECC5 we are in support pack level 6. Should we need to update the support pack to any target version to start with CU&UC or we can start with ECC5 with SP 6 itself.
Since we cant afford more downtime for support pack update also, is it ok to start with upgrade and unicode conversion with current version.
please advice.
Regards
Vinay

Hello Vinay,
please note that as a prerequisite the Basis SP should be accurate for an MDMP conversion.
There is no MUST to have the latest Basis SP, but without you could have severe issues in SPUMG.
On the application side, there are in most cases no hard requirements on the SP level.
Best regards,
Nils Buerckel
SAP AG

Unicode Conversion for Solution Manager

I would like to convert non-unicode for unicode my SM4.0. The SM4.0 was
upgraded with SR2 (3.2 -> 4.0 SR2).
What guides "Unicode Conversion" and "System Copy" I use?

I would upgrade to the latest stack and start conversion then. The latest SAP_BASIS has the most fixes for the programs needed to run.
Check
http://service.sap.com/unicode@sap
--> Unicode Conversion Guides
--> Single Code Page Conv. Guides
If you upgrade to SP 17 use
Single Code Page Conversion Guide NW 7.0 SP 14 et sqq.
Markus

NW 7.3 vs Unicode - Question for SAP

Hi,
Is it true that we have to convert to Unicode before we start the upgrade for NW BW 7.3?
Please confirm.
Regards,
SC

If your system is MDMP yes you will have to, but if your system is non-unicode single code-page system - till date SAP just mentions that a upgrade to SCP non-unicode is possible until SAP NW 7.0 EhP1 but is not recommended. Check this sap note for further details:
73606 - Supported Languages and Code Pages
Nothing is yet out for SAP NW 7.3.
- Regards, Dibya

Support package requierement for unicode conversion

We are currently planning a unicode conversion for a SAP 4.7enterprise 1.1 extension version, running under Aix and Oracle, Basis/ABAP SP 35, HR SP20.
According to the conversion guide, we must implement at least Support Pachage 60 for Abap and Basis, no explicit requierement for HR SP level.
I believed that we must applied SAP procedure and exclusively HR Support Package Stack up to 27, which include SP 60 for Basis and Abap and HR 61.
Our HR guys argue there is no indication from SAP that the SUPPORT PACKAGE STACK policy is mandatory and that SAP will provide us with normal support if we run the unicode conversion with SP Basis/ABAP 60, in other word even if we do not respect the support package stack combinaison. Need help on this issue before starting the project

Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
later only upgrade to ECC 6.0 after 2 years, as you said.
My answer is yes, to your question.
You can download the installation kits at:
http://service.sap.com/swdc
anyway, it is recommended to have the latest SP in your system.
cheers,
Vincent

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!

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

Unicode conversion on Informix

Hello All,
We are doing unicode conversion on SAP ECC 5.0 system running on Informix database.
We want to use the table split method. In the table split preparation step, we give the file with the large tables and the number of splits the file is as below:
aablg%3
auak%2
aufk%9
bkpf%14
bsad%12
bsak%14
bsas%2
bse_clr%4
bsis%17
cdcls%9
cdhdr%6
cobk%9
cobrb%2
The preparation step fails with error
WARNING: build_dbdiff_list(): description for "MLICHECK" may be missing or incorrect
WARNING: build_dbdiff_list(): description for "SCI_TEMPT" may be missing or incorrect
WARNING: build_dbdiff_list(): description for "TRDIR" may be missing or incorrect
ERROR: aablg is not a DB table
ERROR: couldn't read file "Split/table_splitter_R3ldctl.txt"
ERROR 2011-03-25 15:58:31
CJSlibModule::writeError_impl()
CJS-00396 Call to R3ldctl failed. Return code: 2
Any clue why this could be happening??
Thanks!

HI,
Thnks for the update.
It got solved.
Cheers,
Vamshi T

Unicode conversion BI 7.0 SP15

Hello,
We are planning Unicode conversion for all our systems.
Due to large database size of BI, we want to reduce conversion time as much as possible.
Our PSA tables occupy around 1 terabyte of disk space.
I want to know what action possible to take to avoid conversion of PSA tables.
1. Delete PSA, covert to Unicode and then allocate again.
2. Reduce size to the minimum ( 1 week)
3. Any your suggestions
Thank you,
Mark

Hi Mark,
if the conversion takes too long (for example more than a weekend), then you could consider building a new BI Unicode system offline. You can load it either from the original sources or from the current BI system. Then on the go-live weekend, you switch over and load the remaining data.
However, you will need two big BI systems for a while.
Regards,
Marc
SAP NetWeaver RIG

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

User logoff session for SAP Upgrade 4.6C to ECC4 EHP4

hi All,
currently i was performing an upgrade and unicode conversion from SAP 4.6C to SAP ECC6 EHP4 (Windows + Oracle), my question is when is the phrase where by i need to ask all the user logoff from the system when i performing the upgrade, below is the Roadmaps for the upgrade and i'm using the downtime minimized for the SAPUP.
initialization - extraction - configuration - check - preprocessing - downtime - postprocessing - finalization

Hello Hariyono,
actually users can work up to the end of preprocessing phase, just before the downtime. Just please be aware that your system will be locked for changes in phase REPACHK2:
Phase
REPACHK2
Upgrade Actions
Finds SAP objects locked in repairs or requests and locks the development environment
Log file
REPACHK2.LOG
Comments
Confirm locks for ABAP Workbench
Best regards,
Tomas Black

DDIC Activation error for SAP HR SP 23

Hello,
We have installed ECC 6.0 SR3 with DB2 as database and HP UX OS.
When I am updating HR Software component to SP23, it gives an DDIC Activation error. After checking the logs, "Table Type HRPP_T_PPDIT_HASH could not be activated" was displayed.
Did a consistency check on table PPDIT, which said it was consistent.
Kernel level is latest 185. R3 trans and Tp is also latest.
Kindly help.
Regards,
Sagar

Hi
Please check the following SAP Notes
Note 672651 - OCS: Known problems with Support Packages in Basis Rel.6.40
Note 573044 - Unicode conversion for HR application
Regards
Chen

Unicode Conversion for SAP BI

Similar Messages

Maybe you are looking for